UE group based model management

By adopting UE group-based model management, the signaling overhead and scalability issues in conventional 5G NR systems are addressed, enhancing resource efficiency and flexibility in managing AI/ML models across multiple UEs.

WO2026235433A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096383
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-05
Filing Date
2026-04-28
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Conventional 5G NR systems rely on UE-dedicated signaling for AI/ML model management, leading to significant signaling overhead and scalability limitations due to redundant transmissions and increased resource consumption, especially in scenarios involving large groups of UEs.

Method used

Implementing a mechanism for coordinated UE group-based model management, allowing networks to deliver model management commands to multiple UEs through a common signaling mechanism, reducing redundant transmissions and enhancing scalability.

Benefits of technology

This approach reduces signaling overhead, optimizes radio resource utilization, and improves the scalability and flexibility of AI/ML model lifecycle management in large-scale UE deployments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096383_12112026_PF_FP_ABST
    Figure KR2026096383_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method and apparatus for a User Equipment (UE) group-based model management is provided. A UE determines a UE group to which the UE belongs, and receives group management related information from a network. Based on the group management related information applying to the UE group, the UE performs an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.
Need to check novelty before this filing date? Find Prior Art

Description

UE GROUP BASED MODEL MANAGEMENT

[0001] The present disclosure relates a User Equipment (UE) group-based model management.

[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 conventional 5G NR systems, AI / ML model management has been designed primarily around User Equipment (UE)-dedicated signaling mechanisms. Under this paradigm, the network transmits model management may command (e.g., instructions to activate, deactivate, or switch an AI / ML model) to each UE individually, even when the same command is intended for multiple UEs simultaneously. This UE-specific signaling architecture may reflect the legacy design philosophy of individualized radio resource control, which, while suitable for UE-specific parameter configuration, may not be well-suited for scenarios involving coordinated model management across a population of UEs.

[0006] As AI / ML functionality becomes increasingly integrated into NR operations, the number of models deployed across the network and the frequency of model lifecycle events (e.g., model updates, version transitions, and applicability changes) are expected to grow substantially. In such environments, the requirement to transmit individual model management commands to each UE may result in a significant increase in signaling overhead. When a common model management action applies to a large group of UEs, the network may need nonetheless generate and deliver a separate dedicated message per UE, leading to redundant transmission of semantically identical information. This redundancy may cause non-trivial consumption of downlink control and data channel resources, potentially degrading the efficiency of radio resource utilization.

[0007] Furthermore, the reliance on UE-dedicated signaling for model management may impose scalability limitations on the network. As the number of UEs subject to AI / ML model management grows, the cumulative signaling burden associated with per-UE command delivery may become a bottleneck, constraining the network's ability to manage AI / ML models in a timely and resource-efficient manner.

[0008] Accordingly, there may be a need for a mechanism that enables the network to efficiently deliver model management commands to multiple UEs in a coordinated manner, thereby reducing redundant signaling overhead and improving the scalability of AI / ML model lifecycle management in NR systems.

[0009] In an aspect, A method performed by a User Equipment (UE) is provided. The method comprises: determining a UE group to which the UE belongs, receiving group management related information from a network, and based on the group management related information applying to the UE group, performing an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.

[0010] In another aspect, A User Equipment (UE) is provided. The UE comprises 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 UE to perform operations. The operations comprise: determining a UE group to which the UE belongs, receiving group management related information from a network, and based on the group management related information applying to the UE group, performing an action related to an LCM of an inference based on the group management related information.

[0011] In another aspect, a processing apparatus is provided. The processing apparatus comprises at least one processor that is integrated with a UE, and at least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform operation. The operations comprise: determining a UE group to which the UE belongs, receiving group management related information from a network, and based on the group management related information applying to the UE group, performing an action related to an LCM of an inference based on the group management related information.

[0012] In another aspect, a non-transitory Computer Readable Medium (CRM) is provided. The non-transitory CRM stores instructions that, based on being executed by at least one processor, cause a User Equipment (UE) to perform operations. The operations comprise: determining a UE group to which the UE belongs, receiving group management related information from a network, and based on the group management related information applying to the UE group, performing an action related to an LCM of an inference based on the group management related information.

[0013] In another aspect, a method performed by a base station is provided. The method comprises: transmitting a group management related configuration to a UE, and transmitting group management related information to the UE. Based on the group management related information applying to a UE group to which the UE belongs, an action related to an LCM of an inference is performed based on the group management related information.

[0014] In another aspect, A base station is provided. The base station comprises 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 operations. The operations comprise: transmitting a group management related configuration to a UE, and transmitting group management related information to the UE. Based on the group management related information applying to a UE group to which the UE belongs, an action related to an LCM of an inference is performed based on the group management related information.

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

[0016] For example, by enabling the network to deliver model management commands to multiple UEs through a common signaling mechanism rather than through individual UE-dedicated transmissions, the amount of signaling overhead generated during model lifecycle events such as activation, deactivation, and switching can be significantly reduced. This reduction in redundant control signaling can contribute to more efficient utilization of downlink radio resources, allowing the freed capacity to be allocated to data transmission or other control functions.

[0017] For example, the scalability of AI / ML model management in large-scale UE deployment scenarios can be enhanced. In environments where a substantial number of UEs are subject to coordinated model management operations, the ability to convey a single command applicable to a group of UEs can prevent the signaling burden from growing proportionally with the number of UEs, thereby enabling the network to sustain efficient model lifecycle management even as the density and diversity of AI / ML-capable UEs increase.

[0018] For example, greater flexibility in controlling AI / ML models and associated functions across the network can be provided. By supporting group-oriented command delivery, the network can selectively target specific subsets of UEs for model management operations, enabling fine-grained and adaptive control over which models or functional capabilities are active at any given time. This can facilitate more responsive and context-aware management of AI / ML functionality in dynamically changing network conditions.

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

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

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

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

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

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

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

[0026] FIG. 8 shows an example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0027] FIG. 9 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0028] FIG. 10 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0029] FIG. 11 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0030] FIG. 12 shows an example of LCM command via dedicated signaling for each UE to which implementations of the present disclosure are applied.

[0031] FIG. 13 shows an example of a method performed by a UE to which implementations of the present disclosure are applied.

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

[0033] FIG. 15 shows an example of LCM command via common signaling to which implementations of the present disclosure are applied.

[0034] FIG. 16 shows an example of LCM command for UE group to which implementations of the present disclosure are applied.

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

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

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

[0038] 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".

[0039] 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".

[0040] 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".

[0041] 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".

[0042] 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".

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

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

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

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

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

[0048] 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).

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

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

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

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

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

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

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

[0056] 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).

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

[0058] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] 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).

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

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

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

[0097] 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).

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

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

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

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

[0102] 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).

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

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

[0105] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0107] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

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

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

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

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

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

[0115] Features related to Artificial Intelligence (AI) / Machine Learning (ML) are described.

[0116] The objective of AI / ML for NR air interface is to improve network performance and user experience, through AI / ML-enabled enhancements to the following features: beam management, Channel State Information (CSI) prediction and positioning.

[0117] AI / ML-based beam management may utilize intra-cell downlink beam prediction of the serving cell to reduce measurement / RS overhead and to improve the accuracy of beam selection. Two types of beam prediction may be supported:

[0118] - Spatial-domain downlink transmission beam prediction for one set of beams based on measurement results of another set of beams where the set of beams for prediction can be Synchronization Signal Block (SSB) or CSI-RS beams and another set of beams for measurement can be SSB or CSI-RS beams; and

[0119] - Temporal-domain downlink transmission beam prediction for one set of beams based on historic measurement results of another set of beams (these two sets may be different).

[0120] For AI / ML-based beam management, both network-side model and UE-side model may be supported.

[0121] For network-side model, the CSI measurement and reporting is used to acquire input data for inference.

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

[0123] For UE-side model, the gNB initiates performance monitoring, and makes management decisions based on the performance monitoring results. The UE can be configured to send either the measurement reports or the calculated performance metrics.

[0124] For an aspect related to Life Cycle Management (LCM) signaling procedures, signaling procedures for different scenarios for model-ID-based management and / or functionality-based management are exemplified. The procedures may at least be considered for UE-side models. These may include scenarios for which the management decision is taken by the network or by the UE. For network-side decision, this may be either network-initiated, or UE-initiated and requested to the network. While for UE-side decision, this may be either event-triggered as configured by the network and where the UE's decision is reported to the network, or UE-autonomous, with or without UE's decision being reported to the network.

[0125] The scenarios discussed below may not imply support for all potential functionality and / or model management instructions (e.g., (de)activation, selection, switching, fallback, etc.) for every use case.

[0126] FIG. 8 shows an example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0127] FIG. 8 shows a case where the LCM decision is taken and initiated by the network. The management instruction may be a result of model / functionality performance monitoring at the network. The management instruction may include information about the model or functionality.

[0128] FIG. 9 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0129] FIG. 9 shows a case where the LCM decision is taken by the network but where the request is initiated by the UE. The management request may be a result of model / functionality monitoring at the UE. In response to the management request, the network may send a management instruction to the UE. The management request may include information about the model or functionality. The network may accept or reject the management request from the UE. The management request may include information related to model / functionality performance metrics. The management instruction may include information about the model or functionality.

[0130] FIG. 10 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0131] FIG. 10 shows a case where the LCM decision is taken by the UE according to prior network configuration. Use case-specific events / conditions may be configured by the network for event-triggered AI / ML management at the UE. The UE may send a management decision report to the network following event-triggered AI / ML management at the UE. The management decision report may include information about the model or functionality.

[0132] FIG. 11 shows another example of an AI / ML management procedure to which implementations of the present disclosure are applied.

[0133] FIG. 11 shows a case where the LCM decision can autonomously be taken by the UE. The UE may be configured to send a management decision report to the network upon performing a model / functionality management decision.

[0134] For the case where the LCM decision can autonomously be taken by the UE and where the decision is not reported to the network, the AI / ML management is transparent from a network perspective.

[0135] In FIG. 8 to FIG. 11 described above, management request / management instruction / management decision report may include details about the model / functionality selection, (de)activation, switching or fallback).

[0136] When the network is responsible for the management of one or more functionalities or models associated with a UE-side model or a two-sided model, the network may control each UE through dedicated signaling. Corresponding dedicated signaling may include LCM command, such as functionality / model (de)activation, fallback, switching, update, etc.

[0137] FIG. 12 shows an example of LCM command via dedicated signaling for each UE to which implementations of the present disclosure are applied.

[0138] Referring to FIG. 12, the network may transmit LCM command for each UE via individual dedicated signaling. For example, the network may transmit an LCM command #1 to UE1 via signaling dedicated to UE1, an LCM command #2 to UE2 via signaling dedicated to UE2, and an LCM command #3 to UE3 via signaling dedicated to UE3.

[0139] As a common issue for functionalities / models, or depending on network conditions, it may be necessary to provide updates, new datasets, and / or parameters for specific or all models at a given time. Management-related commands such as model deactivation, switching, or fallback may also need to be delivered. Even when identical commands need to be delivered to all UEs, if the transmission is performed via dedicated signaling per UE, it may result in significant resource consumption due to redundant and duplicated information. Consequently, unnecessary signaling overhead may occur.

[0140] To address the problem mentioned above, the present disclosure may provide a method for UE group-based model management.

[0141] According to implementations of the present disclosure, the UE may determine the UE group to which it belongs. The UE group may be determined based on at least one of the network configuration, model / functionality-related factors, pre-determined settings, and other considerations.

[0142] According to implementations of the present disclosure, the network may transmit management-related information for a specific UE group. If the management-related information is related to the UE group to which the UE belongs, the UE may perform actions indicated by the management-related information. If the information is not related to the UE group to which the UE belongs, the UE may ignore the management-related information.

[0143] In the present disclosure, the following definitions may apply.

[0144] - ML model: a manageable representation of an ML model algorithm.

[0145] - AI / ML inference: a process of running a set of input data through a trained ML model to produce set of output data, such as predictions.

[0146] - AI / ML inference function: a logical function that employs trained ML model(s) to conduct inference.

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

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

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

[0150] FIG. 13 shows an example of a method performed by a UE to which implementations of the present disclosure are applied.

[0151] In step S1300, the method comprises determining a UE group to which the UE belongs.

[0152] In some implementations, the UE group may be determined based on at least one of configuration information related to a group management received from a network, or a UE decision.

[0153] In some implementations, the network may configure group management related configuration. The configuration information may comprise at least one of UE group ID related information, network command related information for the group management, or pre-configuration information associated with the group management.

[0154] In some implementations, the UE group ID related information may comprise at least one of a specific UE group ID assigned to the UE or a UE group determination factor for determining a UE group ID.

[0155] For example, the UE group determination factor may include at least one of the followings.

[0156] - zone / site / dataset ID

[0157] - associated ID / functionality ID / model ID

[0158] - model structure

[0159] - UE type (XR, aerial, RedCap, etc.)

[0160] - UE (group) ID determined by the UE

[0161] - UE (group) ID configured by the network

[0162] - a specific configuration related ID

[0163] - UE vendor / network vendor

[0164] - UE ID (legacy method)

[0165] - Training related site (e.g., training network entity, training server, etc.)

[0166] - Pre-determination (e.g., defined in a specific specification)

[0167] For example, a UE group may also be further divided into sub-groups based on the above-mentioned factors.

[0168] In some implementations, the network command related information may comprise information related to time or frequency resource allocation for receiving group management related information.

[0169] In some implementations, the pre-configuration information may comprise at least one of model related information (e.g., pre-configuration model structure and / or model parameter), time or location related information, or specific reporting configuration information (e.g., for inference, monitoring function). The pre-configuration information may be associated with a specific UE group management related information.

[0170] In step S1310, the method comprises receiving group management related information from a network.

[0171] In some implementations, the group management related information may comprise at least one of UE group related information, LCM command related information for functionality or model, time information, or location information.

[0172] For example, the UE group related information may also indicate whether it is intended for a specific UE group or for all UE groups (i.e., all UEs)

[0173] For example, LCM command related information for functionality or model may include and / or indicate at least one of the followings.

[0174] - (de-)activation

[0175] - fallback to legacy operation (e.g., non-AI operation)

[0176] - fallback to default operation (e.g., AI operation)

[0177] - switching to the other functionality / model

[0178] - command(activation) for inference / monitoring operation: A specific reporting configuration (e.g., CSI reporting configuration, measurement configuration, etc.) may be associated / linked / designated to the command.

[0179] - update (based on pre-configuration)

[0180] - model structure related information (e.g., model structure, model parameter, etc.): It may be either full configuration, or a simple indication based on pre-configuration.

[0181] For example, the time information may include at least one of the followings.

[0182] - Time window information for applying LCM command

[0183] - Start time information for applying LCM command

[0184] - Stop time information for stopping LCM command

[0185] The time information may be associated with LCM command in a pre-configuration. Or, a simple indication based on pre-configuration may be included in the group management related information.

[0186] The time information may include an offset value, reference time value, etc.

[0187] For example, the location information may include location information for applying LCM command, which may be at least one of Public Land Mobile Network (PLMN), Tracking Area (TA), cell list, beam list, area information (e.g., altitude, latitude, longitude, vector, angle, velocity, etc.)

[0188] The location information may be associated with LCM command in a pre-configuration. Or, a simple indication based on pre-configuration may be included in the group management related information.

[0189] In some implementations, the group management related information may be received via a group signaling or a broadcast signaling.

[0190] For example, the UE may be assigned / addressed to the UE-group common Radio Network Temporary Identity (RNTI). Then, the UE may decode UE-group specific DCI, or may decode UE-group specific a block determined by the network configuration. For example, the starting position of a block may be determined by the parameterstartingBitOfFormatXXXorstartingBitOfFormatYYYSULprovided for the UE configured with the block (where the XXX and YYY are DCI identification).

[0191] For example, the UE may be assigned to the UE-group.

[0192] For example, enhancement of (new) DCI or (new) group common DCI may be introduced.

[0193] For example, enhancement of (new) DCI for paging (e.g., scrambled by Paging RNTI (P-RNTI)) or (new) DCI for PEI (e.g., scrambled by Paging Early Indication RNTI (PEI-RNTI)) may be introduced.

[0194] In some implementations, the method may further comprise determining whether to the group management related information applies to the UE group or not.

[0195] In step S1320, based on the group management related information applying to the UE group, the method comprises performing an action related to an LCM of an inference (e.g., LCM command related information for functionality / model) based on the group management related information.

[0196] In some implementations, based on the group management related information not applying to the UE group, the method may further comprise ignoring the group management related information.

[0197] In some implementations, depending on the UE status, the method may further comprise rejecting the group management related information, and informing rejection of the action to the network.

[0198] In some implementations, the method may further comprise informing the network of completion of the action after performing the action.

[0199] In some implementations, to determine an applicable functionality / model for group management, the method may further comprise informing the network of at least one of applicability information related to the inference (e.g., applicable / available functionality / model information) or monitoring related information related to the inference (e.g., functionality / model monitoring related information). The monitoring related information may include at least one of model accuracy, system performance Key Performance Indicator (KPI) related information (e.g., radio quality (Reference Signal Received Power (RSRP) / Reference Signal Received Quality (RSRQ) / Signal to Interference Noise Ratio (SINR)) difference between prediction and actual measurement, Block Error Rate (BLER), data throughput, etc.).

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

[0201] The UE 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 UE to perform the method described in FIG. 13.

[0202] More specifically, the UE determines a UE group to which the UE belongs.

[0203] In some implementations, the UE group may be determined based on at least one of configuration information related to a group management received from a network, or a UE decision.

[0204] In some implementations, the network may configure group management related configuration. The configuration information may comprise at least one of UE group ID related information, network command related information for the group management, or pre-configuration information associated with the group management.

[0205] In some implementations, the UE group ID related information may comprise at least one of a specific UE group ID assigned to the UE or a UE group determination factor for determining a UE group ID.

[0206] In some implementations, the network command related information may comprise information related to time or frequency resource allocation for receiving group management related information.

[0207] In some implementations, the pre-configuration information may comprise at least one of model related information (e.g., pre-configuration model structure and / or model parameter), time or location related information, or specific reporting configuration information (e.g., for inference, monitoring function). The pre-configuration information may be associated with a specific UE group management related information.

[0208] The UE receives group management related information from a network.

[0209] In some implementations, the group management related information may comprise at least one of UE group related information, LCM command related information for functionality or model, time information, or location information.

[0210] In some implementations, the group management related information may be received via a group signaling or a broadcast signaling.

[0211] In some implementations, the UE may determine whether to the group management related information applies to the UE group or not.

[0212] Based on the group management related information applying to the UE group, the UE performs an action related to an LCM of an inference (e.g., LCM command related information for functionality / model) based on the group management related information.

[0213] In some implementations, based on the group management related information not applying to the UE group, the UE may ignore the group management related information.

[0214] In some implementations, depending on the UE status, the UE may reject the group management related information, and inform rejection of the action to the network.

[0215] In some implementations, the UE may inform the network of completion of the action after performing the action.

[0216] In some implementations, to determine an applicable functionality / model for group management, the UE may inform the network of at least one of applicability information related to the inference (e.g., applicable / available functionality / model information) or monitoring related information related to the inference (e.g., functionality / model monitoring related information). The monitoring related information may include at least one of model accuracy, system performance KPI related information (e.g., radio quality (RSRP / RSRQ / SINR) difference between prediction and actual measurement, BLER, data throughput, etc.).

[0217] Furthermore, the method described above in FIG. 13 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.

[0218] The processing apparatus comprises at least one processor that is integrated with a UE, 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. 13.

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

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

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

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

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

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

[0225] 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. 13.

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

[0227] In step S1400, the method comprises transmitting a group management related configuration to a UE.

[0228] In step S1410, the method comprises transmitting group management related information to the UE.

[0229] In step S1420, based on the group management related information applying to a UE group to which the UE belongs, an action related to Life Cycle Management (LCM) of an inference is performed based on the group management related information.

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

[0231] 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. 14.

[0232] More specifically, the base station transmits a group management related configuration to a UE.

[0233] The base station transmits group management related information to the UE.

[0234] based on the group management related information applying to a UE group to which the UE belongs, an action related to LCM of an inference is performed based on the group management related information.

[0235] FIG. 15 shows an example of LCM command via common signaling to which implementations of the present disclosure are applied.

[0236] Referring to FIG. 15, the network may transmit LCM command to UE1 / UE2 / UE3 commonly via group common signaling.

[0237] FIG. 16 shows an example of LCM command for UE group to which implementations of the present disclosure are applied.

[0238] Referring to FIG. 16, LCM command for UE group 1 is transmitted to UE group 1, and LCM command for UE group 2 is transmitted to UE group 2.

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

[0240] For example, by enabling the network to deliver model management commands to multiple UEs through a common signaling mechanism rather than through individual UE-dedicated transmissions, the amount of signaling overhead generated during model lifecycle events such as activation, deactivation, and switching can be significantly reduced. This reduction in redundant control signaling can contribute to more efficient utilization of downlink radio resources, allowing the freed capacity to be allocated to data transmission or other control functions.

[0241] For example, the scalability of AI / ML model management in large-scale UE deployment scenarios can be enhanced. In environments where a substantial number of UEs are subject to coordinated model management operations, the ability to convey a single command applicable to a group of UEs can prevent the signaling burden from growing proportionally with the number of UEs, thereby enabling the network to sustain efficient model lifecycle management even as the density and diversity of AI / ML-capable UEs increase.

[0242] For example, greater flexibility in controlling AI / ML models and associated functions across the network can be provided. By supporting group-oriented command delivery, the network can selectively target specific subsets of UEs for model management operations, enabling fine-grained and adaptive control over which models or functional capabilities are active at any given time. This can facilitate more responsive and context-aware management of AI / ML functionality in dynamically changing network conditions.

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

[0244] 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:determining, by a User Equipment (UE), a UE group to which the UE belongs;receiving, by the UE, group management related information from a network; andbased on the group management related information applying to the UE group, performing, by the UE, an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.2.The method of claim 1, wherein, based on the group management related information not applying to the UE group, the method further comprises ignoring, by the UE, the group management related information.3.The method of claim 1, wherein the UE group is determined based on at least one of configuration information related to a group management received from a network, or a UE decision.4.The method of claim 3, wherein the configuration information comprises at least one of UE group identity (ID) related information, network command related information for the group management, or pre-configuration information associated with the group management5.The method of claim 4, wherein the UE group ID related information comprises at least one of a specific UE group ID assigned to the UE or a UE group determination factor for determining a UE group ID.6.The method of claim 4, wherein the network command related information comprises information related to time or frequency resource allocation.7.The method of claim 4, wherein the pre-configuration information comprises at least one of model related information, time or location related information, or specific reporting configuration information.8.The method of claim 1, wherein the group management related information comprises at least one of UE group related information, LCM command related information for functionality or model, time information, or location information.9.The method of claim 8, wherein the UE group related information informs whether the UE group related information is intended for a specific UE group or for all UE groups.10.The method of claim 8, wherein the LCM command related information is related to at least one of activation or deactivation of the inference, fallback to a legacy operation, fallback to a default operation, switching to other functionality or model, command for inference or monitoring operation, or update of the inference.11.The method of claim 8, wherein the time information comprises at least one of time window information for applying an LCM command, start time information for applying the LCM command, stop time information for stopping the LCM command.12.The method of claim 8, wherein the location information comprises at least one of a Public Land Mobile Network (PLMN), Tracking Area (TA), cell list, beam list, or area information.13.The method of claim 1, wherein the group management related information is received via a group signaling or a broadcast signaling.14.The method of claim 1, wherein the method further comprises determining whether to the group management related information applies to the UE group or not.15.The method of claim 1, wherein the method further comprises rejecting the group management related information, and informing rejection of the action to the network.16.The method of claim 1, wherein the method further comprises informing the network of completion of the action after performing the action.17.The method of claim 1, wherein the method further comprises informing the network of at least one of applicability information related to the inference or monitoring related information related to the inference.18.A User Equipment (UE) 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 UE to perform operations comprising:determining a UE group to which the UE belongs;receiving group management related information from a network; andbased on the group management related information applying to the UE group, performing an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.19.A processing apparatus comprising:at least one processor that is integrated with a User Equipment (UE); andat least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform operation comprising:determining a UE group to which the UE belongs;obtaining group management related information; andbased on the group management related information applying to the UE group, performing an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.20.A non-transitory Computer Readable Medium (CRM) storing instructions that, based on being executed by at least one processor, cause a User Equipment (UE) to perform operations comprising:determining a UE group to which the UE belongs;receiving group management related information from a network; andbased on the group management related information applying to the UE group, performing an action related to a Life Cycle Management (LCM) of an inference based on the group management related information.21.A method comprising:transmitting, by a base station, a group management related configuration to a User Equipment (UE); andtransmitting, by the base station, group management related information to the UE,wherein, based on the group management related information applying to a UE group to which the UE belongs, an action related to Life Cycle Management (LCM) of an inference is performed based on the group management related information.22.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 operations comprising:transmitting a group management related configuration to a User Equipment (UE); andtransmitting group management related information to the UE,wherein, based on the group management related information applying to a UE group to which the UE belongs, an action related to Life Cycle Management (LCM) of an inference is performed based on the group management related information.