Method and apparatus for configuring artificial intelligence and machine learning functions in communication

Abstract

A processing method and apparatus for configuring artificial intelligence and machine learning functions in communication are disclosed. In an example from the perspective of a user equipment, the user equipment receives one or more configurations. The user equipment reports a single list of entries containing applicability information for one or more configurations. Each entry in the single list of entries contains an identifier and a flag. The flag indicates the applicability status of the configuration associated with the identifier in one or more configurations. The identifier is a first type of identifier indicating a predicted configuration for a first function, a second type of identifier indicating a predicted set of relevant parameters for a second function, and / or a third type of identifier corresponding to CSI-ReportConfigId.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 739,932, filed December 30, 2024, the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for configuring artificial intelligence and machine learning functions in wireless communication systems. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This type of IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-bearing voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate the evolution and completion of the 3GPP standards. Summary of the Invention

[0006] According to this disclosure, one or more apparatuses and / or methods are provided. In an example from the perspective of a User Equipment (UE), the UE receives one or more configurations. The UE reports a single list of entries containing applicability information for one or more configurations. Each entry in the single list of entries includes an identifier (ID) and a flag. The flag indicates the applicability status of the configuration associated with the ID in one or more configurations. The ID is a first type of ID indicating a predicted configuration for a first function, a second type of ID indicating a predicted set of relevant parameters for a second function, and / or a third type of ID corresponding to CSI-ReportConfigId.

[0007] In an example from the UE's perspective, the UE receives one or more first configurations from a first list, including a first configuration associated with a first identifier (ID) corresponding to a first type. The UE receives one or more second configurations from a second list, including a second configuration associated with a second ID corresponding to a second type, and the first type is different from the second type. The UE reports a single list containing applicability information for the first and second configurations, wherein each entry in the single list includes a first parameter indicating the ID and the type of the ID, and a second parameter indicating the applicability status of the configuration associated with the ID. Attached Figure Description

[0008] Figure 1 A diagram illustrating a wireless communication system according to an exemplary embodiment is shown.

[0009] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment.

[0010] Figure 3 This is a functional block diagram of a communication system according to an exemplary embodiment.

[0011] Figure 4 This is based on an exemplary embodiment. Figure 3 Functional block diagram of the program code.

[0012] Figure 5 This illustration depicts a scenario associated with a successful Radio Resource Control (RRC) reconfiguration process, according to an exemplary embodiment.

[0013] Figure 6 This illustrates a scenario associated with a failed RRC reconfiguration process, according to an exemplary embodiment.

[0014] Figure 7 This illustration depicts a scenario associated with providing UE Assistance Information (UAI) according to an exemplary embodiment.

[0015] Figure 8 This illustrates a scenario associated with an applicable functional report according to an exemplary embodiment.

[0016] Figure 9 An example representation of a first configuration according to an exemplary embodiment is shown.

[0017] Figure 10 An example representation of an applicability report according to an exemplary embodiment is shown.

[0018] Figure 11 This is a flowchart based on an exemplary embodiment.

[0019] Figure 12 This is a flowchart based on an exemplary embodiment.

[0020] Figure 13 This is a flowchart based on an exemplary embodiment.

[0021] Figure 14 This is a flowchart based on an exemplary embodiment.

[0022] Figure 15 This is a flowchart based on an exemplary embodiment.

[0023] Figure 16 This is a flowchart based on an exemplary embodiment.

[0024] Figure 17 This is a flowchart based on an exemplary embodiment.

[0025] Figure 18 This is a flowchart based on an exemplary embodiment.

[0026] Figure 19 This is a flowchart based on an exemplary embodiment.

[0027] Figure 20 This is a flowchart based on an exemplary embodiment.

[0028] Figure 21 This is a flowchart based on an exemplary embodiment. Detailed Implementation

[0029] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or the 3rd Generation Partnership Project (3GPP). rdGeneration Partnership Project (3GPP) Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) radio access for 5G, or some other modulation techniques.

[0030] Specifically, the exemplary wireless communication systems and apparatus described below may be designed to support one or more standards, such as those provided by an association known as the "Third Generation Partnership Project" (referred to herein as 3GPP), including: RP-240082, "SID Revision of AIML for Mobility in NR"; RP-240774, "WID Revision for NR_AIML_air"; 3GPP TR 38.843 V18.0.0 (2023-12) 3GPP, TSG RAN, Research on Artificial Intelligence (AI) / Machine Learning (ML) for NR Air Interface (Revision 18); 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP, TSG RAN, NR, Radio Resource Control (RRC) Protocol Specification (Revision 18); RAN2 #127bis Report; RAN1 #119 Report. The standards and documents listed above are expressly incorporated herein by reference in their entirety.

[0031] Figure 1 A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. Access network 100 (AN) includes multiple antenna groups, one antenna group including 104 and 106, another antenna group including 108 and 110, and yet another antenna group including 112 and 114. Figure 1In the diagram, only two antennas are shown for each antenna group; however, each antenna group can utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplexing (FDD) system, communication links 118, 120, 124, and 126 can communicate using different frequencies. For example, forward link 120 can use a different frequency than the frequency used by reverse link 118.

[0032] Each antenna group and / or the area in which the antenna groups are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group may be designed to communicate with an access terminal in a sector of an area covered by access network 100.

[0033] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links used for different access terminals 116 and 122. Furthermore, compared to an access network transmitting to all its access terminals via a single antenna, using beamforming to transmit to access terminals randomly distributed within its coverage area typically causes less interference to access terminals in neighboring cells.

[0034] An access network (AN) can be a fixed station or base station used for communication with terminals, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB (eNB), Next Generation NodeB (gNB), or any other term. An access terminal (AT) can be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or any other term.

[0035] Figure 2 An embodiment of a multiple-input multiple-output (MIMO) system 200 is presented, comprising a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)). At the transmitter system 210, service data for multiple data streams can be provided from a data source 212 to a transmit (TX) data processor 214.

[0036] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, encodes, and interleaves the service data of the data streams based on a specific encoding scheme selected for each data stream to provide encoded data.

[0037] Orthogonal frequency-division multiplexing (OFDM) technology can be used to multiplex coded data and pilot data for each data stream. The pilot data can typically be a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data of the data streams can then be modulated (i.e., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PK), or M-ary quadrature amplitude modulation (M-QAM)) to provide modulation symbols. The data rate, coding, and / or modulation for each data stream can be determined by instructions executed by processor 230.

[0038] Next, modulation symbols for the data stream are provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). Then, the TX MIMO processor 220 will... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 can apply beamforming weights to symbols of the data stream and to the antennas from which the symbols are being transmitted.

[0039] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates the analog signals (e.g., amplification, filtering, and / or up-conversion) to provide a modulated signal suitable for transmission over a MIMO channel. Then, signals can be transmitted from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0040] At receiver system 250, by N RAntennas 252a to 252r receive the transmitted modulated signal and can provide the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 can modulate the corresponding received signal (e.g., filter, amplify, and downconvert), digitize the modulated signal to provide a sample, and / or further process the sample to provide a corresponding "received" symbol stream.

[0041] Next, the RX data processor 260 from N R Each receiver 254 receives N R N symbol streams and / or processing based on specific receiver processing techniques R Each received symbol stream provides N T Each detected symbol stream is then demodulated, deinterleaved, and / or decoded by the RX data processor 260 to recover the service data used for the data stream. The processing performed by the RX data processor 260 can complement the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0042] Processor 270 can periodically determine which precoding matrix to use (discussed below). Processor 270 formulates a reverse link message that includes a matrix index portion and a rank portion.

[0043] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message may then be processed by the TX data processor 238, which may also receive service data for multiple data streams from the data source 236, modulated by the modulator 280, regulated by the transmitters 254a to 254r, and / or transmitted back to the transmitter system 210.

[0044] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 can then determine which precoding matrix to use to determine beamforming weights and process the extracted message.

[0045] Figure 3 An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1 UE (or AT) 116 and 122 or Figure 1The communication device 300 includes a base station (or AN) 100, and the wireless communication system can be an LTE system or an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306. The communication device 300 in a wireless communication system can also be used for this purpose. Figure 1 AN 100 in the middle.

[0046] Figure 4 This is an embodiment based on the disclosed subject matter. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 can perform radio resource control. Layer 2 portion 404 can perform link control. Layer 1 portion 406 can perform and / or implement physical connections.

[0047] The Study Item Description (SID) RP-240082 specifies one or more objectives related to artificial intelligence (AI) / machine learning (ML) mobility. The following quotes from one or more sections of RP-240082:

[0048] 3. Argumentation

[0049] Existing L3 handover mechanisms are triggered and executed based on reported historical measurements and / or measurement events; that is, they are inherently passive. While they work well between macrocells when UE mobility is low for existing services, they can become problematic for existing or future services (e.g., XR) when UE mobility is high, microcell density is high, or both. This reactive approach can lead to more unintended events such as handover failures, radio link failures, ping-pong, throughput loss, or premature / late handovers. Conditional handover was introduced in Rel-16 to improve handover robustness, and LTM HO was introduced in Rel-18 to reduce downtime from frequent inter-cell handovers. However, these mechanisms are insufficient as they remain passive by design. On the other hand, AI / ML algorithm-based mechanisms have the potential to realize proactive solutions.

[0050] In Rel-18, the SID known as FS_NR_AIML_air was extensively studied in physical layer-centric use cases involving spatial and temporal beam prediction. Temporal prediction within the serving cell primarily predicts the best or top K beams or beam pairs in the time domain to improve UE throughput. Predicting the best or top K beams or beam pairs within a smaller set of beams can help reduce RS signaling overhead, measurement workload, and UE power consumption. Much of the RAN1 workload can be reused through extended L1 beam measurements from the serving cell to neighboring cells. Since L3 measurements are based on filtering of L1 measurements, studies of AI / ML in the air can be leveraged for mobility purposes; for example, temporal prediction can be used to predict worsening beams / cells, thus avoiding unexpected events such as radio link failures or brief handovers.

[0051] Mobility enhancements were also studied in RAN3 in Rel-17 within a SID called FS_NR_ENDC_data_collect, and are now specified in Rel-18 WID NR_AIML_NGRAN-Core. In these RAN3 projects, research and specification work on mobility enhancements were based on network-side information, such as inter-cell handover and historical dwell times, to predict UE trajectories in single hops, and thus predict potential candidates. In Rel-19, RAN3 will further focus on multi-hop UE trajectories. Predicted UE trajectories can, to some extent, contribute to the study of AI / ML mobility at the air interface.

[0052] Based on the progress made to date in RAN1 and RAN3 and the assumptions made about UE trajectories, it is feasible to predict RRM measurements and / or events, and thus predict candidate target cells on the UE side. On the network side, new auxiliary information (if needed) and statistical information based on measurement reports from the UE and / or neighboring nodes can also be used for intelligent prediction. If the network can know some predictive information, proactive measures can be taken to improve handover and / or RRM performance, to make better decisions or avoid unforeseen events.

[0053] 4. Objectives

[0054] 4.1 Target of SI or core WI or test WI

[0055] This research will focus on mobility enhancements in RRC_CONNECTED mode on the air interface, following the existing mobility framework where handover decisions are always made on the network side. Mobility use cases are concentrated on independent NR PCell changes. Both UE-side and network-side AI / ML models can be considered separately.

[0056] The study and evaluation of the potential benefits and gains of AI / ML-assisted mobility for network-triggered L3-based handover considers the following aspects:

[0057] • AI / ML-based RRM measurement and event prediction

[0058] • Includes cell-level measurement predictions (UE-side and NW-side models) both within and between frequencies [RAN2]

[0059] • Inter-cell beam-level measurement prediction for L3 mobility (UE-side and NW-side models) [RAN2]

[0060] • HO Fault / RLF Prediction (UE-side Model) [RAN2]

[0061] • Measurement event prediction (UE-side model) [RAN2]

[0062] • Investigate the need / benefits of any other UE-assisted information used in the network-side model [RAN2]

[0063] • The evaluation of the benefits of AI / ML-assisted mobility should consider HO performance KPIs (e.g., ping-pong HO, HOF / RLF, dwell time, handover interruption, prediction accuracy, and measurement reduction) and complexity trade-offs [RAN2]

[0064] • Note: Simulation assumptions and methods can utilize TR 38.901, 38.843, and 36.839. A detailed discussion will be left to RAN2.

[0065] • Potential AI mobility-specific enhancements should be based on the Rel19 AI / ML-Air Interface WID general framework (e.g., LCM, performance monitoring, etc.) [RAN2]

[0066] • Note: This will only be addressed after sufficient progress has been made in the Rel-19 AI / ML air interface WID.

[0067] • Potential canonical implications of AI / ML-assisted mobility [RAN2]

[0068] …

[0069] Work Item Description (WID) RP-240774 discusses one or more objectives for AI / ML used in the NR air interface. The following quotes from one or more sections of RP-240774:

[0070] 3. Argumentation

[0071] The application of AI / ML technology in the NR air interface was studied in FS_NR_AIML_Air.

[0072] In this work, we provide normative support for a general framework for AI / ML used in over-the-air interfaces and implement use cases recommended in previous research. Furthermore, several research objectives in this project will focus on resolving some outstanding issues identified during the research process, aiming to deepen understanding and provide a basis for future normative work.

[0073] 4. Objectives

[0074] 4.1 Target of SI or core WI or test WI

[0075] Provides standard support for the following aspects:

[0076] - A general AI / ML framework for one-sided AI / ML models in the domain studied in the FS_NR_AIML_Air project [RAN2]:

[0077] Regarding the signaling and protocols of Life Cycle Management (LCM), the implementation of functions and models (if reasonable) for selection, activation, deactivation, switching, and rollback.

[0078] ■ Signaling related to identification is part of the aforementioned objectives.

[0079] ○ LCM facilitates the necessary signaling / mechanisms for both UE-side and NW-side models in model training, inference, performance monitoring, and data collection (besides the purpose of CN / OAM / OTT collection of UE-side model training data).

[0080] ○ Signaling mechanism for applicable functions / models

[0081] - Beam management - DL Tx beam prediction for both UE-side and NW-side models, covering [RAN1 / RAN2]:

[0082] ○ Spatial Domain DL Tx Beam Prediction for Beam Group A Based on Measurement Results of Beam Group B (“BM-Case 1”)

[0083] ○ Time-based DL Tx beam prediction for beam group A based on historical measurement results of beam group B (“BM-Case 2”)

[0084] ○ Define the necessary signaling / mechanisms to facilitate LCM operation specific to beam management use cases (if applicable).

[0085] ○ Enable a method to ensure consistency between training and inference regarding NW-side additional conditions (if identified) used for inference at the UE.

[0086] Note: We aim to support a universal framework design for both BM-Case1 and BM-Case2.

[0087] - Enhanced positioning accuracy, covering [RAN1 / RAN2 / RAN3]:

[0088] ○ Direct AI / ML localization:

[0089] ■ (Priority 1) Case 1: Direct AI / ML positioning using UE-based positioning from the UE-side model

[0090] ■ (Second Priority) Case 2b: UE-assisted / LMF-based localization using LMF-side model for direct AI / ML localization

[0091] ■ (Priority 1) Case 3b: Direct AI / ML localization using NG-RAN node-assisted localization based on LMF side model

[0092] ○ AI / ML assisted localization

[0093] ■ (Second Priority) Case 2a: UE-assisted / LMF localization using UE-side model, AI / ML-assisted localization

[0094] ■ (Priority 1) Case 3a: NG-RAN node-assisted localization using gNB-side model, AI / ML-assisted localization

[0095] ○ Define the necessary measurements, signaling / mechanisms to facilitate LCM operation specific to positioning accuracy enhancement use cases (if applicable).

[0096] ○ Investigate and specify the necessary signaling for any required measurement enhancements (if applicable).

[0097] ○ Implement a method for relevant localization sub-use cases to ensure consistency between training and inference regarding NW-side additional conditions (if identifiers) for inference at the UE.

[0098] …

[0099] The research objective for the corresponding checkpoint in RAN#105 (September 2024):

[0100] - CSI feedback enhancement [RAN1]:

[0101] ○ For CSI compression (two-sided model), the following methods will be further investigated:

[0102] ■ The trade-off between improving performance and complexity / overhead

[0103] • For example, consider extending spatial / frequency compression to spatial / temporal / frequency compression, cell / site specific models, CSI compression plus prediction (compared to Rel-18 non-AI / ML based methods), etc.

[0104] ■ Relieve / resolve issues related to training collaboration between vendors.

[0105] At the same time, it addresses other aspects that require further research / summarization as documented in the conclusion section of TR 38.843.

[0106] For CSI prediction (UE-side model), further research is needed on the performance gains and associated complexities compared to Rel-18-based non-AI / ML methods, while addressing other aspects requiring further research / summarization as documented in the conclusions of TR 38.843 (e.g., cell / site-specific models could be considered to improve performance gains).

[0107] - Necessity and details of model identification concepts and procedures in the context of LCM [RAN2 / RAN1]

[0108] - Collection of CN / OAM / OTT data for UE-side model training [RAN2 / RAN1]:

[0109] ○ For the FS_NR_AIML_Air research use case, identify the corresponding UE data collection content.

[0110] ○ Analysis of the UE data collection mechanisms identified during the study period of FS_NR_AIML_Air (TR 38.843 Section 7.2.1.3.2), as well as the meaning and limitations of each method.

[0111] - Model delivery / transfer [RAN2 / RAN1]:

[0112] ○ Determine whether a standardized solution for delivering AI / ML models needs to be considered, at least considering the solutions identified during the FS_NR_AIML_Air study.

[0113] …

[0114] Note: For the purposes of this project, it is assumed that offline training will be conducted.

[0115] Note: The results of the study should be recorded in TR 38.843 for future reference.

[0116] Note: Coordinate ongoing research / work with SA / SA WG, as this may be relevant to their requested work.

[0117] The general framework and operation of LCM are discussed in 3GPP TR 38.843 V18.0.0 (2023-12). The following quotes one or more sections of 3GPP TR 38.843 V18.0.0 (2023-12):

[0118] 4. General AI / ML Frameworks

[0119] The purpose of this clause is to identify common notations and terminology for AI / ML related functions, procedures, and interfaces.

[0120] 4.1 Description of the AI / ML stage

[0121] This clause characterizes the definition phase and associated complexity of AI / ML-related algorithms, namely:

[0122] - Model generation, such as model training (including input / output, preprocessing / postprocessing, online / offline (if applicable)), model validation, and model testing (if applicable).

[0123] - Inference operations, such as input / output, preprocessing / postprocessing (if applicable).

[0124] In addition, the processing of the datasets used for training, validation, testing, and inference is documented.

[0125] 4.2 Lifecycle Management

[0126] This clause characterizes the lifecycle management (LCM) of AI / ML models (e.g., model training, model deployment, model inference, model listening, and model updates) and AI / ML functions.

[0127] The following aspects were examined in LCM, including the definition (if necessary) and necessity of components:

[0128] - Data collection

[0129] - Note: This also includes related supplementary information, if applicable.

[0130] - Model training

[0131] - Function / Model Identifier

[0132] - Model delivery / transfer

[0133] - Model inference operation

[0134] - Function / model selection, activation, deactivation, switching, and rollback operations.

[0135] - Includes: network decisions (initiated by the network or initiated by the UE and requested from the network), UE decisions (configured by the network as event-triggered, with the UE reporting its decisions to the network, or the UE making its own decisions, where the UE may or may not report its decisions to the network).

[0136] - Function / Model Listening

[0137] - Model Update

[0138] - UE capabilities

[0139] 4.2.1 Characteristics of LCM

[0140] The LCM procedure is studied for cases where the AI / ML model has a model ID with associated information and / or for cases where a given function is provided by some AI / ML operations. Note: The applicability of function-based LCM and model ID-based LCM is discussed separately.

[0141] From RAN1's ​​perspective, an AI / ML model identified by a model ID can be logical, and how it maps to a physical AI / ML model can depend on the implementation. When a distinction is necessary for argumentative purposes, companies may use the term "logical AI / ML model" to refer to the model that is identified and assigned a model ID, and "physical AI / ML model" to refer to the actual implementation of such a model.

[0142] For the UE-side model and the UE portion of the dual-side model:

[0143] - For AI / ML function identifiers

[0144] - Starting with the traditional 3GPP feature framework.

[0145] - UE indicates one or more functions supported for a given sub-use case.

[0146] - Use the UE capability report as a starting point.

[0147] - For AI / ML model identification

[0148] - The model is identified by a model ID at the network. The UE indicates the supported AI / ML models.

[0149] In function-based LCM, the network instructs the activation / deactivation / fallback / switching of AI / ML functions via 3GPP signaling (e.g., RRC, MAC-CE, DCI). Model identification is not required at the network level, and the UE can perform model-level LCM. Further research is needed on whether the NW should have awareness / interaction with model-level LCM and how much awareness / interaction it should have. For function identification, one or more functions can exist within AI / ML-supporting features, where AI / ML-supporting features are those in which AI / ML can be used. Note: A UE can have one AI / ML model for a function, or a UE can have multiple AI / ML models for a function.

[0150] For the AI / ML function identifier and function-based LCM of the UE portion of the UE-side model and / or dual-side model, a function refers to an AI / ML-supporting feature / FG enabled by configuration, where the configuration is supported based on conditions indicated by UE capabilities. Accordingly, the function-based LCM operates based on at least one configuration of an AI / ML-supporting feature / FG or a specific configuration of an AI / ML-supporting feature / FG.

[0151] Following the function identification, the study examines the necessity and mechanism for the UE to report updates regarding applicable functions, where applicable functions can be a subset of all functions. The UE can report applicable functions.

[0152] In model ID-based LCM, the model is identified at the network, and the network / UE can activate / deactivate / select / switch individual AI / ML models via the model ID.

[0153] For the AI / ML model identifier and model ID-based LCM of the UE portion of the UE-side model and / or dual-side model, the model ID-based LCM operates based on the identified model, wherein the model may be associated with a specific configuration / condition, which is associated with the UE capability of supporting AI / ML features / FGs and additional conditions (e.g., scene, site, and dataset) determined / identified between the UE side and the NW side.

[0154] Following model identification, the necessity and mechanism for UE reporting updates regarding applicable UE-part / UE-side models were investigated, where applicable models can be a subset of all identified models. UEs can report the applicable models.

[0155] The study aims to investigate how to address the impact of the UE's internal conditions (such as memory, battery, and other hardware limitations) on functional / model operation and AI / ML support features. Note: This does not exclude any existing solutions.

[0156] For LCMs based on feature / model IDs, once a feature / model is identified, the same or similar procedures can be used for its activation, deactivation, toggling, rollback, and monitoring.

[0157] If needed, the model ID can be used in the functions of LCM operations (defined in function-based LCM).

[0158] The procedure for RRC Reconfiguration is discussed in 3GPP TS 38.331 V18.1.0 (2024-03). Notably, section 5.3.5.1 of 3GPP TS 38.331 V18.1.0 (2024-03), titled "RRC Reconfiguration, Success,"... Figure 5 .3.5.1-1 is reproduced in this paper as Figure 5 The section 5.3.5.1 of 3GPPTS 38.331 V18.1.0 (2024-03) titled "RRC reconfiguration, failure" Figure 5 .3.5.1-2 is reproduced in this paper as Figure 6 The section 5.7.4.1 of 3GPP TS 38.331 V18.1.0 (2024-03) entitled "UE Assistance Information" contains... Figure 5 .7.4.1-1 is reproduced in this paper as Figure 7 The following quotes one or more parts of 3GPP TS 38.331 V18.1.0 (2024-03):

[0159] 5.3.5 RRC Reconfiguration

[0160] 5.3.5.1 Overview

[0161] Figure 5 3.5.1-1: RRC reconfiguration successful.

[0162] Figure 5 3.5.1-2: RRC reconfiguration failed.

[0163] The purpose of this procedure is to modify RRC connections, such as establishing / modifying / releasing RB / BH RLC channels / Uu relay RLC channels / PC5 relay RLC channels, performing synchronized reconfigurations, setting / modifying / releasing measurements, adding / modifying / releasing SCells and cell groups, adding / modifying / releasing conditional reconfiguration configurations, adding / modifying / releasing LTM configurations, and adding / modifying / releasing MP configurations. As part of the procedure, NAS-specific information can be transferred from the network to the UE.

[0164] Performing an RRC reconfiguration with synchronous reconfiguration includes, but is not limited to, the following:

[0165] - Reconfiguration with synchronization and security key refresh, involving RA and MAC resets, security refreshes, and RLC and PDCP re-establishment triggered by explicit indicators for PCell / PSCell;

[0166] - Reconfiguration with synchronization but no security key refresh, involving RA and MAC reset of PCell / PSCell, as well as RLC re-establishment and PDCP data recovery triggered by explicit indicators (for AM DRB or AM MRB).

[0167] - Features reconfiguration for DAPS synchronization and security key refresh, involving the establishment of the target PCell's RA, target MAC, and

[0168] - For non-DAPS bearers: Secure refresh and re-establishment of RLC and PDCP triggered by explicit indicators;

[0169] - For DAPS bearers: RLC establishment for the target PCell, security refresh, and PDCP reconfiguration for adding encryption, integrity protection, and ROHC functionality to the target PCell;

[0170] - For SRB: Secure refresh and establishment of RLC and PDCP for target PCell;

[0171] - Reconfiguration with synchronization for DAPS but without security key refresh, involving the establishment of the target PCell's RA, target MAC, and

[0172] - For non-DAPS bearers: RLC re-establishment and PDCP data recovery triggered by explicit indicators (for AMDRB or AM MRB).

[0173] - For DAPS bearers: Establishment of RLC for the target PCell, addition of encryption, integrity protection and ROHC functions of the target PCell and reconfiguration of PDCP;

[0174] - For SRB: Establishment of RLC and PDCP for target PCell.

[0175] - Features synchronous reconfiguration for direct-to-indirect path switching or indirect-to-indirect path switching, without involving the RA at the target side, but involving PDCP re-establishment / PDCP data recovery triggered by explicit indicators (for AM DRB).

[0176] - Features reconfiguration with synchronization for LTM cell handover (without security key refresh), and

[0177] - The RA that is involved or not involved in the target LTM candidate SpCell according to the network indication;

[0178] - MAC reset;

[0179] - Depending on network indications, RLC re-establishment and PDCP data recovery may or may not be involved (for AM DRB).

[0180] In (NG)EN-DC and NR-DC, SRB3 can be used for: measurement configuration and reporting, UE-assisted (re)configuration and reporting for power saving, IP address (re)configuration and reporting for IAB nodes, to (re)configure the MAC, RLC, BAP, physical layer, and RLF timers and constants configured in the SCG, and to reconfigure for communication with SK. gNB Or the PDCP of the DRB associated with SRB3, reconfigured for use in NGEN-DC and NR-DC with SK gNBThe associated DRB's SDAP, adding / modifying / releasing conditional PSCell change configurations or subsequent CPAC configurations, and adding / modifying / releasing LTM configurations associated with the SCG (only in NR-DC) under conditions where (re)configuration does not require any MN involvement, and transmitting RRC messages between the MN and UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, ltm-Config (only in NR-DC), bap-Config, iab-IP-AddressConfigurationList, otherConfig, appLayerMeasConfig, and / or secondaryCellGroup are included in the RRCReconfiguration received via SRB3, except when the RRCReconfiguration is received within DLInformationTransferMRDC.

[0181] When clause 5.3.5 is executed due to an LTM cell handover (i.e., as specified in 5.3.5.18.6) or due to a conditional reconfiguration for subsequent CPAC (i.e., as specified in 5.3.5.13.8), each occurrence of "received" before the RRCReconfiguration message, before the field name, or before the IE name refers to the RRCReconfiguration message applied by the UE, as specified in 5.3.5.18.6 or 5.3.5.13.8, or to a field or IE within that RRCReconfiguration message.

[0182] …

[0183] 5.3.5.3 UE reception of RRCReconfiguration

[0184] The UE should perform the following actions upon receiving an RRCReconfiguration, during the execution of a conditional reconfiguration (CHO, CPA, CPC, or subsequent CPAC), or during an LTM cell handover:

[0185] …

[0186] 1> If RRCReconfiguration contains masterCellGroup, then:

[0187] 2> According to 5.3.5.5, perform cell group configuration for the received masterCellGroup;

[0188] …

[0189] 1> If RRCReconfiguration contains secondaryCellGroup, then:

[0190] 2> Perform SCG cell group configuration according to 5.3.5.5;

[0191] 1> If RRCReconfiguration contains mrdc-SecondaryCellGroupConfig, then:

[0192] 2> If mrdc-SecondaryCellGroupConfig is set to setup, then:

[0193] 3> If mrdc-SecondaryCellGroupConfig contains mrdc-ReleaseAndAdd, then:

[0194] 4> Perform MR-DC release as specified in Clause 5.3.5.10;

[0195] 3> If the received mrdc-SecondaryCellGroup is set to nr-SCG, then:

[0196] 4> Perform RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;

[0197] 3> If the received mrdc-SecondaryCellGroup is set to eutra-SCG, then:

[0198] 4> Perform RRC connection reconfiguration for the RRCConnectionReconfiguration message contained in the eutra-SCG, as specified in Clause 5.3.5.3 of TS 36.331

[10] ;

[0199] 2> Otherwise (mrdc-SecondaryCellGroupConfig is set to release):

[0200] 3> Perform MR-DC release as specified in Clause 5.3.5.10;

[0201] …

[0202] 1> If the RRCReconfiguration message contains otherConfig, then:

[0203] 2> Perform other configuration procedures, as specified in 5.3.5.9;

[0204] …

[0205] 1> Configure the content of the RRCReconfigurationComplete message as follows:

[0206] …

[0207] 1> Otherwise (received via SRB1, RRCReconfiguration):

[0208] …

[0209] 2> Submit an RRCReconfigurationComplete message to the lower layer via SRB1 to deliver the new configuration;

[0210] …

[0211] 5.3.5.5 Cell Group Configuration

[0212] 5.3.5.5.1 Overview

[0213] The network configures the UE using a Master Cell Group (MCG) and zero or one Secondary Cell Group (SCG). In (NG) EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . The network provides the configuration parameters for the cell groups in the CellGroupConfig IE.

[0214] Based on the received CellGroupConfig IE, the UE performs the following actions:

[0215] …

[0216] 1> If CellGroupConfig contains spCellConfig, then:

[0217] 2> Configure SpCell as specified in 5.3.5.5.7;

[0218] 1> If CellGroupConfig contains sCellToAddModList, then:

[0219] 2> Perform SCell addition / modification as specified in 5.3.5.5.9;

[0220] …

[0221] 5.3.5.5.7 SpCell Configuration

[0222] UE should:

[0223] …

[0224] 1> Otherwise

[0225] …

[0226] 2> If SpCellConfig contains spCellConfigDedicated, then:

[0227] 3> Configure SpCell according to spCellConfigDedicated;

[0228] …

[0229] 5.3.5.5.9 Adding / Modifying SCell

[0230] UE should:

[0231] 1> For each sCellIndex value contained in sCellToAddModList that is not part of the current UE configuration (SCell added):

[0232] 2> Based on sCellConfigCommon and sCellConfigDedicated, add the SCell corresponding to sCellIndex;

[0233] 2> If sCellState is included, then:

[0234] 3> Configure the lower layer to treat SCell as active;

[0235] 2> Otherwise:

[0236] 3> Configure the lower layer to treat SCell as inactive;

[0237] …

[0238] 1> For each sCellIndex value contained in sCellToAddModList and which is part of the current UE configuration (SCell modification):

[0239] 2> Modify the SCell configuration according to sCellConfigDedicated;

[0240] 2> If sCellToAddModList is received in an RRCReconfiguration message containing reconfigurationWithSync, or in an RRCReconfiguration message, or in an RRCReconfiguration message containing reconfigurationWithSync embedded in an RRCReconfiguration message, or in an E-UTRA RRCConnectionReconfiguration message, or in an E-UTRA RRCConnectionResume message, or in an RRCReconfiguration message embedded in an RRCReconfiguration message, or in an E-UTRA RRCConnectionReconfiguration message that activates or deactivates the SCG:

[0241] 3> If sCellState is included, then:

[0242] 4> Configure the lower layer to treat SCell as active;

[0243] 3> Otherwise:

[0244] 4> Configure the lower layer to treat SCell as inactive.

[0245] 5.3.5.9 Other Configurations

[0246] UE should:

[0247] 1> If the received otherConfig contains delayBudgetReportingConfig, then:

[0248] 2> If delayBudgetReportingConfig is set to setup, then:

[0249] 3> According to 5.7.4, consider configuring it to send delay budget reports;

[0250] 2> Otherwise:

[0251] 3> Consider not configuring it to send a delay budget report and stop timer T342 (if it is running).

[0252] …

[0253] 5.7.4 UE Auxiliary Information

[0254] 5.7.4.1 Overview

[0255] Figure 5 7.4.1-1: UE Assistance Information

[0256] The purpose of this procedure is for the UE to notify the network:

[0257] - Its delay budget report, which carries the expected increment / decrement of the DRX cycle length for the connection mode; or

[0258] …

[0259] 5.7.4.2 Initiate

[0260] A UE capable of providing a delay budget report in RRC_CONNECTED can initiate the procedure in several situations, including after being configured to provide a delay budget report and after a change in delay budget preferences.

[0261] …

[0262] After initiating the procedure, the UE should:

[0263] 1> If configured to provide delayed budget reports, then:

[0264] 2> If the UE does not transmit a UEAssistanceInformation message with a delayBudgetReport from the point of configuration to provide a delay budget report; or

[0265] 2> If the current delay budget differs from the current delay budget indicated in the last transmission of the UEAssistanceInformation message containing the delayBudgetReport, and timer T342 is not running, then:

[0266] 3> Start or restart timer T342, where the timer value is set to delayBudgetReportingProhibitTimer;

[0267] 3> Initiate the transmission of the UEAssistanceInformation message according to 5.7.4.3 to provide a delay budget report.

[0268] …

[0269] 5.7.4.3 Actions related to the transmission of UEAssistanceInformation messages

[0270] The UE should configure the content of the UEAssistanceInformation message as follows:

[0271] 1> If the transmission of a UEAssistanceInformation message is initiated according to 5.7.4.2 or 5.3.5.3 to provide a delay budget report, then:

[0272] 2> Set delayBudgetReport to type1 based on the expected value;

[0273] …

[0274] UE should:

[0275] …

[0276] 1> Otherwise:

[0277] 2> Submit UEAssistanceInformation messages to the lower layer for transmission.

[0278] …

[0279] 6.2.2 Message Definition

[0280] …

[0281] - RRCReconfiguration

[0282] The RRCReconfiguration message is a command to modify the RRC connection. It can convey information for measurement configuration, mobility control, radio resource configuration (including RB, MAC master configuration, and physical channel configuration), and AS security configuration.

[0283] Signaling radio bearer: SRB1 or SRB3

[0284] RLC-SAP: AM

[0285] Logical Channel: DCCH

[0286] Direction: Network to UE

[0287] RRCReconfiguration message

[0288] -- ASN1 begins

[0289] -- Tag-RRCRECONFIGURATION-Start

[0290] RRCReconfiguration ::= SEQUENCE {

[0291] rrc-TransactionIdentifier RRC-TransactionIdentifier,

[0292] criticalExtensions CHOICE {

[0293] rrcReconfiguration RRCReconfiguration-IEs,

[0294] criticalExtensionsFuture SEQUENCE {}

[0295] }

[0296] }

[0297] RRCReconfiguration-IEs ::= SEQUENCE {

[0298] radioBearerConfig RadioBearerConfig OPTIONAL, -- Requires M

[0299] secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG

[0300] measConfig MeasConfig OPTIONAL, -- Requires M

[0301] lateNonCriticalExtension OCTET STRING OPTIONAL,

[0302] nonCriticalExtension RRCReconfiguration-v1530-IEs OPTIONAL

[0303] }

[0304] RRCReconfiguration-v1530-IEs ::= SEQUENCE {

[0305] masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Requires M

[0306] fullConfig ENUMERATED {true} OPTIONAL, -- Cond FullConfig

[0307] dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message Optional, -- Cond nonHO

[0308] masterKeyUpdate MasterKeyUpdate optional, -- Cond MasterKeyChange

[0309] dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) Optional, -- Requires N

[0310] dedicatedSystemInformationDelivery OCTET STRING (CONTAININGSystemInformation) Optional, -- N required

[0311] otherConfig OtherConfig is optional, -- requires M

[0312] nonCriticalExtension RRCReconfiguration-v1540-IEs (Optional)

[0313] }

[0314] RRCReconfiguration-v1540-IEs ::= SEQUENCE {

[0315] otherConfig-v1540 OtherConfig-v1540 Optional, -- Requires M

[0316] nonCriticalExtension RRCReconfiguration-v1560-IEs (Optional)

[0317] }

[0318] RRCReconfiguration-v1560-IEs ::= SEQUENCE {

[0319] mrdc-SecondaryCellGroupConfig SetupRelease { MRDC-SecondaryCellGroupConfig} Optional, -- M required

[0320] radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig) Optional, -- Requires M

[0321] sk-Counter SK-Counter Optional, -- Requires N

[0322] nonCriticalExtension RRCReconfiguration-v1610-IEs (Optional)

[0323] }

[0324] …

[0325] - RRCReconfigurationComplete

[0326] The RRCReconfigurationComplete message is used to confirm the successful completion of RRC connection reconfiguration.

[0327] Signaling radio bearer: SRB1 or SRB3

[0328] RLC-SAP: AM

[0329] Logical Channel: DCCH

[0330] Direction: UE to network

[0331] RRCReconfigurationComplete message

[0332] RRCReconfigurationComplete ::= SEQUENCE {

[0333] rrc-TransactionIdentifier RRC-TransactionIdentifier,

[0334] criticalExtensions CHOICE {

[0335] rrcReconfigurationComplete RRCReconfigurationComplete-IEs,

[0336] criticalExtensionsFuture SEQUENCE {}

[0337] }

[0338] }

[0339] RRCReconfigurationComplete-IEs ::= SEQUENCE {

[0340] lateNonCriticalExtension OCTET STRING, optional

[0341] nonCriticalExtension RRCReconfigurationComplete-v1530-IEs, optional

[0342] }

[0343] RRCReconfigurationComplete-v1530-IEs ::= SEQUENCE {

[0344] uplinkTxDirectCurrentList UplinkTxDirectCurrentList, optional

[0345] nonCriticalExtension RRCReconfigurationComplete-v1560-IEs, optional

[0346] }

[0347] RRCReconfigurationComplete-v1560-IEs ::= SEQUENCE {

[0348] scg-Response CHOICE {

[0349] nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete),

[0350] eutra-SCG-Response OCTET STRING

[0351] }, optional

[0352] nonCriticalExtension RRCReconfigurationComplete-v1610-IEs, optional

[0353] }

[0354] …

[0355] - UEAssistanceInformation

[0356] The UEAssistanceInformation message is used to indicate UE assistance information to the network.

[0357] Signaling radio bearers: SRB1, SRB3

[0358] RLC-SAP: AM

[0359] Logical Channel: DCCH

[0360] Direction: UE to network

[0361] UEAssistanceInformation message

[0362] UEAssistanceInformation ::= SEQUENCE {

[0363] criticalExtensions CHOICE {

[0364] ueAssistanceInformation UEAssistanceInformation-IEs,

[0365] criticalExtensionsFuture SEQUENCE {}

[0366] }

[0367] }

[0368] UEAssistanceInformation-IEs ::= SEQUENCE {

[0369] DelayBudgetReport (Optional)

[0370] lateNonCriticalExtension OCTET STRING (optional)

[0371] nonCriticalExtension UEAssistanceInformation-v1540-IEs (Optional)

[0372] }

[0373] DelayBudgetReport::= CHOICE {

[0374] type1 ENUMERATED {

[0375] msMinus1280, msMinus640, msMinus320, msMinus160, msMinus80, msMinus60, msMinus40,

[0376] msMinus20, ms0, ms20, ms40, ms60, ms80, ms160, ms320, ms640, ms1280}, ...

[0378] }

[0379] …

[0380] 6.3.2 Radio Resource Control Information Elements

[0381] …

[0382] - CellGroupConfig

[0383] The CellGroupConfig IE is used to configure a primary cell group (MCG) or a secondary cell group (SCG). A cell group includes a MAC entity, a set of logical channels with associated RLC entities, a primary cell (SpCell), and one or more secondary cells (SCells). For NCR-MT, the CellGroupConfig IE is also used to configure side control information for NCR-Fwd access links.

[0384] -- Configuration of one Cell-Group:

[0385] CellGroupConfig ::= SEQUENCE {

[0386] cellGroupId CellGroupId

[0387] rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig Optional, -- Requires N

[0388] rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OFLogicalChannelIdentity Optional, -- Requires N

[0389] mac-CellGroupConfig Optional, -- Requires M

[0390] physicalCellGroupConfig PhysicalCellGroupConfig is optional, -- requires M

[0391] spCellConfig (Optional, -- requires M)

[0392] sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig (optional, -- requires N)

[0393] sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex (optional, -- requires N)

[0394] ...,

[0395] }

[0396] …

[0397] -- Serving cell-specific MAC and PHY parameters for SpCell:

[0398] SpCellConfig ::= SEQUENCE {

[0399] servCellIndex ServCellIndex optional, -- Cond SCG

[0400] reconfigurationWithSync ReconfigurationWithSync optional, -- CondReconfWithSync

[0401] rlf-TimersAndConstants SetupRelease { RLF-TimersAndConstants} Optional, -- Requires M

[0402] rlmInSyncOutOfSyncThreshold ENUMERATED {n1} Optional, -- Requires S

[0403] spCellConfigDedicated ServingCellConfig Optional, -- Requires M

[0404] ...,

[0405] }

[0406] …

[0407] SCellConfig ::= SEQUENCE {

[0408] sCellIndex SCellIndex,

[0409] sCellConfigCommon ServingCellConfigCommon Optional, -- Cond SCellAdd

[0410] sCellConfigDedicated ServingCellConfig Optional, -- Cond SCellAddMod

[0411] ..., [[

[0413] SMTC SSB-MTC Optional -- Requires S

[0414] ]], [[

[0416] sCellState-r16 ENUMERATED {activated} Optional, -- Cond SCellAddSync

[0417] secondaryDRX-GroupConfig-r16 ENUMERATED {true} Optional -- Requires S

[0418] ]], [[

[0420] preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) Optional, --Cond PreConfigMG

[0421] goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 Optional, -- Requires R

[0422] sCellSIB20-r17 SetupRelease {SCellSIB20-r17} Optional -- Requires M

[0423] ]], [[

[0425] plmn-IdentityInfoList-r17 SetupRelease {PLMN-IdentityInfoList} Optional, -- Cond SCellSIB20-Opt

[0426] npn-IdentityInfoList-r17 SetupRelease {NPN-IdentityInfoList-r16} Optional -- Cond SCellSIB20-Opt ]]

[0428] }

[0429] …

[0430] - CSI-MeasConfig

[0431] IE CSI-MeasConfig is used to configure the CSI-RS (reference signal) belonging to the serving cell containing CSI-MeasConfig, the channel state information report to be transmitted on the PUCCH of the serving cell containing CSI-MeasConfig, and the channel state information report on the PUSCH triggered by the DCI received on the serving cell containing CSI-MeasConfig. See also TS 38.214

[19] , Clause 5.2.

[0432] CSI-MeasConfig information element

[0433] CSI-MeasConfig ::= SEQUENCE {

[0434] nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource Optional, -- Requires N

[0435] nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId Optional, -- Requires N

[0436] nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet

[0437] Optional, -- requires N

[0438] nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId

[0439] Optional, -- requires N

[0440] csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource Optional, -- Requires N

[0441] csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId Optional, -- Requires N

[0442] csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet Optional, -- Requires N

[0443] csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId Optional, -- Requires N

[0444] csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet Optional, -- Requires N

[0445] csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId Optional, -- Requires N

[0446] csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig

[0447] Optional, -- requires N

[0448] csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId

[0449] Optional, -- requires N

[0450] csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig Optional, -- Requires N

[0451] csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId

[0452] Optional, -- requires N

[0453] reportTriggerSize INTEGER (0..6) Optional, -- requires M

[0454] `aperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList}` Optional, -- requires M

[0455] semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList} Optional, -- Requires M

[0456] ...,

[0457] }

[0458] …

[0459] - CSI-ReportConfig

[0460] IE CSI-ReportConfig is used to configure periodic or semi-static reports to be sent on the PUCCH of a cell that contains CSI-ReportConfig, or to configure semi-static or non-periodic reports to be sent on the PUSCH triggered by a DCI received on a cell that contains CSI-ReportConfig (in which case the cell on which the report is sent is determined by the received DCI). See TS 38.214

[19] , Clause 5.2.1.

[0461] CSI-ReportConfig Information Elements

[0462] CSI-ReportConfig ::= SEQUENCE {

[0463] reportConfigId CSI-ReportConfigId,

[0464] carrier ServCellIndex optional, -- Requires S

[0465] resourcesForChannelMeasurement CSI-ResourceConfigId,

[0466] csi-IM-ResourcesForInterference CSI-ResourceConfigId optional, -- Requires R

[0467] nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId optional, -- Requires R

[0468] reportConfigType CHOICE {

[0469] periodic SEQUENCE {

[0470] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0471] pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0472] }

[0473] semiPersistentOnPUCCH SEQUENCE {

[0474] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0475] pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0476] }

[0477] semiPersistentOnPUSCH SEQUENCE {

[0478] reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},

[0479] reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),

[0480] p0alpha P0-PUSCH-AlphaSetId

[0481] },

[0482] aperiodic SEQUENCE {

[0483] reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)

[0484] }

[0485] },

[0486] reportQuantity CHOICE {

[0487] none NULL,

[0488] cri-RI-PMI-CQI NULL,

[0489] cri-RI-i1 NULL,

[0490] cri-RI-i1-CQI SEQUENCE {

[0491] pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Requires S <​​​​​​​​​​​​​​​​

[0498] reportFreqConfiguration SEQUENCE {

[0499] cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI} OPTIONAL, -- Requires R

[0500] pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI} OPTIONAL, -- Requires R

[0501] csi-ReportingBand CHOICE {

[0502] subbands3 BIT STRING(SIZE(3)),

[0503] subbands4 BIT STRING(SIZE(4)),

[0504] subbands5 BIT STRING(SIZE(5)),

[0505] subbands6 BIT STRING(SIZE(6)),

[0506] subbands7 BIT STRING(SIZE(7)),

[0507] subbands8 BIT STRING(SIZE(8)),

[0508] subbands9 BIT STRING(SIZE(9)),

[0509] subbands10 BIT STRING(SIZE(10)),

[0510] subbands11 BIT STRING(SIZE(11)),

[0511] subbands12 BIT STRING(SIZE(12)),

[0512] subbands13 BIT STRING(SIZE(13)),

[0513] subbands14 BIT STRING(SIZE(14)),

[0514] subbands15 BIT STRING(SIZE(15)),

[0515] subbands16 BIT STRING(SIZE(16)),

[0516] subbands17 BIT STRING(SIZE(17)),

[0517] subbands18 BIT STRING(SIZE(18)),

[0518] ...,

[0519] subbands19-v1530 BIT STRING(SIZE(19))

[0520] } Optional -- Requires S

[0521] } Optional, -- requires R

[0522] timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},

[0523] timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},

[0524] codebookConfig Optional, -- requires R

[0525] dummy ENUMERATED {n1, n2} Optional, -- requires R

[0526] groupBasedBeamReporting CHOICE {

[0527] enabled NULL,

[0528] disabled SEQUENCE {

[0529] nrofReportedRS ENUMERATED {n1, n2, n3, n4} Optional -- Requires S

[0530] }

[0531] },

[0532] cqi-Table ENUMERATED {table1, table2, table3, table4-r17} OPTIONAL, -- Requires R

[0533] subbandSize ENUMERATED {value1, value2},

[0534] non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Requires R

[0535] ...,

[0536] }

[0537] CSI-ReportPeriodicityAndOffset ::= CHOICE {

[0538] slots4 INTEGER(0..3),

[0539] slots5 INTEGER(0..4),

[0540] slots8 INTEGER(0..7),

[0541] slots10 INTEGER(0..9),

[0542] slots16 INTEGER(0..15),

[0543] slots20 INTEGER(0..19),

[0544] slots40 INTEGER(0..39),

[0545] slots80 INTEGER(0..79),

[0546] slots160 INTEGER(0..159),

[0547] slots320 INTEGER(0..319)

[0548] }

[0549] PortIndexFor8Ranks ::= CHOICE {

[0550] portIndex8 SEQUENCE{

[0551] rank1-8 PortIndex8 is optional, -- requires R

[0552] rank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 Optional, -- Requires R

[0553] rank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 Optional, -- Requires R

[0554] rank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 Optional, -- Requires R

[0555] rank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 Optional, -- Requires R

[0556] rank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 Optional, -- Requires R

[0557] rank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 Optional, -- Requires R

[0558] rank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 Optional -- Requires R

[0559] },

[0560] portIndex4 SEQUENCE{

[0561] rank1-4 PortIndex4 is optional, -- requires R

[0562] rank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 Optional, -- Requires R

[0563] rank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 Optional, -- Requires R

[0564] rank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 Optional -- Requires R

[0565] },

[0566] portIndex2 SEQUENCE{

[0567] rank1-2 PortIndex2 is optional, -- requires R

[0568] rank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 Optional -- Requires R

[0569] },

[0570] portIndex1 NULL

[0571] }

[0572] PortIndex8::= INTEGER (0..7)

[0573] PortIndex4::= INTEGER (0..3)

[0574] PortIndex2::= INTEGER (0..1)

[0575] …

[0576] - MeasConfig

[0577] IE MeasConfig specifies the measurements to be performed by the UE and covers the configuration of intra-frequency, inter-frequency, and inter-RAT mobility as well as measurement gaps.

[0578] MeasConfig information element

[0579] MeasConfig ::= SEQUENCE {

[0580] measObjectToRemoveList (Optional, -- requires N)

[0581] measObjectToAddModList Optional, -- Requires N

[0582] `reportConfigToRemoveList` is optional; -- requires N.

[0583] `reportConfigToAddModList` is optional; -- requires N.

[0584] measIdToRemoveList MeasIdToRemoveList is optional, -- requires N

[0585] measIdToAddModList (Optional, -- requires N)

[0586] s-MeasureConfig CHOICE {

[0587] ssb-RSRP RSRP-Range,

[0588] csi-RSRP RSRP-Range

[0589] } Optional, -- Requires M

[0590] `quantityConfig` (Optional, -- requires M)

[0591] measGapConfig MeasGapConfig is optional, -- requires M

[0592] measGapSharingConfig (Optional, -- requires M)

[0593] ..., [[

[0595] interFrequencyConfig-NoGap-r16 ENUMERATED {true} Optional -- Requires R

[0596] ]], [[

[0598] effectiveMeasWindowConfig-r18 SetupRelease {MeasWindowConfig-r18} Optional -- Requires M ]]

[0600] }

[0601] MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OFMeasObjectId

[0602] MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId

[0603] ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId))OF ReportConfigId

[0604] …

[0605] - MeasId

[0606] IE MeasId is used to identify the measurement configuration, that is, the link between the measurement object and the reporting configuration.

[0607] MeasId information element

[0608] MeasId ::= INTEGER (1..maxNrofMeasId)

[0609] …

[0610] - MeasIdToAddModList

[0611] The IE MeasIdToAddModList contains a list of measurement identities to be added or modified, where each entry contains a measId, an associated measObjectId, and an associated reportConfigId.

[0612] MeasIdToAddModList information element

[0613] MeasIdToAddModList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OFMeasIdToAddMod

[0614] MeasIdToAddMod ::= SEQUENCE {

[0615] measId MeasId,

[0616] measObjectId MeasObjectId,

[0617] reportConfigId ReportConfigId

[0618] }

[0619] …

[0620] - MeasObjectId

[0621] The IE MeasObjectId is used to identify the measurement object configuration.

[0622] MeasObjectId information element

[0623] MeasObjectId ::= INTEGER (1..maxNrofObjectId)

[0624] …

[0625] - MeasObjectNR

[0626] IE MeasObjectNR specifies information applicable to intra-frequency / inter-frequency measurements of the SS / PBCH block and / or intra-frequency / inter-frequency measurements of the CSI-RS.

[0627] MeasObjectNR information element

[0628] -- ASN1 begins

[0629] -- Tag-MEASOBJECTNR-Start

[0630] MeasObjectNR ::= SEQUENCE {

[0631] ssbFrequency ARFCN-ValueNR Optional, -- Cond SSBorAssociatedSSB

[0632] ssbSubcarrierSpacing SubcarrierSpacing Optional, -- CondSSBorAssociatedSSB

[0633] smtc1 SSB-MTC optional, -- Cond SSBorAssociatedSSB

[0634] smtc2 SSB-MTC2 Optional, -- Cond IntraFreqConnected

[0635] refFreqCSI-RS ARFCN-ValueNR Optional, -- Cond CSI-RS

[0636] referenceSignalConfig ReferenceSignalConfig,

[0637] absThreshSS-BlocksConsolidationThesholdNR Optional, -- Requires R

[0638] absThreshCSI-RS-Consolidation ThresholdNR Optional, -- Requires R

[0639] `nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage)` is optional; -- requires R.

[0640] nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) Optional, -- Requires R

[0641] quantityConfigIndex INTEGER (1..maxNrofQuantityConfig),

[0642] offsetMO Q-OffsetRangeList,

[0643] cellsToRemoveList PCI-List Optional, -- Requires N

[0644] cellsToAddModList CellsToAddModList Optional, -- Requires N

[0645] excludedCellsToRemoveList PCI-RangeIndexList Optional, -- Requires N

[0646] excludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OFPCI-RangeElement Optional, -- Requires N

[0647] allowedCellsToRemoveList PCI-RangeIndexList Optional, -- Requires N

[0648] allowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OFPCI-RangeElement Optional, -- Requires N

[0649] ...,

[0650] }

[0651] ReferenceSignalConfig::= SEQUENCE {

[0652] ssb-ConfigMobility (Optional, -- requires M)

[0653] csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility} Optional -- Requires M

[0654] }

[0655] SSB-ConfigMobility::= SEQUENCE {

[0656] ssb-ToMeasure SetupRelease { SSB-ToMeasure} Optional, -- requires M

[0657] deriveSSB-IndexFromCell BOOLEAN,

[0658] SS-RSSI-Measurement (optional, -- requires M)

[0659] ...,

[0660] }

[0661] Q-OffsetRangeList ::= SEQUENCE {

[0662] rsrpOffsetSSB Q-OffsetRange DEFAULT dB0,

[0663] rsrqOffsetSSB Q-OffsetRange DEFAULT dB0,

[0664] sinrOffsetSSB Q-OffsetRange DEFAULT dB0,

[0665] rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0,

[0666] rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0,

[0667] sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0

[0668] }

[0669] ThresholdNR ::= SEQUENCE{

[0670] thresholdRSRP RSRP-Range OPTIONAL, -- Required for R

[0671] thresholdRSRQ RSRQ-Range OPTIONAL, -- Required for R

[0672] thresholdSINR SINR-Range OPTIONAL -- Required for R

[0673] }

[0674] CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod

[0675] CellsToAddMod ::= SEQUENCE {

[0676] physCellId PhysCellId,

[0677] cellIndividualOffset Q-OffsetRangeList

[0678] }

[0679] …

[0680] - MeasObjectToAddModList

[0681] The IE MeasObjectToAddModList relates to a list of measurement objects to be added or modified.

[0682] MeasObjectToAddModList information element

[0683] MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod

[0684] MeasObjectToAddMod ::= SEQUENCE {

[0685] measObjectId MeasObjectId,

[0686] measObject CHOICE {

[0687] measObjectNR MeasObjectNR,

[0688] ...

[0689] measObjectEUTRA MeasObjectEUTRA,

[0690] measObjectUTRA-FDD-r16 MeasObjectUTRA-FDD-r16,

[0691] measObjectNR-SL-r16 MeasObjectNR-SL-r16,

[0692] measObjectCLI-r16 MeasObjectCLI-r16,

[0693] measObjectRxTxDiff-r17 MeasObjectRxTxDiff-r17,

[0694] measObjectRelay-r17 SL-MeasObject-r16,

[0695] measObjectNR-SL-r18 MeasObjectNR-SL-r18

[0696] }

[0697] }

[0698] …

[0699] - ReportConfigId

[0700] The IE ReportConfigId is used to identify the measurement report configuration.

[0701] ReportConfigId information element

[0702] ReportConfigId ::= INTEGER (1..maxReportConfigId)

[0703] …

[0704] - ReportConfigNR

[0705] IE ReportConfigNR specifies the criteria for triggering NR measurement report events, or CHO, CPA, or CPC events, or L2 U2N relay measurement report events. For events marked AN, where N equals 1, 2, etc., measurement report events and CHO, CPA, or CPC events are based on cell measurement results, which can be derived from SS / PBCH blocks or CSI-RS.

[0706] Event A1: Service becomes better than the absolute threshold;

[0707] Event A2: The service becomes worse than the absolute threshold;

[0708] Event A3: The neighbor becomes one offset better than PCell / PSCell;

[0709] Event A4: Neighbors become better than the absolute threshold;

[0710] Event A5: PCell / PSCell becomes worse than absolute threshold 1, and the neighboring cell / Scell ​​becomes better than another absolute threshold 2;

[0711] Event A6: The neighbor becomes one offset better than SCell;

[0712] ReportConfigNR information element

[0713] ReportConfigNR ::= SEQUENCE {

[0714] reportType CHOICE {

[0715] periodical PeriodicalReportConfig,

[0716] eventTriggered EventTriggerConfig,

[0717] ...,

[0718] reportCGI ReportCGI,

[0719] reportSFTD ReportSFTD-NR,

[0720] condTriggerConfig-r16 CondTriggerConfig-r16,

[0721] cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,

[0722] cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,

[0723] rxTxPeriodical-r17 RxTxPeriodical-r17,

[0724] reportOnScellActivation-r18 ReportOnScellActivation-r18

[0725] }

[0726] }

[0727] EventTriggerConfig ::= SEQUENCE {

[0728] eventId CHOICE {

[0729] eventA1 SEQUENCE {

[0730] a1-Threshold MeasTriggerQuantity,

[0731] reportOnLeave BOOLEAN,

[0732] hysteresis Hysteresis,

[0733] timeToTrigger TimeToTrigger

[0734] },

[0735] eventA2 SEQUENCE {

[0736] a2-Threshold MeasTriggerQuantity,

[0737] reportOnLeave BOOLEAN,

[0738] hysteresis Hysteresis,

[0739] timeToTrigger TimeToTrigger

[0740] },

[0741] eventA3 SEQUENCE {

[0742] a3-Offset MeasTriggerQuantityOffset,

[0743] reportOnLeave BOOLEAN,

[0744] hysteresis Hysteresis,

[0745] timeToTrigger TimeToTrigger,

[0746] useAllowedCellList BOOLEAN

[0747] },

[0748] eventA4 SEQUENCE {

[0749] a4-Threshold MeasTriggerQuantity,

[0750] reportOnLeave BOOLEAN,

[0751] hysteresis Hysteresis,

[0752] timeToTrigger TimeToTrigger,

[0753] useAllowedCellList BOOLEAN

[0754] },

[0755] eventA5 SEQUENCE {

[0756] a5-Threshold1 MeasTriggerQuantity,

[0757] a5-Threshold2 MeasTriggerQuantity,

[0758] reportOnLeave BOOLEAN,

[0759] hysteresis Hysteresis,

[0760] timeToTrigger TimeToTrigger,

[0761] useAllowedCellList BOOLEAN

[0762] },

[0763] eventA6 SEQUENCE {

[0764] a6-Offset MeasTriggerQuantityOffset,

[0765] reportOnLeave BOOLEAN,

[0766] hysteresis Hysteresis,

[0767] timeToTrigger TimeToTrigger,

[0768] useAllowedCellList BOOLEAN

[0769] },

[0770] ...,

[0771] },

[0772] rsType NR-RS-Type,

[0773] reportInterval ReportInterval,

[0774] reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

[0775] reportQuantityCell MeasReportQuantity,

[0776] maxReportCells INTEGER (1..maxCellReport),

[0777] reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- REQUIRED R

[0778] maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL,-- REQUIRED R

[0779] includeBeamMeasurements BOOLEAN,

[0780] reportAddNeighMeas ENUMERATED {setup} OPTIONAL, -- REQUIRED R

[0781] ...,

[0782] }

[0783] PeriodicalReportConfig ::= SEQUENCE {

[0784] rsType NR-RS-Type,

[0785] reportInterval ReportInterval,

[0786] reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},

[0787] reportQuantityCell MeasReportQuantity,

[0788] maxReportCells INTEGER (1..maxCellReport),

[0789] reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- REQUIRED R

[0790] maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL,-- REQUIRED R

[0791] includeBeamMeasurements BOOLEAN,

[0792] useAllowedCellList BOOLEAN,

[0793] ...,

[0794] }

[0795] NR-RS-Type ::= ENUMERATED {ssb, csi-rs}

[0796] MeasTriggerQuantity ::= CHOICE {

[0797] rsrp RSRP-Range,

[0798] rsrq RSRQ-Range,

[0799] sinr SINR-Range

[0800] }

[0801] MeasTriggerQuantityOffset ::= CHOICE {

[0802] rsrp INTEGER (-30..30),

[0803] rsrq INTEGER (-30..30),

[0804] sinr INTEGER (-30..30)

[0805] }

[0806] MeasReportQuantity ::= SEQUENCE {

[0807] rsrp BOOLEAN,

[0808] rsrq BOOLEAN,

[0809] sinr BOOLEAN

[0810] }

[0811] …

[0812] - ReportConfigToAddModList

[0813] The IE ReportConfigToAddModList is a list of report configurations to be added or modified.

[0814] ReportConfigToAddModList Information Element

[0815] ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId))OF ReportConfigToAddMod

[0816] ReportConfigToAddMod ::= SEQUENCE {

[0817] reportConfigId ReportConfigId,

[0818] reportConfig CHOICE {

[0819] reportConfigNR ReportConfigNR,

[0820] ...,

[0821] reportConfigInterRAT ReportConfigInterRAT,

[0822] reportConfigNR-SL-r16 ReportConfigNR-SL-r16

[0823] }

[0824] }

[0825] …

[0826] - ServingCellConfig

[0827] The IE ServingCellConfig is used to configure (add or modify) the serving cell for the UE, which can be an SpCell or SCell of an MCG or SCG. The parameters in this document are primarily UE-specific, but some are also cell-specific (e.g., in the bandwidth section of a separate configuration). Reconfiguration between PUCCH and PUCCH-free SCells is supported only using SCell release and addition.

[0828] ServingCellConfig information element

[0829] -- ASN1 begins

[0830] -- Tag - SERVINGCELLCONFIG - Start

[0831] ServingCellConfig ::= SEQUENCE {

[0832] tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated Optional, --Cond TDD

[0833] initialDownlinkBWP BWP-DownlinkDedicated Optional, -- Requires M

[0834] downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id (optional, -- requires N)

[0835] downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink Optional, -- Requires N

[0836] firstActiveDownlinkBWP-Id BWP-Id optional, -- Cond SyncAndCellAdd

[0837] bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,

[0838] ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500,

[0839] ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8,

[0840] spare7, spare6, spare5, spare4, spare3, spare2, spare1} Optional, --Requires R

[0841] defaultDownlinkBWP-Id BWP-Id is optional, -- requires S

[0842] uplinkConfig (Optional, -- requires M)

[0843] supplementaryUplink UplinkConfig is optional, -- requires M

[0844] pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig} Optional, -- Requires M

[0845] pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig} Optional, -- Requires M

[0846] csi-MeasConfig SetupRelease { CSI-MeasConfig} Optional, -- Requires M

[0847] sCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240,

[0848] ms320, ms400, ms480, ms520, ms640, ms720,

[0849] ms840, ms1280, spare2, spare1} are optional.

[0850] …

[0851] 6.3.4 Other Information Elements

[0852] …

[0853] - OtherConfig

[0854] IE OtherConfig contains configurations related to other miscellaneous configurations.

[0855] OtherConfig information element

[0856] -- ASN1 begins

[0857] -- Tag-OTHERCONFIG-Start

[0858] OtherConfig ::= SEQUENCE {

[0859] delayBudgetReportingConfig CHOICE{

[0860] release NULL,

[0861] setup SEQUENCE{

[0862] delayBudgetReportingProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30}

[0863] }

[0864] } Optional -- Requires M

[0865] }

[0866] …

[0867] In the RAN2 #127bis report, a consensus has been reached on the procedures for reporting applicable functions. It is worth noting that the diagram in the RAN2 #127bis report illustrating exemplary scenarios associated with applicable function reporting is reproduced in this document. Figure 8 The following quotes one or more sections of the RAN2 #127bis report:

[0868] 8.1.2.2 LCM of the UE-side model for beam management use cases

[0869] …

[0870]

[0871]

[0872]

[0873] The RAN1 #119 report has reached some consensus on beam management lifecycle management (LCM). The following quotes one or more sections of the RAN1 #119 report:

[0874] R1-2410737 FL Summary of AI / ML in Beam Management #4 Moderator (Samsung)

[0875] From Friday's meeting

[0876] Summarize

[0877] For the CSI-ReportConfig provided in step 5 for inferring the configuration,

[0878] • After RRCReconfigurationComplete, NW can activate / trigger non-periodic CSI reports and semi-static CSI reports.

[0879] • Periodic CSI reports are considered to be activated after RRCReconfigurationComplete.

[0880] • Note: It is not expected that the UE will be configured with CSI-ReportConfig for inference configurations of inapplicable inference parameter sets or with inapplicable CSI-ReportConfig.

[0881] ○ Any normative impact is a separate discussion.

[0882] consensus

[0883] Send an LS with the following information to RAN2.

[0884] RAN1 thanks RAN2 for providing the LS report on the applicable functionality of the beam management UE-side model.

[0885] In RAN1's ​​discussion of RAN2 terminology regarding beam management,

[0886] • The “function” in the concept / terminology can refer to UE capability information / parameters, i.e., Rel-19 features / FG that support AI / ML.

[0887] • In the context of the concepts / terms applicable to this concept / term, "function" can refer to the CSI-ReportConfig used for inferring the configuration, or the set of parameters related to inference.

[0888] • Activated features can be enabled based on the CSI framework.

[0889] Therefore, the meaning and granularity of "function" can be the same or different for the applicable function, the activated function, and the supported function.

[0890] RAN 1 reached the following consensus regarding issues arising from RAN 2:

[0891]

[0892]

[0893] Artificial intelligence (AI) / machine learning (ML) is introduced in fifth-generation (5G) advanced technology to enhance the network.

[0894] For challenging scenarios involving high frequency, rapidly changing conditions, and narrow beam coverage, the introduction of AI / ML models in 5G Advanced aims to pave the way for 6G, with AI / ML models expected to outperform traditional methods in terms of performance.

[0895] For the air interface, 3GPP Working Group 1 (WG1) identified the following use cases for enhancement: Channel State Information (CSI) feedback enhancement, beam management, and positioning accuracy enhancement. Beam management is one of the most important use cases. The current beam management procedure includes the following steps: (1) beam sweeping, (2) User Equipment (UE) beam measurement, and (3) UE beam reporting. For example, a next-generation Node B (gNB) first transmits multiple beams in different directions and angles. Then, the UE measures all the transmitted beams and determines the beam with the best measurement result (e.g., Reference Signal Received Power (RSRP) or Signal to Interference plus Noise Ratio (SINR)). The best result is reported through the CSI reporting framework. The UE can be configured and / or activated to perform periodic, semi-static, or non-periodic reporting of beam results. Beam configuration and measurement can be labor-intensive. With AI / ML assistance, the UE can spatially predict the beam to reduce the number of measurements performed. The UE can also predict future beams in time for challenging conditions that are changing rapidly, making it more feasible to establish beam pairs in frequency range 2 (FR2) scenarios.

[0896] Several aspects of the Layer 3 (L3) measurement framework also have potential for enhancement in mobility. The current L3 handover mechanism relies on a customized measurement configuration that utilizes the measurement object, reporting configuration, and measurement identity to configure the frequencies and cells for the UE to measure. The UE first measures the configured frequencies and cells, and then reports the measurement results to the network (NW) when the measurement results meet the reporting trigger conditions. The NW can then reconfigure the UE to perform handover based on the triggered event type and the measurement results. This mechanism works well but remains limited to a passive approach. In cases of lower coverage at higher frequencies, handover may occur more frequently, and therefore a more proactive approach could be sought. Currently, for AI / ML mobility enhancements, Radio Resource Management (RRM) measurement prediction, Radio Link Failure (RLF) / Handover Failure (HoF) prediction, and measurement event prediction have been investigated. For RRM measurement prediction, the UE can predict measurement results for future time instances or measurements from another cell based on historical measurements and include the predicted measurements in the measurement report. For RLF / HoF prediction, the UE can predict the probability of an RLF / HoF occurring within a time window (or period) prior to its actual occurrence. For measurement event prediction, the UE can predict the probability of a measurement event (e.g., event A3) occurring (or triggering a report, meeting entry and / or exit conditions) within a time window (or period) and send a measurement report to the NW. With the assistance of AI / ML models, the UE can proactively respond to potential radio problems and enhance handover performance. Redundant measurements can also be reduced to save resources (e.g., measurement gaps, UE power).

[0897] The general framework of the AI / ML procedure has been agreed upon in reports RAN2 #127bis and / or RAN1 #119. The procedure includes at least one or more of the following steps: In the first two steps, the NW queries and receives UE capabilities. In step 3, the NW can provide one or more inference configurations (e.g., CSI reporting configurations for inference). In step 3, the NW can provide one or more sets of inference-related parameters. In step 4, the UE can report whether the provided configuration and / or inference-related parameter sets are suitable for the NW. In response to step 4, the NW can reconfigure the UE in step 5.

[0898] In research on AI / ML for beam management, numerous use cases and variations have been identified. For example, configuration inference can be used for spatial and / or temporal prediction. For instance, the prediction of a set of beams can be based on various beam numbers and / or beam patterns. These multiple use cases lead to a large number of combinations, resulting in an excessive amount of potential configuration and / or inferred-related parameter sets being sent to the UE via signaling, most of which are often unnecessary.

[0899] For example, an NW might want to configure a UE to report a (specific) set of beams. In Release 18, this could be achieved using a traditional CSI reporting configuration (e.g., CSI reporting configurations prior to Release 19). With the introduction of AI / ML, multiple variations of the inference configuration (e.g., the CSI reporting configuration for inference) serving this purpose can exist (e.g., inference configurations for predicting the set of beams based on different beam numbers and / or different beam patterns). Each variation can be associated with one or more inference configurations (e.g., signaled in step 3). Each variation can be associated with one or more sets of inference-related parameters (e.g., signaled in step 3). Ultimately, only one variation may be configured and / or applied.

[0900] Furthermore, the UE can support multiple AI / ML features / functions. For example, AI / ML features / functions may include AI / ML for beam management and / or AI / ML for mobility. This results in multiple potential configurations across different use cases and AI / ML features / functions. As more AI / ML features / functions are introduced, the processing of management and signal transmission may become more complex.

[0901] To at least solve the above problems, at least some of the methods described below may be used or considered. At least one or more of the methods (or instances, concepts) described below may be used or considered. At least one or more of the methods (or instances, concepts) may be combined.

[0902] In the following text, "traditional configuration" can be replaced with "configuration prior to version 19", "configuration without AI / ML enhancements", and / or "configuration without version 19 (AI / ML) enhancements". "Inference configuration" can be replaced with "configuration used for inference", "configuration related to AI / ML", or "(inference) configuration". "Function" can be replaced with "inference configuration", "inference-related parameter set", and / or "group". Functions can be features (e.g., beam prediction, CSI prediction, CSI compression, AI mobility), use cases (e.g., time, space), and / or variants (e.g., 4-beam to 8-beam prediction, 8-beam to 16-beam prediction). "Configuration" can be replaced with "traditional configuration" and / or "inference configuration". (Inference) configuration can be used for CSI reporting (e.g., CSI-ReportConfig). (Inference) configuration can be used for mobility (e.g., measId, measObject, and / or reportConfig).

[0903] In the following text, "parameter set" can refer to "inference-related parameter set". Parameter sets can be used in AI / MI-based CSI reports.

[0904] The UE can receive a first configuration related to AI / ML from the NW (e.g., as step 3 of the AI / ML procedure during Radio Resource Control (RRC) reconfiguration). The configuration can be provided in step 3 of the AI / ML procedure. The configuration can be (or include) configurations for inference. The configuration can be (or include) configurations for applicability reporting (e.g., step 4 of the AI / ML procedure). The UE can perform applicability reporting based on the configuration (e.g., step 4 of the AI / ML procedure).

[0905] For example, in the first configuration, the NW can provide one or more (inferred) configurations and / or one or more inferred related parameter sets to the UE.

[0906] For example, inferring relevant parameters may include at least one or more of the following: associated identifier (ID), CSI resource configuration ID for measurement, CSI resource configuration ID for prediction, information related to reporting (e.g., number of reports, PUCCH resources, etc.), time-related information for measurement (e.g., (maximum) measurement window (in timeslots, ms, time, duration, etc.), (maximum) number of instances to be measured, measurement and / or measurement window offset), time-related information for prediction (e.g., (maximum) prediction window (in timeslots, ms, time, duration, etc.), (maximum) number of instances to be predicted, prediction and / or prediction window offset), information for BM-Case 1, information for beam management (BM)-Case 2, relationships between beams for measurement (e.g., number of beams to be measured, number of beams to be predicted, etc.), etc.

[0907] For example, inference-related parameters can be included in one or more (inference) configurations.

[0908] For example, inferred relevant parameters can be included in reports sent to NW (e.g., reports on applicable and / or non-applicable functions).

[0909] Figure 9 Example representation 900 illustrates a first configuration according to some embodiments (e.g., received from the NW in step 3 of an AI / ML procedure). For example, in the first configuration, the NW may provide (inferred) configurations in a first list. The first list can be used for both conventional and (inferred) configurations (e.g., csi-ReportConfigToAddModList). In example representation 900 of the first configuration, the first list may be provided after “1. Configure CSI-ReportConfig in the first list.”

[0910] For example, in the first configuration, NW can provide (inferred) configuration in the second list. The second list can be used for the (inferred) configuration. For example, the (inferred) configuration can be identified by an ID (e.g., a feature ID). In example representation 900 of the first configuration, the second list can be provided after "2. Configure CSI-ReportConfig in the second list."

[0911] For example, in the first configuration, NW can provide the inference-related parameter set in the third list. The third list can be (and / or include) the inference-related parameter set. For example, each inference-related parameter set can be encapsulated in a container (e.g., a new Information Element, IE)). For example, the container can include multiple parameters. For example, the container can include multiple fields, each of which can be associated with a parameter. For example, the container can be identified by an ID (e.g., container ID). The ID can be separate from CSI-ReportConfigId, the associated ID, and / or the model ID. In example representation 900 of the first configuration, the third list can be provided after “3. Configure the inference-related parameter set in the third list (e.g., aiml-FunctionalityContainer).”

[0912] For example, in the first configuration, the NW can provide one or more options for inferred relevant parameters. In example representation 900 of the first configuration, options can be provided after “4. Parameter Options”. For example, in the (inferred) configuration, the NW can provide one or more options for one or more parameters in one or more fields (e.g., in a list). For example, in the inferred relevant parameter set, the NW can provide one or more options for one or more parameters in one or more fields (e.g., in a list). In example representation 900 of the first configuration, one or more options can be provided after “5. Options Provided in the Inferred Relevant Parameter Set (e.g., aiml-FunctionalityContainer) or CSI-ReportConfig”. For example, in the inferred relevant parameter set, the NW can provide one or more options for all parameters in all fields (e.g., in a list). For example, the UE can apply (and / or report) (applicable and / or inapplicable) configurations and / or inferred relevant parameter sets based on the provided options. For example, the UE can select one or more options to be applied and / or reported.

[0913] For example, in the first configuration, the NW may not provide one or more inferred parameters (or may not provide an option to provide one or more inferred parameters). For example, in the (inferred) configuration, the NW may indicate (e.g., implicitly indicate) one or more parameters not specified by the NW. For example, the NW may indicate one or more parameters by not providing one or more fields and / or one or more parameters. For example, the NW may indicate one or more parameters by not providing an option to provide one or more fields and / or one or more parameters (e.g., providing an empty list). In the example representation 900 of the first configuration, an indication field is provided empty after “6. Indications provided in the container or CSI-ReportConfig” to indicate (e.g., implicitly indicate) one or more parameters. For example, in the set of inferred parameters, the NW may indicate (e.g., implicitly indicate) one or more parameters not specified by the NW. For example, the NW may indicate one or more parameters by not providing one or more fields and / or one or more parameters. For example, the NW may indicate by not providing an option to provide one or more fields and / or one or more parameters (e.g., providing an empty list). For example, the UE can apply (and / or report) (applicable and / or inapplicable) configurations and / or infer relevant parameter sets based on internal UE conditions (e.g., AI / ML model capabilities, power levels, memory utilization, computing resources, etc.). For example, the UE can apply and / or report preferred values ​​for fields and / or parameters that are not provided or indicated as not specified by the NW.

[0914] For example, in the first configuration, the NW can group one or more configurations and / or one or more inferred related parameter sets. In some examples, the NW can use one or more nested lists to group one or more configurations and / or one or more inferred related parameter sets. In example representation 900 of the first configuration, one or more lists (e.g., nested lists) of groups of inferred related parameter sets and / or CSI-ReportConfig are provided after “7. Lists in lists can be used to group inferred related parameter sets or CSI-ReportConfig”. For example, IDs (e.g., group IDs) can be included in the inferred configurations and / or inferred related parameter sets. Configurations and / or inferred related parameter sets with the same group ID can be considered grouped together. In example representation 900 of the first configuration, group IDs 0 and 1 for grouping configurations and / or inferred related parameter sets are provided after “8. IDs (e.g., group IDs) can be used to group inferred related parameter sets or CSI-ReportConfig”. For example, IEs (e.g., lists) can include one or more configurations and / or one or more inferred related parameter sets. The NW can provide one or more of the IEs to the UE. One or more configuration and / or one or more inferred related parameter sets within the same IE can be considered as grouped together. For example, a UE can apply (and / or report) (applicable and / or inapplicable) configuration and / or inferred related parameter sets based on grouping. For example, a UE can select one or more inferred configuration and / or one or more inferred related parameter sets to be applied and / or reported for each group.

[0915] For example, in a first configuration, the NW may indicate whether one or more configurations can be activated / triggered. For example, fields (or indications) may be included in one or more configurations and / or groups to indicate whether a configuration within a configuration and / or group is activated / triggered, whether it can be activated / triggered, and / or whether it can be activated / triggered. For example, a configuration within a configuration and / or group may be activated / triggered after (e.g., by the NW and / or UE) reports applicable and / or inapplicable functions (for the configuration and / or group). For example, fields (or indications) may be included in one or more configurations and / or groups to indicate whether a configuration within a configuration and / or group is not activated / triggered, whether it cannot be activated / triggered, and / or whether it can be deactivated / triggered.

[0916] For example, for each configuration, parameter set, and / or group, a priority can be indicated (e.g., by the NW). Priorities can be applied within groups, fields, parameters, and / or across all configurations and / or parameter sets. For example, fields (or indications) can be included in configurations, parameter sets, and / or groups to indicate the priority of a configuration, parameter set, and / or group. Lower values ​​in fields can indicate higher priorities. For example, within a list of configurations, parameter sets, and / or groups, entries with lower indices can have higher priorities. For example, configurations, parameter sets, and / or groups identified by IDs with lower numerical values ​​can have higher priorities. For example, the UE can apply (and / or report) inferred (applicable and / or inapplicable) configurations and / or related parameter sets based on the priority of groups, fields, parameters, options, configurations, and / or inferred related parameter sets. For example, the UE can select one or more inferred configurations and / or one or more inferred related parameter sets with higher priorities to apply and / or report. For example, the UE can select one or more fields, parameters, and / or options with higher priorities to apply and / or report.

[0917] The UE can perform / transmit / initiate an suitability report (for AI / ML) to the NW (e.g., as step 4 of the AI / ML procedure, after receiving the above configuration (or in response to it)). In step 4, the UE can report applicable and / or inapplicable functions to the NW (e.g., by transmitting an suitability report). The report can be based on one or more inferred configurations and / or one or more inferred related parameter sets provided in step 3. Hereinafter, a function can be an inferred configuration, an inferred related parameter set, and / or a group.

[0918] Figure 10Example representation 1000 illustrates an applicability report according to some embodiments (e.g., provided by the UE to the NW to indicate applicable and / or inapplicable functions). In some examples, the first section of example representation 1000 of the applicability report (following “1. Report ID (based on step 3, e.g., CSI-ReportConfigID, Container ID, Associated ID, Group ID)”) can use IDs to report applicability (e.g., performing applicability reporting by ID). For example, functions associated with ID 0 and ID 1 can be indicated as applicable functions, and / or functions associated with ID 2 and ID 3 can be indicated as inapplicable functions. In some examples, the second section of example representation 1000 of the applicability report (following “2. Report Inferred Related Parameter Sets”) reports applicability with respect to one or more inferred related parameter sets (e.g., instances of aiml-FunctionalityContainer). For example, functions associated with aiml-FunctionalityContainer 0 and aiml-FunctionalityContainer (with option) 1 can be indicated as applicable functions, and / or functions associated with aiml-FunctionalityContainer 2 and aiml-FunctionalityContainer (with option) 3 can be indicated as inapplicable functions. In some examples, the third section of the applicability report (following “3. Report Selected Parameters”) can report the applicability of one or more selected parameters associated with a function. For example, a function with selected parameters such as {associatedID: [0, 1], setA: [0, 1], setB: [1, 2], subcase: [time]} can be indicated as an applicable function, and / or a function with selected parameters such as {associatedID: [2], setA: [2], setB: [0], subcase: [space]} can be indicated as an inapplicable function. In some examples, the fourth section of the applicability report (following “4. Report ID and Selected Parameters”) allows applicability to be reported for combinations of ID and one or more selected parameters. For example, entries such as {ID: 0, setB: [1]} and {ID: 1, setB: [1, 2, 3]} can each be indicated as applicable functions.

[0919] For example, the UE can report applicable and / or inapplicable functions to the NW based on IDs (e.g., CSI-ReportConfigId, associated ID, function ID, container ID, group ID). For example, the UE can indicate whether a function associated with an ID is applicable or inapplicable. For example, one or more flags (or indicators / parameters) can be included in the report (e.g., within a single list). Flags (or indicators / parameters) can be associated with IDs. When a function is applicable (or in response to a function being applicable), the associated flag (or indicator / parameter) can be set to a first value (e.g., true). When a function is inapplicable (or in response to a function being inapplicable), the associated flag (or indicator / parameter) can be set to a second value (e.g., false). Flags (or indicators / parameters) can be IE, numeric, integer, enumeration, bit string, or Boolean (existence). For example, the UE can include one or more IDs in the first report. Each ID can be associated with a function. More than one type of function can be included in the applicability report (e.g., the applicability report can include the first report). Functions associated with IDs included in the first report can be applicable functions. For example, the UE may include one or more IDs in a second report (and / or a first report). Each ID may be associated with a function. More than one type of function may be included in the applicability report (e.g., the applicability report may include a second report). The function associated with an ID included in the second report may be an inapplicable function. The applicability report may include a first report and / or a second report. The first report may indicate one or more applicable functions, and / or the second report may indicate one or more inapplicable functions. For example, the first and second reports may be included in the same message and / or IE sent to the NW. For example, the first and second reports may be included in different messages and / or IEs sent to the NW. For example, more than one type of ID may be included in the report (e.g., each ID may correspond to one or more ID types). ID types may include: CSI-ReportConfigId, associated ID, function ID, container ID, and / or group ID. For example, a function ID may indicate the inferred configuration for a function and / or be associated with the inferred configuration for a function. For example, a container ID may indicate the inferred related parameter set for a function and / or be associated with the inferred related parameter set for a function.

[0920] For example, the UE can report applicable and / or inapplicable functions to the NW based on inferred configuration and / or inferred related parameter sets. For example, the report (e.g., within a single list) may include IDs (e.g., container ID, function ID, associated ID). Each ID can be associated with a function. IDs may or may not be (based on) IDs, configurations, and / or inferred related parameter sets provided by the NW. For example, the UE can indicate whether a function is applicable (or inapplicable). For example, the report may include one or more flags / indicators / parameters. Flags / indicators / parameters can be associated with functions. When a function is applicable (in response to the applicability of a function), the associated flag / indicator / parameter can be set to a first value (e.g., true). When a function is inapplicable (in response to the inapplicability of a function), the associated flag / indicator / parameter can be set to a second value (e.g., false). Flags / indicators / parameters can be IE, numeric, integer, enumeration, bit string, or Boolean (existence). For example, the UE can indicate one or more inferred configurations and / or one or more inferred related parameter sets in a third report. The inferred configuration and / or inferred related parameter set included in the third report may be (or include) applicable functions. For example, the UE may indicate one or more inferred configurations and / or one or more inferred related parameter sets in the fourth report (and / or the third report). The inferred configuration and / or inferred related parameter set included in the fourth report (and / or the third report) may be (or include) non-applicable functions. For example, the third and fourth reports may be included in the same message and / or IE sent to the NW. For example, the third and fourth reports may be included in different messages and / or IEs sent to the NW.

[0921] For example, the UE may report one or more inferred related parameters (one or more selected options of inferred related parameters). The UE may report to the NW the applicability and / or inapplicability of functions (e.g., based on ID or not based on ID), and one or more inferred related parameters (one or more selected options of inferred related parameters) (for one or more fields and / or parameters). For example, one or more (selected) inferred related parameters may be included in the report. One or more inferred related parameters may be associated with ID and / or function. For example, the included (selected) inferred related parameters may be the same set or subset of parameters provided by the NW (in a previous message, such as step 3). For example, the included (selected) inferred related parameters may be one or more of the function options provided by the NW (in a previous message, such as step 3). The included inferred related parameters may be the value of an option and / or an indication of an option. For example, the included (selected) inferred related parameters may not be included in the parameters and / or options provided by the NW. For example, when configuring and / or applying a function based on the included parameters (or in response to this), the included (selected) inferred related parameters may indicate to the UE whether the function is applicable or inapplicable. For example, when no option is selected, an option is provided, and / or the UE is applicable to all available options (or in response to this), the (selected) inferred relevant parameters may not be included. For example, the UE may include one or more (selected) inferred relevant parameters and / or one or more IDs (e.g., CSI-ReportConfigId, Function ID, Associated ID, Container ID, Group ID) in the fifth report. When configuring and / or applying a function based on the included parameters (or in response to this), the parameters included in the fifth report may indicate that the UE is applicable to the function. For example, the UE may include one or more (selected) inferred relevant parameters and / or one or more IDs (e.g., CSI-ReportConfigId, Function ID, Associated ID, Container ID, Group ID) in the sixth report (and / or the fifth report). When configuring and / or applying a function based on the included parameters (or in response to this), the parameters included in the sixth report (and / or the fifth report) may indicate that the UE is not applicable to the function. For example, the fifth and sixth reports may be included in the same message and / or IE sent to the NW. For example, the fifth and sixth reports may be included in different messages and / or IEs sent to the NW.

[0922] For example, for each report, preferences can be indicated (e.g., to the NW). The UE can indicate preferences for functions, parameters, and / or options. For example, one or more fields can be included. Fields can be associated with IDs, functions, parameter sets, and / or options. Lower values ​​in fields can indicate higher preferences for functions, parameters, and / or options. For example, within a list of IDs, functions, parameters, and / or options, the UE may prefer entries with lower indices. For example, the UE may prefer functions identified by IDs with lower numerical values.

[0923] The UE can receive a (second) configuration related to AI / ML from the NW (e.g., as step 5 of the AI / ML procedure during RRC reconfiguration). The configuration can be provided in step 5 of the AI / ML procedure. The configuration can be (or include) a configuration for inference. The configuration can be provided after the UE transmits an applicability report (e.g., step 4 of the AI / ML procedure). The second configuration (e.g., provided in step 5) can differ from the first configuration (e.g., provided in step 3). In step 5, the NW can provide the inferred configuration to the UE.

[0924] For example, in the (second) configuration, the NW can (re)configure the UE upon receiving a report of applicable and / or inapplicable functions (or in response to this). For example, the NW can provide and / or configure (inferred) configurations in the first and / or second lists.

[0925] For example, upon receiving a report of applicable and / or inapplicable functions (or in response to such a report), the NW can activate / trigger one or more configurations. For example, the NW can send L1 / L2 / L3 signaling (e.g., RRC messages, Medium Access Control (MAC) Control Element (CE), Downlink Control Information (DCI)) to the UE for activation / triggering. For example, signaling can activate / trigger one or more configurations until the NW confirms that one or more functions (e.g., configurations) are applicable. For example, the NW can send L1 / L2 / L3 signaling (e.g., RRC messages, MAC CE, DCI) to the UE for deactivation.

[0926] For example, in the (second) configuration, the NW may provide one or more (inferred) configurations as supplements to one or more parameter sets. For example, the (inferred) configuration may include an ID (e.g., container ID) associated with a parameter set. The (inferred) configuration may be associated with an inferred-related parameter set. For example, the (inferred) configuration may include content not associated with the (inferred) configuration (e.g., provided in step 3 and / or included in step 4). The (inferred) configuration may not include content associated with the (inferred) configuration (e.g., provided in step 3 and / or included in step 4). For example, the UE may apply the configuration based on the (inferred) configuration and the inferred-related parameter set associated with the (inferred) configuration. For example, the UE may apply fields and / or parameters in the (inferred) configuration. When indicated by the NW (or in response to an indication from the NW), the UE may apply fields and / or parameters from the inferred-related parameter set associated with the (inferred) configuration. For example, one or more fields and / or parameters may remain empty and / or not provided by the NW (for indication). For example, one or more fields and / or parameters can be set as values ​​(for indication).

[0927] Steps 3, 4, and / or 5 do not need to be in sequence. Steps 3, 4, and / or 5 may not imply that steps 1 and / or 2 must exist. Steps 3, 4, and / or 5 may not imply that previous steps must exist. Steps 3, 4, and / or 5 may not imply that no other signaling exists in between.

[0928] In some examples, the UE may receive one or more inferred configurations (related to AI / ML) in step 3, for example. The UE may then report applicable and / or inapplicable features (related to AI / MI) in step 4, for example. For example, the inferred configurations may be provided in a first list. For example, the inferred configurations may be provided in a second list. For example, the UE may report applicable and / or inapplicable features based on ID.

[0929] Before the UE performs an (initial) suitability report (e.g., step 4), the UE may treat AI / ML-related configurations (e.g., provided in step 3) as inactive / not triggered. The UE may treat the AI / ML-related configuration as inactive / not triggered upon receiving it (e.g., step 3). The UE may evaluate the suitability of the configuration after receiving the inferred configuration (or function) (e.g., step 3).

[0930] For applicable functions, the inferred configuration can be activated / triggered after (and / or in response to) the UE reports that the function is applicable and / or the inferred configuration is not applicable. The UE can report (e.g., a function to be activated / triggered) or the inferred configuration is (or becomes) applicable in the report. The inferred configuration can be activated / triggered when the UE reports that the inferred configuration and / or the corresponding function is (or becomes) applicable. For example, the inferred configuration can be activated / triggered after (and / or in response to) the UE reports applicable and / or inapplicable functions in RRCRecompilationComplete. For example, the inferred configuration can be activated / triggered after (and / or in response to) the UE reports applicable and / or inapplicable functions in UAI. For example, the inferred configuration can be used for periodic reporting, semi-static reporting, and / or non-periodic reporting. For example, the inferred configuration can remain unactivated / triggered until a function (e.g., a configuration) becomes applicable. For example, the inferred configuration can remain unactivated / triggered until the UE reports that a function (e.g., a configuration) is applicable. For example, inferred configuration may not be activated / triggered until the UE receives a lower-level acknowledgment (ACK) for a report of applicable and / or inapplicable functions via UAI and / or RRCReconfigurationComplete (for functions such as configuration). For example, the UE may not consider a function to be applicable and / or inapplicable until it receives a lower-level ACK for a report of applicable and / or inapplicable functions via UAI and / or RRCReconfigurationComplete.

[0931] For inapplicable functions, the inferred configuration may not be activated / triggered, for example, in response to the UE reporting applicable and / or inapplicable functions. The UE may not report (e.g., remain inactive / untriggered) a function or inferred configuration as (becoming) applicable. The UE may report (e.g., remain inactive / untriggered) a function or inferred configuration as inapplicable. For example, the UE may retain the configuration. The UE may treat the configuration as inactive and / or not be activated / triggered by the NW. For example, the UE may retain the configuration. The UE may treat the configuration as activated and / or be activated / triggered by the NW. The UE may discard one or more reports (e.g., when the UE cannot perform inference and / or cannot generate a report (or in response to the UE's inability to perform inference and / or generate a report)). For example, the UE may not retain the configuration (e.g., from the first and / or second lists). The UE may (autonomously) discard (or remove or release) the configuration (e.g., from the first and / or second lists).

[0932] Functions that were previously not considered active and / or could not be activated / triggered by the NW (e.g., configurations) may become active (e.g., after a function is reported as active and / or inactive). For example, a UE may report a function (e.g., configuration) as active (e.g., via UAI) and treat the configuration as active and / or potentially active / triggered. Alternatively, a UE may report a function (e.g., configuration) as active (e.g., via UAI) but treat the configuration as inactive and / or potentially inactive / not triggered unless the function (e.g., configuration) is reconfigured by the NW.

[0933] In some examples, the UE may receive configuration related to AI / ML (e.g., in step 3, in the RRC reconfiguration message). The UE may perform an applicability report (e.g., in step 4, after step 3, in the RRC reconfiguration completion message based on the configuration). The UE may determine whether to retain (or remove / release / discard or apply) the configuration after transmitting an applicability report (or in response to this) based on whether the configuration (or the functionality associated with the configuration) is applicable. The UE may determine whether to retain (or remove / release / discard or apply) the configuration after transmitting an applicability report (or in response to this) based on whether the report (explicitly or implicitly) indicates that the configuration (or the functionality associated with the configuration) is applicable.

[0934] For example, if (at least) the UE indicates that the configuration (or function) is applicable (e.g., in the suitability report, in step 4), the UE may retain and / or apply the configuration (e.g., after transmitting the report or in response to step 4). If (at least) the UE indicates that the configuration (or function) is not applicable (e.g., in the suitability report, in step 4), the UE may discard (or release or remove) the configuration (e.g., after transmitting the report or in response to step 4). If (at least) the UE does not indicate that the configuration (or function) is applicable (e.g., in the suitability report, in step 4), the UE may discard (or release or remove) the configuration (e.g., after transmitting the report or in response to step 4). The suitability report may be included in the configuration response message (e.g., an RRC reconfiguration complete message).

[0935] In some examples, the UE may receive configuration related to AI / ML (e.g., in step 3, in the RRC reconfiguration message). The UE may perform an applicability report (e.g., in step 4, after step 3, based on the configuration, in the RRC reconfiguration complete message). The UE may retain the configuration (and / or may not voluntarily discard / release / remove the configuration) after (or in response to) transmitting the applicability report (e.g., in the RRC reconfiguration complete message). If (at least) the configuration (or associated functionality) is applicable (and / or the report indicates that the configuration or associated functionality is applicable), the UE may apply the configuration after (or in response to) transmitting the applicability report (e.g., in the RRC reconfiguration complete message). If (at least) the configuration (or associated functionality) is not applicable (and / or the report indicates that the configuration or associated functionality is not applicable, and / or the report does not indicate that the configuration or associated functionality is applicable), the UE may not apply the configuration after (or in response to) transmitting the applicability report (e.g., in the RRC reconfiguration complete message). If (at least) a configuration (or associated function) is not applicable (and / or a report indicates that the configuration or associated function is not applicable, and / or a report does not indicate that the configuration or associated function is applicable), the UE may store the configuration after (e.g., in an RRC reconfiguration complete message) is transmitted (or in response to this). When the configuration (or associated function) (e.g., from not applicable) becomes applicable, the UE may execute an applicability report (or initiate UE assistance information) to indicate that the configuration (or associated function) is (or has become) applicable. The UE may apply the configuration after (e.g., in a UE assistance information) is transmitted (or in response to this).

[0936] In some examples, the UE may receive one or more inferred configurations (related to AI / ML) in step 3, for example. The UE may report applicable and / or inapplicable functions (related to AI / MI) based on the configuration after step 3, for example, in step 4. The NW may activate one or more of the configurations after step 4, for example, in step 5. The UE may activate one or more of the configurations indicated by the NW after step 4, for example, in step 5. For example, inferred configurations may be provided in a first list. For example, inferred configurations may be provided in a second list. For example, the UE may report applicable and / or inapplicable functions based on ID. For example, when an inferred configuration is provided in step 3 (or in response to this) and / or after reporting applicable and / or inapplicable functions in step 4, the inferred configuration is not activated / triggered, cannot be activated / triggered, and / or may not be activated / triggered. For example, when the UE receives signaling in step 5 (or in response to receiving signaling in step 5), the inferred configuration may be activated / triggered.

[0937] In some examples, the UE may receive one or more inferred configurations (related to AI / ML) from a second list, for example, in step 3. The UE may then report applicable and / or inapplicable functions (related to AI / MI) based on the configuration, for example, in step 4. The NW may provide one or more inferred configurations (to the UE) from a first list, for example, in step 5, after step 4. For example, the UE may report applicable and / or inapplicable functions based on ID. For example, when an inferred configuration is provided in the first list (or in response to it), the inferred configuration may be activated / triggered.

[0938] In some examples, the UE may receive, for example, one or more inferred configurations and / or one or more inferred-related parameter sets (related to AI / ML) in step 3. The UE may report applicable and / or inapplicable functions based on the (AI / ML related) inferred configurations and / or inferred-related parameter sets after step 3, for example, in step 4. The NW may provide inferred configurations (to the UE) based on the reported applicable and / or inapplicable functions. For example, inferred configurations may be provided in a first and / or second list. For example, inferred-related parameter sets may be provided in a third list. For example, one or more options may be provided for one or more fields and / or parameters in the inferred configurations and / or inferred-related parameter sets. For example, one or more options may be provided for all fields and / or parameters in the inferred configurations and / or inferred-related parameter sets. For example, one or more fields and / or parameters may be missing and / or not provided by the NW. For example, IDs (e.g., container ID, function ID, associated ID) may be included in the report. Each ID may be associated with a function. IDs may or may not be (based on) IDs, configurations, and / or inferred-related parameter sets provided by the NW. For example, one or more reported functions may be inferred configuration and / or inferred related parameter sets. For example, a reported function may be inferred configuration and / or inferred related parameter sets, wherein one or more of the fields and / or parameters include (at least) one value (selected / provided to the UE). For example, a reported function may be inferred configuration and / or inferred related parameter sets, wherein all fields and / or parameters include (at least) one value (selected / provided to the UE).

[0939] In some examples, the UE may receive, for example, one or more inferred configurations and / or one or more inferred parameter sets (related to AI / ML) in step 3. The UE may report applicable and / or inapplicable functions (related to AI / ML) after step 3, for example, in step 4. The NW may provide one or more inferred configurations as a supplement to one or more parameter sets (related to AI / ML) after step 4, for example, in step 5. For example, the inferred configurations in step 3 may be provided in a first and / or second list. For example, the inferred parameter sets may be provided in a third list. For example, the UE may report applicable and / or inapplicable functions based on IDs. For example, the UE may report applicable and / or inapplicable functions based on inferred configurations and / or inferred parameter sets. For example, IDs (e.g., container ID, function ID, associated ID) may be included in the report. For example, one or more inferred configurations in step 5 may supplement one or more configurations and / or inferred parameter sets in step 3. For example, one or more inferred configurations in step 5 may supplement one or more configurations and / or inferred parameter sets in step 4.

[0940] In some examples, the UE may receive, for example, one or more inferred configurations and / or one or more sets of inferred parameters (related to AI / ML) in step 3. The UE may report applicable and / or inapplicable functions and one or more inferred parameters (one or more selected options for the inferred parameters) (for one or more fields and / or parameters) after step 3, for example, in step 4. The NW may provide the inferred configuration (to the UE) based on the reported applicable and / or inapplicable functions. For example, the inferred configuration may be provided in a first and / or second list. For example, the set of inferred parameters may be provided in a third list. For example, one or more options may be provided for one or more fields and / or parameters in the inferred configuration and / or inferred parameter set. For example, one or more options may be provided for all fields and / or parameters in the inferred configuration and / or inferred parameter set. For example, one or more fields and / or parameters may be missing and / or not provided by the NW. For example, the reported function may be based on an ID associated with the function (e.g., CSI-ReportConfigId, container ID, function ID, associated ID). For example, IDs (e.g., container ID, function ID, associated ID) may be included in the report. Each ID can be associated with a function. The ID may or may not be (based on) an ID, configuration, and / or inferred related parameter set provided by the NW. For example, one or more reported functions may be an inferred configuration and / or inferred related parameter set. For example, a reported function may be an inferred configuration and / or inferred related parameter set where one or more fields and / or parameters include (at least) one value (selected / provided to the UE). For example, a reported function may be an inferred configuration and / or inferred related parameter set where all fields and / or parameters include (at least) one value (selected / provided to the UE). For example, a reported function may be an inferred configuration and / or inferred related parameter set where one or more fields and / or parameters include one or more options (selected / provided to the UE). For example, a reported function may be an inferred configuration and / or inferred related parameter set where all fields and / or parameters include one or more options (selected / provided to the UE). For example, the reported options / values ​​may or may not be based on the provided options (e.g., in step 3). The UE may report options / values ​​for one or more fields and / or parameters that the NW does not provide (with options).

[0941] In some examples, one or more configurations can be grouped together. For example, a group may include one or more inferred configurations. For example, a group may include one or more inferred configurations and / or legacy configurations. For example, at least one of the configurations within a group can be activated / triggered (e.g., after the UE reports applicable and / or inapplicable functions). For example, at least one of the configurations within a group can be reported as applicable. Configurations that can be activated / triggered may not include those reported as applicable and / or inapplicable. Configurations that may not be activated / triggered may be reported as applicable. One or more configurations within a group may not be included in the reports of applicable and / or inapplicable functions. When no other configurations (other than those reported as inapplicable) are reported as applicable (or in response to this), a configuration within a group being reported as inapplicable may mean that all configurations within that group (other than legacy configurations) are inapplicable. For example, the UE may indicate in the reports of applicable and / or inapplicable functions whether a configuration can be activated / triggered. For example, one or more flags may be included in the report. Flags may be associated with configurations. When a configuration can be activated / triggered (or in response to a configuration being able to be activated / triggered), the associated flag can be set to a first value (e.g., true). When a configuration can be deactivated / triggered (or in response to a configuration not being activated / triggered), the associated flag can be set to a second value (e.g., false). The flag can be an IE, numeric, integer, enumeration, bit string, or boolean value (presence). For example, a legacy configuration can be activated / triggered when no configuration is reported as applicable (or one or more configurations are reported as inapplicable).

[0942] In some examples, priorities can be assigned to one or more configurations (e.g., those provided in step 3). For example, the provided configuration can be an inferred configuration. For example, the provided configuration can be an inferred configuration and / or a traditional configuration. For example, the provided configuration can be within a configuration group. For example, a first configuration can be activated / triggered, where the first configuration is the highest priority applicable configuration. For example, a second configuration can be maintained but treated as inactive and / or may not be activated / triggered, where the second configuration is not the highest priority applicable configuration (e.g., second highest priority). A configuration can be activated / triggered when it becomes the highest priority applicable configuration (e.g., the first configuration becomes inapplicable and / or is removed / deactivated by the NW). For example, a configuration may not be maintained (e.g., discarded) when it is not the highest priority applicable configuration. For example, the UE can report to the NW the highest priority applicable configuration for an applicable function (e.g., the first configuration). For example, the UE can report to the NW the lowest priority applicable configuration for an inapplicable function. This may mean that all relevant configurations (e.g., within the group) are inapplicable. For example, the UE can report to the NW that the applicable configuration for an applicable function is not the highest priority (e.g., the second configuration). For example, the UE may not report to the NW the applicable configuration that is not the highest priority for the applicable function (e.g., the second configuration).

[0943] In some examples, one or more inference-related parameter sets may be grouped together. For example, a group may include one or more inference-related parameter sets. For example, at least one inference-related parameter set within a group may be reported as applicable and / or inapplicable. One or more inference-related parameter sets within a group may not be included in the reports of applicable and / or inapplicable functions. When no other inference-related parameter set (other than the one reported as inapplicable) is reported as applicable (or in response to this), the fact that an inference-related parameter set within a group is reported as inapplicable may mean that all inference-related parameter sets within that group are inapplicable.

[0944] In some examples, priorities can be assigned to one or more sets of inferred relevant parameters (e.g., those provided in step 3). For example, the provided sets of inferred relevant parameters may be within a group of inferred relevant parameter clusters. For example, the UE may report to the NW the applicable set of inferred relevant parameters with the highest priority for applicable functions. For example, the UE may report to the NW the applicable set of inferred relevant parameters with the lowest priority for inapplicable functions. This may mean that all relevant sets of inferred relevant parameters (e.g., within the group) are inapplicable. For example, the UE may report to the NW the applicable set of inferred relevant parameters with a priority that is not the highest priority for applicable functions. For example, the UE may not report to the NW the applicable set of inferred relevant parameters with a priority that is not the highest priority for applicable functions (e.g., in a second configuration).

[0945] In some examples, the UE can provide preferences for one or more inferred parameters. For example, the UE can provide preferences for one or more sets of inferred parameters (e.g., included in step 4). For example, the UE can provide preferences for one or more sets of inferred parameters within a group (e.g., included in step 4). For example, the UE can provide preferences for one or more options / values ​​for one or more fields and / or parameters within an inferred parameter set (e.g., included in step 4). For example, the UE can provide preferences for one or more inferred configurations (e.g., included in step 4). For example, the UE can provide preferences for one or more inferred configurations within a group (e.g., included in step 4). For example, the UE can provide preferences for one or more options / values ​​for one or more fields and / or parameters within an inferred configuration (e.g., included in step 4).

[0946] A scope, some and / or all of the foregoing examples, concepts, techniques and / or embodiments may be formed and / or combined to form new embodiments.

[0947] In some examples, the embodiments disclosed herein may be implemented independently and / or separately. Alternatively and / or additionally, combinations of the embodiments described herein may be implemented. Alternatively and / or additionally, combinations of the embodiments described herein may be implemented in parallel and / or simultaneously.

[0948] The various techniques, embodiments, methods, and / or alternatives disclosed herein can be performed independently and / or separately. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be combined and / or implemented using a single system. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be implemented in parallel and / or simultaneously.

[0949] Figure 11 This is a flowchart 1100 from the UE's perspective, according to an exemplary embodiment. In step 1105, the UE receives one or more first configurations from the NW. In step 1110, the UE discards and / or does not follow one or more second configurations from the one or more configurations.

[0950] In one embodiment, one or more first configurations may be associated with inference of AI / ML functions.

[0951] In one embodiment, one or more second configurations that the UE discards and / or does not follow are not applicable. For example, based on the determination that one or more second configurations are not applicable, the UE may discard and / or not follow one or more second configurations (e.g., the UE may not perform inference operations based on one or more second configurations).

[0952] In one embodiment, a UE not following a configuration includes periodic reports of UE not activating (and / or not being able to activate) (e.g., associated with the configuration), semi-static reports of UE not activating (and / or not being able to activate) (e.g., associated with the configuration), non-periodic reports of UE not triggering (and / or not being able to trigger) (e.g., associated with the configuration), and / or reports of UE discarding (e.g., associated with the configuration).

[0953] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive one or more first configurations from the NW, and (ii) discard and / or not follow one or more second configurations from the one or more configurations. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0954] Figure 12 This is a flowchart 1200 from the perspective of the UE, according to an exemplary embodiment. In step 1205, the UE receives one or more configurations related to inference from the NW. In step 1210, the UE follows one or more configurations until the NW confirms whether the one or more configurations are applicable to the UE. For example, the UE can perform one or more inference operations based on one or more configurations, at least until the NW confirms whether the one or more configurations are applicable to the UE.

[0955] In some examples, in response to the NW confirming that a configuration in one or more configurations applies to the UE (e.g., the NW can confirm that the configuration applies to the UE by transmitting an indication to the UE that the configuration applies to the UE), the UE can continue to follow the configuration (e.g., the UE can perform one or more inferred operations based on the configuration). In some examples, in response to the NW confirming that a configuration in one or more configurations does not apply to the UE (e.g., the NW can confirm that the configuration does not apply to the UE by transmitting an indication to the UE that the configuration does not apply to the UE), the UE can stop following the configuration (e.g., the UE can stop performing one or more inferred operations based on the configuration).

[0956] In one embodiment, the UE follows one or more configurations (and / or continues to follow one or more configurations) based on receiving an ACK (e.g., from the NW).

[0957] In one embodiment, the UE reports one or more applicable functions and / or one or more non-applicable functions via UAI.

[0958] In one embodiment, the UE reports one or more applicable functions and / or one or more non-applicable functions via RRCReconfigurationComplete.

[0959] In one embodiment, the UE follows one or more configurations including UE activation (and / or ability to activate) periodic reports (e.g., associated with the configuration), UE activation (and / or ability to activate) semi-static reports (e.g., associated with the configuration), UE triggering (and / or ability to trigger) non-periodic reports (e.g., associated with the configuration), and / or UE sending reports (e.g., associated with the configuration).

[0960] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. The CPU 308 can execute program code 312 to enable the UE to (i) receive one or more configurations related to inference from the NW, and (ii) follow one or more configurations until the NW confirms that the one or more configurations are applicable to the UE. Furthermore, the CPU 308 can execute program code 312 to perform one, some, and / or all of the aforementioned actions and steps and / or other actions and steps described herein.

[0961] Figure 13 This is a flowchart 1300 from the UE's perspective according to an exemplary embodiment. In step 1305, the UE receives one or more first configurations related to the inference from the NW. In step 1310, the UE transmits an suitability report to the NW indicating one or more applicable functions and / or one or more inapplicable functions (e.g., to report one or more applicable functions and / or one or more inapplicable functions to the NW). For example, one or more applicable functions may indicate (and / or be used to determine) one or more second configurations applicable to the UE in one or more first configurations. One or more inapplicable functions may indicate (and / or be used to determine) one or more third configurations not applicable to the UE in one or more first configurations. In step 1315, the UE receives a message transmitted by the NW in response to the suitability report, wherein the message is based on one or more configurations and / or indicates one or more activations of one or more fourth configurations in one or more first configurations (and / or indicates one or more allowances for triggering one or more fourth configurations in one or more first configurations). In some examples, one or more fourth configurations may include one, some, or all of the one or more second configurations applicable to the UE reported by the UE.

[0962] Return to reference Figure 3 and 4In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive one or more first configurations related to inference from the NW, (ii) transmit an applicability report to the NW indicating one or more applicable functions and / or one or more inapplicable functions, and (iii) receive a message transmitted by the NW in response to the applicability report, wherein the message is based on one or more configurations and / or indicates one or more activations of one or more of the one or more first configurations (and / or indicates one or more permissions for triggering one or more of the one or more first configurations). Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0963] Figure 14 This is a flowchart 1400 from the perspective of the UE, according to an exemplary embodiment. In step 1405, the UE receives one or more first configurations related to inference from a first list from the NW. In step 1410, the UE transmits an applicability report to the NW indicating one or more applicable functions and / or one or more inapplicable functions (e.g., to report one or more applicable functions and / or one or more inapplicable functions to the NW). For example, one or more applicable functions may indicate (and / or be used to determine) one or more second configurations applicable to the UE from one or more first configurations. One or more inapplicable functions may indicate (and / or be used to determine) one or more third configurations not applicable to the UE from one or more first configurations. In step 1415, the UE receives one or more fourth configurations related to inference from a second list from the NW.

[0964] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive one or more configurations related to inference from a first list from the NW, (ii) transmit an applicability report to the NW indicating one or more applicable functions and / or one or more inapplicable functions, and (iii) receive one or more configurations related to inference from a second list from the NW. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0965] Figure 15This is a flowchart 1500 from the perspective of the UE, according to an exemplary embodiment. In step 1505, the UE receives from the NW one or more first configurations and / or one or more sets of first inference-related parameters related to inference. In step 1510, the UE transmits an applicability report to the NW indicating one or more applicable functions and / or one or more inapplicable functions (e.g., to report one or more applicable functions and / or one or more inapplicable functions to the NW). For example, one or more applicable functions may indicate (and / or be used to determine) one or more second configurations applicable to the UE in one or more first configurations. Alternatively and / or additionally, one or more applicable functions may indicate (and / or be used to determine) one or more sets of second inference-related parameters applicable to the UE in one or more sets of first inference-related parameters. One or more inapplicable functions may indicate (and / or be used to determine) one or more third configurations not applicable to the UE in one or more first configurations. Alternatively and / or additionally, one or more inapplicable functions may indicate (and / or be used to determine) one or more sets of third inference-related parameters not applicable to the UE in one or more sets of first inference-related parameters. In step 1515, the UE receives configurations from the NW as supplements to one or more first configurations and / or one or more sets of first inference-related parameters.

[0966] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive from the NW one or more first configurations and / or one or more sets of first inference-related parameters related to inference, (ii) transmit to the NW an applicability report indicating one or more applicable functions and / or one or more inapplicable functions, and (iii) receive configurations from the NW as supplements to one or more first configurations and / or one or more sets of first inference-related parameters. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0967] Figure 16This is a flowchart 1600 from the perspective of the UE, according to an exemplary embodiment. In step 1605, the UE receives from the NW one or more first configurations and / or one or more sets of first inference-related parameters related to inference. In step 1610, the UE receives from the NW one or more options containing one or more fields and / or one or more parameters in one or more first configurations and / or one or more sets of first inference-related parameters. For example, one or more options may include potential values ​​(e.g., beam count, prediction window, etc.) of one or more fields and / or one or more parameters in one or more first configurations and / or one or more sets of first inference-related parameters. In step 1615, the UE transmits a report to the NW, the report including content indicating (e.g., one or more applicable configurations in one or more first configurations), (e.g., one or more inapplicable configurations in one or more first configurations), (e.g., one or more applicable sets of inference-related parameters in one or more sets of first inference-related parameters), and / or (e.g., one or more inapplicable sets of inference-related parameters in one or more sets of first inference-related parameters). In some examples, the UE may generate a report (and / or determine which configurations and / or inference-related parameter sets are applicable and / or inapplicable) based on one or more options, one or more first configurations, and / or one or more first inference-related parameter sets. In step 1620, the UE receives one or more second configurations related to the inference from the NW. For example, the NW may determine one or more second configurations based on the report. The one or more second configurations may include one or more updated inference configurations for the UE to use to perform the inference. Alternatively and / or additionally, the NW may instruct the UE to activate (e.g., one or more first configurations) one or more second configurations based on the report.

[0968] In one embodiment, one or more options are provided to the UE explicitly or implicitly. For example, the NW can explicitly provide a first option of one or more options to the UE by directly including an indication of a first option in a field of a message transmitted to the UE. The NW can implicitly provide a second option of one or more options to the UE by omitting a field in a message transmitted to the UE, providing an empty entry in a field, setting a field to "unspecified", etc., in a manner that can be interpreted by the UE (e.g., based on one or more predefined rules) as indicating a second option.

[0969] In one embodiment, the UE reports to the NW one or more configurations (e.g., in one or more first configurations) and / or one or more inference-related parameter sets (e.g., in one or more first inference-related parameter sets).

[0970] In one embodiment, the UE reports to the NW one or more second options for one or more fields in one or more configurations and / or one or more fields in one or more inferred parameter sets. For example, the report may include one or more second options. In some examples, the UE may select one or more second options from one or more options provided by the NW.

[0971] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive from NW one or more first configurations and / or one or more first inference-related parameter sets associated with inference, (ii) receive from NW one or more options including one or more fields and / or one or more parameters in one or more first configurations and / or one or more first inference-related parameter sets, (iii) transmit a report to NW including content indicating one or more applicable configurations, one or more inapplicable configurations, one or more applicable inference-related parameter sets and / or one or more inapplicable inference-related parameter sets, and (iv) receive from NW one or more second configurations associated with inference. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0972] Figure 17 This is a flowchart 1700 from the UE's perspective, according to an exemplary embodiment. In step 1705, the UE groups one or more first configurations and / or one or more first inferred related parameter sets into a first group. In some examples, the UE groups one or more first configurations and / or one or more first inferred related parameter sets into a first group based on grouping information received from the NW. Alternatively and / or additionally, the NW may group one or more first configurations and / or one or more first inferred related parameter sets into a first group and / or transmit an indication of the first group to the UE. In some examples, one or more first configurations and / or one or more first inferred related parameter sets may be grouped into a first group based on one or more first configurations and / or one or more first inferred related parameter sets sharing a first function and / or sharing a first inference model (e.g., by the UE and / or the NW).

[0973] In some examples, the UE groups one or more second configurations and / or one or more second inferred related parameter sets into a second group. In some examples, the UE groups one or more second configurations and / or one or more second inferred related parameter sets into a second group based on grouping information received from the NW. Alternatively and / or additionally, the NW may group one or more second configurations and / or one or more second inferred related parameter sets into a second group and / or transmit an indication of the second group to the UE. In some examples, one or more second configurations and / or one or more second inferred related parameter sets may be grouped into a second group based on one or more second configurations and / or one or more second inferred related parameter sets that share a second function and / or share a second inference model (e.g., by the UE and / or the NW).

[0974] In one embodiment, the UE selects one or more configurations within a group (e.g., a first group and / or a second group) to apply and / or follow. For example, the UE can perform one or more inferred operations based on one or more configurations.

[0975] In one embodiment, the UE selects one or more inferred relevant parameter sets within a group (e.g., a first group and / or a second group) to report (e.g., to the NW). For example, the UE may transmit a report indicating one or more inferred relevant parameter sets (e.g., to the NW).

[0976] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to group one or more first configurations and / or one or more first inferred related parameter sets into a first group. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0977] Figure 18 This is a flowchart 1800 from the perspective of the NW according to an exemplary embodiment. In step 1805, the NW provides the UE with one or more first configurations and / or one or more first priorities of one or more first inferred related parameter sets. In step 1810, the NW provides the UE with one or more configurations (e.g., in one or more first configurations) and / or one or more parameters within one or more inferred related parameter sets (e.g., in one or more first inferred related parameter sets) and one or more second priorities.

[0978] In one embodiment, the UE applies one or more of the highest priority configurations among one or more first configurations (e.g., one or more configurations among one or more first configurations that are associated with one or more of the highest priority among one or more first priorities).

[0979] In one embodiment, the UE includes one or more lowest-priority configurations (e.g., one or more configurations among one or more first configurations associated with one or more lowest priorities among one or more first priorities) and / or the lowest-priority inferred related parameter set (e.g., one or more inferred related parameter sets among one or more first inferred related parameter sets associated with one or more lowest priorities among one or more first priorities) in the report of inapplicable functions. The UE may transmit the report of inapplicable functions to the NW.

[0980] In one embodiment, the UE includes one or more highest-priority applicable configurations (e.g., one or more first configurations applicable to the UE and / or one or more configurations associated with one or more of the highest priorities among one or more first priorities) and / or the highest-priority applicable inferred related parameter set (e.g., one or more first inferred related parameter sets applicable to the UE and / or one or more inferred related parameter sets associated with one or more of the highest priorities among one or more first priorities) in the applicable function report. The UE may transmit the applicable function report to the NW.

[0981] In one embodiment, the UE applies one or more configurations in a first configuration based on one or more parameters of the highest priority among the following (e.g., one or more parameters associated with one or more highest priorities in one or more second priority sets): (i) parameters associated with one or more configurations (in one or more first configurations) applicable to the UE (e.g., implementable by the UE and / or compatible with the UE), and / or (ii) parameters associated with one or more sets of inferred related parameters (in one or more first inferred related parameter sets) applicable to the UE (e.g., implementable by the UE and / or compatible with the UE).

[0982] In one embodiment, the UE includes a configuration and / or inferred related parameter set in the report of applicable functions, the configuration and / or inferred related parameter set including one or more parameters of the highest priority among the following (e.g., one or more parameters associated with one or more highest priorities in one or more second priority sets): i) parameters associated with one or more configurations applicable to the UE (e.g., implementable by the UE and / or compatible with the UE) (in one or more first configurations), and / or (ii) parameters associated with one or more inferred related parameter sets applicable to the UE (e.g., implementable by the UE and / or compatible with the UE) (in one or more first inferred related parameter sets).

[0983] In one embodiment, the UE includes a configuration and / or inferred related parameter set in the report of inapplicable functions, the configuration and / or inferred related parameter set including one or more parameters of the lowest priority among the following (e.g., one or more parameters associated with one or more lowest priorities in one or more second priorities): i) parameters associated with one or more configurations (in one or more first configurations), and / or (ii) parameters associated with one or more inferred related parameter sets (in one or more first inferred related parameter sets).

[0984] In one embodiment, one or more first configurations and / or one or more first inferred related parameter sets are grouped together. One or more first configurations and / or one or more first inferred related parameter sets may be grouped by the NW and / or UE.

[0985] Return to reference Figure 3 and 4 In one exemplary embodiment of the NW, device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the NW to (i) provide the UE with one or more first configurations and / or one or more first inferred related parameter sets with one or more first priorities, and (ii) provide the UE with one or more configurations and / or one or more parameters within one or more inferred related parameter sets with one or more second priorities. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0986] Figure 19This is a flowchart 1900 from the perspective of the UE, according to an exemplary embodiment. In step 1905, the UE provides a first preference for one or more first configurations and / or one or more first inferred related parameter sets. For example, the UE may transmit the first preference to the NW. In step 1910, the UE provides a preference for one or more configurations (e.g., in one or more first configurations) and / or one or more parameters within one or more inferred related parameter sets (e.g., in one or more first inferred related parameter sets). For example, the UE may transmit a second preference to the NW.

[0987] In one embodiment, the UE provides a first preference and / or a second preference in the report of applicable functions and / or in the report of inapplicable functions (and / or in the reports of applicable and inapplicable functions). For example, the UE may include the first preference and / or the second preference in the report of applicable functions and / or in the report of inapplicable functions (and / or in the reports of applicable and inapplicable functions), and / or may transmit the reports of applicable functions and / or inapplicable functions (and / or in the reports of applicable and inapplicable functions) to the NW.

[0988] In one embodiment, one or more parameters include (e.g., in one or more first configurations) configurations and / or (e.g., in one or more first inference-related parameter sets) values ​​and / or options within parameters and / or fields in the inference-related parameter set.

[0989] In one embodiment, one or more first configurations and / or one or more first inferred related parameter sets are grouped together. One or more first configurations and / or one or more first inferred related parameter sets may be grouped by the NW and / or UE.

[0990] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) provide a first preference for one or more first configurations and / or one or more first inferred related parameter sets, and (ii) provide a second preference for one or more parameters within one or more configurations and / or one or more inferred related parameter sets. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[0991] Figure 20This is a flowchart 2000 from the perspective of the UE, according to an exemplary embodiment. In step 2005, the UE receives one or more configurations (e.g., one or more configurations on which the UE performs an suitability report). For example, the UE may receive one or more configurations from the network. In step 2010, the UE reports a single list of entries containing suitability information for one or more configurations (e.g., a suitability report). For example, the UE may transmit the single list of entries to the network (e.g., to report suitability information for one or more configurations to the network). Each entry in the single list of entries may include an identifier (ID) and a flag (and / or other information besides the ID and flag). The flag may indicate the suitability status of the configuration associated with the ID in one or more configurations. The ID is a first type of ID indicating an inferred configuration for a first function, a second type of ID indicating an inferred set of related parameters for a second function, and / or a third type of ID (CSI report configuration ID) corresponding to CSI-ReportConfigId.

[0992] In some examples, the set of inference-related parameters for the second function may include an associated ID, a CSI resource configuration ID for measurement, a CSI resource configuration ID for prediction, information related to reporting (e.g., number of reports, PUCCH resources, etc.), time-related information for measurement (e.g., a measurement window (e.g., maximum measurement window) that may be in units of at least one of time slots, ms, time, duration, etc., the number of instances to be measured (e.g., the maximum number of instances to be measured), one or more measurements and / or one or more offsets of one or more measurement windows), time-related information for prediction (e.g., a prediction window (e.g., maximum prediction window) that may be in units of at least one of time slots, ms, time, duration, etc., the number of instances to be predicted (e.g., the maximum number of instances to be predicted), one or more predictions and / or one or more offsets of one or more prediction windows), information for beam management, one or more relationships between beams for measurement (e.g., the number of beams to be measured, the number of beams to be predicted, etc.), and / or one or more other parameters.

[0993] In one embodiment, the UE performs an inference operation after reporting a single list of entries (e.g., in response to this). In some examples, the inference operation may include determining one or more inputs (e.g., measurements, CSI, beam data, mobility information), generating a prediction using AI and / or ML models, and / or using (and / or reporting) the prediction. In some examples, AI and / or ML models to generate predictions may be stored and / or executed on the UE and / or nodes (e.g., network, server, network edge, etc.).

[0994] For example, the inference operation may include beam management inference operations. One or more inputs may include one or more measurements associated with a set of beams (e.g., measurements of one or more resources corresponding to a set of beams), and / or predictions may indicate one or more selected beams in the set of beams that are expected to provide improved communication performance relative to one or more other beams in the set. Based on the predictions, the UE may report one or more selected beams to the network and / or may utilize one or more of the selected beams for communication.

[0995] Alternatively and / or additionally, the inference operation may include a CSI prediction operation. One or more inputs may include one or more channel measurements (e.g., CSI-RS measurements), and / or the prediction may indicate one or more CSI predictions including one or more future CSI values. Based on the prediction, the UE may perform local channel selection (e.g., based on one or more future CSI values). Alternatively and / or additionally, the UE may report one or more future CSI values ​​to the network.

[0996] Alternatively and / or additionally, the inference operation may include CSI compression. One or more inputs may include one or more channel measurements (e.g., CSI-RS measurements), and / or the AI ​​and / or ML model may generate a compressed CSI representation (e.g., prediction) based on one or more inputs (e.g., one or more channel measurements). The UE may report the compressed CSI representation to the network.

[0997] Alternatively and / or additionally, the inference operation may include mobility inference operations. One or more inputs may include one or more radio measurements associated with the serving cell and / or neighboring cells, and / or predictions may indicate one or more mobility predictions, said one or more mobility predictions including the probability of RLF, the probability of HoF, the expected target cell for handover, the expected serving cell degradation, and / or one or more future measurements of one or more neighboring cells. Based on the predictions, the UE may report one or more mobility predictions to the network, may adjust one or more mobility parameters, and / or may trigger a handover before the expected serving cell degradation is expected to occur.

[0998] In one embodiment, one or more configurations (e.g., received from the network) include one or more (prediction or inference) configurations for one or more (prediction or inference) functions, one or more CSI-ReportConfigs (e.g., CSI reporting configurations) for prediction or inference, and / or one or more prediction or inference-related parameter sets for one or more (prediction or inference) functions.

[0999] In one embodiment, one or more configurations are received (e.g., received from a network) by receiving one or more lists indicating one or more configurations (e.g., one or more lists include one or more configurations).

[1000] In one embodiment, one or more first configurations associated with the same type of ID (e.g., a first type of ID, a second type of ID, or a third type of ID) are included in a list (e.g., a single list) of one or more lists (e.g., received from the network). For example, one, some, and / or all configurations associated with a first type of ID in one or more configurations may be included in a first list (e.g., a single list) of one or more lists (e.g., received from the network). For example, one, some, and / or all configurations associated with a second type of ID in one or more configurations may be included in a second list (e.g., a single list) of one or more lists (e.g., received from the network). For example, one, some, and / or all configurations associated with a third type of ID in one or more configurations may be included in a third list (e.g., a single list) of one or more lists (e.g., received from the network).

[1001] In one embodiment, each ID indicated by a single list of entries is associated with a configuration (e.g., a single configuration) in one or more configurations (e.g., received from the network).

[1002] In one embodiment, a single entry list (e.g., an applicability report) may include multiple types of IDs. For example, the first entry in a single entry list may include a first type of ID, the second entry in a single entry list may include a second type of ID, and / or the third entry in a single entry list may include a third type of ID.

[1003] In one embodiment, a single list of entries is included in the RRCReconfigurationComplete (e.g., an RRC reconfiguration complete message) or the UAI. For example, the UE may transmit an RRCReconfigurationComplete that includes a single list of entries (e.g., to the network). Alternatively and / or additionally, the UE may transmit a UAI that includes a single list of entries (e.g., to the network).

[1004] In one embodiment, the first function includes inferring configuration and / or inferring a set of related parameters.

[1005] In one embodiment, the second function includes inferring configuration and / or inferring a set of related parameters.

[1006] In one embodiment, the suitability state (indicated by a flag) indicates whether the configuration is suitable (e.g., suitable for the UE and / or implementable by the UE) or unsuitable (e.g., not suitable for the UE and / or not implementable by the UE). For example, based on determining that the UE has sufficient processing resources, sufficient memory space, sufficient power availability, one or more required measurement resources, configuration-compatible hardware, configuration-compatible software, configuration-compatible operating system, and / or required models (e.g., AI and / or ML models) to perform configuration-associated AI and / or ML functions (e.g., collecting input, running AI and / or ML models, activating and / or transmitting periodic reports, semi-static reports, and / or non-periodic reports based on the output of AI and / or ML models, etc.), the suitability state can be set to indicate that the configuration is suitable. Alternatively and / or additionally, based on the determination that the UE has insufficient processing resources, memory space, and / or power availability to perform configuration-related AI and / or ML functions (e.g., collecting input, running AI and / or ML models, activating and / or transmitting periodic reports, semi-static reports, and / or non-periodic reports based on the output of AI and / or ML models, etc.), and / or the UE lacks one or more of the required measurement resources, configuration-compatible hardware, configuration-compatible software, configuration-compatible operating system, and / or required models (e.g., AI and / or ML models) to perform configuration-related AI and / or ML functions, the suitability state may be set to indicate that the configuration is unsuitable.

[1007] In some examples, the first entry in a single entry list (e.g., an applicability report) may include an ID indicating a first type of inferred configuration for a first function and a flag indicating that the applicability status of the inferred configuration is applicable, the flag indicating that the inferred configuration for the first function is applicable (e.g., applicable to the UE and / or can be implemented by the UE). For example, after reporting the single entry list (e.g., in response to this), the UE may perform one or more inferred operations based on the inferred configuration for the first function. When the inferred configuration and / or the first function corresponds to a beam management inferred operation, the one or more inferred operations may include a beam management inferred operation. When the inferred configuration and / or the first function corresponds to a CSI prediction operation, the one or more inferred operations may include a CSI prediction operation. When the inferred configuration and / or the first function corresponds to a CSI compression operation, the one or more inferred operations may include a CSI compression operation. When the inferred configuration and / or the first function corresponds to a mobility inferred operation, the one or more inferred operations may include a mobility inferred operation. In some examples, a first entry including a flag indicating that the applicability status of the inferred configuration is inapplicable may indicate that the inferred configuration for the first function is inapplicable (e.g., not applicable to the UE and / or cannot be implemented by the UE). For example, after reporting a single list of entries (e.g., in response to this), the UE may perform one or more inference operations (e.g., beam management inference operation, CSI prediction operation, CSI compression operation, mobility inference operation, etc.) without based on the inference configuration used for the first function.

[1008] In some examples, a second entry in a single entry list (e.g., an applicability report) may include an ID indicating a second type of inferred relevant parameter set for a second function and a flag indicating that the applicability status of the inferred relevant parameter set is applicable (e.g., applicable to the UE and / or implementable by the UE). For example, after reporting a single entry list (e.g., in response to this), the UE may perform one or more inference operations based on the inferred relevant parameter set for the second function. When the inferred relevant parameter set and / or the second function corresponds to a beam management inference operation, one or more inference operations may include a beam management inference operation. When the inferred relevant parameter set and / or the second function corresponds to a CSI prediction operation, one or more inference operations may include a CSI prediction operation. When the inferred relevant parameter set and / or the second function corresponds to a CSI compression operation, one or more inference operations may include a CSI compression operation. When the inferred relevant parameter set and / or the second function corresponds to a mobility inference operation, one or more inference operations may include a mobility inference operation. In some examples, a first entry including a flag indicating that the applicability status of the inferred relevant parameter set is inapplicable can indicate that the inferred relevant parameter set used for the second function is inapplicable (e.g., not applicable to the UE and / or cannot be implemented by the UE). For example, after reporting a single list of entries (e.g., in response to this), the UE may not perform one or more inference operations (e.g., beam management inference operation, CSI prediction operation, CSI compression operation, mobility inference operation, etc.) based on the predicted relevant parameter set used for the second function.

[1009] Return to reference Figure 3 and 4 In one exemplary embodiment of the UE, the device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive one or more configurations, and (ii) report a single entry list containing suitability information for one or more configurations, wherein each entry in the single entry list includes an ID and a flag, the flag indicating the suitability status of the configuration associated with the ID in one or more configurations, and the ID is a first type of ID indicating a predicted configuration for a first function, a second type of ID indicating a predicted set of relevant parameters for a second function, and / or a third type of ID corresponding to CSI-ReportConfigId. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above-described actions and steps and / or other actions and steps described herein.

[1010] Figure 21This is a flowchart 2100 from the UE's perspective, according to an exemplary embodiment. In step 2105, the UE receives one or more first configurations from a first list, including a first configuration associated with a first ID corresponding to a first type. In step 2110, the UE receives one or more second configurations from a second list, including a second configuration associated with a second ID corresponding to a second type, and the first type is different from the second type. In step 2115, the UE reports a single list containing applicability information for the first configuration and applicability information for the second configuration, wherein each entry in the single list includes a first parameter and a second parameter (and / or other information besides the first and second parameters). The first parameter indicates the ID and / or ID type. The second parameter indicates the applicability status of the configuration associated with the ID.

[1011] In one embodiment, after reporting a single list (e.g., in response to this), the UE performs a first prediction operation based on a first configuration. For example, the UE may perform the first prediction operation based on determining that the first configuration is applicable (e.g., applicable to the UE and / or implementable by the UE), where the single list may include an applicability state indicating the applicability of the first configuration. In some examples, the first prediction operation may include determining one or more inputs (e.g., measurements, CSI, beam data, mobility information), generating a prediction using an AI and / or ML model, and / or using (and / or reporting) the prediction. In some examples, the AI ​​and / or ML model to generate the prediction may be stored and / or executed on the UE and / or nodes (e.g., network, server, network edge, etc.).

[1012] For example, the first prediction operation may include beam management prediction operations. One or more inputs may include one or more measurements associated with a set of beams (e.g., measurements of one or more resources corresponding to a set of beams), and / or the prediction may indicate one or more selected beams in the set of beams that are expected to provide improved communication performance relative to one or more other beams in the set. Based on the prediction, the UE may report one or more selected beams to the network and / or may utilize one or more of the selected beams for communication.

[1013] Alternatively and / or additionally, the first prediction operation may include a CSI prediction operation. One or more inputs may include one or more channel measurements (e.g., CSI-RS measurements), and / or the prediction may indicate one or more CSI predictions including one or more future CSI values. Based on the prediction, the UE may perform local channel selection (e.g., based on one or more future CSI values). Alternatively and / or additionally, the UE may report one or more future CSI values ​​to the network.

[1014] Alternatively and / or additionally, the first prediction operation may include a CSI compression operation. One or more inputs may include one or more channel measurements (e.g., CSI-RS measurements), and / or the AI ​​and / or ML model may generate a compressed CSI representation (e.g., a prediction) based on one or more inputs (e.g., one or more channel measurements). The UE may report the compressed CSI representation to the network.

[1015] Alternatively and / or additionally, the first prediction operation may include a mobility prediction operation. One or more inputs may include one or more radio measurements associated with the serving cell and / or neighboring cells, and / or the prediction may indicate one or more mobility predictions, said one or more mobility predictions including the probability of RLF, the probability of HoF, the expected target cell for handover, the expected serving cell degradation, and / or one or more future measurements of one or more neighboring cells. Based on the predictions, the UE may report one or more mobility predictions to the network, may adjust one or more mobility parameters, and / or may trigger a handover before the expected serving cell degradation is expected to occur.

[1016] In one embodiment, after reporting a single list (e.g., in response to this), the UE does not perform a second prediction operation (e.g., beam management prediction operation, CSI prediction operation, CSI compression operation, mobility prediction operation, etc.) based on the second configuration. For example, the UE may determine that the second configuration is inapplicable (e.g., not applicable to the UE and / or cannot be implemented by the UE) and therefore not perform a second prediction operation based on the second configuration, wherein the single list may include an applicability state indicating that the second configuration is inapplicable.

[1017] In one embodiment, the UE generates or transmits a report (in response to the report indicating applicable first configuration applicability information) based on a first predictive operation associated with a first configuration. The report is or includes periodic reports.

[1018] In one embodiment, the UE does not (directly) generate or transmit a report associated with the second configuration (in response to reporting the applicability information of the second configuration).

[1019] In one embodiment, the value of the first ID is the same as the value of the second ID.

[1020] In one embodiment, the value of the first ID is different from the value of the second ID.

[1021] In one embodiment, the first ID (corresponding to the first type) indicates a first prediction configuration for a first function, or the first ID (corresponding to the first type) corresponds to a first CSI-ReportConfigId (e.g., a first CSI report configuration ID). The first CSI-ReportConfigId may indicate a first CSI report configuration for performing beam management prediction operations and / or CSI prediction operations and / or CSI compression operations.

[1022] In one embodiment, the second ID (corresponding to the second type) indicates a second prediction configuration for a second function, the second ID (corresponding to the second type) indicates a prediction-related parameter set for a third function, or the second ID (corresponding to the second type) corresponds to a second CSI-ReportConfigId (e.g., a second CSI report configuration ID). For example, the second CSI-ReportConfigId may indicate a second CSI report configuration for performing beam management prediction operations and / or CSI prediction operations and / or CSI compression operations.

[1023] In one embodiment, the first prediction configuration (for the first function) and / or the second prediction configuration (for the second function) are different from the CSI-ReportConfig associated with the prediction (e.g., the CSI reporting configuration) (e.g., the first prediction configuration and / or the second prediction configuration are different from the CSI reporting configuration that indicates and / or can be used to perform CSI prediction operations and / or CSI compression operations).

[1024] In one embodiment, the first prediction configuration (for the first function) corresponds to the prediction configuration for mobility (e.g., a mobility prediction configuration that indicates and / or can be used to perform mobility prediction operations).

[1025] In one embodiment, the second prediction configuration (for the second function) corresponds to the prediction configuration for mobility (e.g., a mobility prediction configuration that indicates and / or can be used to perform mobility prediction operations).

[1026] In one embodiment, a single list is contained in an RRCReconfigurationComplete (e.g., an RRC reconfiguration complete message) or a UAI. For example, the UE may transmit an RRCReconfigurationComplete that includes a single list. Alternatively and / or additionally, the UE may transmit a UAI that includes a single list (e.g., to the network).

[1027] In one embodiment, the suitability state (indicated by a flag) indicates whether the configuration is suitable (e.g., suitable for the UE and / or implementable by the UE) or unsuitable (e.g., not suitable for the UE and / or not implementable by the UE). For example, based on determining that the UE has sufficient processing resources, sufficient memory space, sufficient power availability, one or more required measurement resources, configuration-compatible hardware, configuration-compatible software, configuration-compatible operating system, and / or required models (e.g., AI and / or ML models) to perform configuration-associated AI and / or ML functions (e.g., collecting input, running AI and / or ML models, activating and / or transmitting periodic reports, semi-static reports, and / or non-periodic reports based on the output of AI and / or ML models, etc.), the suitability state can be set to indicate that the configuration is suitable. Alternatively and / or additionally, based on the determination that the UE has insufficient processing resources, memory space, and / or power availability to perform configuration-related AI and / or ML functions (e.g., collecting input, running AI and / or ML models, activating and / or transmitting periodic reports, semi-static reports, and / or non-periodic reports based on the output of AI and / or ML models, etc.), and / or the UE lacks one or more of the required measurement resources, configuration-compatible hardware, configuration-compatible software, configuration-compatible operating system, and / or required models (e.g., AI and / or ML models) to perform configuration-related AI and / or ML functions, the suitability state may be set to indicate that the configuration is unsuitable.

[1028] In one embodiment, in response to receiving one or more first configurations and one or more second configurations, a single list is reported (e.g., to the network).

[1029] In one embodiment, a single list includes applicability information (e.g., applicability status) for each of one or more first configurations and one or more second configurations. For example, a single list may include multiple entries, including one or more first entries for one or more first configurations and one or more second entries for one or more second configurations. Each of the one or more first entries may include a first parameter (e.g., indicating the ID and / or ID type of the corresponding configuration in one or more first configurations) and / or a second parameter (e.g., indicating the applicability status of the corresponding configuration in one or more first configurations). Each of the one or more second entries may include a first parameter (e.g., indicating the ID and / or ID type of the corresponding configuration in one or more second configurations) and / or a second parameter (e.g., indicating the applicability status of the corresponding configuration in one or more second configurations).

[1030] In one embodiment, a first entry in a single list includes a first parameter indicating a first ID (corresponding to a first type) and a second parameter indicating a first suitability state of a first configuration (as associated with the first ID). Alternatively and / or additionally, the first parameter of the first entry may indicate a first (ID) type of the first ID. In some examples, the first ID and / or first type indicated by the first parameter of the first entry can be used to determine the first configuration. Thus, the first and second parameters of the first entry can be used to determine a first suitability state of the first configuration for the UE. In some examples, the network may determine, based on the first entry, whether it expects the UE to perform a prediction operation according to the first configuration. In some examples, in response to determining that the first configuration is suitable (e.g., suitable for the UE and / or can be implemented by the UE) based on the first entry, the network allocates one or more resources for receiving prediction reports from the UE (e.g., one or more selected beams, compressed CSI representations, one or more future CSI values, one or more mobility predictions, etc.), which are determined via prediction operations performed by the UE according to the first configuration.

[1031] In one embodiment, a second entry in a single list includes a first parameter indicating a second ID (corresponding to a second type) and a second parameter indicating a second suitability state of a second configuration (as associated with the second ID). Alternatively and / or additionally, the first parameter of the second entry may indicate a second (ID) type of the second ID. In some examples, the second ID and / or second type indicated by the first parameter of the second entry can be used to determine the second configuration. Thus, the first and second parameters of the second entry can be used to determine a second suitability state of the second configuration for the UE. In some examples, the network may determine, based on the second entry, whether it expects the UE to perform a prediction operation according to the second configuration. In some examples, in response to determining that the second configuration is suitable (e.g., suitable for the UE and / or can be implemented by the UE) based on the second entry, the network allocates one or more resources for receiving prediction reports from the UE (e.g., one or more selected beams, compressed CSI representations, one or more future CSI values, one or more mobility predictions, etc.), which are determined via prediction operations performed by the UE according to the second configuration.

[1032] In one embodiment, a single list includes multiple IDs corresponding to multiple ID types (e.g., a first type of ID, a second type of ID, a third type of ID, etc.).

[1033] Return to reference Figure 3 and 4In one exemplary embodiment of the UE, device 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive one or more first configurations in a first list, including a first configuration associated with a first ID corresponding to a first type, (ii) receive one or more second configurations in a second list, including a second configuration associated with a second ID corresponding to a second type, and the first type is different from the second type, and (iii) report a single list containing applicability information for the first configuration and applicability information for the second configuration, wherein each entry in the single list includes a first parameter indicating the ID and / or ID type and a second parameter indicating the applicability status of the configuration associated with the ID. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above-described actions and steps and / or other actions and steps described herein.

[1034] A communication device (e.g., UE, base station, network node, etc.) may be provided, wherein the communication device may include control circuitry, a processor mounted in the control circuitry, and / or a memory mounted in the control circuitry and coupled to the processor. The processor may be configured to execute program code stored in the memory to perform... Figure 11-21 The method steps are shown in the diagram. Furthermore, the processor can execute program code to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[1035] A computer-readable medium may be provided. The computer-readable medium may be a non-transitory computer-readable medium. The computer-readable medium may include flash memory devices, hard disks, disks (e.g., magnetic disks and / or optical disks, such as at least one of digital versatile discs (DVDs), compact discs (CDs), etc.), and / or memory semiconductors, such as at least one of static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc. The computer-readable medium may include processor-executable instructions that, when executed, cause execution to... Figure 11-21 The steps of one, some and / or all of the methods shown, and / or one, some and / or all of the foregoing actions and steps and / or other actions and steps described herein.

[1036] It is understood that applying one or more of the techniques proposed herein can produce one or more benefits, including but not limited to improved communication efficiency between devices and / or improved efficiency of the network in configuring AI / ML functions for the UE.

[1037] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be embodied in a wide variety of forms, and any specific structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented using structures, functions, or structures and functions other than or different from one or more of the aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.

[1038] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[1039] Those skilled in the art will further understand that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, designed using source coding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure.

[1040] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented within, or executed by, an integrated circuit (“IC”), an access terminal, or an access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration.

[1041] It should be understood that any specific order or hierarchy of steps in any disclosed process is an instance of a sample method. It should be understood that the specific order or hierarchy of steps in a process can be rearranged based on design preferences while remaining within the scope of this disclosure. The appended method claims present elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[1042] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module (e.g., containing executable instructions and associated data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. The sample storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The sample storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. Alternatively and / or additionally, in some aspects, any suitable computer program product can include a computer-readable medium comprising code relating to one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.

[1043] While the disclosed subject matter has been described in conjunction with various aspects, it should be understood that further modifications can be made to the disclosed subject matter. This application is intended to cover any changes, uses, or adaptations to the disclosed subject matter that generally follow the principles of the disclosed subject matter and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which the disclosed subject matter pertains.

Claims

1. A method for a user equipment, characterized in that, include: Receive one or more configurations; as well as The report contains a single list of entries containing applicability information for the one or more configurations, wherein: Each entry in the single entry list includes an identifier and a flag; The flag indicates the suitability status of the configuration associated with the identifier in one or more configurations; The identifier is at least one of the following: An identifier of the first type indicating the predicted configuration for the first function; A second type of identifier indicating the set of prediction-related parameters used for the second function; or A third type of identifier corresponding to CSI-ReportConfigId.

2. The method according to claim 1, characterized in that, include: The prediction operation is performed after the single list of entries is reported.

3. The method according to claim 1, characterized in that, The one or more configurations include at least one of the following: One or more prediction configurations for one or more functions; One or more CSI-ReportConfigs used for prediction; or One or more sets of prediction-related parameters used for one or more functions.

4. The method according to claim 1, characterized in that: Receiving the one or more configurations includes receiving one or more lists indicating the one or more configurations.

5. The method according to claim 4, characterized in that: One or more first configurations associated with identifiers of the same type in the one or more configurations are included in a single second list in the one or more lists.

6. The method according to claim 1, characterized in that: Each identifier indicated by the single list of entries is associated with a configuration in one or more of the configurations.

7. The method according to claim 1, characterized in that: The list of individual entries includes identifiers of various types.

8. The method according to claim 1, characterized in that: The list of individual entries is contained in RRCReconfigurationComplete or User Equipment Auxiliary Information.

9. The method according to claim 1, characterized in that, At least one of the first function or the second function includes at least one of the following: Predictive configuration; or Predict the relevant parameter set.

10. The method according to claim 1, characterized in that: The applicability status indicates whether the configuration is applicable or not.

11. A method for a user equipment, characterized in that, include: Receive one or more first configurations from a first list, including a first configuration, wherein the first configuration is associated with a first identifier corresponding to a first type; Receive one or more second configurations from a second list, including a second configuration, wherein the second configuration is associated with a second identifier corresponding to a second type, and the first type is different from the second type; as well as The report contains a single list of applicability information for the first configuration and the second configuration, wherein each entry in the single list includes: The first parameter indicates the identifier and the type of the identifier; as well as A second parameter indicating the suitability status of the configuration associated with the identifier.

12. The method according to claim 11, characterized in that, Includes at least one of the following: In response to reporting the suitability information of the first configuration, perform a prediction operation based on the first configuration; or In response to the reporting of the applicability information of the second configuration, no prediction operation is performed based on the second configuration.

13. The method according to claim 12, characterized in that, The user equipment generates or transmits periodic reports based on the prediction operation associated with the first configuration.

14. The method according to claim 11, characterized in that: The value of the first identifier is the same as the value of the second identifier, or The value of the first identifier is different from the value of the second identifier.

15. The method according to claim 11, characterized in that, At least one of the following: The first identifier corresponding to the first type: Indicates the first predictive configuration for the first function; or Corresponding to the first CSI-ReportConfigId; or The second identifier corresponding to the second type: Indicates a second predictive configuration for the second function; Indicates the set of prediction-related parameters used for the third function; or This corresponds to the second CSI-ReportConfigId.

16. The method according to claim 15, characterized in that, At least one of the following: At least one of the first prediction configuration or the second prediction configuration is different from the CSI-ReportConfig associated with the prediction, or At least one of the first prediction configuration or the second prediction configuration corresponds to a prediction configuration for mobility.

17. The method according to claim 11, characterized in that: The single list is contained in RRCReconfigurationComplete or User Equipment Auxiliary Information.

18. The method according to claim 11, characterized in that: The applicability status indicates whether the configuration is applicable or not.

19. The method according to claim 11, characterized in that, At least one of the following: In response to receiving the one or more first configurations and the one or more second configurations, the single list is reported. The single list includes applicability information for each of the one or more first configurations and the one or more second configurations; The first entry in the single list includes a first parameter indicating the first identifier corresponding to the first type and a second parameter indicating the first applicability state of the first configuration; The second entry in the single list includes the first parameter indicating the second identifier corresponding to the second type and the second parameter indicating the second applicability state of the second configuration; or The single list includes multiple identifiers corresponding to various identifier types.

20. A user equipment, characterized in that, include: Control circuit; A processor, which is installed in the control circuit; as well as A memory, mounted in the control circuitry and operatively coupled to the processor, wherein the processor is configured to execute program code stored in the memory to perform operations, including: Receive one or more configurations; and The report contains a single list of entries containing applicability information for the one or more configurations, wherein: Each entry in the single entry list includes an identifier and a flag; The flag indicates the suitability status of the configuration associated with the identifier in one or more configurations; The identifier is at least one of the following: An identifier of the first type indicating the predicted configuration for the first function; A second type of identifier indicating the set of prediction-related parameters used for the second function; or A third type of identifier corresponding to CSI-ReportConfigId.

Images