L1 measurement logging based on l3 event

Abstract

A method and apparatus for a Layer-1 (L1) measurement logging based on a Layer-3 (L3) event is provided. A wireless device receives a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. The wireless device performs a logging related to the event based on the information.

Description

L1 MEASUREMENT LOGGING BASED ON L3 EVENT

[0001] The present disclosure relates to a Layer-1 (L1) measurement logging based on a Layer-3 (L3) event.

[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 3GPP NR, measurement events defined at Layer-3 (L3) are fundamentally designed with the assumption that a measurement report will be transmitted to the network upon event triggering. Specifically, the use of L3 measurement events requires the configuration of aReportConfigNRand its association with a measurement identity (measId), which together form the structural basis for the measurement reporting procedure. This design reflects the original intent of L3 events as triggers for active reporting rather than passive observation.

[0006] However, this tight coupling between event triggering and the reporting procedure may introduce a significant limitation when measurement logging is the sole objective. BecauseReportConfigNRandmeasIdlinkage is mandatory for event utilization, the logging operation and the reporting procedure become structurally intertwined. As a result, it may not be possible to independently control and / or activate logging operation without simultaneously engaging the reporting machinery, even when no measurement report transmission is intended or desired. This structural dependency may lead to unnecessary signaling overhead, unintended report transmissions, and / or an inability to configure logging-only measurement behavior in a flexible and isolated manner.

[0007] Furthermore, the absence of a mechanism to decouple logging from reporting may impose constraints on network deployments where passive, non-reporting measurement collection is required (e.g., in scenarios involving Minimization of Drive Tests (MDT), network optimization, or AI / ML-based data collection for model training). In such cases, the inability to independently trigger and control logging without invoking the full reporting procedure may reduce the efficiency and flexibility of measurement management.

[0008] Accordingly, there may be a need for a mechanism that allows measurement events to be utilized exclusively for logging purposes, independent of theReportConfigNR-based reporting procedure, so that logging-only measurement operations can be configured and controlled without structural coupling to measurement report transmission.

[0009] In an aspect, a method performed by a wireless device is provided. The method includes receiving a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. The method includes performing a logging related to the event based on the information.

[0010] In another aspect, a wireless device is provided. The wireless device includes at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform operations. The operations include receiving a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. The operations include performing a logging related to the event based on the information.

[0011] In another aspect, a processing apparatus is provided. The processing apparatus includes at least one processor that is integrated with a wireless device, and at least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform operations. The operations include obtaining a logged measurement configuration. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. The operations include performing a logging related to the event based on the information.

[0012] In another aspect, a non-transitory Computer Readable Medium (CRM) is provided. The non-transitory CRM stores instructions that, based on being executed by at least one processor, cause a wireless device to perform operations. The operations include receiving a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. The operations include performing a logging related to the event based on the information.

[0013] In another aspect, a method performed by a base station is provided. The method includes transmitting a logged measurement configuration to a wireless device. The logged measurement configuration comprises an event-triggered measurement logging configuration. The event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. A logging related to the event is performed based on the information.

[0014] In another aspect, a base station is provided. The base station includes 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 include transmitting a logged measurement configuration to a wireless device. The logged measurement configuration comprises an event-triggered measurement logging configuration. The event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. A logging related to the event is performed based on the information.

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

[0016] For example, a functional and structural separation between the reporting domain and the logging domain can be enabled. By decoupling the logging operation from theReportConfigNR-based reporting procedure, a UE can perform logging-only measurement activities without being required to engage the measurement reporting machinery, thereby allowing each domain to operate independently according to its respective purpose and configuration.

[0017] For example, unnecessary reporting configuration procedures that would otherwise be mandated solely as a prerequisite for event utilization can be eliminated. Since logging behavior can be triggered and controlled without the establishment of ameasIdassociation or a correspondingReportConfigNR, the overhead associated with configuring and maintaining reporting-related parameters solely for logging purposes can be avoided.

[0018] Furthermore, by achieving the structural separation, the flexibility and efficiency of measurement management can be enhanced in various deployment scenarios where passive, non-reporting measurement collection is the primary objective (e.g., in contexts involving Minimization of Drive Tests (MDT), AI / ML-based data collection, or network optimization). The ability to independently configure and activate logging without invoking the reporting procedure can contribute to reduced signaling overhead and more streamlined measurement operations overall.

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

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

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

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

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

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

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

[0026] FIG. 8 shows an example of an initial applicability and applicability status change reporting procedure to which implementations of the present disclosure are applied.

[0027] FIG. 9 shows an example of a method performed by a wireless device to which the implementation 1 of the present disclosure is applied.

[0028] FIG. 10 shows an example of a method performed by a base station to which the implementation 1 of the present disclosure is applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0099] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0101] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

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

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

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

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

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

[0109] Features related to measurements are described.

[0110] The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signaling, i.e., using theRRCReconfigurationorRRCResume.

[0111] The network may configure the UE to perform the following types of measurements:

[0112] - NR measurements;

[0113] - Inter-RAT measurements of E-UTRA frequencies;

[0114] - Inter-RAT measurements of UTRA-FDD frequencies;

[0115] - NR sidelink measurements of Layer 2 (L2) UE-to-Network (U2N) Relay UEs.

[0116] The network may configure the UE to report the following measurement information based on Synchronization Signal (SS) / PBCH block(s) (SSB(s)):

[0117] - Measurement results per SS / PBCH block;

[0118] - Measurement results per cell based on SS / PBCH block(s);

[0119] - SS / PBCH block(s) indexes.

[0120] The network may configure the UE to report the following measurement information based on Channel State Information Reference Signal (CSI-RS) resources:

[0121] - Measurement results per CSI-RS resource;

[0122] - Measurement results per cell based on CSI-RS resource(s);

[0123] - CSI-RS resource measurement identifiers.

[0124] The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:

[0125] - Channel Busy Ratio (CBR) measurements.

[0126] The network may configure the UE to report the following Cross-Link Interference (CLI) measurement information based on Sounding Reference Signal (SRS) resources:

[0127] - Measurement results per SRS resource;

[0128] - SRS resource(s) indexes.

[0129] The network may configure the UE to report the following CLI measurement information based on CLI-Reference Signal Strength Indicator (RSSI) resources:

[0130] - Measurement results per CLI-RSSI resource;

[0131] - CLI-RSSI resource(s) indexes.

[0132] The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or Positioning Reference Signal (PRS):

[0133] - UE Rx-Tx time difference measurement result.

[0134] The measurement configuration includes the following parameters:

[0135] 1. Measurement objects: A list of objects on which the UE shall perform the measurements.

[0136] - For intra-frequency and inter-frequency measurements a measurement object indicates the frequency / time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'exclude-listed' cells and a list of 'allow-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.

[0137] - ThemeasObjectIdof the MO which corresponds to each serving cell is indicated byservingCellMOwithin the serving cell configuration.

[0138] - For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of 'exclude-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting.

[0139] - For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.

[0140] - For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.

[0141] - For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.

[0142] - For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery.

[0143] - For CBR measurement of NR sidelink positioning, a measurement object is a set of positioning dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink positioning on a single carrier frequency for NR sidelink positioning.

[0144] - For CLI measurements a measurement object indicates the frequency / time location of SRS resources and / or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.

[0145] 2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:

[0146] - Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

[0147] - RS type: The RS that the UE uses for beam and cell measurement results (SS / PBCH block or CSI-RS).

[0148] - Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g., Reference Signal Received Power (RSRP)) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.

[0149] In case of conditional reconfiguration, each configuration consists of the following:

[0150] - Execution criteria: The criteria the UE uses for conditional reconfiguration execution.

[0151] - RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS / PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.

[0152] 3. Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

[0153] 4. Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

[0154] 5. Measurement gaps: Periods that the UE may use to perform measurements.

[0155] 6. Effective measurement window: Periods that the UE may use to perform inter RAT measurements.

[0156] A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signaling and procedures. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

[0157] The measurement procedures distinguish the following types of cells:

[0158] 1. The NR serving cell(s) - these are the SpCell and one or more SCells.

[0159] 2. Listed cells - these are cells listed within the measurement object(s).

[0160] 3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).

[0161] For NR measurement object(s), the UE measures and reports on the serving cell(s) / serving Relay UE (for L2 U2N Remote UE), listed cells and / or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e., SRS resources and / or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs.

[0162] Whenever the procedural specification refers to a field it concerns a field included in theVarMeasConfigunless explicitly stated otherwise, i.e., only the measurement configuration procedure covers the direct UE action related to the receivedmeasConfig.

[0163] In NR-DC, the UE may receive two independentmeasConfig:

[0164] - ameasConfig, associated with MCG, that is included in theRRCReconfigurationmessage received via SRB1; and

[0165] - ameasConfig, associated with SCG, that is included in theRRCReconfigurationmessage received via SRB3, or, alternatively, included within aRRCReconfigurationmessage embedded in aRRCReconfigurationmessage received via SRB1.

[0166] In this case, the UE maintains two independentVarMeasConfigandVarMeasReportList, one associated with eachmeasConfig, and independently performs all the procedures for eachmeasConfigand the associatedVarMeasConfigandVarMeasReportList, unless explicitly stated otherwise.

[0167] The configurations related to CBR measurements are only included in themeasConfigassociated with MCG.

[0168] The configurations related to Rx-Tx time difference measurement are only included in themeasConfigassociated with MCG.

[0169] Table 5 shows an example of a measurement configuration, i.e.,MeasConfigInformation Element (IE). The IEMeasConfigspecifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.

[0170] -- ASN1START-- TAG-MEASCONFIG-STARTMeasConfig ::= SEQUENCE {measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need NmeasObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need NreportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need NreportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need NmeasIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need NmeasIdToAddModList MeasIdToAddModList OPTIONAL, -- Need Ns-MeasureConfig CHOICE {ssb-RSRP RSRP-Range,csi-RSRP RSRP-Range},quantityConfig QuantityConfig OPTIONAL, -- Need MmeasGapConfig MeasGapConfig OPTIONAL, -- Need MmeasGapSharingConfig MeasGapSharingConfig OPTIONAL, -- Need M...,[[interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL -- Need R]],[[effectiveMeasWindowConfig-r18 SetupRelease {MeasWindowConfig-r18} OPTIONAL -- Need M]]}

[0171] Referring to Table 5, themeasConfigIE includes the followings fields:

[0172] -measObjectToAddModList: List of measurement objects to add and / or modify.

[0173] -reportConfigToAddModList: List of measurement reporting configurations to add and / or modify.

[0174] - measIdToAddModList:List of measurement identities to add and / or modify

[0175] -quantityConfig

[0176] -measGapConfig:Used to setup and release measurement gaps in NR.

[0177] -effectiveMeasWindowConfig:Used to setup and release effective measurement window in NR for E-UTRA measurements

[0178] In other words, the measurement configuration (e.g.,MeasConfig) may include information related to a measurement object (e.g.,measObjectToAddModList) and information related to a report configuration (e.g.,reportConfigToAddModList), and the information related to a measurement object and the information related to a report configuration may be associated with each other based on information related to a measurement identity (e.g.,measIdToAddModList).

[0179] Table 6 shows an example of a report configuration to be included in theReportConfigToAddModListIE, i.e.,reportConfigNRIE. The IEReportConfigNRspecifies criteria for triggering of an NR measurement reporting event or of a Conditional Handover (CHO), Conditional PSCell Addition (CPA) or Conditional PSCell Chang e(CPC) event or of an L2 UE-to-Network (U2N) relay measurement reporting event. For events labelled AN with N equal to 1, 2 and so on, measurement reporting events and CHO, CPA or CPC events are based on cell measurement results, which can either be derived based on SS / PBCH block or CSI-RS.

[0180] -- ASN1START-- TAG-REPORTCONFIGNR-STARTReportConfigNR ::= SEQUENCE {reportType CHOICE {periodical PeriodicalReportConfig,eventTriggered EventTriggerConfig,...,reportCGI ReportCGI,reportSFTD ReportSFTD-NR,condTriggerConfig-r16 CondTriggerConfig-r16,cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,rxTxPeriodical-r17 RxTxPeriodical-r17,reportOnScellActivation-r18 ReportOnScellActivation-r18}}ReportCGI ::= SEQUENCE {cellForWhichToReportCGI PhysCellId,...,[[useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL -- Need R]]}ReportSFTD-NR ::= SEQUENCE {reportSFTD-Meas BOOLEAN,reportRSRP BOOLEAN,...,[[reportSFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need Rdrx-SFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need RcellsForWhichToReportSFTD SEQUENCE (SIZE (1..maxCellSFTD)) OF PhysCellId OPTIONAL -- Need R]]}...EventTriggerConfig ::= SEQUENCE {eventId CHOICE {eventA1 SEQUENCE {a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},eventA2 SEQUENCE {a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},...},rsType NR-RS-Type,reportInterval ReportInterval,reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport),reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- Need RmaxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need RincludeBeamMeasurements BOOLEAN,reportAddNeighMeas ENUMERATED {setup} OPTIONAL, -- Need R...,[[measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need RuseT312-r16 BOOLEAN OPTIONAL, -- Need MincludeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need RincludeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need MincludeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need MincludeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M]],[[coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need RreportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R]],[[numberOfTriggeringCells-r18 INTEGER (2..maxCellReport) OPTIONAL, -- Need RcellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellIndividualOffsetList-r18 OPTIONAL, -- Need ReventX1-SD-Threshold1-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SeventX2-SD-Threshold-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SreportOnBestCellChange-r18 ENUMERATED {n1, n2} OPTIONAL, -- Need RenteringLeavingReport-r18 ENUMERATED {true} OPTIONAL -- Need R]]}...

[0181] Referring to Table 6, thereportConfigNRIE includes thereportTypefield. If thereportTypefield is set toeventTriggered, thereportConfigNRIE includesEventTriggerConfigfield. TheEventTriggerConfigfield includes information related to various events, e.g., event A1, event A2, etc. Furthermore, theEventTriggerConfigfield includes various parameters related to event-triggered measurement reporting, e.g.,rsType,reportInterval,reportAmount, etc.

[0182] In other words, the information related to the various events may be included in the report configuration for event-triggered measurement reporting.

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

[0184] 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, CSI prediction and positioning.

[0185] 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:

[0186] - 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 SSB or CSI-RS beams and another set of beams for measurement can be SSB or CSI-RS beams; and

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

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

[0189] For UE-side model, the gNB may provide inference configuration or inference related parameters based on UE supported functionalities. The UE may report its applicable functionalities, inapplicable functionalities with its preference to release the configuration and subsequent changes of applicability status of functionalities to gNB.

[0190] FIG. 8 shows an example of an initial applicability and applicability status change reporting procedure to which implementations of the present disclosure are applied.

[0191] 1. The gNB may inquire about the UE capability information.

[0192] 2. If the gNB may inquire the UE capability information then the UE indicates its supported AI / ML functionalities to the gNB viaUECapabilityInformationmessage.

[0193] 3. The gNB may provide inference configuration with Network-side additional conditions (i.e., associated ID) to UE via CSI report configuration or inference related parameters configuration.

[0194] 4. The UE may determine the applicable AI / ML functionalities based on Network-side additional conditions (if provided), UE-side additional conditions (internally known by UE) and model availability in the UE.

[0195] 5. The UE may report its functionality applicability inRRCReconfigurationCompletemessage.

[0196] 6. When the inference configuration consists of periodic CSI report configuration, upon reporting the applicable functionalities, the UE may autonomously activate the applicable AI / ML functionalities. When the inference configuration consists of semi-persistent CSI reporting and / or aperiodic CSI report configuration, upon reporting the applicable AI / ML functionalities, semi-persistent CSI reporting can be activated by MAC CE / DCI and aperiodic CSI reporting can be activated by DCI.

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

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

[0199] During handover, the UE may receive the inference configuration related to the target gNB via handover command. Then the UE may report its applicable / inapplicable AI / ML functionalities to the target gNB after the handover completion.

[0200] UE assistance information can be sent from the source gNB to the target gNB to exchange applicability reporting referring to the configurations from the source gNB. The source gNB can send to the target gNB applicability information referring to the configurations from the source gNB, via handover preparation information message.

[0201] The UE can also report functionality applicability during RRC connection resume procedure.

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

[0203] For Network-side model, the gNB may be 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 may not be informed about any gNB-side management decision.

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

[0205] AI / ML-based CSI prediction is supported with similar principles and procedures for AI / ML-based beam management with the following differences:

[0206] - Only temporal-domain CSI prediction with UE-side model is supported.

[0207] - During the applicability reporting procedure, there is no inference related parameters configuration provided from gNB to UE for CSI prediction.

[0208] Network-side data collection may apply only to AI / ML beam management feature.

[0209] Network-side data collection for network-side model training can be initiated by Operation, 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:

[0210] - The UE can be configured by gNB to log L1 measurements in the AS layer memory and report them via an RRC message(s).

[0211] - Both periodic and L3 measurement event-triggered data collection are supported. The UE may store the logged data at the AS layer memory. When the AS layer memory for storing logged data becomes full, the UE may stop 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 may indicate data availability to the gNB.

[0212] - 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 may release the UE data collection configuration for Network-side model.

[0213] - The gNB can indicate the UE whether the logged data should be kept or not during handover. When indicated to keep the logged data, the UE may retain it during handover and indicates its availability after handover.

[0214] UE-side data collection may apply to AI / ML Beam management and CSI prediction features.

[0215] For UE-side data collection for UE-side model training, the gNB can configure whether the 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.

[0216] As mentioned above, L3 measurement event-triggered data collection may be supported for network-side data collection. For the event-triggered L3 measurement, the legacy logged Minimization of Drive Test (MDT) mechanism may be re-used. That is, if report type is set toEventTriggered, the UE may perform the logging at regular time interval as logging interval only when the conditions are met.

[0217] Meanwhile, it has been discussed and / or studied to use L3 measurement event to determine whether the UE performs logging or not. That is, the L3 measurement event may be used for triggering L1 measurement logging in connected state. For example, when event A1 (e.g., serving becomes better than a threshold) or event A2 (e.g., serving becomes worse than a threshold) is fulfilled for TTT based on L3 serving cell measurement, the UE may determine to perform logging. Separate L1 measurement event may not be supported.

[0218] When the L3 measurement event is used to determine whether the UE performs logging or not, the event-related configuration for logging (e.g.,eventTriggeredConfig) may need to be linked to L3 measurement event. To link the event-related configuration for logging and the L3 measurement event, the event-related configuration for logging may be link tomeasIdassociated with a specific measurement object / report configuration. This may allow the UE to recognize which event should trigger logging for a particular measurement object.

[0219] However, the L3 measurement events are designed based on the premise of transmitting measurement reports. If the event-related configuration for logging is linked to the L3 measurement event based onmeasIdassociated with a specific measurement object / report configuration as mentioned above, the L1 logging operation and the measurement reporting procedure may be structurally intertwined, making independent control solely for logging difficult.

[0220] In other words, since the L1 measurement logging linked to L3 measurement event does not need to trigger an actual measurement reporting, a measurement configuration may need to be enhanced for L1 measurement logging.

[0221] To address the problem mentioned above, the present disclosure provides various implementations for a measurement configuration without measurement reporting for L1 measurement logging.

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

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

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

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

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

[0227] 1. Implementation 1

[0228] According to the implementation 1 of the present disclosure, the event-related configuration for the L1 measurement logging may be separated from the measurement reporting. That is, an independent L1 measurement logging event configuration which is not dependent on conventional measurement reporting procedure may be configured / introduced. In this case, the conventional L3 filtering and event evaluation may be reused, but the measurement reporting procedure is not executed (i.e., event architecture reconfiguration).

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

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

[0231] FIG. 9 shows an example of a method performed by a wireless device to which the implementation 1 of the present disclosure is applied.

[0232] In step S900, the method includes receiving a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration.

[0233] In some implementations, the event-triggered measurement logging configuration may not be included in a report configuration.

[0234] In some implementations, the event-triggered measurement logging configuration may not be related to a reporting of logging results.

[0235] In some implementations, the event-triggered measurement logging configuration may not include a report configuration related to reporting of logging results.

[0236] In some implementations, the logged measurement configuration may be a CSI logged measurement configuration. The CSI logged measurement configuration may define a group of one or more CSI resources for which the wireless device logs the associated L1 radio measurements. The CSI logged measurement configuration may be for a network-side data collection.

[0237] In some implementations, the event-triggered measurement logging configuration may be used to configure the wireless device with an event-triggered measurement logging.

[0238] In some implementations, the event-triggered measurement logging configuration may include an event ID indicating the event used for measurement logging.

[0239] In step S910, the method includes performing a logging related to the event based on the information. The event includes at least one of an event A1 or event A2.

[0240] In some implementations, the event A1 may be that a serving cell quality becomes better than a threshold. The event A2 may be that a serving cell quality becomes worse than a threshold.

[0241] In some implementations, the logging may be performed at regular time intervals based on the measurement logging triggering condition being fulfilled.

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

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

[0244] More specifically, the wireless device receives a logged measurement configuration from a base station. The logged measurement configuration includes an event-triggered measurement logging configuration. The event-triggered measurement logging configuration includes information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration.

[0245] In some implementations, the event-triggered measurement logging configuration may not be included in a report configuration.

[0246] In some implementations, the event-triggered measurement logging configuration may not be related to a reporting of logging results.

[0247] In some implementations, the event-triggered measurement logging configuration may not include a report configuration related to reporting of logging results.

[0248] In some implementations, the logged measurement configuration may be a CSI logged measurement configuration. The CSI logged measurement configuration may define a group of one or more CSI resources for which the wireless device logs the associated L1 radio measurements. The CSI logged measurement configuration may be for a network-side data collection.

[0249] In some implementations, the event-triggered measurement logging configuration may be used to configure the wireless device with an event-triggered measurement logging.

[0250] In some implementations, the event-triggered measurement logging configuration may include an event ID indicating the event used for measurement logging.

[0251] The wireless device performs a logging related to the event based on the information. The event includes at least one of an event A1 or event A2.

[0252] In some implementations, the event A1 may be that a serving cell quality becomes better than a threshold. The event A2 may be that a serving cell quality becomes worse than a threshold.

[0253] In some implementations, the logging may be performed at regular time intervals based on the measurement logging triggering condition being fulfilled.

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

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

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

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

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

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

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

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

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

[0263] FIG. 10 shows an example of a method performed by a base station to which the implementation 1 of the present disclosure is applied.

[0264] In step S1000, the method includes transmitting a logged measurement configuration to a wireless device. The logged measurement configuration comprises an event-triggered measurement logging configuration. The event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. A logging related to the event is performed based on the information.

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

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

[0267] More specifically, the base station transmits a logged measurement configuration to a wireless device. The logged measurement configuration comprises an event-triggered measurement logging configuration. The event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event. The event is associated with the event-triggered measurement logging configuration. A logging related to the event is performed based on the information.

[0268] According to the implementation 1 of the present disclosure, the measurement configuration without measurement reporting for L1 measurement logging may be implemented as follows.

[0269] Table 7 shows an example of a CSI logged measurement configuration, i.e.,CSI-LoggedMeasurementConfigIE, according to the implementation 1 of the present disclosure. The IECSI-LoggedMeasurementConfigis used to configure a CSI logged measurement configuration. It defines a group of one or more CSI resources for which the UE logs the associated L1 radio measurements.

[0270] -- ASN1START-- TAG-CSI-LOGGEDMEASUREMENTCONFIG-STARTCSI-LoggedMeasurementConfig-r19 ::= SEQUENCE {csi-LoggedMeasurementConfigId-r19 CSI-LoggedMeasurementConfigId-r19,csi-LoggedResourceConfig-r19 CSI-ResourceConfigId,loggingPeriodicity-r19 ENUMERATED {n2, n3, n4, n5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need Rcsi-LoggedMeasurementEventTriggerConfig-r19 CSI-LoggedMeasurementEventTriggerConfig-r19 OPTIONAL, -- Need R...}CSI-LoggedMeasurementEventTriggerConfig-r19 ::= SEQUENCE {eventId-r19 CHOICE {eventA1-r19 SEQUENCE {a1-Threshold-r19 MeasTriggerQuantity,hysteresis-r19 Hysteresis,timeToTrigger-r19 TimeToTrigger},eventA2-r19 SEQUENCE {a2-Threshold-r19 MeasTriggerQuantity,hysteresis-r19 Hysteresis,timeToTrigger-r19 TimeToTrigger},...}}

[0271] TheCSI-LoggedMeasurementConfigIE may correspond to the logged measurement configuration described in FIG. 9 and / or FIG. 10.

[0272] Referring to Table 7, theCSI-LoggedMeasurementConfigIE may include thecsi-LoggedMeasurementEventTriggerConfigfield. This field may be used to configure the UE with event-triggered CSI measurement logging. If this field is not included, the UE may start the measurement logging according tocsiLoggedResourceConfigupon reception. Thecsi-LoggedMeasurementEventTriggerConfigfield may correspond to the event-triggered measurement logging configuration described in FIG. 9 and / or FIG. 10.

[0273] TheCSI-LoggedMeasurementConfigIE may further include thecsi-LoggedResourceConfigfield. This field may indicate resource in which the UE performs channel measurement whose associated measurement results are logged by the UE. Thecsi-LoggedResourceConfigindicated here may contain only Non-Zero-Power (NZP)-CSI-RS resources and / or SSB resources.

[0274] TheCSI-LoggedMeasurementConfigIE may further include thecsi-LoggedMeasurementConfigIdfield. This field may indicate the instance ofCSI-LoggedMeasurementConfig.

[0275] Thecsi-LoggedMeasurementEventTriggerConfigfield may include theeventIDfield. This field may indicate an event used for measurement logging. If this field is set toeventA1, the UE may start performing logging of measurements when the entering condition is met and stop logging when the corresponding leaving condition is met. If this field is set toeventA2, the UE may start performing logging of measurements when the entering condition is met and stop logging when the corresponding leaving condition is met. Various parameters related to event A1 and / or event A2 included in thecsi-LoggedMeasurementEventTriggerConfigmay correspond to the information related to the measurement logging triggering condition for an event described in FIG. 9 and / or FIG. 10.

[0276] Furthermore, theCSI-LoggedMeasurementConfigIE may be included in a CSI measurement configuration, i.e.,CSI-MeasConfigIE. The IECSI-MeasConfigmay be used to configure logging of channel state information for the serving cell in whichCSI-MeasConfigis included.

[0277] That is, theCSI-LoggedMeasurementConfigIE may not be included in a general measurement configuration, i.e.,measConfigIE, which includes ameasIDandreportConfigNR.

[0278] According to the implementation 1 of the present disclosure, since the event-related configuration for L1 measurement logging is not included inreportConfigNR, the L1 measurement logging operation may be structurally independent from the measurement reporting procedure.

[0279] Event A1 may mean that serving becomes better than threshold. The UE shall:

[0280] 1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;

[0281] 1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;

[0282] 1> for this measurement, consider the NR serving cell corresponding to the associatedmeasObjectNRassociated with this event.

[0283] Inequality A1-1 (Entering condition)

[0284] Ms - Hys > Thresh

[0285] Inequality -2 (Leaving condition)

[0286] Ms + Hys < Thresh

[0287] The variables in the formula are defined as follows:

[0288] -Msis the measurement result of the serving cell, not taking into account any offsets.

[0289] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).

[0290] -Threshis the threshold parameter for this event (i.e.a1-Thresholdas defined withinreportConfigNRfor this event).

[0291] -Msis expressed in dBm in case of RSRP, or in dB in case of Reference Signal received Quality (RSRQ) and Reference Signal (RS)-Signal-to-Interference and Noise Ratio (SINR).

[0292] -Hysis expressed in dB.

[0293] -Threshis expressed in the same unit asMs.

[0294] Event A1 may mean that serving becomes worse than threshold. The UE shall:

[0295] 1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled;

[0296] 1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled;

[0297] 1< for this measurement, consider the serving cell indicated by themeasObjectNRassociated to this event.

[0298] If the SCell indicated by themeasObjectNRassociated to this event is not detectable, then the UE may consider for the value ofMsthe lowest value of the value range of the measurement quantity as the SCell measurement.

[0299] Inequality A2-1 (Entering condition)

[0300] Ms + Hys < Thresh

[0301] Inequality A2-2 (Leaving condition)

[0302] Ms - Hys > Thresh

[0303] The variables in the formula are defined as follows:

[0304] -Msis the measurement result of the serving cell, not taking into account any offsets.

[0305] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).

[0306] -Threshis the threshold parameter for this event (i.e.a2-Thresholdas defined withinreportConfigNRfor this event).

[0307] -Msis expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0308] -Hysis expressed in dB.

[0309] -Threshis expressed in the same unit asMs.

[0310] According to the implementation 1 of the present disclosure, the logged measurements for network-side data collection procedure may be implemented as follows.

[0311] The purpose of the logged measurements for network-side data collection procedure is to configure the UE to perform logging of measurement results while in RRC_CONNECTED. This procedure may apply to UEs in RRC_CONNECTED that are capable of logged measurements for network-side data collection.

[0312] NG-RAN may initiate the logged measurement configuration procedure to UE in RRC_CONNECTED for a serving cell by sendingcsi-LoggedMeasurementConfigToAddModListin thecsi-MeasConfigof a serving cell.

[0313] Upon receivingcsi-LoggedMeasurementConfigToAddModListin thecsi-MeasConfigof a serving cell, the UE shall:

[0314] 1> for each CSI logged measurement configuration included incsi-LoggedMeasurementConfigToAddModList:

[0315] 2> if the current UE configuration for the serving cell includes the CSI logged measurement configuration associated with the givencsi-LoggedMeasurementConfigId:

[0316] 3> modify the CSI logged measurement configuration according to the configuration received incsiLoggedMeasurementConfigToAddModList;

[0317] 2> else:

[0318] 3> add the received CSI logged measurement configuration to the UE configuration;

[0319] 2> perform measurements logging.

[0320] The UE may keep the logged data for a CSI logged measurement configuration when that configuration is modified.

[0321] The measurement logging procedure specifies the logging of available measurements by a UE in RRC_CONNECTED that has a logged measurement configuration for network-side data collection.

[0322] The UE shall:

[0323] 1> for each CSI logged measurement configuration associated with arefCSI-LoggedMeasurementConfigIdincsiLogMeasInfoConfigListinVarCSI-LogMeasReport,perform the logging of measurements for the serving cell associated withcellId, in accordance with the corresponding CSI logged measurement configuration:

[0324] 2> if thecsi-LoggedMeasurementEventTriggerConfigis not included and the memory for network-side data collection is not full:

[0325] 3> perform the logging at regular time intervals, according tologgingPeriodicity(if present) or according to the periodicity of the resources indicated bycsi-LoggedResourceConfigin the corresponding CSI logged measurement configuration, ifloggingPeriodicityis not present;

[0326] 2> if thecsi-LoggedMeasurementEventTriggerConfigis included and the memory for network-side data collection is not full:

[0327] 3> ifeventIdwithincsi-LoggedMeasurementEventTriggerConfigis set toeventA1and the entering condition is fulfilled for the serving cell associated withcellIdfor all measurements taken duringtimeToTriggerdefined for this event; or

[0328] 3> ifeventIdwithincsi-LoggedMeasurementEventTriggerConfigis set toeventA2and the entering condition is fulfilled for the serving cell associated withcellIdfor all measurements taken duringtimeToTriggerdefined for this event:

[0329] 4> perform the logging at regular time intervals, according tologgingPeriodicity(if present) or according to the periodicity of the resources indicated bycsi-LoggedResourceConfigin the corresponding CSI logged measurement configuration, ifloggingPeriodicityis not present;

[0330] 3> ifeventIdwithincsi-LoggedMeasurementEventTriggerConfigis set toeventA1and the leaving condition is fulfilled for the serving cell associated withcellIdfor all measurements taken duringtimeToTriggerdefined for this event; or

[0331] 3> ifeventIdwithincsi-LoggedMeasurementEventTriggerConfigis set toeventA2and the leaving condition is fulfilled for the serving cell associated withcellIdfor all measurements taken duringtimeToTriggerdefined for this event:

[0332] 4> stop performing the logging for the corresponding CSI logged measurement configuration;

[0333] 2> when performing the logging:

[0334] 3> if the cell identity of the serving cell for which the measurements shall be logged, i.e. the serving cell associated with the serving cell configuration in whichcsi-LoggedMeasurementConfigToAddModListwas received, is not included in an entry incsi-LogMeasInfoCellListinVarCSI-LogMeasReport:

[0335] 4> include an entry incsi-LogMeasInfoCellListwithinVarCSI-LogMeasReport;

[0336] 4> setcellIdto the global cell identity, if available, otherwise to the physical cell identity and carrier frequency of the serving cell associated with the serving cell configuration in whichcsiLoggedMeasurementConfigToAddModListwas received;

[0337] 3> if not already present, include an entry incsi-LogMeasInfoConfigListwithinVarCSI-LogMeasReportand setrefCSI-LoggedMeasurementConfigIdto thecsi-LoggedMeasurementConfigIdassociated to the CSI logged measurement configuration;

[0338] 3> for each CSI logged measurement configuration associated torefCSI-LoggedMeasurementConfigIdincsi-LogMeasInfoConfigListinVarCSI-LogMeasReport:

[0339] 4> for each logging instance:

[0340] 5> include an entry incsi-LogMeasInfoListand set thecsi-RS-MeasResultListand / orSSBMeasResultListto include the quantities the UE is logging measurements for, upon receiving the quantities from the lower layers;

[0341] 5> if the time between the measurements that are logged and included in this instance ofcsiLogMeasInfoListand the measurements for the previous instance ofcsi-LogMeasInfoListwith the samerefCSI-LoggedMeasurementConfigId, for the same serving cell, is longer than the logging periodicity (if configured) or the periodicity of the measurement resources (if the logging periodicity is not configured):

[0342] 6> set thetimeGaptotrue;

[0343] 2> when the memory reserved for the logged measurement information for data collection becomes full, stop logging;

[0344] 2> when the memory reserved for the logged measurement information for data collection is no longer full, resume logging.

[0345] 2. Implementation 2

[0346] According to the implementation 2 of the present disclosure, a separate report type for L1 measurement logging may be introduced. In this case, the separate report type may not include report related configuration (e.g., report interval, report amount, etc.).

[0347] Table 8 shows an example of a CSI logged measurement configuration, i.e.,CSI-LoggedMeasurementConfigIE, according to the implementation 2 of the present disclosure. The IECSI-LoggedMeasurementConfigis used to configure a CSI logged measurement configuration. It defines a group of one or more CSI resources for which the UE logs the associated L1 radio measurements.

[0348] CSI-LoggedMeasurementConfig-r19 ::= SEQUENCE {csi-LoggedMeasurementConfigId-r19 CSI-LoggedMeasurementConfigId-r19,csi-LoggedResourceConfig-r19 CSI-ResourceConfigId,eventTriggeredConfig-r19 MeasId OPTIONAL, -- Need R...}-- TAG-CSI-LOGGEDMEASUREMENTCONFIG-STOP-- ASN1STOP

[0349] Referring to Table 8, theCSI-LoggedMeasurementConfigIE may include theeventTriggerConfigfield. This field may be used to configure the UE with event-triggered measurement logging. If this field is not included, the UE may start the measurement logging according tocsi-LoggedResourceConfigupon reception. Furthermore, theeventTriggerConfigfield may be associated with theMeasID.

[0350] Table 9 shows an example of a report configuration, i.e.,reportConfigNRIE, according to the implementation 2 of the present disclosure.

[0351] -- ASN1START-- TAG-REPORTCONFIGNR-STARTReportConfigNR ::= SEQUENCE {reportType CHOICE {periodical PeriodicalReportConfig,eventTriggered EventTriggerConfig,...,reportCGI ReportCGI,reportSFTD ReportSFTD-NR,condTriggerConfig-r16 CondTriggerConfig-r16,cli-Periodical-r16 CLI-PeriodicalReportConfig-r16,cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,rxTxPeriodical-r17 RxTxPeriodical-r17,reportOnScellActivation-r18 ReportOnScellActivation-r18eventTriggeredLogging-r19 EventTriggerConfigLogging-r19,}}...EventTriggerConfig ::= SEQUENCE {eventId CHOICE {eventA1 SEQUENCE {a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},eventA2 SEQUENCE {a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},...},rsType NR-RS-Type,reportInterval ReportInterval,reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport),reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- Need RmaxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need RincludeBeamMeasurements BOOLEAN,reportAddNeighMeas ENUMERATED {setup} OPTIONAL, -- Need R...,[[measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need RuseT312-r16 BOOLEAN OPTIONAL, -- Need MincludeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need RincludeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need MincludeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need MincludeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M]],[[coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need RreportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R]],[[numberOfTriggeringCells-r18 INTEGER (2..maxCellReport) OPTIONAL, -- Need RcellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellIndividualOffsetList-r18 OPTIONAL, -- Need ReventX1-SD-Threshold1-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SeventX2-SD-Threshold-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SreportOnBestCellChange-r18 ENUMERATED {n1, n2} OPTIONAL, -- Need RenteringLeavingReport-r18 ENUMERATED {true} OPTIONAL -- Need R]]}EventTriggerConfigLogging-r19::= SEQUENCE {logEventId CHOICE {logEventA1 SEQUENCE {a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},logEventA2 SEQUENCE {a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN,hysteresis Hysteresis,timeToTrigger TimeToTrigger},...},...}...

[0352] Referring to Table 9, the report type in thereportConfigNRIE may include a new separate report type for L1 measurement logging, i.e.,eventTriggeredLogging. If the report type is set toeventTriggeredLogging, thereportConfigNRIE may include an event-related configuration for L1 measurement logging, i.e.,EventTriggerConfigLoggingfield. TheEventTriggerConfigLoggingfield may include various parameters related to event A1 and / or event A2 for L1 measurement logging, but may not include parameters related to measurement reporting (e.g., report interval, report amount, etc.).

[0353] For example, theEventTriggerConfigLoggingfield may not include parameters related to measurement reporting shown in Table 10 below.

[0354] rsType NR-RS-Type,reportInterval ReportInterval,reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport),reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- Need RmaxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need RincludeBeamMeasurements BOOLEAN,reportAddNeighMeas ENUMERATED {setup} OPTIONAL, -- Need R...,[[measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need RuseT312-r16 BOOLEAN OPTIONAL, -- Need MincludeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need RincludeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need MincludeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need MincludeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M]],[[coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need RreportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R]],[[numberOfTriggeringCells-r18 INTEGER (2..maxCellReport) OPTIONAL, -- Need RcellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellIndividualOffsetList-r18 OPTIONAL, -- Need ReventX1-SD-Threshold1-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SeventX2-SD-Threshold-r18 SL-MeasTriggerQuantity-r16 OPTIONAL, -- Need SreportOnBestCellChange-r18 ENUMERATED {n1, n2} OPTIONAL, -- Need RenteringLeavingReport-r18 ENUMERATED {true} OPTIONAL -- Need R]]

[0355] 3. Implementation 3

[0356] According to the implementation 3 of the present disclosure, the UE may ignore the measurement reporting if satisfied reporting event for a corresponding measurement object is associated with themeasIdconfigured in CSI logged measurement configuration, e.g.,CSI-LoggedMeasurementConfigIE.

[0357] 4. Implementation 4

[0358] According to the implementation 4 of the present disclosure, an indication to ignore measurement reporting may be configured for a certainmeasId,or within a certain measurement object or measurement reporting configuration.

[0359] For example, ifmeasIdis related to the indication, the UE may ignore the measurement reporting.

[0360] For example, ifmeasIdis associated with the certain measurement object or measurement reporting configuration, which has the indication, the UE may ignore the measurement reporting.

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

[0362] For example, a functional and structural separation between the reporting domain and the logging domain can be enabled. By decoupling the logging operation from theReportConfigNR-based reporting procedure, a UE can perform logging-only measurement activities without being required to engage the measurement reporting machinery, thereby allowing each domain to operate independently according to its respective purpose and configuration.

[0363] For example, unnecessary reporting configuration procedures that would otherwise be mandated solely as a prerequisite for event utilization can be eliminated. Since logging behavior can be triggered and controlled without the establishment of ameasIdassociation or a correspondingReportConfigNR, the overhead associated with configuring and maintaining reporting-related parameters solely for logging purposes can be avoided.

[0364] Furthermore, by achieving the structural separation, the flexibility and efficiency of measurement management can be enhanced in various deployment scenarios where passive, non-reporting measurement collection is the primary objective (e.g., in contexts involving Minimization of Drive Tests (MDT), AI / ML-based data collection, or network optimization). The ability to independently configure and activate logging without invoking the reporting procedure can contribute to reduced signaling overhead and more streamlined measurement operations overall.

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

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

Claims

1.A method comprising:receiving, by a wireless device, a logged measurement configuration from a base station,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event, andwherein the event is associated with the event-triggered measurement logging configuration;performing, by the wireless device, a logging related to the event based on the information,wherein the event comprises at least one of an event A1 or event A2.2.The method of claim 1, wherein the event-triggered measurement logging configuration is not included in a report configuration.3.The method of claim 1, wherein the event-triggered measurement logging configuration is not related to a reporting of logging results.4.The method of claim 1, wherein the event-triggered measurement logging configuration does not comprise a report configuration related to reporting of logging results.5.The method of claim 1, wherein the event A1 is that a serving cell quality becomes better than a threshold.6.The method of claim 1, wherein the event A2 is that a serving cell quality becomes worse than a threshold.7.The method of claim 1, wherein the logged measurement configuration is a channel state information (CSI) logged measurement configuration.8.The method of claim 7, wherein the CSI logged measurement configuration defines a group of one or more CSI resources for which the wireless device logs the associated Layer-1 (L1) radio measurements.9.The method of claim 7, wherein the CSI logged measurement configuration is for a network-side data collection.10.The method of claim 1, wherein the event-triggered measurement logging configuration is used to configure the wireless device with an event-triggered measurement logging.11.The method of claim 1, wherein the event-triggered measurement logging configuration comprises an event identifier (ID) indicating the event used for measurement logging.12.The method of claim 1, wherein the logging is performed at regular time intervals based on the measurement logging triggering condition being fulfilled.13.A wireless device comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform operations comprising:receiving a logged measurement configuration from a base station,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event, andwherein the event is associated with the event-triggered measurement logging configuration;performing a logging related to the event based on the information,wherein the event comprises at least one of an event A1 or event A2.14.A processing apparatus comprising:at least one processor that is integrated with a wireless device; andat least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform operation comprising:obtaining a logged measurement configuration from a base station,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event, andwherein the event is associated with the event-triggered measurement logging configuration;performing a logging related to the event based on the information,wherein the event comprises at least one of an event A1 or event A2.15.A non-transitory Computer Readable Medium (CRM) storing instructions that, based on being executed by at least one processor, cause a wireless device to perform operations comprising:receiving a logged measurement configuration from a base station,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event, andwherein the event is associated with the event-triggered measurement logging configuration;performing a logging related to the event based on the information,wherein the event comprises at least one of an event A1 or event A2.16.A method comprising:transmitting, by a base station, a logged measurement configuration to a wireless device,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event,wherein the event is associated with the event-triggered measurement logging configuration, andwherein a logging related to the event is performed based on the information.17.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 logged measurement configuration to a wireless device,wherein the logged measurement configuration comprises an event-triggered measurement logging configuration,wherein the event-triggered measurement logging configuration comprises information related to a measurement logging triggering condition for an event,wherein the event is associated with the event-triggered measurement logging configuration, andwherein a logging related to the event is performed based on the information.

Images