Partial discarding of logged data based on delta configuration
The selective retention of logged data based on configuration updates addresses the issue of unnecessary data loss in AI/ML-based data collection, enhancing data continuity and efficiency in UE logging configurations.
Patent Information
- Application Number
- PCT/KR2026/096645
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
The conventional logged Minimization of Drive Tests (MDT) procedures in 3GPP specifications require the complete discard of all previously collected data upon receiving a new logging configuration, leading to unnecessary loss of valid training data in AI/ML-based data collection scenarios due to incremental configuration updates.
A method for User Equipment (UE) to selectively retain or discard logged data based on the specific scope of a configuration update, preserving data collected under unchanged entries and discarding only data associated with modified or removed entries.
This approach prevents the unnecessary loss of relevant training data, reduces re-collection overhead, and ensures continuous and efficient AI/ML data collection by managing logging configurations in a granular and entry-aware manner.
Smart Images

Figure KR2026096645_12112026_PF_FP_ABST
Abstract
Description
PARTIAL DISCARDING OF LOGGED DATA BASED ON DELTA CONFIGURATION
[0001] The present disclosure relates partial discarding of logged data based on a delta configuration.
[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 existing logged Minimization of Drive Tests (MDT) procedures defined in 3GPP specifications, a User Equipment (UE) is required to discard all previously collected logged data upon receiving a new logging configuration from the network. This behavior was originally designed for traditional MDT use cases, where a reconfiguration typically signals a fundamental change in the measurement objective or reporting conditions, rendering previously collected data irrelevant. However, this blanket discard policy may become problematic in more sophisticated data collection scenarios.
[0006] In the context of AI / ML-based data collection for wireless networks, logging configurations tend to be more granular and structured. Such configurations may be list-based, enumerating multiple individual measurement or logging targets, and may support delta configuration updates, e.g., incremental modifications that add, remove, or update only a subset of entries within an existing configuration, rather than replacing the configuration entirely. This structural characteristic reflects the nature of AI / ML training data collection, where different measurement targets or feature sets may be managed independently, and where continuity and volume of collected data are critical factors for model training quality.
[0007] Under the conventional logged MDT behavior, however, even a minor delta update to the logging configuration, such as the addition of a single new entry or the modification of one parameter among many, may trigger the complete deletion of all previously accumulated logged data. As a result, measurement records that were collected under configuration entries that remain unchanged may be unnecessarily discarded. This may lead to a significant loss of valid training data that could otherwise have been used for AI / ML model training or inference. Furthermore, the repeated loss of accumulated data due to incremental reconfigurations may substantially degrade the overall efficiency of AI / ML data collection and model training workflows, as the UE may need to restart data accumulation from scratch each time any portion of the configuration is updated.
[0008] Accordingly, there may be a need for an improved logged data management mechanism in which the UE selectively retains or discards previously collected logged data based on the specific scope of a configuration update, such that data collected under unchanged configuration entries is preserved while only data associated with modified or removed entries is discarded.
[0009] In an aspect, a method performed by a User Equipment (UE) is provided. The method comprises: receiving a list of first configurations related to logging from a network, each of the first configurations comprising an identity related to each of the first configurations, performing the logging based on a first configuration from the list, receiving a second configuration related to logging from the network, and based on the second configuration being related to a specific identity, discarding logged data related to the specific identity.
[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: receiving a list of first configurations related to logging from a network, each of the first configurations comprising an identity related to each of the first configurations, performing the logging based on a first configuration from the list, receiving a second configuration related to logging from the network, and based on the second configuration being related to a specific identity, discarding logged data related to the specific identity.
[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: obtaining a list of first configurations related to logging from a network, each of the first configurations comprising an identity related to each of the first configurations, performing the logging based on a first configuration from the list, obtaining a second configuration related to logging from the network, and based on the second configuration being related to a specific identity, discarding logged data related to the specific identity.
[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: receiving a list of first configurations related to logging from a network, each of the first configurations comprising an identity related to each of the first configurations, performing the logging based on a first configuration from the list, receiving a second configuration related to logging from the network, and based on the second configuration being related to a specific identity, discarding logged data related to the specific identity.
[0013] In another aspect, a method performed by a base station is provided. The method comprises: transmitting a list of first configurations related to logging to a User Equipment (UE), each of the first configurations comprising an identity related to each of the first configurations, transmitting a second configuration related to logging to the UE, and, based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.
[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 list of first configurations related to logging to a User Equipment (UE), each of the first configurations comprising an identity related to each of the first configurations, transmitting a second configuration related to logging to the UE, and, based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.
[0015] The present disclosure may have various advantageous effects.
[0016] For example, by selectively retaining logged data based on the scope of a configuration update rather than discarding all accumulated data upon any reconfiguration, valid measurement records that remain applicable under unchanged configuration entries can be preserved. This can prevent the unnecessary loss of training data that would otherwise be discarded despite remaining relevant to the current logging objectives, thereby improving the overall efficiency of AI / ML model training and inference workflows.
[0017] Additionally, signaling and processing overhead associated with repeated data re-collection can be reduced. Because previously accumulated logged data can be retained when the corresponding configuration entries remain unmodified, the UE can avoid restarting data accumulation from scratch following incremental configuration updates. This can contribute to more stable and continuous data collection behavior, which can be particularly beneficial in scenarios where training data volume and consistency are important factors for AI / ML model performance.
[0018] Furthermore, flexible management of logging configurations can be enabled without sacrificing data continuity. For example, even when the network applies a delta configuration update to add, remove, or modify a subset of logging entries, the UE can manage its logged data in a granular and entry-aware manner. This can allow the logging framework to accommodate evolving network requirements or changing AI / ML model needs while retaining the maximum amount of usable data, thereby supporting more adaptive and efficient AI / ML data collection across diverse deployment scenarios.
[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 a method performed by a UE to which implementations of the present disclosure are applied.
[0027] FIG. 9 shows an example of a method performed by a base station to which implementations of the present disclosure are applied.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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".
[0032] 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".
[0033] 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".
[0034] 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".
[0035] 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".
[0036] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.
[0037] 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.
[0038] 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.
[0039] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.
[0040] 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.
[0041] 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).
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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).
[0050] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz
[0051] 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).
[0052] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz
[0053] 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.
[0054] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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).
[0071] 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.
[0072] 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.
[0073] 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.
[0074] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.
[0075] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.
[0076] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.
[0077] 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.
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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).
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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).
[0091] 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.
[0092] 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.
[0093] 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.
[0094] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.
[0095] 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).
[0096] 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.
[0097] 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.
[0098] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016
[0099] 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.
[0100] uNslotsymbNframe,uslotNsubframe,uslot212404
[0101] 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.
[0102] 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.
[0103] 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.
[0104] 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.
[0105] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.
[0106] 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.
[0107] 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.
[0108] The purpose of logged measurement configuration procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE and RRC_INACTIVE. The procedure applies to logged measurements capable UEs that are in RRC_CONNECTED.
[0109] NG-RAN may retrieve stored logged measurement information by means of the UE information procedure.
[0110] NG-RAN initiates the logged measurement configuration procedure to UE in RRC_CONNECTED by sending theLoggedMeasurementConfigurationmessage.
[0111] Upon receiving theLoggedMeasurementConfigurationmessage, the UE may:
[0112] 1> discard the logged measurement configuration as well as the logged measurement information;
[0113] 1> store the receivedloggingDuration,reportTypeandareaConfiguration, if included, inVarLogMeasConfig;
[0114] 1> If the UE is in Stand-alone Non-Public Network (SNPN) access mode:
[0115] 2> if theLoggedMeasurementConfigurationmessage includessnpn-ConfigList:
[0116] 3> set thesnpn-ConfigID-ListinVarLogMeasReportto include the current registered SNPN identity as well as SNPN identities insnpn-Config-List;
[0117] 2> else:
[0118] 3> set thesnpn-ConfigID-ListinVarLogMeasReportto include the current registered SNPN identity;
[0119] 1> else if theLoggedMeasurementConfigurationmessage includesplmn-IdentityList:
[0120] 2> setplmn-IdentityListinVarLogMeasReportto include the Registered Public Land Mobil Network (RPLMN) as well as the PLMNs included inplmn-IdentityList;
[0121] 1> else:
[0122] 2> setplmn-IdentityListinVarLogMeasReportto include the RPLMN;
[0123] 1> store the receivedabsoluteTimeInfo,traceReference,traceRecordingSessionRef, andtce-IdinVarLogMeasReport;
[0124] 1> store the receivedbt-NameList, if included, inVarLogMeasConfig;
[0125] 1> store the receivedwlan-NameList, if included, inVarLogMeasConfig;
[0126] 1> store the receivedsensor-NameList, if included, inVarLogMeasConfig;
[0127] 1> start timer T330 with the timer value set to theloggingDuration;
[0128] 1> store the receivedsigLoggedMeasType,if included, inVarLogMeasReport;
[0129] 1> store the receivedearlyMeasIndication,if included, inVarLogMeasConfig;
[0130] Upon expiry of T330, the UE may:
[0131] 1> releaseVarLogMeasConfig;
[0132] The UE is allowed to discard stored logged measurements, i.e. to releaseVarLogMeasReport, 48 hours after T330 expiry.
[0133] The purpose of logged measurement configuration release procedure is to release the logged measurement configuration as well as the logged measurement information.
[0134] The UE may initiate the procedure upon receiving a logged measurement configuration in same or another RAT. The UE may also initiate the procedure upon power off or upon deregistration.
[0135] The UE may:
[0136] 1> stop timer T330, if running;
[0137] 1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variablesVarLogMeasConfigandVarLogMeasReport.
[0138] The measurements logging procedure specifies the logging of available measurements by a UE in RRC_IDLE and RRC_INACTIVE that has a logged measurement configuration. The actual process of logging within the UE, takes place in RRC_IDLE state could continue in RRC_INACTIVE state or vice versa.
[0139] While T330 is running and Small Data Transmission (SDT) procedure is not ongoing, the UE may:
[0140] 1> if measurement logging is suspended:
[0141] 2> if during the last logging interval the In-Device Coexistence (IDC) problems detected by the UE is resolved, resume measurement logging;
[0142] 1> if not suspended, perform the logging in accordance with the following:
[0143] 2> if thereportTypeis set toperiodicalin theVarLogMeasConfig:
[0144] 3> if the UE is in any cell selection state:
[0145] 4> perform the logging at regular time intervals, as defined by theloggingIntervalin theVarLogMeasConfig;
[0146] 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport; or
[0147] 3> if the UE is in camped normally state on an NR cell and if the registered SNPN identity is included insnpn-ConfigID-Liststored inVarLogMeasReport:
[0148] 4> ifareaConfigurationis not included inVarLogMeasConfig; or
[0149] 4> if the serving cell is part of the area indicated byareaConfiginareaConfigurationinVarLogMeasConfig; or
[0150] 4> if the serving cell is part of the area indicated bycag-ConfigListinareaConfigurationinVarLogMeasConfig; or
[0151] 4> if the serving cell is part of the area indicated bysnpn-ConfigListinareaConfigurationinVarLogMeasConfig:
[0152] 5> perform the logging at regular time intervals, as defined by theloggingIntervalin theVarLogMeasConfig;
[0153] 2> else if thereportTypeis set toeventTriggered, andeventTypeis set tooutOfCoverage:
[0154] 3> perform the logging at regular time intervals as defined by theloggingIntervalinVarLogMeasConfigonly when the UE is in any cell selection state;
[0155] 3> upon transition from any cell selection state to camped normally state in NR:
[0156] 4> if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport, or if the registered SNPN identity is included insnpn-ConfigID-Liststored inVarLogMeasReport; and
[0157] 4> ifareaConfigurationis not included inVarLogMeasConfigor if the current camping cell is part of the area indicated byareaConfigofareaConfigurationinVarLogMeasConfig, or if the current camping cell is part of the area indicated bycag-ConfigListofareaConfigurationinVarLogMeasConfig,or if the current camping cell is part of the area indicated bysnpn-ConfigListofareaConfigurationinVarLogMeasConfig:
[0158] 5> perform the logging;
[0159] 2> else if thereportTypeis set toeventTriggeredandeventTypeis set toeventL1:
[0160] 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport; or
[0161] 3> if the UE is in camped normally state on an NR cell and if the registered SNPN identity is included insnpn-ConfigID-Liststored inVarLogMeasReport:
[0162] 4> ifareaConfigurationis not included inVarLogMeasConfig; or
[0163] 4> if the serving cell is part of the area indicated byareaConfiginareaConfigurationinVarLogMeasConfig; or
[0164] 4> if the current serving cell is part of the area indicated bycag-ConfigListofareaConfigurationinVarLogMeasConfig,or if the current camping cell is part of the area indicated bysnpn-ConfigListofareaConfigurationinVarLogMeasConfig;
[0165] 5> perform the logging at regular time intervals as defined by theloggingIntervalinVarLogMeasConfigonly when the conditions indicated by theeventL1are met;
[0166] 2> when performing the logging:
[0167] 3> ifInterFreqTargetInfois configured and if the UE detected IDC problems on at least one of the frequencies included inInterFreqTargetInfoor any inter-RAT frequency during the last logging interval, or
[0168] 3> ifInterFreqTargetInfois not configured and if the UE detected IDC problems during the last logging interval:
[0169] 4> ifmeasResultServingCellin theVarLogMeasReportis not empty:
[0170] 5> includeinDeviceCoexDetected;
[0171] 5> suspend measurement logging from the next logging interval;
[0172] 4> else:
[0173] 5> suspend measurement logging;
[0174] 3> set therelativeTimeStampto indicate the elapsed time since the moment at which the logged measurement configuration was received;
[0175] 3> if location information became available during the last logging interval, set the content of thelocationInfo:
[0176] 3> if the UE is in any cell selection state:
[0177] 4> setanyCellSelectionDetectedto indicate the detection of no suitable or no acceptable cell found;
[0178] 4> if thereportTypeis set toeventTriggeredin theVarLogMeasConfig; and
[0179] 4> if the RPLMN at the time of entering the any cell selection state is included inplmn-IdentityListstored inVarLogMeasReportor if the registered SNPN identity at the time of entering the any cell selection state is included insnpn-ConfigID-Liststored inVarLogMeasReport; and
[0180] 4> ifareaConfigurationis not included inVarLogMeasConfigor if the last suitable cell that the UE was camping on is part of the area indicated byareaConfigofareaConfigurationinVarLogMeasConfig, or if last suitable cell that the UE was camping on is part of the area indicated bycag-ConfigListofareaConfigurationinVarLogMeasConfig,or if last suitable cell that the UE was camping on is part of the area indicated bysnpn-ConfigListofareaConfigurationinVarLogMeasConfig:
[0181] 5> set theservCellIdentityto indicate global cell identity of the last suitable cell that the UE was camping on;
[0182] 5> set themeasResultServingCellto include the quantities of the last suitable cell the UE was camping on;
[0183] 4> else if thereportTypeis set toperiodicalin theVarLogMeasConfig:
[0184] 5> set theservCellIdentityto indicate global cell identity of the last logged cell that the UE was camping on;
[0185] 5> set themeasResultServingCellto include the quantities of the last logged cell the UE was camping on;
[0186] 3> else:
[0187] 4> set theservCellIdentityto indicate global cell identity of the cell the UE is camping on;
[0188] 4> set themeasResultServingCellto include the quantities of the cell the UE is camping on;
[0189] 3> if available, set themeasResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following:
[0190] 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following:
[0191] 5> ifinterFreqTargetInfois included inVarLogMeasConfig:
[0192] 6> ifearlyMeasIndicationis included inVarLogMeasConfig;
[0193] 7> include measurement results for NR neighbouring frequencies that are included in bothinterFreqTargetInfoand either inmeasIdleCarrierListNR(within theVarMeasIdleConfig) orSIB4;
[0194] 6> else:
[0195] 7> include measurement results for NR neighbouring frequencies that are included in bothinterFreqTargetInfoandSIB4;
[0196] 5> else:
[0197] 6> ifearlyMeasIndicationis included inVarLogMeasConfig;
[0198] 7> include measurement results for NR neighbouring frequencies that are included in eithermeasIdleCarrierListNR(within theVarMeasIdleConfig) orSIB4;
[0199] 6> else:
[0200] 7> include measurement results for NR neighbouring frequencies that are included inSIB4;
[0201] 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following:
[0202] 5> ifearlyMeasIndicationis included inVarLogMeasConfig:
[0203] 6> include measurement results for inter-RAT neighbouring frequencies that are included in eithermeasIdleCarrierListEUTRA(within theVarMeasIdleConfig) orSIB5;
[0204] 5> else:
[0205] 6> include measurement results for inter-RAT frequencies that are included inSIB5;
[0206] 4> for each neighbour cell included, include the optional fields that are available;
[0207] 2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330.
[0208] Features related to Artificial Intelligence (AI) / Machine Learning (ML) are described.
[0209] 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.
[0210] 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:
[0211] - 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
[0212] - 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).
[0213] For AI / ML-based beam management, both network-side model and UE-side model may be supported.
[0214] For network-side model, the CSI measurement and reporting is used to acquire input data for inference.
[0215] 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.
[0216] 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.
[0217] Network-side data collection applies only to AI / ML beam management feature.
[0218] Network-side data collection for network-side model training can be initiated by Operations, Administration, and Maintenance (OAM) or by gNB. In case of NR-DC, the data collection can only be configured for MCG. The following enablers are introduced for Network-side data collection for network-side model over air interface:
[0219] - The UE can be configured by gNB to log L1 measurements in the AS layer memory and report them via an RRC message(s).
[0220] - Both periodic and L3 measurement event-triggered data collection are supported. The UE stores the logged data at the AS layer memory. When the AS layer memory for storing logged data becomes full, the UE stops measurement and logging for data collection. When the AS layer memory reserved for storing logged data becomes full or reaches an absolute threshold (if configured), the UE indicates data availability to the gNB.
[0221] - When low power state is detected, the UE can indicate the low power state to the gNB. Upon reception of the low power state indication, the gNB should release the UE data collection configuration for network-side model.
[0222] - The gNB can indicate UE whether the logged data should be kept or not during handover. When indicated to keep the logged data, UE retains it during handover and indicates its availability after handover.
[0223] UE-side data collection applies to AI / ML Beam management and CSI prediction features.
[0224] For UE-side data collection for UE-side model training, the gNB can configure whether UE is allowed to initiate a request for data collection configuration (e.g., UE's preference to start or to stop data collection, preferred configuration from a list of candidate configurations provided by network). The gNB can also provide UE with data collection configuration or release the data collection configuration at any point in time, with or without UE request.
[0225] As mentioned above, measurement logging may be performed for AI / ML data collection, as similar as legacy measurement logging operation (e.g., logged Minimization of Drive Tests (MDT) operation).
[0226] If the power-off and / or deregistration happened or the valid time for the logged data has expired, the UE may consider the logged data as no longer valid and clear the logged data for the next logging operation. The conditions for releasing logged data may be similar with the existing logged measurement operation. For example, the UE may release the logged data for AI / ML data collection under the following conditions: upon power off, upon deregistration, upon a certain time later (e.g., 48 hours after release of logged measurement configuration), and / or upon successful delivery of theUEInformationResponsemessage (with logged data).
[0227] However, when a new logging configuration is set / configured, the behavior related to releasing the logged data for AI / ML data collection may differ from legacy logged measurement operation due to differences.
[0228] For example, in legacy logged measurement operation, the network may set logging configuration with a separate RRC message, e.g.,LoggedMeasurementConfigurationmessage. Upon receiving theLoggedMEasurementConfigurationmessage, the UE may discard the logged measurement configuration as well as the logged measurement information.
[0229] On the other hand, a logging configuration for AI / ML data collection may be included in theRRCReconfigurationmessage. In theRRCReconfigurationmessage, a list-based structure (e.g.,ToAddModListandToReleaseList) may be typically used based on a delta confiruation.
[0230] For example, a configuration to be added and / or modified related to the existing configuration may be provided via a delta configuration inToAddModList. The configuration may be added and / or modified related to the existing configuration, and other configurations in the existing configuration may be maintained.
[0231] For example, a configuration to be released from the existing configuration may be provided via a delta configuration inToReleaseList. The configuration may be released from the existing configuration, and other configurations in the existing configuration may be maintained.
[0232] When the logging configuration for AI / ML data collection is provided via delta configuration, it may be inefficient to discard all logged data unconditionally.
[0233] Therefore, to address the problem mentioned above, a differentiated approach may be applied for AI / ML-oriented data collection to ensure efficient data retention and avoid unnecessary loss of valid training data according to implementations of the present disclosure.
[0234] According to implementations of the present disclosure, a method for partial discarding of logged data based on delta configuration received from the network may be provided. Upon receiving a new configuration, the UE may discard only the logged data that corresponds to the configuration IDs included in theToAddModListorToReleaseList.
[0235] For example, if a configuration ID in theToAddModListmatches an existing logged data entry, the UE may discard / remove the corresponding logged data. For example, if a configuration ID in theToReleaseListmatches an existing logged data entry, the UE deletes the associated logged data. For example, the UE may retain any logged data that is not associated with configuration IDs in either theToAddModListor theToReleaseList.
[0236] According to implementations of the present disclosure, the network may explicitly indicate whether all logged data, or data related to specific logging configurations, should be discarded when reconfiguring logging parameters.
[0237] According to implementations of the present disclosure, partial management of logged data may be enabled depending on the scope of configuration changes. For example, logged data associated with unchanged configurations can be retained.
[0238] According to implementations of the present disclosure, a configuration identifier (ID) may refer to various types of configuration granularity. For example, the configuration ID may correspond to at least one of the followings.
[0239] 1) A specific configuration type (e.g., CSI configuration, measurement configuration);
[0240] 2) A configuration entry within a specific configuration (e.g., the first entry in the CSI configuration);
[0241] 3) A specific data set, which may be identified by:
[0242] - A resource ID (e.g., Non-Zero-Power (NZP) CSI-RS resource ID);
[0243] - A use case (e.g., beam prediction, mobility prediction);
[0244] - Time or location context;
[0245] - Beam or cell characteristics (e.g., port index, Transmission Reception Point (TRP) index);
[0246] - A condition (e.g., beam / cell quality threshold).
[0247] - If the configuration ID corresponds to a specific data set, the UE may manage logged data accordingly. For example, upon reconfiguration, the UE may retain or discard logged data based on the associated data set ID.
[0248] In the present disclosure, the following definitions may apply.
[0249] - ML model: a manageable representation of an ML model algorithm.
[0250] - 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.
[0251] - AI / ML inference function: a logical function that employs trained ML model(s) to conduct inference.
[0252] 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.
[0253] 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.
[0254] 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.
[0255] FIG. 8 shows an example of a method performed by a UE to which implementations of the present disclosure are applied.
[0256] In step S800, the method comprises receiving a list of first configurations related to logging from a network. Each of the first configurations comprises an identity related to each of the first configurations.
[0257] In some implementations, each of the first configurations may further comprise at least one of a resource configuration related to the logging or information related to an event triggering the logging.
[0258] In some implementations, the identity may correspond to at least one of i) a specific configuration type, ii) a configuration entry within a specific configuration, or iii) a specific data set. The specific data set may be identified based on at least one of i) a resource identity, ii) a use case, iii) time or location context, iv) beam or cell characteristics, or v) a condition related to beam or cell quality.
[0259] In step S810, the method comprises performing the logging based on a first configuration from the list.
[0260] In some implementations, the method may further comprise storing logging information as a result of the logging based on the first configuration. The logging information may be identified by the identity related to the first configuration.
[0261] In step S820, the method comprises receiving a second configuration related to the logging from the network.
[0262] In some implementations, the second configuration may be received via at least one of ToAddModList and / or ToReleaseList. The ToAddModList and / or the ToReleaseList may be included in RRC reconfiguration message.
[0263] In some implementations, the second configuration may correspond to a delta configuration.
[0264] In step S830, based on the second configuration being related to a specific identity, the method comprises discarding logged data related to the specific identity.
[0265] In some implementations, the specific identity may match an existing logged data entry in the logging information.
[0266] In some implementations, logged data not related to the specific identity may be retained.
[0267] In some implementations, logged data associated with unchanged configuration may be retained.
[0268] In some implementations, the method may further comprise receiving information related to whether the logged data should be discarded upon a reconfiguration.
[0269] 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.
[0270] 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. 8.
[0271] More specifically, the UE receives a list of first configurations related to logging from a network. Each of the first configurations comprises an identity related to each of the first configurations.
[0272] In some implementations, each of the first configurations may further comprise at least one of a resource configuration related to the logging or information related to an event triggering the logging.
[0273] In some implementations, the identity may correspond to at least one of i) a specific configuration type, ii) a configuration entry within a specific configuration, or iii) a specific data set. The specific data set may be identified based on at least one of i) a resource identity, ii) a use case, iii) time or location context, iv) beam or cell characteristics, or v) a condition related to beam or cell quality.
[0274] The UE performs the logging based on a first configuration from the list.
[0275] In some implementations, the UE may store logging information as a result of the logging based on the first configuration. The logging information may be identified by the identity related to the first configuration.
[0276] The UE receives a second configuration related to the logging from the network.
[0277] In some implementations, the second configuration may be received via at least one of ToAddModList and / or ToReleaseList. The ToAddModList and / or the ToReleaseList may be included in RRC reconfiguration message.
[0278] In some implementations, the second configuration may correspond to a delta configuration.
[0279] Based on the second configuration being related to a specific identity, the UE discards logged data related to the specific identity.
[0280] In some implementations, the specific identity may match an existing logged data entry in the logging information.
[0281] In some implementations, logged data not related to the specific identity may be retained.
[0282] In some implementations, logged data associated with unchanged configuration may be retained.
[0283] In some implementations, the UE may receive information related to whether the logged data should be discarded upon a reconfiguration.
[0284] Furthermore, the method described above in FIG. 8 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.
[0285] 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. 8.
[0286] Furthermore, the method described above in FIG. 8 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.
[0287] 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.
[0288] 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.
[0289] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.
[0290] 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.
[0291] 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.
[0292] 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. 8.
[0293] FIG. 9 shows an example of a method performed by a base station to which implementations of the present disclosure are applied.
[0294] In step S1400, the method comprises transmitting a group management related configuration to a UE.
[0295] In step S900, the method comprises transmitting a list of first configurations related to logging to a UE. Each of the first configurations comprises an identity related to each of the first configurations. The logging is performed based on a first configuration from the list.
[0296] In step S910, the method comprises transmitting a second configuration related to logging to the UE.
[0297] In step S920, based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.
[0298] Furthermore, the base station may be implemented by the second wireless device 200 shown in FIG. 2.
[0299] 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. 9.
[0300] More specifically, the base station transmits a list of first configurations related to logging to a UE. Each of the first configurations comprises an identity related to each of the first configurations. The logging is performed based on a first configuration from the list.
[0301] The base station transmits a second configuration related to logging to the UE.
[0302] based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.
[0303] Various example according to implementations of the present disclosure are described.
[0304] 1. Modification procedure
[0305] (1) The UE network may configure a first logging configuration.
[0306] Table 5 shows an example of the first logging configuration.
[0307] #1 entry of logging configuration- Config id #1- RS related config #1...#2 entry of logging configuration- Config id #2- RS related config #2...#3 entry of logging configuration- Config id #3- RS related config #3...
[0308] Referring to Table 5, the first logging configuration includes three entries of logging configuration (e.g., config #1, config #2, config #3).
[0309] (2) The UE derives measurement results and stores the measurement results in the logged data based on the first logging configuration.
[0310] Table 6 shows an example of logged data entry according to the first logging configuration.
[0311] #1 logged data for the first entry of logging configuration- Config id #1- Measurement results #1...#2 logged data for the second entry of logging configuration- Config id #2- Measurement results #2...#3 logged data for the third entry of logging configuration- Config id #3- Measurement results #3...
[0312] Referring to Table 6, the logged data entry also includes three entries (e.g., measurement results #1, measurement results #2, measurement results #3) according to the three entries of logging configuration in the first logging configuration.
[0313] (3) The network configures a second logging configuration.
[0314] Table 7 shows an example of the second logging configuration.
[0315] #2 entry of logging Configuration- Config id #2- RS related config #X...
[0316] Referring to Table 7, the second logging configuration intends to modify the second entry of logging configuration in the first logging configuration (e.g., RS related config #2 -> RS related config #X).
[0317] (4) The UE evaluates whether a configuration ID matches an existing logged data entry. The UE manages the logged data depending on the evaluation.
[0318] For the logging configuration, if a configuration ID matches an existing logged data entry, the UE releases the previous configuration. For example, since Config id #2 related to the #2 entry of logging configuration matches the existing logged data entry, the UE releases the #2 entry of logging configuration in the first logging configuration, and applies the #2 entry of logging configuration in the second logging configuration. The UE maintains the #1 and #3 entry of the first logging configuration.
[0319] For the logged data, if a configuration ID matches an existing logged data entry, the UE discards the relevant logged data entry. For example, since Config id #2 related to the #2 entry of logging configuration matches the existing logged data entry, the UE discards the #2 logged data entry. The UE maintains the #1 and #3 entry of logged data.
[0320] 2. Addition procedure
[0321] (1) The UE network may configure a first logging configuration. Table 5 described above may be used for the first logging configuration.
[0322] (2) The UE derives measurement results and stores the measurement results in the logged data based on the first logging configuration. Table 6 described above may be used for the logged data entry according to the first logging configuration.
[0323] (3) The network configures a second logging configuration.
[0324] Table 8 shows an example of the second logging configuration.
[0325] # 4 entry of logging Configuration- Config id #4- RS related config #Y...
[0326] Referring to Table 8, the second logging configuration intends to add the fourth entry of logging configuration in the first logging configuration (e.g., RS related config #Y).
[0327] (4) The UE evaluates whether a configuration ID matches an existing logged data entry. The UE manages the logged data depending on the evaluation.
[0328] For the logging configuration, if a configuration ID does not match an existing logged data entry, the UE maintains the previous configuration. For example, since Config id #4 related to the #4 entry of logging configuration does not match the existing logged data entry, the UE maintains the #1, #2, and #3 entry of logging configuration in the first logging configuration. The UE also applies the #4 entry of logging configuration in the second logging configuration.
[0329] For the logged data, if a configuration ID does not match an existing logged data entry, the UE maintains the previous logged data entry. For example, since Config id #4 related to the #4 entry of logging configuration does not match the existing logged data entry, the UE maintains the #1, #2, and #3 entry of logged data. The UE also starts logging operation for the #4 entry of logging configuration and stores the measurement results in the #4 entry of logged data.
[0330] 3. Release procedure
[0331] (1) The UE network may configure a first logging configuration. Table 5 described above may be used for the first logging configuration.
[0332] (2) The UE derives measurement results and stores the measurement results in the logged data based on the first logging configuration. Table 6 described above may be used for the logged data entry according to the first logging configuration.
[0333] (3) The network configures a second logging configuration. The second logging configuration includes a release command for a specific entry of logging configuration.
[0334] Table 9 shows an example of the second logging configuration.
[0335] Release list- Config id #2
[0336] Referring to Table 9, the second logging configuration intends to release the second entry of logging configuration in the first logging configuration.
[0337] (4) The UE evaluates whether a configuration ID matches an existing logged data entry. The UE manages the logged data depending on the evaluation.
[0338] For the logging configuration, if a configuration ID matches an existing logged data entry, the UE releases the previous configuration. For example, since Config id #2 related to the #2 entry of logging configuration matches the existing logged data entry, the UE releases the #2 entry of logging configuration in the first logging configuration. The UE maintains the #1 and #3 entry of the first logging configuration.
[0339] For the logged data, if a configuration ID matches an existing logged data entry, the UE discards the relevant logged data entry. For example, since Config id #2 related to the #2 entry of logging configuration matches the existing logged data entry, the UE discards the #2 logged data entry. The UE maintains the #1 and #3 entry of logged data.
[0340] 4. Top-N beam measurement logging - Partial management within an entry of logged data
[0341] (1) The UE network may configure a first logging configuration. In the first logging configuration, the network configures logging of the top-N beams (e.g., N=4) among M measured beams based on Reference Signal Received Power (RSRP).
[0342] Table 10 shows an example of the first logging configuration.
[0343] #2 entry of logging configuration- Config id #2- RS related config #2 (w / RS #1, RS #2, RS #3, RS #4)...
[0344] Referring to Table 10, the first logging configuration includes #2 entry logging configuration, and the #2 entry logging configuration includes RS related configuration #2 with four beams (e.g., RS #1, RS #2, RS #3, RS #4).
[0345] (2) The UE derives measurement results and stores the measurement results in the logged data based on the first logging configuration.
[0346] Table 11 shows an example of logged data entry according to the first logging configuration.
[0347] #2 logged data for the second entry of logging Configuration- Config id #2- Measurement results #2 (measurement results for RS #1, RS #2, RS #3, RS #4)...
[0348] Referring to Table 11, the logged data entry includes #2 logged data for the #2 entry of logging configuration (e.g., measurement results #2), and the measurement results #2 includes measurement results for RS #1, RS #2, RS #3, RS #4.
[0349] (3) The network configures a second logging configuration.
[0350] Table 12 shows an example of the second logging configuration.
[0351] #2 entry of logging configuration- Config id #2- RS related config #2 (w / RS #1, RS #2, RS #3, RS #4, RS #5)...
[0352] Referring to Table 12, the second logging configuration intends to modify the second entry of logging configuration in the first logging configuration by adding RS #5. With addition of RS #5, the UE may not determine retrospectively whether measurement results of RS#5 would have ranked in the top-N set at the time of previous measurements.
[0353] (4) The UE discards previously logged data because the original top-N selection is no longer valid under the changed measurement context.
[0354] 5. Port / TRP-based logging - Partial management within an entry of logged data
[0355] (1) The UE network may configure a first logging configuration. In the first logging configuration, the network configures logging of for even-numbered port (e.g., port #0, port #2, and port #4).
[0356] Table 13 shows an example of the first logging configuration.
[0357] #2 entry of logging configuration- Config id #2- RS related config #2 (w / port #0, port #2, port #4)...
[0358] (2) The UE derives measurement results and stores the measurement results in the logged data based on the first logging configuration.
[0359] Table 14 shows an example of logged data entry according to the first logging configuration.
[0360] #2 logged data for the second entry of logging Configuration- Config id #2- Measurement results #2 (measurement results for port #0, port #2, port #4)...
[0361] Referring to Table 14, the logged data entry includes #2 logged data for the #2 entry of logging configuration (e.g., measurement results #2), and the measurement results #2 includes measurement results for port #0, port #2, and port #4.
[0362] (3) The network configures a second logging configuration.
[0363] Table 15 shows an example of the second logging configuration.
[0364] #2 entry of logging Configuration- Config id #2- RS related config #2 (w / port #1, port #3, port #5)...
[0365] Referring to Table 15, the second logging configuration intends to modify the second entry of logging configuration in the first logging configuration to target odd-numbered ports (e.g., port #1, port #3, and port #5).
[0366] (4) The UE retains the previously logged data associated with even-numbered ports, since the new configuration does not invalidate or overlap with the old port-based logged data.
[0367] The present disclosure may have various advantageous effects.
[0368] For example, by selectively retaining logged data based on the scope of a configuration update rather than discarding all accumulated data upon any reconfiguration, valid measurement records that remain applicable under unchanged configuration entries can be preserved. This can prevent the unnecessary loss of training data that would otherwise be discarded despite remaining relevant to the current logging objectives, thereby improving the overall efficiency of AI / ML model training and inference workflows.
[0369] Additionally, signaling and processing overhead associated with repeated data re-collection can be reduced. Because previously accumulated logged data can be retained when the corresponding configuration entries remain unmodified, the UE can avoid restarting data accumulation from scratch following incremental configuration updates. This can contribute to more stable and continuous data collection behavior, which can be particularly beneficial in scenarios where training data volume and consistency are important factors for AI / ML model performance.
[0370] Furthermore, flexible management of logging configurations can be enabled without sacrificing data continuity. For example, even when the network applies a delta configuration update to add, remove, or modify a subset of logging entries, the UE can manage its logged data in a granular and entry-aware manner. This can allow the logging framework to accommodate evolving network requirements or changing AI / ML model needs while retaining the maximum amount of usable data, thereby supporting more adaptive and efficient AI / ML data collection across diverse deployment scenarios.
[0371] 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.
[0372] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.
Claims
1.A method comprising:receiving, by a User Equipment (UE), a list of first configurations related to logging from a network,wherein each of the first configurations comprises an identity related to each of the first configurations;performing, by the UE, the logging based on a first configuration from the list;receiving, by the UE, a second configuration related to the logging from the network; andbased on the second configuration being related to a specific identity, discarding, by the UE, logged data related to the specific identity.2.The method of claim 1, wherein each of the first configurations further comprises at least one of a resource configuration related to the logging or information related to an event triggering the logging.3.The method of claim 1, wherein the method further comprises storing logging information as a result of the logging based on the first configuration.4.The method of claim 3, wherein the logging information is identified by the identity related to the first configuration.5.The method of claim 3, wherein the specific identity matches an existing logged data entry in the logging information.6.The method of claim 1, wherein the second configuration is received via at least one of ToAddModList and / or ToReleaseList.7.The method of claim 6, wherein the ToAddModList and / or the ToReleaseList is included in a radio resource control (RRC) reconfiguration message.8.The method of claim 1, wherein the second configuration corresponds to a delta configuration.9.The method of claim 1, wherein logged data not related to the specific identity is retained.10.The method of claim 1, wherein logged data associated with unchanged configuration is retained.11.The method of claim 1, wherein the method further comprises receiving information related to whether the logged data should be discarded upon a reconfiguration.12.The method of claim 1, wherein the identity corresponds to at least one of i) a specific configuration type, ii) a configuration entry within a specific configuration, or iii) a specific data set.13.The method of claim 12, wherein the specific data set is identified based on at least one of i) a resource identity, ii) a use case, iii) time or location context, iv) beam or cell characteristics, or v) a condition related to beam or cell quality.14.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:receiving a list of first configurations related to logging,wherein each of the first configurations comprises an identity related to each of the first configurations;performing the logging based on a first configuration from the list;receiving a second configuration related to logging; andbased on the second configuration being related to a specific identity, discarding logged data related to the specific identity.15.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:obtaining a list of first configurations related to logging,wherein each of the first configurations comprises an identity related to each of the first configurations;performing the logging based on a first configuration from the list;obtaining a second configuration related to logging; andbased on the second configuration being related to a specific identity, discarding logged data related to the specific identity.16.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:receiving a list of first configurations related to logging,wherein each of the first configurations comprises an identity related to each of the first configurations;performing the logging based on a first configuration from the list;receiving a second configuration related to logging; andbased on the second configuration being related to a specific identity, discarding logged data related to the specific identity.17.A method comprising:transmitting, by a base station, a list of first configurations related to logging to a User Equipment (UE),wherein each of the first configurations comprises an identity related to each of the first configurations, andwherein the logging is performed based on a first configuration from the list; andtransmitting, by the base station, a second configuration related to logging to the UE,wherein, based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.18.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 list of first configurations related to logging to a User Equipment (UE),wherein each of the first configurations comprises an identity related to each of the first configurations, andwherein the logging is performed based on a first configuration from the list; andtransmitting a second configuration related to logging to the UE,wherein, based on the second configuration being related to a specific identity, logged data related to the specific identity is discarded.
