Determining timing of model operation

Abstract

　A method and apparatus for determining a timing of a model operation is provided. A wireless device transmits applicability information related to an applicable functionality among at least one functionality to a base station, and starts a task related to the applicable functionality upon a confirmation for application information. The method comprises the steps of: receiving, by the wireless device, a configuration related to one or more functionalities from the base station; determining, by the wireless device, an applicability of the at least one functionality among the one or more functionalities; transmitting, by the wireless device, the applicability information related to the applicable functionality among the at least one functionality to the base station; and starting, by the wireless device, the task related to the applicable functionality upon the confirmation for the application information, and the apparatus implements the above method.

Description

DETERMINING TIMING OF MODEL OPERATION

[0001] The present disclosure relates to determining a timing of a model operation.

[0002] 3rd Generation Partnership Project (3GPP) New Radio (NR) targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLLC), etc. The NR shall be inherently forward compatible. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0003] 6G is the successor to 5G cellular technology. 6G networks will be able to use higher frequencies than 5G networks and provide substantially higher capacity and much lower latency. The 6G technology market is expected to facilitate large improvements in the areas of imaging, presence technology and location awareness. Working in conjunction with Artificial Intelligence (AI), the 6G computational infrastructure will be able to identify the best place for computing to occur. This includes decisions about data storage, processing and sharing.

[0004] The integration of Artificial Intelligence and Machine Learning (AI / ML) technologies has emerged as a key enabler for enhanced performance and intelligent network operation in 5G and 6G. AI / ML techniques can be applied to various aspects of wireless communications, including channel state prediction, beam management, positioning accuracy improvement, and / or network optimization. By leveraging AI / ML capabilities, communication systems can achieve improved spectral efficiency, reduced latency, and more adaptive resource management compared to conventional rule-based approaches.

[0005] In recent standardization efforts, particularly within 3GPP and other international standards organizations, there has been growing interest in defining frameworks and procedures for AI / ML-assisted functionalities in radio access networks. These efforts may include specifying how AI / ML models can be trained, deployed, and managed within the network infrastructure and a User Equipment (UE). Various AI / ML use cases have been identified, such as Channel State Information (CSI) feedback enhancement, beam prediction, and positioning refinement, which can potentially provide significant performance gains.

[0006] In wireless communication systems, a User Equipment (UE) performs various types of reporting procedures to provide the network with information necessary for radio resource management, link adaptation, and / or performance optimization. These reporting procedures may generally be categorized into different layers of the protocol stack.

[0007] For conventional periodic Layer 1 (L1) reporting procedures, such as periodic Channel State Information (CSI) reporting, and / or periodic Layer 3 (L3) reporting procedures, such as periodic measurement reports for mobility management, the operational flow is relatively straightforward. Typically, once the UE receives the relevant configuration from the network, the UE may immediately begin performing measurements and transmitting the corresponding reports according to the configured periodicity. The timing and activation of these conventional reporting mechanisms are well-defined, allowing for predictable and deterministic behavior.

[0008] However, with the introduction of Artificial Intelligence and Machine Learning (AI / ML) based functionalities in wireless communication systems, the reporting procedures may become more complex. When reporting operations are associated with or dependent upon AI / ML functionalities, additional procedural steps may need to be performed before the actual measurement and reporting can commence.

[0009] Specifically, for AI / ML-related operations, the UE may need to first execute an applicability reporting procedure to verify whether a particular AI / ML functionality is available and applicable under current conditions. This applicability check may involve assessing various factors such as UE capabilities, current radio conditions, computational resources, model availability, and / or other prerequisites. Only after a functionality has been determined to be applicable should the UE proceed with activation of that functionality.

[0010] However, conventional approaches do not clearly define the precise timing or conditions under which an applicable AI / ML functionality should be activated. This ambiguity may create uncertainty in the operational flow and lead to several problems. For instance, there may be inconsistent interpretations between different UE implementations regarding when activation should occur. The network may also lack clear expectations about when to anticipate the commencement of AI / ML-based measurements or reporting after configuration.

[0011] Furthermore, the unclear activation timing may result in delays or inefficiencies in initiating AI / ML functionalities, potentially degrading the performance benefits that these advanced features are intended to provide. The network may allocate resources or make scheduling decisions based on assumptions about activation timing that do not align with actual UE behavior.

[0012] Therefore, there may be a need for clearly defining the activation timing and procedures for AI / ML functionalities that have been determined to be applicable, thereby enabling more predictable, efficient, and coordinated operation of AI / ML-based reporting procedures in wireless communication systems.

[0013] In an aspect, a method performed by a wireless device is provided. The method comprises transmitting applicability information related to an applicable functionality among at least one functionality to a base station, and starting a task related to the applicable functionality upon a confirmation for the application information.

[0014] In another aspect, an apparatus for implementing the above method is provided.

[0015] The present disclosure may have various advantageous effects.

[0016] For example, by clearly defining the activation timing for AI / ML functionalities, the UE can perform operations at the time points expected by the network, thereby enabling more coordinated and predictable system behavior.

[0017] For example, based on the activation timing which is explicitly specified, both the network and the UE can have aligned expectations regarding when AI / ML-based measurements and reporting procedures should commence. This clarity can reduce ambiguity in implementation, minimize potential discrepancies between different UE behaviors, and allow the network to more accurately schedule resources and make decisions based on reliable assumptions about when AI / ML functionality will become active.

[0018] For example, establishing clear activation criteria can prevent premature or delayed initiation of reporting procedures. For instance, if the UE were to begin reporting before the network starts transmitting RSs or before appropriate measurement conditions are established, the reported values may be unreliable or invalid as they would not be based on proper signal measurements. By defining when the UE should begin periodic CSI reporting operations associated with AI / ML functionalities, the system can ensure that measurements are performed only when valid reference signals are available, thereby improving the accuracy and reliability of the reported information.

[0019] For example, clear activation timing can enhance resource efficiency by preventing unnecessary measurements or reports during periods when the underlying conditions for valid AI / ML operation have not yet been satisfied. This can reduce computational overhead at the UE and signaling overhead in the system.

[0020] For example, the improved coordination between the network and UE regarding activation timing can also facilitate better performance of AI / ML-based features, as the network can be able to optimize transmission parameters, resource allocation, and / or other operational aspects with greater confidence about when AI / ML functionalities will become active and begin providing feedback.

[0021] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0022] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.

[0023] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.

[0024] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.

[0025] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0026] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0027] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.

[0028] FIG. 8 shows an example of applicability status reporting to which implementations of the present disclosure are applied.

[0029] FIG. 9 shows an example of a method performed by a wireless device to which implementations of the present disclosure are applied.

[0030] FIG. 10 shows an example of a method performed by a base station to which implementations of the present disclosure are applied.

[0031] FIG. 11 shows an example of a procedure for periodic CSI reporting to which implementations of the present disclosure are applied.

[0032] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi Carrier Frequency Division Multiple Access (MC-FDMA) system. CDMA may be embodied through radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA may be embodied through radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is a part of a Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in Downlink (DL) and SC-FDMA in Uplink (UL). Evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, 5G New Radio (NR) and / or 6G.

[0033] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0034] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

[0035] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0036] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0037] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0038] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".

[0039] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0040] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0041] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0042] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0043] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.

[0044] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0045] Three main requirement categories for 5G include (1) a category of enhanced Mobile BroadBand (eMBB), (2) a category of massive Machine Type Communication (mMTC), and (3) a category of Ultra-Reliable and Low Latency Communications (URLLC).

[0046] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, Base Stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0047] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0048] The wireless devices 100a to 100f represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet-of-Things (IoT) device 100f, and an Artificial Intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

[0049] In the present disclosure, the wireless devices 100a to 100f may be called User Equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, a slate Personal Computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0050] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V) / Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0051] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or Device-to-Device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, Integrated Access and Backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0052] NR supports multiples numerologies (and / or multiple Sub-Carrier Spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0053] The NR frequency band may be defined as two types of frequency range, i.e., Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter Wave (mmW).

[0054] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0055] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0056] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0057] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include NarrowBand IoT (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate Personal Area Networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

[0058] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.

[0059] In FIG. 2, The first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / parts, and / or modules.

[0060] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and / or one or more antennas 108.

[0061] The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. Additional and / or alternatively, the memory 104 may be placed outside of the processing chip 101.

[0062] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106 and then store information obtained by processing the second information / signals in the memory 104.

[0063] The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a firmware and / or a software code 105 which implements codes, commands, and / or a set of commands that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more protocols. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.

[0064] Herein, the processor 102 and the memory 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0065] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and / or one or more antennas 208.

[0066] The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. Additional and / or alternatively, the memory 204 may be placed outside of the processing chip 201.

[0067] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 106 and then store information obtained by processing the fourth information / signals in the memory 204.

[0068] The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a firmware and / or a software code 205 which implements codes, commands, and / or a set of commands that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more protocols. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.

[0069] Herein, the processor 202 and the memory 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0070] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Unit (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0071] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a memory control processor.

[0072] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cash memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0073] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0074] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208. Additionally and / or alternatively, the one or more transceivers 106 and 206 may include one or more antennas 108 and 208. The one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0075] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202.

[0076] Although not shown in FIG. 2, the wireless devices 100 and 200 may further include additional components. The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, an Input / Output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The additional components 140 may be coupled to the one or more processors 102 and 202 via various technologies, such as a wired or wireless connection.

[0077] In the implementations of the present disclosure, a UE may operate as a transmitting device in UL and as a receiving device in DL. In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

[0078] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

[0079] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.

[0080] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.

[0081] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a Subscriber Identification Module (SIM) card 145, a speaker 146, and a microphone 147.

[0082] The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of DSP, CPU, GPU, a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by QUALCOMM®, EXYNOSTMseries of processors made by SAMSUNG®, A series of processors made by APPLE®, HELIOTMseries of processors made by MEDIATEK®, ATOMTMseries of processors made by INTEL®or a corresponding next generation processor.

[0083] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0084] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

[0085] The power management module 141 manages power for the processor 102 and / or the transceiver 106. The battery 142 supplies power to the power management module 141.

[0086] The display 143 outputs results processed by the processor 102. The keypad 144 receives inputs to be used by the processor 102. The keypad 144 may be shown on the display 143.

[0087] The SIM card 145 is an　integrated circuit　that is intended to　securely store the　International Mobile Subscriber Identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0088] The speaker 146 outputs sound-related results processed by the processor 102. The microphone 147 receives sound-related inputs to be used by the processor 102.

[0089] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0090] In particular, FIG. 4 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 5 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 4, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 5, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a Non-Access Stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an Access Stratum (AS).

[0091] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network Quality of Service (QoS) flows.

[0092] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from Transport Blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through Hybrid Automatic Repeat reQuest (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

[0093] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast Control Channel (BCCH) is a downlink logical channel for broadcasting system control information, Paging Control Channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing Public Warning Service (PWS) broadcasts, Common Control Channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and Dedicated Control Channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated Traffic Channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to Broadcast Channel (BCH); BCCH can be mapped to Downlink Shared Channel (DL-SCH); PCCH can be mapped to Paging Channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to Uplink Shared Channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0094] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0095] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using Robust Header Compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

[0096] In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS Flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

[0097] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5G Core network (5GC) or Next-Generation Radio Access Network (NG-RAN); establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.

[0098] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0099] The frame structure shown in FIG. 6 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., SCS, Transmission Time Interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or Cyclic Prefix (CP)-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).

[0100] Referring to FIG. 6, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a CP. In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing Δf = 2u*15 kHz.

[0101] Table 3 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing Δf = 2u*15 kHz.

[0102] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0103] Table 4 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing Δf = 2u*15 kHz.

[0104] uNslotsymbNframe,uslotNsubframe,uslot212404

[0105] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid ofNsize,ugrid,x*NRBscsubcarriers andNsubframe,usymbOFDM symbols is defined, starting at Common Resource Block (CRB)Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), whereNsize,ugrid,xis the number of Resource Blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system,NRBscis 12 generally. There is one resource grid for a given antenna portp, subcarrier spacing configurationu, and transmission direction (DL or UL). The carrier bandwidthNsize,ugridfor subcarrier spacing configurationuis given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna portpand the subcarrier spacing configurationuis referred to as a Resource Element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an indexkin the frequency domain and an indexlrepresenting a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

[0106] In the 3GPP NR system, RBs are classified into CRBs and Physical Resource Blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configurationu. The center of subcarrier 0 of CRB 0 for subcarrier spacing configurationucoincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a BandWidth Part (BWP) and numbered from 0 toNsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+NsizeBWP,i, whereNsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0107] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL Component Carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

[0108] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of Special Cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For Dual Connectivity (DC) operation, the term SpCell refers to the PCell of the Master Cell Group (MCG) or the Primary SCell (PSCell) of the Secondary Cell Group (SCG). An SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

[0109] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.

[0110] Referring to FIG. 7, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

[0111] In the PHY layer, the uplink transport channels UL-SCH and Random Access Channel (RACH) are mapped to their physical channels Physical Uplink Shared Channel (PUSCH) and Physical Random Access Channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH) and PDSCH, respectively. In the PHY layer, Uplink Control Information (UCI) is mapped to PUCCH, and Downlink Control Information (DCI) is mapped to Physical Downlink Control Channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

[0112] UE procedure for reporting Channel State Information (CSI) is described.

[0113] The procedures on aperiodic CSI reporting may assume that the CSI reporting is triggered by DCI format 0_1, but they equally apply to CSI reporting triggered by DCI format 0_2, by applying the higher layer parameterreportTriggerSizeDCI-0-2instead ofreportTriggerSize. The procedures on aperiodic CSI reporting may assume that the CSI reporting is triggered by DCI format 0_1, but they equally apply to CSI reporting triggered by DCI format 0_3.

[0114] The time and frequency resources that can be used by the UE to report CSI may be controlled by the gNB. CSI may consist of Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-Reference Signal (RS) Resource Indicator (CRI), Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block (SSB) Resource indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), L1-Reference Signal Received Power (RSRP), L1-Signal to interference and Noise Ratio (SINR),CapabilityIndexor Time-Domain Channel Properties (TDCP).

[0115] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR,CapabilityIndex, TDCP, a UE may be configured by higher layers with N≥1CSI-ReportConfigReporting Settings and / or X≥1LTM-CSI-ReportConfigReporting Settings, M≥1CSI-ResourceConfigResource Settings and / or Y≥1LTM-CSI-ResourceConfigResource Settings, and one or two list(s) of trigger states (given by the higher layer parametersCSI-AperiodicTriggerStateListandCSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in CSI-AperiodicTriggerStateListmay contains a list of associatedCSI-ReportConfigsorLTM-CSI-ReportConfigsindicating the Resource Set IDs for channel and optionally for interference where a Resource Set for interference can only be present for a Report Setting given by aCSI-ReportConfigand a trigger state additionally contains one or moreCSI-ReportSubConfigIdif the associatedCSI-ReportConfigconfigured with a list of sub-configurations. Each trigger state inCSI-SemiPersistentOnPUSCH-TriggerStateListmay contain one associatedCSI-ReportConfigorLTM-CSI-ReportConfig, and a trigger state additionally contain one or moreCSI-ReportSubConfigIdif the associatedCSI-ReportConfigis configured with a list of sub-configurations.

[0116] Each Reporting SettingCSI-ReportConfigmay be associated with a single downlink BWP (indicated by higher layer parameterBWP-Id) given in the associatedCSI-ResourceConfigfor channel measurement and contain the parameter(s) for one CSI reporting band: codebook configuration including codebook subset restriction, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configurations, and the CSI-related quantities to be reported by the UE such as LI, L1-RSRP, L1-SINR, CRI, SSBRI,CapabilityIndexand / or TDCP.

[0117] Each Reporting SettingLTM-CSI-ReportConfigmay be associated with anLTM-CSI-ResourceConfigfor channel measurement and contain the parameters(s) for time-domain behavior provided byltm-ReportConfigType, the number of cells and the number of reference signals per candidate cell provided bynrOfReportedCells, andnrOfReportedRS-PerCell, respectively, comprising L1 measurement results associated with current SpCell ifspCellInclusionis configured.

[0118] The time domain behavior of theCSI-ReportConfigmay be indicated by the higher layer parameterreportConfigTypeand can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH' / 'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset may apply in the numerology of the UL BWP in which the CSI report is configured to be transmitted on. The higher layer parameterreportQuantitymay indicate the CSI-related, L1-RSRP-related, L1-SINR-related,CapabilityIndex-related or TDCP-related quantities to report. ThereportFreqConfigurationmay indicate the reporting granularity in the frequency domain, including the CSI reporting band and if PMI / CQI reporting is wideband or sub-band. ThetimeRestrictionForChannelMeasurementsparameter inCSI-ReportConfigmay be configured to enable time domain restriction for channel measurements andtimeRestrictionForInterferenceMeasurementsmay be configured to enable time domain restriction for interference measurements. TheCSI-ReportConfigmay also containCodebookConfig, which contains configuration parameters for Type-I, Type II, Enhanced Type II CSI, Further Enhanced Type II Port Selection, Enhanced Type II for Coherent Joint Transmission (CJT), Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI, or Further Enhanced Type II Port Selection for predicted PMI including codebook subset restriction when applicable, and configurations of group-based reporting. A UE is not expected to be configured with a CSI report setting associated with a dormant DL BWP if thereportConfigTypeis set to 'aperiodic'. ACSI-ReportConfigmay contain a list of sub-configurations, provided by the higher layer parametercsi-ReportSubConfigToAddModList, where each sub-configuration is identified byCSI-ReportSubConfigIdand configured withnzp-CSI-RS-ResourceListwhich corresponds to a list of one or more CSI-RS resources or configured withportSubsetIndicatorwhich corresponds to a CSI-RS antenna port subset, and / or configured withpowerOffsetwhich corresponds to a power offset for PDSCH relative to CSI-RS additional topowerControlOffsetof the CSI-RS resource(s). A UE is not expected to be configured with aCSI-ReportConfigthat contains a mix of sub-configuration(s) each configured withnzp-CSI-RS-ResourceListwhich corresponds to a list of one or more CSI-RS resources and some other sub-configuration(s) each configured withportSubsetIndicatorwhich corresponds to CSI-RS antenna port subset.

[0119] The time domain behavior ofLTM-CSI-ReportConfigmay be indicated by the higher layer parameterltm-ReportConfigTypeand can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH' / 'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset may apply in the numerology of the UL BWP in which the CSI report is configured to be transmitted on.

[0120] Each CSI Resource SettingCSI-ResourceConfigmay contain a configuration of a list of S≥1 CSI Resource Sets (given by higher layer parametercsi-RS-ResourceSetList), where the list is comprised of references to either or both of Non-Zero Power (NZP) CSI-RS resource set(s) and SSB set(s) or the list is comprised of references to CSI-Interference Measurement (IM) resource set(s). Each CSI Resource Setting may be located in the DL BWP identified by the higher layer parameterBWP-id, and all CSI Resource Settings linked to a CSI Report Setting have the same DL BWP.

[0121] The time domain behavior of the CSI-RS resources within a CSI Resource Setting may be indicated by the higher layer parameterresourceTypeand may be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the UE is configured withgroupBasedBeamReporting-r17orgroupBasedBeamReporting-v18, the number of CSI Resource Sets configured may be S=2, otherwise the number of CSI-RS Resource Sets configured may be limited to S=1, except for periodic CSI Resource Settings, when the UE is configured with TDCP reporting, for which the number of CSI-RS Resource Sets in the CSI Resource Setting for channel measurement is KTRS∈{1,2,3} and all the CSI-RS Resource Sets are configured with the higher layer parametertrs-Info. For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset may be given in the numerology of its associated DL BWP, as given byBWP-id. When a UE is configured with multipleCSI-ResourceConfigsconsisting the same NZP CSI-RS resource ID, the same time domain behavior may be configured for theCSI-ResourceConfigs.　When a UE is configured with multiple CSI-ResourceConfigsconsisting the same CSI-IM resource ID, the same time-domain behavior may be configured for theCSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting may have the same time domain behavior.

[0122] The followings may be configured via higher layer signaling for one or more CSI Resource Settings for channel and interference measurement:

[0123] - CSI-IM resource for interference measurement;

[0124] - NZP CSI-RS resource for interference measurement; or

[0125] - NZP CSI-RS resource for channel measurement.

[0126] The UE may assume that the NZP CSI-RS resource(s) for channel measurement and the CSI-IM resource(s) for interference measurement configured for one CSI reporting are resource-wise Quasi-Co-Located (QCL-ed) with respect to 'typeD'. When NZP CSI-RS resource(s) is used for interference measurement, the UE may assume that the NZP CSI-RS resource for channel measurement and the CSI- IM resource or NZP CSI-RS resource(s) for interference measurement configured for one CSI reporting are QCL-ed with respect to 'typeD'.

[0127] For TDCP measurement, one periodic CSI Resource Setting may be configured, and the Resource Setting may be for channel measurement on CSI-RS for tracking.

[0128] For L1-SINR measurement:

[0129] - When one Resource Setting is configured, the Resource Setting (given by higher layer parameterresourcesForChannelMeasurement) may be for channel and interference measurement on NZP CSI-RS for L1-SINR computation. The UE may assume that same 1 port NZP CSI-RS resource(s) with density 3 REs / RB is used for both channel and interference measurements.

[0130] - When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameterresourcesForChannelMeasurement) may be for channel measurement on SSB or NZP CSI-RS and the second one (given by either higher layer parametercsi-IM-ResourcesForInterferenceor higher layer parameternzp-CSI-RS-ResourcesForInterference) may be for interference measurement performed on CSI-IM or on 1 port NZP CSI-RS with density 3 REs / RB, where each SSB or NZP CSI-RS resource for channel measurement is associated with one CSI-IM resource or one NZP CSI-RS resource for interference measurement by the ordering of the SSB or NZP CSI-RS resource for channel measurement and CSI-IM resource or NZP CSI-RS resource for interference measurement in the corresponding resource sets. The number of SSB(s) or CSI-RS resources for channel measurement may equal to the number of CSI-IM resources or the number of NZP CSI-RS resource for interference measurement.

[0131] - The UE may apply the SSB, or 'typeD' RS configured with qcl-Type set to 'typeD' to the NZP CSI-RS resource for channel measurement, as the reference RS for determining 'typeD' assumption for the corresponding　CSI-IM resource or the corresponding NZP CSI-RS resource for interference measurement configured for one CSI reporting.

[0132] - The UE may expect that the NZP CSI-RS resource set for channel measurement and the NZP-CSI-RS resource set for interference measurement, if any, are configured with the higher layer parameter repetition.

[0133] Each LTM CSI Resource SettingLTM-CSI-ResourceConfigmay contains configuration of anLTM-CSI-SSB-ResourceSetwhich comprises of a list of Z≥1 SSB indices (given byltm-CSI-SSB-ResourceList) and a list of ZLTM-CandidateIds(given byltm-CandidateIdList) referring to candidate cells associated with the SSB indices. For each candidate cell, the UE may determine the time domain behavior of anapi SSB fromssb-Periodicityandssb-PositionsInBurstand the frequency domain behavior of a SSB may be determined by the higher layer parameterssubcarrierSpacing,ssbFrequency.

[0134] The UE may calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if reported)

[0135] - LI may be calculated conditioned on the reported CQI, PMI, RI and CRI;

[0136] - CQI may be calculated conditioned on the reported PMI, RI and CRI;

[0137] - PMI may be calculated conditioned on the reported RI and CRI;

[0138] - RI may be calculated conditioned on the reported CRI.

[0139] The Reporting configuration for CSI may be aperiodic (using PUSCH), periodic (using PUCCH) or semi-persistent (using PUCCH, and DCI activated PUSCH). The CSI-RS Resources may be periodic, semi-persistent, or aperiodic.

[0140] For a periodic or semi-persistent CSI report on PUCCH, the periodicity TCSI(measured in slots) and the slot offset Toffsetmay be configured by the higher layer parameterreportSlotConfig. Unless specified otherwise, the UE may transmit the CSI report in frames with System Frame Number (SFN) nfand slot number within the frame ns,fusatisfying

[0141] (Nslotframe,unf+ Ns,fu- Toffset) mod TCSI= 0

[0142] where u is the SCS configuration of the UL BWP the CSI report is transmitted on.

[0143] For semi-persistent or periodic CSI, eachCSI-ReportConfigmay be linked to periodic or semi-persistent Resource Setting(s):

[0144] - When one Resource Setting (given by higher layer parameterresourcesForChannelMeasurement) is configured, the Resource Setting may be for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation.

[0145] - When two Resource Settings are configured, the first Resource Setting (given by higher layer parameterresourcesForChannelMeasurement) may be for channel measurement and the second Resource Setting (given by higher layer parametercsi-IM-ResourcesForInterference) may be used for interference measurement performed on CSI-IM. For L1-SINR computation, the second Resource Setting (given by higher layer parametercsi-IM-ResourcesForInterferenceor higher layer parameternzp-CSI-RS-ResourceForInterference) may be used for interference measurement performed on CSI-IM or on NZP CSI-RS.

[0146] For a UE configured withLTM-CSI-ReportConfig, the aperiodic, semi-persistent or periodic CSI may be associated with one Resource Setting given byltm-ResourcesForChannelMeasurementfor L1-RSRP measurement.

[0147] A UE may be semi-statically configured by higher layers to perform periodic CSI reporting on the PUCCH. A UE may be configured by higher layers for multiple periodic CSI reports corresponding to multiple higher layer configured CSI Reporting Settings, where the associated CSI Resource Settings are higher layer configured. For a Reporting Setting for which theCSI-ReportConfigcontains a list of sub-configurations provided bycsi-ReportSubConfigToAddModList, CSI reporting may be provided for all the sub-configurations in each corresponding reporting instance. Periodic CSI reporting on PUCCH formats 2, 3, 4 may support Type I CSI with wideband granularity.

[0148] A UE may perform semi-persistent CSI reporting on the PUCCH applied starting from the first slot that is after slot n + 3Nslotsubframe,uwhen the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, where u is the SCS configuration for the PUCCH. The activation command will contain one or more Reporting Settings, with or without containing one or more sub-configurations for each Reporting Setting for which theCSI-ReportConfigcontains a list of sub-configurations provided bycsi-ReportSubConfigToAddModList, where the associated CSI Resource Settings are configured. Semi-persistent CSI reporting on the PUCCH may support Type I CSI. Semi-persistent CSI reporting on the PUCCH format 2 may support Type I CSI with wideband frequency granularity. Semi-persistent CSI reporting on PUCCH formats 3 or 4 may support Type I CSI with wideband and sub-band frequency granularities and Type II CSI Part 1.

[0149] When the PUCCH carry Type I CSI with wideband frequency granularity, the CSI payload carried by the PUCCH format 2 and PUCCH formats 3, or 4 may be identical and the same irrespective of RI (if reported), CRI (if reported). ACSI-ReportConfigwithcodebookTypeset to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and N Resource Pairs can be configured with wideband frequency granularity only withcsi-ReportModeset to 'Mode1' and numberOfSingleTRP-CSI-Mode1 set to X=0. For type I CSI sub-band reporting on PUCCH formats 3, or 4, the payload may be split into two parts. The first part may contain RI (if reported), CRI (if reported), CQI for the first codeword. The second part may contain PMI (if reported), LI (if reported) and contains the CQI for the second codeword (if reported) when RI > 4. For a CSI-ReportConfigconfigured with subband reporting,codebookTypeset to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and N Resource Pairs, Part 1 may contain RI(s), CRI(s), CQI(s) for the first codeword and is zero padded to a fixed payload size (if needed). Part 2 may contain the CQI(s) for the second codeword (if reported) when RI is larger than 4, LIs (if reported) and PMI(s). For aCSI-ReportConfigcontaining a list of sub-configurations provided bycsi-ReportSubConfigToAddModList, and configured with subband reporting, for Type I CSI for one or more of the sub-configurations, Part 1 for a sub-configuration may contain corresponding RI (if reported), CRI (if reported), CQI for the first codeword (if reported) and is zero padded to a fixed payload size (if needed). Part 2 for a sub-configuration may contain the corresponding CQI for the second codeword (if reported) when RI is larger than 4, LI (if reported) and PMI (if reported).

[0150] A semi-persistent report carried on the PUCCH formats 3 or 4 may support Type II CSI feedback, but only Part 1 of Type II CSI feedback. Supporting Type II CSI reporting on the PUCCH formats 3 or 4 may be a UE capabilitytype2-SP-CSI-Feedback-LongPUCCH. A Type II CSI report (Part 1 only) carried on PUCCH formats 3 or 4 may be calculated independently of any Type II CSI reports carried on the PUSCH.

[0151] When the UE is configured with CSI Reporting on PUCCH formats 2, 3 or 4, each PUCCH resource may be configured for each candidate UL BWP.

[0152] If the UE is in an active semi-persistent CSI reporting configuration on PUCCH and has not received a deactivation command, the CSI reporting may take place when the BWP in which the reporting is configured to take place is the active BWP, otherwise the CSI reporting is suspended.

[0153] The integration of Artificial Intelligence and Machine Learning (AI / ML) techniques for CSI operations has been under active discussion. AI / ML-based CSI feedback enhancement has been identified as one of the key use cases where AI / ML technologies can be applied to improve system performance.

[0154] AI / ML techniques may be utilized for various CSI-related operations, including CSI prediction, CSI compression, and CSI reconstruction. For instance, AI / ML models may be deployed to predict future channel states based on historical channel measurements, and / or to compress CSI feedback information into a more compact representation that can be transmitted with reduced overhead. The network may then use AI / ML models to reconstruct the full CSI from the compressed feedback.

[0155] AI / ML functionalities for CSI operations may involve procedures such as model delivery, applicability reporting, and activation signaling. The UE may report whether a particular AI / ML functionality is applicable under current conditions, and the network may configure and activate the functionality accordingly. Various signaling mechanisms and reporting formats have been discussed to support AI / ML-enhanced CSI operations.

[0156] FIG. 8 shows an example of applicability status reporting to which implementations of the present disclosure are applied.

[0157] 1. Step 1:

[0158] The network may enquire about the UE capability information.

[0159] 2. Step 2:

[0160] The UE may indicate its supported functionalities to the network.

[0161] For example, the supported functionalities may be indicated viaUECapabilityInformationmessage.

[0162] For example, theUECapabilityInformationmessage may includeaiml-ParametersInformation Element (IE). The IEAIML-Parametersmay be used to convey the capabilities supported by the UE for AI / ML beam management and AI / ML CSI prediction.

[0163] Table 5 shows an example of the IEAIML-Parameters.

[0164] AIML-Parameters-r19 ::= SEQUENCE {applicabilityReportingCSI-r19 ENUMERATED {supported} OPTIONAL,applicabilityReportingOther-r19 ENUMERATED {supported} OPTIONAL,loggedDataCollection-r19 ENUMERATED {supported} OPTIONAL,eventBasedTriggeredDataCollection-r19 ENUMERATED {supported} OPTIONAL,dataThresholdAvailabilityIndication-r19 ENUMERATED {supported} OPTIONAL}-- TAG-AIML-PARAMETERS-STOP-- ASN1STOP

[0165] 3. Step 3:

[0166] The network may provide inference configuration with NW-side additional conditions (e.g., associated ID) and / or inference related parameters configuration to the UE.

[0167] For example, the inference configuration may be provided via CSI report configuration.

[0168] Table 6 shows an example of the inference configuration provided via the CSI report configuration.

[0169] predictionConfiguration-r19 CHOICE {csi-InferencePrediction-r19 ENUMERATED {true},configurationForChannelPrediction-r19 SEQUENCE {resourcesForChannelPrediction-r19 CSI-ResourceConfigId OPTIONAL, -- Need RassociatedIdForChannelPrediction-r19 AssociatedId-r19 OPTIONAL, -- Need RassociatedIdForChannelMeasurement-r19 AssociatedId-r19 OPTIONAL, -- Need RnrofReportedPredicted-RS-r19 ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need RnrofTimeInstance-r19 ENUMERATED {n1, n2, n4, n8} OPTIONAL, -- Need RtimeGap-r19 ENUMERATED {ms10, ms20, ms40, ms80, ms160, spare3, spare2, spare1} OPTIONAL, -- Need R...}},configurationForChannelMonitoring-r19 SEQUENCE {refToPredictionConfig-r19 CSI-ReportConfigId,nrofBeamForMonitoring-r19 ENUMERATED {n1, n2} OPTIONAL, -- Need RnrofTransmissionOccasion-r19 ENUMERATED {n1, n3, n7, n15} OPTIONAL, -- Need RtimeInstanceFor-RS-PAI-r19 ENUMERATED {n1, n2, n8, spare1} OPTIONAL, -- Need RmappingToResourcesForChannelPrediction-r19 BIT STRING (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OPTIONAL, -- Need RtimeInstanceFor-SGCS-r19 ENUMERATED {n1, spare3, spare2, spare1} OPTIONAL, -- Need R...} OPTIONAL, -- Need R

[0170] Referring to Table 6, theresourcesForChannelPredictionfield may indicate resources to be predicted based on measurements performed onresourcesForChannelMeasurement. The UE is not expected to measure the resources to be predicted, unless thereportQuantity-r19is set to 'none-BM-r19'. TheassociatedIdForChannelPredictionfield may indicate that the UE may assume the similar properties of a DL Tx beam or beam set / list associated with the sameassociatedIdForChannelMeasurementor with the sameassociatedIdForChannelPrediction. This field is absent ifresourcesForChannelPredictionis not configured. TheassociatedIdForChannelMeasurementfield may indicate that the UE may assume the similar properties of a DL Tx beam or beam set / list associated with the sameassociatedIdForChannelMeasurementor with the sameassociatedIdForChannelPrediction. This field is absent ifresourcesForChannelPredictionis not configured or ifresourcesForChannelMeasurementis equal to or a subset ofresourcesForChannelPrediction. The fieldrefToPredictionConfigmay indicate the linkedCSI-ReportConfigIdcorresponding to a prediction report configuration. ThemappingToResourcesForChannelPredictionfield, if configured, may indicate the resources included inresourcesForChannelMeasurementto be used for monitoring the channel predictions in the resourcesresourcesForChannelPredictionincluded within the linked prediction report configuration indicated byrefToPredictionConfig.

[0171] For example, the inference related parameters configuration may be provided viaOtherConfig.

[0172] Table 7 shows an example of the inference related parameters configuration provided via theOtherConfig.

[0173] OtherConfig-v1900 ::= SEQUENCE {gapOccasionCancelRatioReportConfig-r19 SetupRelease {GapOccasionCancelRatioReportConfig-r19} OPTIONAL, -- Need Mlpwus-OffsetPreferenceConfig-r19 SetupRelease {LPWUS-OffsetPreferenceConfig-r19} OPTIONAL, -- Need MapplicabilityReportConfig-r19 SetupRelease {ApplicabilityReportConfig-r19} OPTIONAL, -- Need MdataCollectionPreferenceConfig-r19 SetupRelease {DataCollectionPreferenceConfig-r19} OPTIONAL, -- Need MloggedDataCollectionAssistanceConfig-r19 SetupRelease {LoggedDataCollectionAssistanceConfig-r19} OPTIONAL, -- Need Massisted-SSB-MTC-Config SetupRelease {Assisted-SSB-MTC-Config-r19} OPTIONAL -- Need M}ApplicabilityReportConfig-r19 ::= SEQUENCE {reportApplicabilityUAI-r19 ENUMERATED {true} OPTIONAL, -- Need RapplicabilityConfigList-r19 SEQUENCE (SIZE (1..maxNrofServingCells)) OF ApplicabilityConfig-r19 OPTIONAL, -- Need R...}ApplicabilityConfig-r19 ::= SEQUENCE {applicabilityConfigCellId-r19 ServCellIndex OPTIONAL, -- Need RapplicabilitySetConfigList-r19 SEQUENCE (SIZE (1..maxNrofApplicabilitySets-r19)) OF ApplicabilitySetConfig-r19 OPTIONAL, -- Need R...}ApplicabilitySetConfig-r19 ::= SEQUENCE {applicabilitySetConfigId-r19 ApplicabilitySetConfigId-r19 OPTIONAL, -- Need RresourcesForChannelMeasurement CSI-ResourceConfigId OPTIONAL, -- Need RresourcesForChannelPrediction-r19 CSI-ResourceConfigId OPTIONAL, -- Need RassociatedIdForChannelMeasurement-r19 AssociatedId-r19 OPTIONAL, -- Need RassociatedIdForChannelPrediction-r19 AssociatedId-r19 OPTIONAL, -- Need RreportQuantity-r19 CHOICE {none-BM-r19 NULL,none-CSI-r19 NULL,p-CRI-r19 NULL,p-SSB-Index-r19 NULL,p-CRI-RSRP-r19 NULL,p-SSB-Index-RSRP-r19 NULL,rs-PAI-r19 NULL,sgcs-r19 NULL} OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},...

[0174] Referring to Table 7, the fieldapplicabilityReportConfigmay correspond to a configuration for the UE to indicate the applicability of configurations subject to the applicability determination procedure. The fieldapplicabilitySetConfigListmay indicate for each serving cell the list of sets of prediction related parameters configured for UE applicability reporting.

[0175] 4. Step 4:

[0176] The UE may determine the applicable AI / ML functionalities based on at least one of NW-side additional conditions (if provided), UE-side additional conditions (internally known by UE) or model availability in the UE. The UE may report its functionality applicability to the network.

[0177] For example, applicability reporting may be transmitted via theRRCReconfigurationCompletemessage.

[0178] Table 8 shows an example of the applicability reporting transmitted via theRRCReconfigurationCompletemessage.

[0179] RRCReconfigurationComplete-v1900-IEs ::= SEQUENCE {applicabilityReportList-r19 ApplicabilityReportList-r19 OPTIONAL,csi-LogMeasAvailable-r19 ENUMERATED {true} OPTIONAL,referenceLocationReport-r19 BIT STRING (SIZE (6)) OPTIONAL,nonCriticalExtension SEQUENCE {} OPTIONAL}

[0180] Referring to Table 8, the fieldapplicabilityReportListmay correspond to the applicability reports related to prediction configurations and sets of parameters for prediction configurations.

[0181] 5. Step 5: RRC Reconfiguration

[0182] Based on the applicability reporting, the network may provide inference configuration.

[0183] 6. Step 6: Activation / Deactivation / Inference / Monitoring

[0184] When the inference configuration consists of periodic CSI report configuration, upon reporting the applicable functionalities, the UE may autonomously activate the applicable AI / ML functionalities. When the inference configuration consists with semi-persistent CSI and / or aperiodic CSI report configuration, upon reporting the applicable AI / ML functionalities, applicable AI / ML functionality activation can be activated by MAC Control Element (CE) / DCI and aperiodic CSI reporting can be activated by DCI.

[0185] When the network enables applicability reporting viaOtherConfig, and applicability of the functionality changes, the UE can report updated functionality applicability status inUEAssistanceInformationmessage. When an activated AI / ML functionality becomes inapplicable, the UE may not autonomously deactivate it, but the UE may indicate to the network the change in the applicability. Upon reception of UE indication of the functionality becoming inapplicable, the network should deactivate or release this activated functionality.

[0186] Upon receiving one or more inference configuration(s), the UE may maintain all the inference configuration(s) no matter the inference configuration is applicable or inapplicable until the network releases it.

[0187] For NW-side model, the CSI measurement and reporting may be used to acquire input data for inference.

[0188] For NW-side model, the gNB may be responsible for performance monitoring (i.e., calculates performance metrics). There may be no additional impacts on the UE for monitoring and management, except for being configured to provide the required measurement / data. Additionally, the UE may not be informed about any gNB-side management decision.

[0189] For UE-side model, the network may initiate performance monitoring, and make management decisions based on the performance monitoring results. The UE can be configured to send either the measurement reports or the calculated performance metrics.

[0190] As mentioned above, beam-level measurement prediction has been under discussion. This approach may reduce the need for measurements in the spatial domain and enable proactive beam management by utilizing temporal prediction in advance. The UE may report predictive measurement results via the CSI reporting. Aperiodic and semi-persistent CSI reporting can be activated through a network command via MAC CE or DCI. In contrast, periodic CSI reporting may start when the UE receives the corresponding CSI reporting configuration.

[0191] However, referring to FIG. 8, the applicable functionality reporting (i.e., step 4) may precede the activation of CSI reporting (i.e., step 6). That is, the applicable functionality may be considered as activated only if the applicable functionality reporting of the applicable functionality is reported. For example, the applicable periodic CSI reporting may be considered as activated only if the applicability of the correspondingCSI-ReportConfigis reported in theRRCReconfigurationComplete (step 4).

[0192] In the case of periodic CSI reporting, if only a part of the configured CSI report configuration is applicable, transmitting all RSs related to the configured CSI report configuration may be wasteful. Therefore, the network may transmit only the applicable RSs (e.g., CSI-RS). For example, the network may start transmitting the RSs after receiving the applicable functionality reporting from the UE.

[0193] However, considering the time required for the network to start transmitting the relevant RSs after receiving the applicable functionality reporting from the UE, it may be unclear when the UE should begin the periodic CSI reporting. If the UE performs measurement and reporting immediately after sending the applicable functionality reporting, the initial reported values may not be accurate because the network may not have started transmitting the necessary RSs (e.g., CSI-RS) yet. If the UE performs measurement before the network begins transmission, it may report CSI values without valid RSs, leading to inaccurate results.

[0194] For example, conventional approaches do not clearly define the precise timing or conditions under which an applicable AI / ML functionality should be activated. This ambiguity may create uncertainty in the operational flow and lead to several problems. For instance, there may be inconsistent interpretations between different UE implementations regarding when activation should occur. The network may also lack clear expectations about when to anticipate the commencement of AI / ML-based measurements or reporting after configuration.

[0195] For example, the unclear activation timing may result in delays or inefficiencies in initiating AI / ML functionalities, potentially degrading the performance benefits that these advanced features are intended to provide. The network may allocate resources or make scheduling decisions based on assumptions about activation timing that do not align with actual UE behavior.

[0196] Therefore, a clear criterion may be needed to determine when the UE should begin periodic CSI reporting. There may be a need for clearly defining the activation timing and procedures for AI / ML functionalities that have been determined to be applicable, thereby enabling more predictable, efficient, and coordinated operation of AI / ML-based reporting procedures in wireless communication systems.

[0197] To address the problem mentioned above, the present disclosure provides a method for determining the timing of model-related tasks (e.g., training, inference, monitoring, etc.). More specifically, when a UE informs an applicability-related model / function (e.g., applicable functionality reporting) to the network, the UE may start reporting model / function-related tasks (e.g., periodic CSI reporting) upon obtaining a confirmation of the applicability functionality reporting.

[0198] According to implementations of the present disclosure, the confirmation may be explicitly received from the network. The explicit confirmation may include at least one of the followings:

[0199] - Acknowledgement (e.g., RLC acknowledgement)

[0200] - HARQ ACK

[0201] - A command for activation, e.g., via RRC message / MAC CE / DCI

[0202] According to implementations of the present disclosure, the confirmation may be implicitly obtained. The implicit confirmation may include at least one of the followings:

[0203] - Subsequent network operation after applicability reporting, e.g., No Retransmission command for the applicability reporting, UL grant for MAC CE / UCI for reporting for model / functionality related task, (updated) PUCCH / PUSCH configuration, etc.

[0204] - After a certain amount of time since the UE transmitted applicability reporting.

[0205] In the present disclosure, "function", "functionality", "inference function", "model inference function", "AI / ML model inference function", "model", "AI / ML model" may be used interchangeably.

[0206] In the present disclosure, "model", "AI / ML model" may be sub-group of "function", "functionality", "inference function", "model inference function", "AI / ML model inference function". For example, multiple models may belong to and / or may be linked to a specific function.

[0207] The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals / messages / fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.

[0208] An embodiment of the present disclosure related to a specific drawing described below may be combined with various embodiments of the present disclosure related to other drawings, and some descriptions, functions, procedures, proposals, methods and / or operations of the embodiment may be omitted.

[0209] FIG. 9 shows an example of a method performed by a wireless device to which implementations of the present disclosure are applied.

[0210] In step S900, the method comprises receiving a configuration related to one or more functionalities from a base station.

[0211] In step S910, the method comprises determining an applicability of at least one functionality among the one or more functionalities.

[0212] In step S920, the method comprises transmitting applicability information related to an applicable functionality among the at least one functionality to the base station.

[0213] In step S930, the method comprises starting a task related to the applicable functionality upon a confirmation for the application information.

[0214] In some implementations, the method may further comprise determining whether the confirmation is obtained or not.

[0215] In some implementations, the confirmation may be an explicit confirmation received from the base station. For example, the explicit confirmation may include at least one of an acknowledgement for the application information, an HARQ acknowledgement for the application information, or an activation command for the applicable functionality.

[0216] In some implementations, the confirmation may be an implicit confirmation based on a subsequent network operation after transmitting the applicability information. For example, the subsequent network operation may include at least one of i) no retransmission command for the applicability information, ii) a configuration of a UL grant for transmission of a UL signal related to the task, or iii) a configuration of an uplink channel configuration.

[0217] In some implementations, the confirmation may be obtained based on an expiry of a certain amount of time after transmitting the applicability information.

[0218] In some implementations, the task may include at least one of a measurement and reporting related to a CSI, a CSI compression, a measurement and reporting related to an L3 quality, or a measurement and reporting related to a failure.

[0219] In some implementations, the task may be related to at least one of a training, inference or monitoring of the applicable functionality.

[0220] In some implementations, the applicability information may include at least one of an applicability of the applicable functionality, an applicable condition of the applicable functionality, an applicable configuration of the applicable functionality, an updated or changed or reset applicability related information, a preferred configuration for the task, or a reason for applicability of the applicable functionality.

[0221] Furthermore, the wireless device may be implemented by the first wireless device 100 shown in FIG. 2 and / or the UE 100 shown in FIG. 3. The wireless device may be in communication with at least one of a mobile device, a network, and / or autonomous vehicles other than the wireless device.

[0222] The wireless device may comprise at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform the method described in FIG. 9.

[0223] More specifically, the wireless device receives a configuration related to one or more functionalities from a base station.

[0224] The wireless device determines an applicability of at least one functionality among the one or more functionalities.

[0225] The wireless device transmits applicability information related to an applicable functionality among the at least one functionality to the base station.

[0226] The wireless device starts a task related to the applicable functionality upon a confirmation for the application information.

[0227] In some implementations, the wireless device may determine whether the confirmation is obtained or not.

[0228] In some implementations, the confirmation may be an explicit confirmation received from the base station. For example, the explicit confirmation may include at least one of an acknowledgement for the application information, an HARQ acknowledgement for the application information, or an activation command for the applicable functionality.

[0229] In some implementations, the confirmation may be an implicit confirmation based on a subsequent network operation after transmitting the applicability information. For example, the subsequent network operation may include at least one of i) no retransmission command for the applicability information, ii) a configuration of a UL grant for transmission of a UL signal related to the task, or iii) a configuration of an uplink channel configuration.

[0230] In some implementations, the confirmation may be obtained based on an expiry of a certain amount of time after transmitting the applicability information.

[0231] In some implementations, the task may include at least one of a measurement and reporting related to a CSI, a CSI compression, a measurement and reporting related to an L3 quality, or a measurement and reporting related to a failure.

[0232] In some implementations, the task may be related to at least one of a training, inference or monitoring of the applicable functionality.

[0233] In some implementations, the applicability information may include at least one of an applicability of the applicable functionality, an applicable condition of the applicable functionality, an applicable configuration of the applicable functionality, an updated or changed or reset applicability related information, a preferred configuration for the task, or a reason for applicability of the applicable functionality.

[0234] Furthermore, the method described above in FIG. 9 may be performed by control of a processing apparatus. The processing apparatus may be implemented by the processor 102 included in the first wireless device 100 shown in FIG. 2 and / or the processor 102 included in the UE 100 shown in FIG. 3.

[0235] The processing apparatus comprises at least one processor that is integrated with a wireless device, and at least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform the method described in FIG. 9.

[0236] Furthermore, the method described above in FIG. 9 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.

[0237] The technical features of the present disclosure may be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

[0238] Some example of storage medium may be coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For other example, the processor and the storage medium may reside as discrete components.

[0239] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

[0240] For example, non-transitory computer-readable media may include RAM such as Synchronous DRAM (SDRAM), ROM, Non-Volatile RAM (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

[0241] In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0242] According to some implementations of the present disclosure, a non-transitory Computer-Readable Medium (CRM) stores instructions that, based on being executed by at least one processor, perform the method described in FIG. 9.

[0243] FIG. 10 shows an example of a method performed by a base station to which implementations of the present disclosure are applied.

[0244] In step S1000, the method comprises transmitting a configuration related to one or more functionalities to a wireless device.

[0245] In step S1010, the method comprises receiving applicability information related to an applicable functionality among the one or more functionalities from the wireless device. A task related to the applicable functionality is started upon a confirmation for the application information.

[0246] Furthermore, the base station may be implemented by the second wireless device 200 shown in FIG. 2.

[0247] The base station may comprise at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the base station to perform the method described in FIG. 10.

[0248] More specifically, the base station transmits a configuration related to one or more functionalities to a wireless device.

[0249] The base station receives applicability information related to an applicable functionality among the one or more functionalities from the wireless device. A task related to the applicable functionality is started upon a confirmation for the application information.

[0250] FIG. 11 shows an example of a procedure for periodic CSI reporting to which implementations of the present disclosure are applied.

[0251] In step S1100, the network may configure model / functionality-related configuration. For example, the network may configure one or moreCSI-ReportConfigfor inference configuration with periodic CSI reporting to the UE.

[0252] For example, model / functionality-related configuration may include at least one of the following information.

[0253] (1) Model / functionality-related configuration may include information related to model / functionality identification, e.g., model / functionality group ID / group list.

[0254] (2) Model / functionality-related configuration may include model / functionality related parameters.

[0255] For example, in the case of L1 measurement related tasks, such as beam management, CSI feedback, the model / functionality-related configuration may include at least one of the following information.

[0256] - resource related configuration, such as resource / resource set of CSI-RS and SSB

[0257] - report related configuration, such asCSI-ReportConfig

[0258] - report contents related configuration, such as L1-RSRP, beam index, CSI feedback related information (e.g., PMI, RI, CQI, etc)

[0259] - time instance related information, such as time instance for temporal prediction

[0260] For example, in the case of L3 measurement related tasks, such as L3 filtered beam / cell level measurement, the model / functionality-related configuration may include at least one of following:

[0261] - Measurement object related configuration, such as target frequency, sub-carrier spacing, SSB / CSI-RS information for measurement, etc.

[0262] - Report related configuration, such as report condition, report interval, report amount, etc.

[0263] - Report contents related configuration, such as L3 quality (e.g., RSRP, RSRQ, SINR, RSSI, etc.) for a specific beam / cell

[0264] - Time instance related information, such as time instance for temporal prediction

[0265] (3) Additional conditions may be further configured for the model / functionality-related configuration. For example, the model / functionality-related configuration may include the additional conditions. The additional conditions may include conditions under which the UE can perform model / functionality related operations.

[0266] For example, the additional condition may include at least one of the following information.

[0267] - Specific location related information (e.g., polygon type, latitude / longitude, altitude, angle, indoor / outdoor, etc.)

[0268] - Specific time related information (e.g., date, time window, start time, stop time, etc.)

[0269] - Specific speed related information (e.g., 10km / h, 30km / h, 60km / h, 120km / h, etc.)

[0270] - Specific radio quality condition (e.g., RSRP, RSRQ, SINR, etc.)

[0271] - Specific deployment scenario (e.g., Urban Macro (Uma), Urban Micro (UMi), Indoor Hotspot (InH), etc.)

[0272] - Specific cell / frequency related information, (e.g., bandwidth, size of subband, carrier frequency, numerologies, etc.)

[0273] - Specific antenna related information (e.g., antenna port layouts, antenna port numbers, rank numbers / layers, antenna spacing, antenna virtualization, etc.)

[0274] The additional condition may consist of one condition or a combination of several conditions. The additional condition may have a specific condition ID, e.g., associated ID. The additional condition may be linked to a specific functionality / functionality group or a specific model / model group.

[0275] In step S1110, the UE may evaluate the applicability of model / functionality related tasks (e.g., training, inference, monitoring, etc.). The UE may report the applicability-related information (i.e., applicable functionality report) to the network based on the evaluation.

[0276] The UE may evaluate whether at least one model / functionality is applicable based on at least one of the followings.

[0277] - Configured additional conditions from the network

[0278] - UE internal conditions such as internal problems (e.g., memory, battery, thermal, etc.), UE status (e.g., speed, area, etc.)

[0279] - Model availability (e.g., whether the UE has available / applicable model)

[0280] - Configuration for model / functionality related tasks (e.g., training, inference, monitoring, etc.)

[0281] For example, the applicability-related information may include at least one of the following information.

[0282] - Applicability of model / functionality; or

[0283] - No applicability of model / functionality; or

[0284] - Applicable condition / configuration; or

[0285] - Not applicable condition / configuration; or

[0286] - Updated / changed / reset applicability related information; or

[0287] - Applicable / non-applicable CSI reporting configuration / Resource Set / Report Contents / Time instance configuration; or

[0288] - Applicable / non-applicable Measurement object / Report configuration / Report Contents / Time instance configuration;

[0289] For example, the applicability-related information may include a preference for configuration. The preference for configuration may include a preferred configuration for model / functionality related tasks (e.g., training, inference, monitoring, etc.).

[0290] For example, the preferred configuration may include at least one of the followings.

[0291] - Preferred measurement configuration for a certain reference signal / resource set / measurement object

[0292] - Preferred reporting configuration, e.g., the number of reporting contents, reporting interval, etc.

[0293] - Preferred model / functionality related tasks, e.g., time instance for temporal prediction, the number of input / output data, etc.

[0294] - an invalid part of configured configuration

[0295] For example, the applicability-related information may include a reason for applicability / non-applicability. For example, the reason for non-applicability may indicate, e.g., the need of (re)training, invalid configuration, etc.

[0296] The applicability-related information may be transmitted to the network via RRC message (e.g.,RRCReconfigurationComplete,UEAssistanceInformation, etc.), MAC CE, UCI, etc.

[0297] In step S1120, optionally, the network may configureCSI-ReportConfigfor inference configuration.

[0298] In step S1130, the UE may determine a confirmation for the applicability-related information.

[0299] (1) The UE may determine that the confirmation is explicitly received from the network.

[0300] - For example, the UE may receive an PDCP / RLC / RRC / MAC acknowledgement (e.g., RLC acknowledgement for an RRC message)

[0301] - For example, the UE may receive HARQ ACK for a MAC PDU including the applicability-related information.

[0302] - For example, the UE may receive a certain command for activation of model / functionality related task via RRC message / MAC CE / DCI.

[0303] (2) The UE may determine that the confirmation is implicitly obtained.

[0304] - For example, the UE may determine that the confirmation is implicitly obtained when no retransmission command for the applicability-related information is received, e.g., No HARQ retransmission, etc.

[0305] - For example, the UE may determine that the confirmation is implicitly obtained when the UE receives a UL grant for MAC CE / UCI for reporting for model / functionality related task.

[0306] - For example, the UE may determine that the confirmation is implicitly obtained when the UE receives (updated) PUCCH / PUSCH configuration for scheduling.

[0307] - For example, the UE may determine that the confirmation is implicitly obtained after a certain amount of time has passed since the UE transmits the applicability-related information.

[0308] In step S1140, the UE may start / initiate model / functionality related task (e.g., periodic CSI reporting) upon obtaining the confirmation.

[0309] For example, the model / functionality related task may include at least one of the followings.

[0310] - CSI(L1) measurement / reporting for training / inference / monitoring / etc.

[0311] - CSI compression for training / inference / monitoring / etc.

[0312] - L3 measurement / reporting for training / inference / monitoring / etc.

[0313] - Failure related measurement / reporting (e.g., Beam failure, Link failure) for training / inference / monitoring / etc.

[0314] The UE may consider model / functionality related task is activated until the network releases model / functionality related configuration.

[0315] In step S1150, the network may release configuration related to corresponding periodic CSI reporting.

[0316] The present disclosure may have various advantageous effects.

[0317] For example, by clearly defining the activation timing for AI / ML functionalities, the UE can perform operations at the time points expected by the network, thereby enabling more coordinated and predictable system behavior.

[0318] For example, based on the activation timing which is explicitly specified, both the network and the UE can have aligned expectations regarding when AI / ML-based measurements and reporting procedures should commence. This clarity can reduce ambiguity in implementation, minimize potential discrepancies between different UE behaviors, and allow the network to more accurately schedule resources and make decisions based on reliable assumptions about when AI / ML functionality will become active.

[0319] For example, establishing clear activation criteria can prevent premature or delayed initiation of reporting procedures. For instance, if the UE were to begin reporting before the network starts transmitting RSs or before appropriate measurement conditions are established, the reported values may be unreliable or invalid as they would not be based on proper signal measurements. By defining when the UE should begin periodic CSI reporting operations associated with AI / ML functionalities, the system can ensure that measurements are performed only when valid reference signals are available, thereby improving the accuracy and reliability of the reported information.

[0320] For example, clear activation timing can enhance resource efficiency by preventing unnecessary measurements or reports during periods when the underlying conditions for valid AI / ML operation have not yet been satisfied. This can reduce computational overhead at the UE and signaling overhead in the system.

[0321] For example, the improved coordination between the network and UE regarding activation timing can also facilitate better performance of AI / ML-based features, as the network can be able to optimize transmission parameters, resource allocation, and / or other operational aspects with greater confidence about when AI / ML functionalities will become active and begin providing feedback.

[0322] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0323] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

1.A method comprising:receiving, by a wireless device, a configuration related to one or more functionalities from a base station;determining, by the wireless device, an applicability of at least one functionality among the one or more functionalities;transmitting, by the wireless device, applicability information related to an applicable functionality among the at least one functionality to the base station; andstarting, by the wireless device, a task related to the applicable functionality upon a confirmation for the application information.2.The method of claim 1, wherein the method further comprises determining whether the confirmation is obtained or not.3.The method of claim 1, wherein the confirmation is an explicit confirmation received from the base station.4.The method of claim 2, wherein the explicit confirmation includes at least one of an acknowledgement for the application information, an hybrid automatic repeat request (HARQ) acknowledgement for the application information, or an activation command for the applicable functionality.5.The method of claim 1, wherein the confirmation is an implicit confirmation based on a subsequent network operation after transmitting the applicability information.6.The method of claim 5, wherein the subsequent network operation includes at least one of i) no retransmission command for the applicability information, ii) a configuration of an uplink (UL) grant for transmission of a UL signal related to the task, or iii) a configuration of an uplink channel configuration.7.The method of claim 1, wherein the confirmation is obtained based on an expiry of a certain amount of time after transmitting the applicability information.8.The method of claim 1, wherein the task includes at least one of a measurement and reporting related to a channel state information (CSI), a CSI compression, a measurement and reporting related to an L3 quality, or a measurement and reporting related to a failure.9.The method of claim 1, wherein the task is related to at least one of a training, inference or monitoring of the applicable functionality.10.The method of claim 1, wherein the applicability information includes at least one of an applicability of the applicable functionality, an applicable condition of the applicable functionality, an applicable configuration of the applicable functionality, an updated or changed or reset applicability related information, a preferred configuration for the task, or a reason for applicability of the applicable functionality.11.The method of claim 1, wherein the wireless device is in communication with at least one of a mobile device, a network, and / or autonomous vehicles other than the wireless device.12.A wireless device comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform the method of any claims 1 to 10.13.A processing apparatus comprising:at least one processor that is integrated with a wireless device; andat least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform the method of any claims 1 to 11.14.A non-transitory Computer Readable Medium (CRM) storing instructions that, based on being executed by at least one processor, cause a wireless device to perform the method of any claims 1 to 11.15.A method comprising:transmitting, by a base station, a configuration related to one or more functionalities to a wireless device; andreceiving, by the base station, applicability information related to an applicable functionality among the one or more functionalities from the wireless device,wherein a task related to the applicable functionality is started upon a confirmation for the application information.16.A base station comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the base station to perform the method of claim 15.

Images