Method by which device performs communication in wireless communication system and device therefor

Abstract

According to various embodiments, disclosed are a method for performing communication in a wireless communication system and a device therefor. The device may: receive information about a CSI resource configuration; receive information about a logged measurement configuration for network-side data collection; and perform logging on resources for channel measurement associated with the logging on the basis of the logged measurement configuration.

Description

A method for a device to perform communication in a wireless communication system and a device for the same

[0001] This relates to a method for a device to transmit logging measurement information in a wireless communication system and a device for this purpose.

[0002] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), and MC-FDMA (multi carrier frequency division multiple access) systems.

[0003] Sidelink (SL) refers to a communication method in which User Equipment (UE) establishes a direct link to directly exchange voice or data between terminals without passing through a Base Station (BS). SL is being considered as a solution to address the burden on base stations caused by rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-equipped objects through wired or wireless communication. V2X can be classified into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through PC5 interfaces and / or Uu interfaces.

[0005] Meanwhile, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing Radio Access Technology (RAT) is emerging. Accordingly, communication systems considering services or terminals sensitive to reliability and latency are being discussed; next-generation radio access technology that incorporates improved mobile broadband communication, Massive Machine Type Communication (MTC), and Ultra-Reliable and Low Latency Communication (URLC) can be referred to as new radio access technology (new RAT) or new radio (NR). Vehicle-to-everything (V2X) communication can also be supported in NR.

[0006] Figure 1 is a diagram illustrating a comparison between V2X communication based on RAT prior to NR and V2X communication based on NR.

[0007] Regarding V2X communication, prior to NR, RATs mainly discussed methods for providing safety services based on V2X messages such as BSM (Basic Safety Message), CAM (Cooperative Awareness Message), and DENM (Decentralized Environmental Notification Message). V2X messages can include location information, dynamic information, attribute information, etc. For example, a terminal can transmit a CAM of the periodic message type and / or a DENM of the event-triggered message type to another terminal.

[0008] For example, the CAM may include basic vehicle information such as dynamic state information of the vehicle, such as direction and speed, static data of the vehicle, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast the CAM, and the latency of the CAM may be less than 100ms. For example, in the event of an unexpected situation such as a vehicle breakdown or accident, the terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0009] Since then, various V2X scenarios regarding V2X communication have been presented in NR. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, etc.

[0010] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles belonging to said group can receive periodic data from the lead vehicle. For example, vehicles belonging to said group can use said periodic data to reduce or increase the distance between vehicles.

[0011] For example, based on enhanced driving, vehicles can be semi-automated or fully automated. For example, each vehicle can adjust trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Additionally, for example, each vehicle can mutually share driving intentions with nearby vehicles.

[0012] For example, based on extended sensors, raw data or processed data or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals and / or V2X application servers. Thus, for example, a vehicle can perceive an environment that is enhanced compared to the environment it can detect using its own sensors.

[0013] For example, based on remote driving, a remote driver or V2X application can operate or control a remote vehicle for a person unable to drive or for a remote vehicle located in a dangerous environment. For example, in cases where the route is predictable, such as in public transportation, cloud computing-based driving can be used for the operation or control of the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0014] Meanwhile, methods to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, extended sensors, and remote driving, are being discussed in NR-based V2X communication.

[0015] The technical problem that the present invention aims to solve is to provide a method for reporting logging measurement information more accurately and efficiently.

[0016] The technical problems are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0017] A method by a UE (User Equipment) according to one aspect comprises: receiving information regarding a CSI (channel state information) resource setting; receiving information regarding a logged measurement setting for network-side data collection; and performing logging for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and based on the fact that the logged measurement setting does not include logging period information, the logging may be performed at time intervals based on the period of the resources.

[0018] Alternatively, the logging may be performed at time intervals according to the cycle of the resources.

[0019] Alternatively, the logging may be performed at time intervals corresponding to n times the period of the resources (where n is an integer).

[0020] Alternatively, the value of n may be determined or pre-set based on the capabilities of the UE.

[0021] Alternatively, the above resources may include only CSI-RS (channel state information-reference signal) resources or SSB (synchronization signal block) resources among the plurality of resources included in the CSI resource configuration.

[0022] Alternatively, based on the fact that there are multiple cycles associated with the resources, the logging may be performed at time intervals corresponding to the shortest or longest cycle among the multiple cycles of the resources.

[0023] Alternatively, based on the fact that there are multiple cycles associated with the above resources, the logging may be performed at time intervals corresponding to the cycle of the resource having the lowest ID or the highest ID among the IDs (identifiers) of the above resources.

[0024] Alternatively, the method further includes the step of reporting a dataset logged by performing the logging to a base station, wherein the logged dataset may include an initial measurement or a final measurement within the time interval.

[0025] Alternatively, the method further includes a step of reporting information about the dataset logged by performing the logging to a base station, wherein the logged dataset may include the average value of the measurements within the time interval.

[0026] According to another aspect, at least one non-transient computer-readable recording medium comprises instructions for performing operations when executed by at least one processor, said operations comprising: receiving information regarding a CSI (channel state information) resource setting; receiving information regarding a logged measurement setting for network-side data collection; and performing logging for resources for channel measurement associated with logging based on said logged measurement setting, said logged measurement setting comprising information indicating said resources based on said CSI resource setting, and based on said logged measurement setting not including logging period information, said logging may be performed at time intervals based on the period of said resources.

[0027] According to another aspect, a UE (User Equipment) includes an RF (Radio Frequency) transceiver; and a processor connected to the RF transceiver, wherein the processor controls the RF transceiver to receive information regarding a CSI (channel state information) resource setting and receives information regarding a logged measurement setting for network-side data collection, and performs logging for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and based on the fact that the logged measurement setting does not include logging period information, the logging may be performed at time intervals based on the period of the resources.

[0028] According to another aspect, a processing device controlling a UE (User Equipment) comprises at least one processor; and at least one memory connected to the at least one processor and storing instructions that perform operations when executed by the at least one processor, wherein the operations include causing the UE to: receive information regarding a CSI (channel state information) resource setting; receive information regarding a logged measurement setting for network-side data collection; and perform logging for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and based on the fact that the logged measurement setting does not include logging period information, the logging may be performed at time intervals based on the period of the resources.

[0029] A method by a base station according to another aspect comprises the steps of: transmitting information regarding a CSI (channel state information) resource setting to a UE (User Equipment); transmitting information regarding a logged measurement setting for network-side data collection to the UE; and receiving CSI logging data for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and based on the fact that the logged measurement setting does not include logging period information, the CSI logging data may include measurements logged for the resources at time intervals based on the period of the resources.

[0030] A base station according to another aspect includes an RF (Radio Frequency) transceiver; and a processor connected to the RF transceiver, wherein the processor controls the RF transceiver to transmit information regarding a CSI (channel state information) resource setting to a UE (User Equipment), transmits information regarding a logged measurement setting for network-side data collection to the UE, receives CSI logging data for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and wherein the logged measurement setting does not include logging period information, the CSI logging data may include measurements logged for the resources at time intervals based on the period of the resources.

[0031] According to one embodiment of the present invention, reporting of channel measurement information in a wireless communication system can be performed more accurately and efficiently. For example, even if logging period information is not explicitly included in the log measurement settings, the logging interval can be implicitly determined based on the period of resources associated with logging, thereby allowing the UE to clearly determine the time of logging.

[0032] The effects obtainable from various embodiments are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below.

[0033] The drawings attached to this specification are intended to provide an understanding of the present invention, to illustrate various embodiments of the invention, and to explain the principles of the invention together with the description in the specification.

[0034] Figure 1 is a diagram illustrating a comparison between V2X communication based on RAT prior to NR and V2X communication based on NR.

[0035] Figure 2 shows the structure of an LTE system.

[0036] Figure 3 shows the structure of the NR system.

[0037] Figure 4 shows the structure of a wireless frame of NR.

[0038] Figure 5 shows the slot structure of an NR frame.

[0039] FIG. 6 shows a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0040] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.

[0041] Figure 8 shows the radio protocol architecture for SL communication.

[0042] Figure 9 shows a terminal performing V2X or SL communication.

[0043] Figure 10 shows a resource unit for V2X or SL communication.

[0044] FIG. 11 shows an example of a BWP according to one embodiment of the present disclosure.

[0045] FIG. 12 illustrates a procedure in which a terminal performs V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0046] FIGS. 13 and FIGS. 14 illustrate an example of a sensing operation according to an embodiment of the present disclosure.

[0047] FIG. 15 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification.

[0048] Figure 16 illustrates a general functional architecture for an AI / ML model.

[0049] Figure 17 is a diagram illustrating an inference method during AI / ML-based CSI compression.

[0050] Figure 18 is a diagram illustrating a method for performing AI / ML-based CSI prediction.

[0051] FIGS. 19 and 20 are drawings for explaining a signaling method related to a logging procedure between a terminal and a base station according to one embodiment.

[0052] Figure 21 is a diagram illustrating how a UE performs logging based on log measurement settings.

[0053] FIG. 22 is a diagram illustrating how a base station receives CSI logging data logged from a UE.

[0054] FIG. 23 illustrates a communication system to which the present invention is applied.

[0055] FIG. 24 illustrates a wireless device that can be applied to the present invention.

[0056] FIG. 25 shows another example of a wireless device to which the present invention is applied.

[0057] FIG. 26 illustrates a vehicle or autonomous vehicle to which the present invention is applied.

[0058] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), and MC-FDMA (multi carrier frequency division multiple access) systems.

[0059] Sidelink refers to a communication method in which User Equipment (UE) establishes a direct link to directly exchange voice or data between terminals without passing through a Base Station (BS). Sidelink is being considered as a solution to address the burden on base stations caused by rapidly increasing data traffic.

[0060] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-equipped objects through wired or wireless communication. V2X can be classified into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through PC5 interfaces and / or Uu interfaces.

[0061] Meanwhile, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing Radio Access Technology (RAT) is emerging. Accordingly, communication systems considering services or terminals sensitive to reliability and latency are being discussed; next-generation radio access technology that incorporates improved mobile broadband communication, Massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be referred to as new radio access technology (new RAT) or new radio (NR). Vehicle-to-everything (V2X) communication can also be supported in NR.

[0062] The following technologies can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented using wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented using wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) which uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0063] 5G NR is a successor technology to LTE-A and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0064] For clarity of explanation, the description focuses on LTE-A or 5G NR, but the technical concept of the embodiment(s) is not limited thereto.

[0065] Figure 2 shows the structure of an applicable LTE system. This can be called an E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network), or an LTE (Long Term Evolution) / LTE-A system.

[0066] Referring to FIG. 2, the E-UTRAN includes a base station (20; Base Station, BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile and may be referred to by other terms such as MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), or Wireless Device. The base station (20) refers to a fixed station that communicates with the terminal (10) and may be referred to by other terms such as eNB (evolved-NodeB), BTS (Base Transceiver System), or Access Point.

[0067] Base stations (20) can be connected to each other through an X2 interface. The base station (20) is connected to the EPC (Evolved Packet Core, 30) through the S1 interface, more specifically to the MME (Mobility Management Entity) through the S1-MME and to the S-GW (Serving Gateway) through the S1-U.

[0068] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information regarding the terminal's connection information or capabilities, and this information is primarily used for managing the terminal's mobility. The S-GW is a gateway with an E-UTRAN as its endpoint, and the P-GW is a gateway with a PDN as its endpoint.

[0069] The layers of the Radio Interface Protocol between a terminal and a network can be classified into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the lower three layers of the Open System Interconnection (OSI) model, which is widely known in communication systems. Among these, the Physical Layer, belonging to Layer 1, provides Information Transfer Services using a physical channel, while the Radio Resource Control (RRC) layer, located at Layer 3, performs the role of controlling radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0070] Figure 3 shows the structure of the NR system.

[0071] Referring to FIG. 3, the NG-RAN may include gNBs and / or eNBs that provide user plane and control plane protocol termination to terminals. FIG. 7 illustrates a case where only gNBs are included. The gNBs and eNBs are connected to each other via Xn interfaces. The gNBs and eNBs are connected to the 5G Core Network (5GC) via NG interfaces. More specifically, they are connected to the access and mobility management function (AMF) via NG-C interfaces and to the user plane function (UPF) via NG-U interfaces.

[0072] Figure 4 shows the structure of a wireless frame of NR.

[0073] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. The radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame may contain five 1 ms subframes (SF). A subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by the subcarrier spacing (SCS). Each slot may contain 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

[0074] When normal CP is used, each slot may contain 14 symbols. When extended CP is used, each slot may contain 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0075] Table 1 below shows the number of symbols per slot ((N) according to the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame((N frame,u slot ) and the number of slots per subframe((N subframe,u slot ) exemplifies.

[0076] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0077] Table 2 shows the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when an extended CP is used.

[0078] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0079] In an NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols can be configured differently among the merged cells.

[0080] In NR, multiple numerologies or SCSs may be supported to support various 5G services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. If the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

[0081] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges may be FR1 and FR2. The numerical values ​​of the frequency ranges may change, for example, as shown in Table 3 below. Among the frequency ranges used in an NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as millimeter wave (mmW).

[0082] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0083] As described above, the numerical value of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0084] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0085] Figure 5 shows the slot structure of an NR frame.

[0086] Referring to FIG. 5, a slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot may contain 14 symbols, but in the case of an extended CP, one slot may contain 12 symbols. Alternatively, in the case of a normal CP, one slot may contain 7 symbols, but in the case of an extended CP, one slot may contain 6 symbols.

[0087] A carrier includes multiple subcarriers in the frequency domain. A Resource Block (RB) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through the active BWPs. Each element can be referred to as a Resource Element (RE) in a resource grid and can be mapped to a single complex symbol.

[0088] Meanwhile, a wireless interface between terminals or a wireless interface between a terminal and a network may be composed of L1, L2, and L3 layers. In various embodiments of the present disclosure, L1 layer may refer to the physical layer. Additionally, for example, L2 layer may refer to at least one of the MAC layer, RLC layer, PDCP layer, and SDAP layer. Additionally, for example, L3 layer may refer to the RRC layer.

[0089] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0090] New network characteristics in 6G may be as follows.

[0091] - Satellite Integrated Network

[0092] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is innovative and will update wireless evolution from "connected things" to "connected intelligence." AI can be applied at each stage of the communication process (or at each step of the signal processing described below).

[0093] - Seamless integration of wireless information and energy transfer

[0094] - Ubiquitous Super 3D Connectivity: Connectivity to the network and core network functions of drones and very low Earth orbit satellites will create Super 3D connectivity in 6G ubiquitous.

[0095] Some general requirements regarding the new network characteristics of 6G mentioned above may be as follows.

[0096] - Small cell networks

[0097] - Ultra-dense heterogeneous network

[0098] - High-capacity backhaul

[0099] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communication is one of the functions of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0100] - Softwarization and virtualization

[0101] The core implementation technologies of the 6G system are described below.

[0102] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0103] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF.

[0104] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. Key characteristics of THz communication include (i) a widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array techniques that can overcome range limitations.

[0105] - Large-scale MIMO technology

[0106] - Hologram beamforming (HBF)

[0107] - Optical wireless technology

[0108] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0109] - Quantum communication

[0110] - Cell-free communication

[0111] - Integration of wireless information and power transmission

[0112] - Integration of wireless communication and sensing

[0113] - Integrated access and backhaul network

[0114] - Big data analysis

[0115] - Reconfigurable intelligent metasurface

[0116] - Metaverse

[0117] - blockchain

[0118] - Unmanned Aerial Vehicle (UAV): UAVs or drones will be a critical element in 6G wireless communication. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base station (BS) entities can be installed on UAVs to provide cellular connectivity. UAVs can possess specific features not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled degrees of freedom for mobility. During emergencies, such as natural disasters, the deployment of ground communication infrastructure is not economically feasible, and sometimes services cannot be provided in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in the field of wireless communication. This technology facilitates the three fundamental requirements of wireless networks: eMBB, URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most critical technologies for 6G communication.

[0119] - Autonomous Driving (Self-Driving): V2X (Vehicle to Everything), a core element in building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road for autonomous driving, such as wireless communication between vehicles (Vehicle to Vehicle, V2V) and between vehicles and infrastructure (Vehicle to Infrastructure, V2I). Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, future autonomous driving may go beyond simply delivering warning or guidance messages to the driver to actively intervene in vehicle operation and directly control the vehicle in dangerous situations. Since the amount of information to be transmitted and received may become massive for this purpose, it is expected that 6G will be able to maximize autonomous driving through faster transmission speeds and lower latency compared to 5G.

[0120] FIG. 8 illustrates a radio protocol architecture for SL communication. Specifically, FIG. 8 (a) shows the user plane protocol stack of NR, and FIG. 8 (b) shows the control plane protocol stack of NR.

[0121] The Sidelink Synchronization Signal (SLSS) and synchronization information are described below.

[0122] SLSS is an SL-specific sequence that may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal), and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS, and length-127 Gold sequences may be used for S-SSS. For example, a terminal may use S-PSS to detect a primary signal and obtain synchronization. For example, a terminal may use S-PSS and S-SSS to obtain detailed synchronization and detect a synchronization signal ID.

[0123] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel through which basic (system) information that a terminal must know first is transmitted before transmitting or receiving SL signals. For example, the basic information may include information related to SLSS, Duplex Mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, information related to resource pools, types of applications related to SLSS, subframe offsets, broadcast information, etc. For example, to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0124] S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP lengths) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) within the carrier, and the transmission bandwidth may be within a (pre-)set SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RB (Resource Block). For example, the PSBCH may span 11 RB. Additionally, the frequency position of the S-SSB may be (pre-)set. Therefore, the terminal does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0125] Meanwhile, in an NR SL system, multiple numerologies having different SCS and / or CP lengths may be supported. In this case, as the SCS increases, the length of the time resource for the transmitting terminal to transmit S-SSBs may decrease. Consequently, the coverage of S-SSBs may decrease. Therefore, to ensure S-SSB coverage, the transmitting terminal may transmit one or more S-SSBs to the receiving terminal within a single S-SSB transmission cycle according to the SCS. For example, the number of S-SSBs transmitted by the transmitting terminal to the receiving terminal within a single S-SSB transmission cycle may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission cycle may be 160ms. For example, an S-SSB transmission cycle of 160ms may be supported for all SCSs.

[0126] For example, if the SCS is 15 kHz at FR1, the transmitting terminal may transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission cycle. For example, if the SCS is 30 kHz at FR1, the transmitting terminal may transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission cycle. For example, if the SCS is 60 kHz at FR1, the transmitting terminal may transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission cycle.

[0127] For example, if the SCS is 60 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, or 32 S-SSBs to the receiving terminal within one S-SSB transmission cycle. For example, if the SCS is 120 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, 32, or 64 S-SSBs to the receiving terminal within one S-SSB transmission cycle.

[0128] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. Additionally, depending on the CP type, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may differ. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, if the CP type is NCP, the number of symbols mapping PSBCH within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, if the CP type is ECP, the number of symbols mapping PSBCH within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, PSBCH may be mapped to the first symbol within the S-SSB transmitted by the transmitting terminal. For example, the receiving terminal receiving the S-SSB may perform Automatic Gain Control (AGC) operation during the first symbol interval of the S-SSB.

[0129] Figure 9 shows a terminal performing V2X or SL communication.

[0130] Referring to FIG. 9, in V2X or SL communication, the term terminal may primarily refer to a user's terminal. However, if network equipment such as a base station transmits and receives signals according to the communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0131] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the said resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect terminal 1's signal within said resource pool.

[0132] Here, if terminal 1 is within the connection range of the base station, the base station may inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal may inform terminal 1 of the resource pool, or terminal 1 may use a pre-configured resource pool.

[0133] Generally, a resource pool can be composed of multiple resource units, and each terminal can select one or more resource units to use for its SL signal transmission.

[0134] Figure 10 shows a resource unit for V2X or SL communication.

[0135] Referring to FIG. 10, the total frequency resources of the resource pool can be divided into NF units, and the total time resources of the resource pool can be divided into NT units. Thus, a total of NF * NT resource units can be defined within the resource pool. FIG. 10 illustrates an example where the resource pool is repeated in a period of NT subframes.

[0136] As shown in FIG. 10, a single resource unit (e.g., Unit #0) may appear repeatedly over time. Alternatively, to obtain diversity effects in the time or frequency dimension, the index of the physical resource unit to which a single logical resource unit is mapped may change in a predetermined pattern over time. In this structure of resource units, a resource pool may refer to a set of resource units that a terminal intending to transmit an SL signal can use for transmission.

[0137] Resource pools can be subdivided into several types. For example, depending on the content of the SL signals transmitted from each resource pool, resource pools can be classified as follows.

[0138] (1) A Scheduling Assignment (SA) may be a signal containing information such as the location of the resource used by the transmitting terminal for transmission of the SL data channel, the Modulation and Coding Scheme (MCS) or Multiple Input Multiple Output (MIMO) transmission method required for demodulation of the data channel, and Timing Advance (TA). The SA may also be multiplexed and transmitted together with the SL data on the same resource unit, in which case the SA resource pool may refer to a resource pool in which the SA is multiplexed and transmitted together with the SL data. The SA may also be called the SL control channel.

[0139] (2) A Physical Sidelink Shared Channel (PSSCH) may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted along with SL data on the same resource unit, only the form of the SL data channel excluding SA information can be transmitted from the resource pool for the SL data channel. In other words, REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool can still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal can transmit by mapping the PSSCH to a succession of PRBs.

[0140] (3) The discovery channel may be a resource pool for a transmitting terminal to transmit information such as its ID. Through this, the transmitting terminal can enable adjacent terminals to discover it.

[0141] Even if the content of the SL signal described above is the same, different resource pools may be used depending on the transmission and reception attributes of the SL signal. For example, even if the same SL data channel or discovery message is used, it may be divided into different resource pools depending on the method of determining the transmission timing of the SL signal (e.g., whether it is transmitted at the time of reception of the synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the method of resource allocation (e.g., whether the base station assigns the transmission resource of an individual signal to the individual transmission terminal or whether the individual transmission terminal selects the individual signal transmission resource itself from within the resource pool), the signal format (e.g., the number of symbols occupied by each SL signal in one subframe, or the number of subframes used for the transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

[0142] FIG. 11 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure. In the embodiment of FIG. 11, it is assumed that there are three BWPs.

[0143] Referring to FIG. 11, the common resource block (CRB) may be a numbered carrier resource block extending from one end of the carrier band to the other. And, the PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0144] A BWP can be configured by point A, an offset from point A (NstartBWP), and a bandwidth (NsizeBWP). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) is aligned. For example, the offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, the bandwidth may be the number of PRBs in a given numerology.

[0145] SLSS (Sidelink Synchronization Signal) is a sidelink-specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal), and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS, and length-127 Gold sequences may be used for S-SSS. For example, a terminal may use S-PSS to detect the initial signal and obtain synchronization. For example, a terminal may use S-PSS and S-SSS to obtain detailed synchronization and detect the synchronization signal ID.

[0146] The PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel through which basic (system) information that the terminal must know first is transmitted before transmitting or receiving SL signals. For example, the basic information may include information related to SLSS, Duplex Mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, information related to resource pools, types of applications related to SLSS, subframe offsets, broadcast information, etc. For example, to evaluate PSBCH performance, in NR V2X, the payload size of the PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0147] S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP lengths) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) within the carrier, and the transmission bandwidth may be within a (pre-)set SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RB (Resource Block). For example, the PSBCH may span 11 RB. Additionally, the frequency position of the S-SSB may be (pre-)set. Therefore, the terminal does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0148] FIG. 12 illustrates a procedure in which a terminal performs V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0149] Referring to FIG. 12(a), in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S1200, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0150] For example, the first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from the base station. For example, the CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, the DG resource may be a resource that the base station sets / assigns to the first terminal via downlink control information (DCI). In this specification, the CG resource may be a (periodic) resource that the base station sets / assigns to the first terminal via DCI and / or RRC messages. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message containing information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message containing information related to the CG resource to the first terminal, and the base station may transmit DCI related to the activation or release of the CG resource to the first terminal.

[0151] In step S1210, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) associated with the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH associated with the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S1240, the first terminal may transmit / report the HARQ feedback information to the base station via a PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a pre-set rule. For example, the DCI may be a DCI for scheduling SL.

[0152] Referring to FIG. 12(b), in resource allocation mode 2, the terminal can determine an SL transmission resource within an SL resource set by the base station / network or a preset SL resource. For example, the set SL resource or the preset SL resource may be a resource pool. For example, the terminal may autonomously select or schedule a resource for SL transmission. For example, the terminal may perform SL communication by selecting a resource itself within the set resource pool. For example, the terminal may select a resource itself within a selection window by performing a sensing and resource (re)selection procedure. For example, the sensing may be performed on a subchannel basis. For example, in step S1210, the first terminal, having selected a resource itself within the resource pool, may use the resource to transmit PSCCH (e.g., SCI (Sidelink Control Information) or 1st-stage SCI) to the second terminal. In step S1220, the first terminal can transmit PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) associated with the PSCCH to the second terminal. In step S1230, the first terminal can receive PSFCH associated with the PSCCH / PSSCH from the second terminal.

[0153] Referring to FIG. 12 (a) or (b), for example, the first terminal may transmit an SCI to the second terminal over the PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal over the PSCCH and / or PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted over the PSCCH may be referred to as the 1st SCI, the 1st SCI, the 1st-stage SCI, or the 1st-stage SCI format, and an SCI transmitted over the PSSCH may be referred to as the 2nd SCI, the 2nd SCI, the 2nd-stage SCI, or the 2nd-stage SCI format.

[0154] Referring to FIG. 12 (a) or (b), in step S1230, the first terminal can receive PSFCH. For example, the first terminal and the second terminal can determine a PSFCH resource, and the second terminal can use the PSFCH resource to transmit HARQ feedback to the first terminal.

[0155] Referring to FIG. 12(a), in step S1240, the first terminal can transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0156] CSI Measurement / Reporting

[0157] In NR (New Radio) systems, CSI-RS (channel state information-reference signal) is used for time and / or frequency tracking, CSI computation, L1 (layer 1)-RSRP (reference signal received power) computation, and mobility. Here, CSI computation is related to CSI acquisition, and L1-RSRP computation is related to beam management (BM). CSI (channel state information) is a general term for information that can indicate the quality of the radio channel (also called a link) formed between a terminal and an antenna port.

[0158] A base station can transmit CSI-RS to a terminal to determine the characteristics of the downlink channel, and can receive feedback from the terminal regarding channel measurement results based on CSI-RS.

[0159] CSI-RS may be configured for one or more terminals. Different CSI-RS configurations may be provided for each terminal, or the same CSI-RS configuration may be provided for multiple terminals. CSI-RS may support up to 32 antenna ports. CSI-RS corresponding to N (N is 1 or more) antenna ports may be mapped to N RE positions within a time-frequency unit corresponding to one slot and one RB. If N is 2 or more, N-port CSI-RS may be multiplexed in CDM, FDM, and / or TDM modes. A CDM group may include two antenna ports (CDM2) distinguished by code resources on the same two adjacent subcarriers, four antenna ports (CDM4) distinguished by code resources on the same two adjacent subcarriers and the same two adjacent OFDM slots, or eight antenna ports (CDM8) distinguished by code resources on the same two adjacent subcarriers and the same four adjacent OFDM slots. If multiple CDM groups exist, the CDM groups may not be mapped to adjacent subcarriers and / or adjacent OFDM symbols. CSI-RS antenna ports can be indexed in the order of CDM groups, frequency domain, and time domain. CSI-RS can be mapped to REs other than the REs to which CORESET, DMRS, and SSB are mapped.

[0160] In the frequency domain, CSI-RS can be configured for the entire bandwidth, a portion of the bandwidth (BWP), or a portion of the bandwidth. CSI-RS may be transmitted at each RB within the configured bandwidth (i.e., density=1), or at every second RB (e.g., the even or odd RB) (i.e., density=1 / 2). When CSI-RS is used as a Tracking Reference Signal (TRS), a single-port CSI-RS may be mapped onto three subcarriers in each resource block (i.e., density=3).

[0161] One or more CSI-RS resource sets may be configured for the terminal in the time domain. Each CSI-RS resource set may include one or more CSI-RS settings.

[0162] Each CSI-RS resource set can be configured to be periodic, semipersistent, or non-periodic. For periodic CSI-RS resource sets, the period can be configured to a number of slots ranging from 4 to 640. Additionally, a starting offset value for periodic CSI-RS resource sets can be configured. For semipersistent CSI-RS resource sets, an offset and period for CSI-RS resource set candidates can be configured. Here, actual CSI-RS transmission can be activated / deactivated based on a MAC Control Element (CE). When a CSI-RS resource set is activated, CSI-RS transmission may be performed according to the configured offset and period until it is deactivated. When a CSI-RS resource set is deactivated, CSI-RS transmission may not be performed until it is explicitly reactivated. For non-periodic CSI-RS transmission, information regarding each CSI-RS resource set may be explicitly provided by the DCI.

[0163] A CSI-IM resource may be configured for Interference Measurement (IM) of a terminal. A CSI-IM resource may contain four REs within one slot and one resource block. The four REs may correspond to two consecutive OFDM symbols and two consecutive subcarriers, or to one OFDM symbol and four consecutive subcarriers. In the frequency domain, the location of the CSI-IM REs may be determined by the CSI-IM configuration. In the time domain, the CSI-IM resource set may be configured periodic, semi-persistent, or non-periodically, similar to the CSI resource set. Generally, transmission may not be performed in the corresponding cell but may be performed in a neighboring cell. As such, the CSI-IM resource may be configured as Zero Power (ZP)-CSI-RS for the terminal.

[0164] ZP-CSI-RS can be configured to be distinct from Non-Zero Power (NZP)-CSI-RS. When a PDSCH is scheduled on a resource containing a CSI-RS RE, the first terminal may assume that rate matching considering the CSI-RS RE is applied to the PDSCH, so that the PDSCH is not mapped to the CSI-RS RE. Here, the CSI-RS may be configured for the first terminal or for the second terminal. In this case, the CSI-RS for the first terminal may be configured as NZP-CSI-RS for the first terminal, and an NZP-CSI-RS resource set may be configured for the first terminal. Meanwhile, the CSI-RS for the second terminal may be configured as ZP-CSI-RS for the first terminal, and a ZP-CSI-RS resource set may be configured for the first terminal. The NZP-CSI-RS resource set can be used for the CSI report configuration of the terminal. The NZP-CSI-RS resource set may also be associated with a CSI-RS or an SSB. Additionally, multiple periodic NZP-CSI-RS resource sets can be configured as TRS resource sets.

[0165] CSI-related operations can be summarized as follows.

[0166] To perform one of the uses of CSI-RS, a terminal (e.g., user equipment, UE) receives configuration information related to CSI from a base station (e.g., general Node B, gNB) via radio resource control (RRC) signaling. The configuration information related to CSI may include at least one of information related to CSI-IM (interference management) resources, information related to CSI measurement configuration, information related to CSI resource configuration, information related to CSI-RS resources, or information related to CSI report configuration.

[0167] - CSI-IM resource-related information may include CSI-IM resource information, CSI-IM resource set information, etc. A CSI-IM resource set is identified by a CSI-IM resource set ID (identifier), and one resource set includes at least one CSI-IM resource. Each CSI-IM resource is identified by a CSI-IM resource ID.

[0168] - Information related to CSI resource configuration can be expressed as CSI-ResourceConfig IE. Information related to CSI resource configuration defines a group that includes at least one of an NZP (non-zero power) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the information related to CSI resource configuration includes a CSI-RS resource set list, and the CSI-RS resource set list may include at least one of an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID. Through the NZP CSI-RS resource set IE, parameters indicating the use of CSI-RS (e.g., a BM-related 'repetition' parameter, a tracking-related 'trs-Info' parameter) can be set for each NZP CSI-RS resource set. Also, the repetition parameter corresponding to the higher layer parameter corresponds to 'CSI-RS-ResourceRep' of the L1 parameter.

[0169] - Information related to CSI report configuration includes a reportConfigType parameter representing time domain behavior and a reportQuantity parameter representing the CSI-related quantity to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent. Information related to CSI report configuration may be expressed as CSI-ReportConfig IE.

[0170] The terminal measures the CSI based on configuration information related to the above CSI. The terminal's CSI measurement may include a process of receiving CSI-RS on a CSI-RS RE specified based on the higher layer parameter CSI-RS-ResourceMapping, and computing the CSI through the received CSI-RS. By CSI-RS-ResourceMapping, the RE (resource element) mapping of the CSI-RS resource in the time and frequency domains is set for the terminal. In CSI-RS-ResourceMapping, density (D) represents the density of the CSI-RS resource measured in the RE / port / PRB (physical resource block), and nrofPorts represents the number of antenna ports.

[0171] The terminal reports the measured CSI to the base station. If the quantity of CSI-ReportConfig is set to 'none (or No report)', the terminal may omit the CSI report. However, even if the quantity is set to 'none (or No report)', the terminal may still report to the base station. The case where the quantity is set to 'none' is when the aperiodic TRS is triggered or when repetition is enabled. Here, the terminal may omit the report only when repetition is set to 'ON'.

[0172] As time domain behaviors for CSI measurement and reporting, aperiodic / semi-persistent / periodic CM (channel measurement) and IM (interference measurement) are supported. A 4-port NZP CSI-RS RE pattern is used for CSI-IM configuration.

[0173] NR's CSI-IM-based Interference Measurement Resource (IMR) has a design similar to LTE's CSI-IM and is configured independently of ZP CSI-RS resources for PDSCH rate matching. In addition, in the NZP CSI-RS-based IMR, each port emulates an interference layer with (desired channel and) precoded NZP CSI-RS. This is for intra-cell interference measurement in the multi-user case and primarily targets MU interference.

[0174] The base station transmits precoded NZP CSI-RS to the terminal on each port of the configured NZP CSI-RS-based IMR.

[0175] The terminal assumes a channel / interference layer for each port in the resource set and measures interference.

[0176] For a channel, if there is no PMI and RI feedback, multiple resources are set, and the base station or network indicates a subset of NZP CSI-RS resources for channel / interference measurement via DCI.

[0177] Each CSI resource setting 'CSI-ResourceConfig' contains a configuration for S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList). The CSI resource setting corresponds to the CSI-RS-resourcesetlist, where S represents the number of configured CSI-RS resource sets. Here, the list of S≥1 CSI resource sets includes either or both of the NZP CSI-RS resource set(s) and the SS / PBCH block (SSB) set(s) used for L1-RSRP computation, or includes CSI-IM resource set(s).

[0178] Each CSI resource setting is located in a DL BWP (bandwidth part) identified by a higher layer parameter BWP-id. Additionally, all CSI resource settings linked to a CSI reporting setting have the same DL BWP.

[0179] Within the CSI resource setting included in CSI-ResourceConfig IE, the time domain behavior of the CSI-RS resource is dictated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, the number of configured CSI-RS resource sets (S) is limited to '1'. For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given from the numerology of the associated DL BWP, as given by the BWP-id.

[0180] When a UE is configured with multiple CSI-ResourceConfigs containing the same NZP CSI-RS resource ID, the same time domain behavior is configured for the multiple CSI-ResourceConfigs.

[0181] When a UE is configured with multiple CSI-ResourceConfigs containing the same CSI-IM resource ID, the same time domain behavior is configured for the multiple CSI-ResourceConfigs.

[0182] Next, one or more CSI resource settings for channel measurement (CM) and interference measurement (IM) are established through higher layer signaling.

[0183] - CSI-IM resource for interference measurement.

[0184] - NZP CSI-RS resources for interference measurement.

[0185] - NZP CSI-RS resources for channel measurement.

[0186] That is, the CMR (channel measurement resource) may be an NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) may be an NZP CSI-RS for CSI-IM and IM.

[0187] Here, CSI-IM (or ZP CSI-RS for IM) is primarily used for inter-cell interference measurements.

[0188] Also, the NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multi-users.

[0189] A UE can assume that the CSI-RS resource(s) for channel measurement set for one CSI reporting and the CSI-IM / NZP CSI-RS resource(s) for interference measurement (when NZP CSI-RS resource(s) are used for interference measurement) have a QCL relationship with respect to 'QCL-TypeD' on a resource-by-resource basis.

[0190] As examined, resource setting can refer to a resource set list.

[0191] For aperiodic CSI, each trigger state set using the higher layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, and each CSI-ReportConfig is linked to a periodic, semi-persistent, or aperiodic resource setting.

[0192] One reporting setting can be linked to up to three resource settings.

[0193] - When a resource setting is set, that resource setting (given by the higher layer parameter resourcesForChannelMeasurement) is for channel measurement for L1-RSRP computation or channel and interference measurement for L1-SINR computation.

[0194] - When two resource settings are set, the first resource setting (given by the higher layer parameter resourcesForChannelMeasurement) is for channel measurement, and the second resource setting (given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) is for interference measurement performed on CSI-IM or NZP CSI-RS.

[0195] - When three resource settings are set, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, the second resource setting (given by csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement, and the third resource setting (given by nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement.

[0196] For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to periodic or semi-persistent resource setting(s).

[0197] - When a resource setting (given by resourcesForChannelMeasurement) is configured, said resource setting is for channel measurement for L1-RSRP computation or channel and interference measurement for L1-SINR computation.

[0198] - When two resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, and the second resource setting (given by higher layer parameter csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) is used for interference measurement performed on CSI-IM or NZP CSI-RS.

[0199] When interference measurements are performed on CSI-IM, each CSI-RS resource for channel measurement is associated with a CSI-IM resource by resource in the order of CSI-RS resources and CSI-IM resources within the corresponding resource set. The number of CSI-RS resources for channel measurement is equal to the number of CSI-IM resources.

[0200] And, when interference measurement is performed in NZP CSI-RS, the UE does not expect to be set to one or more NZP CSI-RS resources in the associated resource set within the resource setting for channel measurement.

[0201] A terminal with the Higher layer parameter nzp-CSI-RS-ResourcesForInterference configured does not expect more than 18 NZP CSI-RS ports to be configured within a single NZP CSI-RS resource set.

[0202] For CSI measurement(s) other than L1-SINR, the terminal assumes the following:

[0203] - Each NZP CSI-RS port configured for interference measurement corresponds to the interference transport layer.

[0204] - All interference transmission layers of the NZP CSI-RS port for interference measurement consider the associated EPRE (energy per resource element) ratio.

[0205] - Other interference signals on the RE(s) of the NZP CSI-RS resource for channel measurement, the NZP CSI-RS resource for interference measurement, or the CSI-IM resource for interference measurement.

[0206] The terminal can perform measurements of channel characteristics based on CSI-RS and feed back a CSI report to the base station as a result. To this end, a CSI report configuration may be provided to the terminal. Each CSI report configuration may include settings for feedback type, measurement resource, report type, etc.

[0207] Feedback types may include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SSBRI (SSB Resource block Indicator), Layer Indicator (LI), Rank Indicator (RI), Layer 1-Reference Signal Received Strength (RSRP), etc.

[0208] The measurement resource may include settings for downlink signals and / or downlink resources for which the terminal will perform measurements to determine feedback information. The measurement resource may be set as a set of ZP and / or NZP CSI-RS resources associated with a CSI reporting setting. The NZP CSI-RS resource set may include a CSI-RS set or an SSB set. For example, L1-RSRP may be measured against a CSI-RS set or against an SSB set.

[0209] The report type may include settings for the timing at which the terminal performs the report and the uplink channel, etc. The reporting timing may be set to periodic, semi-persistent, or non-periodic. Periodic CSI reports may be transmitted over the PUCCH. Semi-persistent CSI reports may be transmitted over the PUCCH or PUSCH based on MAC CEs indicating activation / deactivation. Non-periodic CSI reports may be indicated by DCI signaling. For example, the CSI request field of an uplink grant may indicate one of various report trigger sizes. Non-periodic CSI reports may be transmitted over the PUSCH.

[0210] CSI can be defined as two types. Type 1 CSI may be associated with cases where a single user is scheduled, and Type 2 CSI may be associated with cases where multiple users are scheduled simultaneously on the same resource. Type 1 CSI may include single-panel CSI and multi-panel CSI, each of which may correspond to a different codebook. The precoding matrix in the codebook may be specified by a combination of w1 and w2. Long-term and wideband characteristics may correspond to w1, and short-term and subband characteristics may correspond to w2. While Type 1 CSI reports one precoding matrix selected by the terminal, Type 2 CSI may report information on the magnitude and phase of up to four beams.

[0211] For CSI reporting, the time and frequency resources available to the UE are controlled by the base station.

[0212] Channel state information (CSI) may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, and / or L-SINR.

[0213] For CQI, PMI, CRI, SSBRI, LI, RI, and L1-RSRP, the terminal is configured by a higher layer with N≥1 CSI-ReportConfig reporting settings, M≥1 CSI-ResourceConfig resource settings, and a list of one or two trigger states (provided by CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). In the CSI-AperiodicTriggerStateList, each trigger state includes an associated list of CSI-ReportConfigs indicating resource set IDs for the channel and optionally interference. In the CSI-SemiPersistentOnPUSCH-TriggerStateList, each trigger state includes one associated CSI-ReportConfig.

[0214] In addition, the time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic.

[0215] i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periodicity and slot offset of Periodic CSI reporting can be set to RRC, and refer to CSI-ReportConfig IE.

[0216] ii) SP (semi-periodic) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH.

[0217] In the case of SP CSI on Short / long PUCCH, the periodicity and slot offset are set to RRC, and CSI reporting is activated / deactivated with a separate MAC CE / DCI.

[0218] In the case of SP CSI on PUSCH, the periodicity of SP CSI reporting is set to RRC, but the slot offset is not set to RRC, and SP CSI reporting is activated / deactivated by DCI(format 0_1). For SP CSI reporting on PUSCH, a separate RNTI (SP-CSI C-RNTI) is used.

[0219] The initial CSI reporting timing follows the PUSCH time domain allocation value specified by DCI, and subsequent CSI reporting timing follows the period set by RRC.

[0220] DCI format 0_1 ​​includes a CSI request field and can activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting has the same or similar activation / deactivation mechanism as the data transmission mechanism on SPS PUSCH.

[0221] iii) aperiodic CSI reporting is performed on PUSCH and triggered by DCI. In this case, information related to the trigger of aperiodic CSI reporting can be transmitted / instructed / set via MAC-CE.

[0222] In the case of an AP CSI with AP CSI-RS, the AP CSI-RS timing is set by the RRC, and the timing for AP CSI reporting is dynamically controlled by the DCI.

[0223] NR does not apply the method of splitting CSIs across multiple reporting instances (e.g., transmitting in the order of RI, WB PMI / CQI, SB PMI / CQI) that was applied to PUCCH-based CSI reporting in LTE. Instead, NR restricts the setting of specific CSI reports in short / long PUCCHs, and CSI omission rules are defined. Regarding AP CSI reporting timing, the PUSCH symbol / slot location is dynamically determined by the DCI, and candidate slot offsets are set by the RRC. For CSI reporting, the slot offset (Y) is set per reporting setting. For UL-SCH, the slot offset K2 is set separately.

[0224] Two CSI latency classes (low latency class and high latency class) are defined in terms of CSI computation complexity. Low-latency CSI refers to WB CSIs that include up to 4-port Type-I codebooks or up to 4-port non-PMI feedback CSIs. High-latency CSI refers to any CSI other than low-latency CSIs. For a normal terminal, (Z, Z') is defined in the unit of OFDM symbols. Here, Z represents the minimum CSI processing time from receiving an Aperiodic CSI-triggering DCI to performing a CSI report. Additionally, Z' represents the minimum CSI processing time from receiving a CSI-RS for channel / interference to performing a CSI report.

[0225] Additionally, the terminal reports the number of CSIs that can be calculated simultaneously.

[0226] The activation / deactivation of a semi-persistent CSI-RS / CSI-IM resource set is directed by the network via a specific MAC CE. The configured semi-persistent CSI-RS / CSI-IM resource set is initially deactivated at the time of configuration and after handover. The MAC entity receiving the corresponding MAC CE instructs the lower layer (e.g., PHY) with the information related to that MAC CE.

[0227] Aperiodic CSI Trigger State subselection is directed from the network via a specific MAC CE, and an Aperiodic CSI Trigger State can be selected from the configured AP CSI trigger states of the serving cell. The MAC entity receiving the corresponding MAC CE instructs the lower layer (e.g., PHY) with information related to that MAC CE.

[0228] Integrated Sensing and Communication (ISAC)

[0229] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, that is, the sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.

[0230] FIGS. 13 and FIGS. 14 illustrate examples of sensing operations according to an embodiment of the present disclosure. Specifically, FIG. 13 illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 14 illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0231] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 13, the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 14, the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.

[0232] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.

[0233] - Mode 1: A mode in which the sensing transmitter and sensing receiver are included in a single base station (e.g., base station-based sensing mode in monostatic mode)

[0234] - Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode)

[0235] - 3rd Mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode)

[0236] - 4th Mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode)

[0237] - 5th Mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode)

[0238] - 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode)

[0239] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently or in combination.

[0240] In relation to the sensing operation in FIGS. 13 and 14, a sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present specification. A sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on a 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0241] Additionally, the sensing operation in FIGS. 13 and 14 is described using a wireless communication system based on a 6G network as a representative example, but it can be extended and applied to cases where terminals / base stations / signals based on previous generations (e.g., 4G, 5G, etc.) networks are utilized.

[0242] Additionally, with respect to the wireless sensing described in this specification, in a wireless communication system based on a 6G network of this specification, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.

[0243] FIG. 15 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.

[0244] Referring to FIG. 15, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 13 and FIG. 14) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.

[0245] For example, as illustrated in FIG. 15, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally or alternatively, unlike those illustrated in FIG. 13 and FIG. 14, sensing resources may also be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).

[0246] Additionally or alternatively, in relation to the setup / allocation / scheduling of resources for general communication described herein, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to the embodiments of the present disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of the present disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are set / allocated / scheduled to overlap according to the embodiments of the present disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of this specification, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.

[0247] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described herein. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.

[0248] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be optimized and configured differently. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of this specification may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.

[0249] artificial intelligence

[0250] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0251] The following describes a functional framework for AI / ML operations.

[0252] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.

[0253] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.

[0254] - AI Model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0255] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0256] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.

[0257] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.

[0258] Figure 16 illustrates a general functional architecture for an AI / ML model.

[0259] In particular, FIG. 16 illustrates a general functional architecture related to both Functionality-based LCM and Model-based LCM. Some functions or some data / information / command flows (i.e., arrows) illustrated in FIG. 16 may be omitted.

[0260] Referring to FIG. 16, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0261] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.

[0262] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).

[0263] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the Training Data (11) delivered from the Data Collection function (10).

[0264] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).

[0265] The Management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the Management function (30) may make decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).

[0266] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).

[0267] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0268] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).

[0269] The inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).

[0270] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0271] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40). The Model Storage function (50) exemplified in FIG. 15 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the Model Storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model and may be omitted.

[0272] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

[0273] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.

[0274] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.

[0275] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.

[0276] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0277] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0278] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0279] A one-side model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.

[0280] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.

[0281] - First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.

[0282] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use cases) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).

[0283] - Third Type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0284] Logged Measurement

[0285] The purpose of the above Logged Measurement procedure is to configure the UE to perform logging of measurement results in the RRC_IDLE and RRC_INACTIVE states. The above procedure can be applied to a UE that supports the logging measurement function in the RRC_CONNECTED state. Meanwhile, NG-RAN can obtain the stored logged measurement information through the UE information procedure.

[0286] NG-RAN can initiate a logged measurement configuration procedure by sending a LoggedMeasurementConfiguration message to a UE in the RRC_CONNECTED state.

[0287] When the UE receives LoggedMeasurementConfiguration, it can perform the following actions.

[0288] 1> Discard log measurement settings and log measurement information.

[0289] 1> Store the received loggingDuration, reportType, and areaConfiguration (if included) in VarLogMeasConfig.

[0290] 1> If the UE is in SNPN access mode:

[0291] 2> If the LoggedMeasurementConfiguration message contains snpn-ConfigList:

[0292] 3> Configure VarLogMeasReport's snpn-ConfigIDList to include the currently registered SNPN identity and the SNPN identifiers within snpn-ConfigList.

[0293] 2> Other cases:

[0294] 3> Set the snpn-ConfigIDList of VarLogMeasReport to include the currently registered SNPN identifier.

[0295] 1> In addition, if the LoggedMeasurementConfiguration message includes plmn-IdentityList:

[0296] 2> Set VarLogMeasReport's plmn-IdentityList to include RPLMN and PLMNs included in plmn-IdentityList.

[0297] 1> Other cases:

[0298] 2> Set VarLogMeasReport's plmn-IdentityList to include RPLMN.

[0299] 1> Save the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id to VarLogMeasReport.

[0300] 1> If the received bt-NameList is included, save it to VarLogMeasConfig.

[0301] 1> If the received wlan-NameList is included, save it to VarLogMeasConfig.

[0302] 1> If the received sensor-NameList is included, save it to VarLogMeasConfig.

[0303] 1> Start timer T330 with the timer value set to loggingDuration.

[0304] 1> If the received sigLoggedMeasType is included, save it to VarLogMeasReport.

[0305] 1> If the received earlyMeasIndication is included, save it to VarLogMeasConfig.

[0306] When timer T330 expires, the UE can disable VarLogMeasConfig. Additionally, the UE can discard the stored log measurement information, namely VarLogMeasReport, after 48 hours have elapsed since the expiration of T330.

[0307] The above procedure for releasing log measurement settings may be a procedure for releasing log measurement settings and log measurement information. The UE may initiate the above procedure when it receives log measurement settings from the same RAT or a different RAT, or when power off or deregistration occurs. In this case, the UE may stop the operating timer T330 and discard the log measurement settings and log measurement information by releasing the UE variables VarLogMeasConfig and VarLogMeasReport if the stored log measurement settings and log measurement information exist.

[0308] The specific details regarding the measurements logging procedure may be as follows.

[0309] The measurement logging procedure defines the process by which a UE with a logged measurement configuration logs available measurement results in the RRC_IDLE and RRC_INACTIVE states. The actual logging process performed within the UE may be initiated in the RRC_IDLE state and continue in the RRC_INACTIVE state, and vice versa.

[0310] In relation to the initiation of the measurement logging procedure, while timer T330 is running and the SDT procedure is not in progress, the UE must perform the following action.

[0311] 1> If measurement logging is stopped:

[0312] 2> If the IDC issues detected by the UE during the previous logging period are resolved, measurement logging is resumed.

[0313] 1> If measurement logging is not interrupted, logging is performed according to the following.

[0314] 2> When reportType is set to periodical in VarLogMeasConfig:

[0315] 3> When the UE is in any cell selection state (as specified in TS 38.304):

[0316] 4> Logging is performed at regular time intervals defined by the loggingInterval of VarLogMeasConfig.

[0317] 3> Or if the UE is in a normally camped state on the NR cell and the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport,

[0318] 3> Or if the UE is in a normal camping state on an NR cell and the registered SNPN identifier is included in the snpn-ConfigIDList stored in VarLogMeasReport:

[0319] 4> VarLogMeasConfig does not include areaConfiguration, or

[0320] 4> If the serving cell is contained within the area specified by areaConfig in VarLogMeasConfig's areaConfiguration,

[0321] 4> If the serving cell is contained within the area indicated by cag-ConfigList in VarLogMeasConfig's areaConfiguration,

[0322] 4> If the serving cell is contained within the area indicated by snpn-ConfigList in VarLogMeasConfig's areaConfiguration:

[0323] 5> Logging is performed at regular time intervals defined by the loggingInterval of VarLogMeasConfig.

[0324] 2> Or if reportType is set to eventTriggered and eventType is set to outOfCoverage:

[0325] 3> Logging is performed at regular time intervals defined by the loggingInterval of VarLogMeasConfig only when the UE is in an arbitrary cell selection state.

[0326] 3> When the UE transitions from an arbitrary cell selection state to a normal camping state in NR:

[0327] 4> If RPLMN is included in plmn-IdentityList stored in VarLogMeasReport, or if a registered SNPN identifier is included in snpn-ConfigIDList stored in VarLogMeasReport,

[0328] 4> If VarLogMeasConfig does not include areaConfiguration, or if the current camping cell is contained within the area specified by areaConfig in VarLogMeasConfig's areaConfiguration, or if the current camping cell is contained within the area specified by cag-ConfigList in VarLogMeasConfig's areaConfiguration, or if the current camping cell is contained within the area specified by snpn-ConfigList in VarLogMeasConfig's areaConfiguration:

[0329] 5> Perform logging.

[0330] 2> Or if reportType is set to eventTriggered and eventType is set to eventL1:

[0331] 3> If the UE is in a normal camping state on an NR cell and the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport,

[0332] 3> Or if the UE is in a normal camping state on an NR cell and the registered SNPN identifier is included in the snpn-ConfigIDList stored in VarLogMeasReport:

[0333] 4> VarLogMeasConfig does not include areaConfiguration, or

[0334] 4> If the serving cell is contained within the area specified by areaConfig in VarLogMeasConfig's areaConfiguration,

[0335] 4> If the current serving cell is contained within the area indicated by cag-ConfigList in VarLogMeasConfig's areaConfiguration, or if the current camping cell is contained within the area indicated by snpn-ConfigList in VarLogMeasConfig's areaConfiguration:

[0336] 5> Logging is performed at regular time intervals defined by the loggingInterval of VarLogMeasConfig only when the condition indicated by eventL1 is met.

[0337] 2> When performing logging:

[0338] 3> If InterFreqTargetInfo is configured and the UE detected an IDC problem at at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the previous logging interval, or

[0339] 3> If InterFreqTargetInfo is not configured and the UE detected an IDC issue during the previous logging period:

[0340] 4> If measResultServingCell in VarLogMeasReport is not empty:

[0341] 5> Includes inDeviceCoexDetected.

[0342] 5> Stop measurement logging from the next logging interval.

[0343] 4> Other cases:

[0344] 5> Stop measurement logging.

[0345] 3> Set relativeTimeStamp to indicate the elapsed time since the logged measurement configuration was received.

[0346] 3> If location information became available during the previous logging period, set the contents of locationInfo according to 5.3.3.7.

[0347] 3> When the UE is in an arbitrary cell selection state:

[0348] 4> Set anyCellSelectionDetected to indicate that no appropriate or acceptable cell was found.

[0349] 4> In VarLogMeasConfig, reportType is set to eventTriggered, and

[0350] 4> The RPLMN at the time of entering the arbitrary cell selection state is included in the plmn-IdentityList stored in VarLogMeasReport, or the registered SNPN identifier at the time of entering the arbitrary cell selection state is included in the snpn-ConfigIDList stored in VarLogMeasReport, and

[0351] 4> If VarLogMeasConfig does not include areaConfiguration, or if the appropriate cell the UE was last camping in is within the area indicated by areaConfig within VarLogMeasConfig's areaConfiguration, or if the last appropriate cell is within the area indicated by cag-ConfigList within areaConfiguration, or if the last appropriate cell is within the area indicated by snpn-ConfigList within areaConfiguration:

[0352] 5> Set servCellIdentity to represent the global cell identifier of the appropriate cell that the UE was last camping in.

[0353] 5> Set measResultServingCell to include the measurement of the appropriate cell that the UE was last camping in.

[0354] 4> In addition, if reportType is set to periodical in VarLogMeasConfig:

[0355] 5> Set servCellIdentity to represent the global cell identifier of the cell last logged by the UE.

[0356] 5> Set measResultServingCell to include the measurement of the cell last logged by the UE.

[0357] 3> Other cases:

[0358] 4> Set servCellIdentity to represent the global cell identifier of the cell the UE is currently camping in.

[0359] 4> Set measResultServingCell to include the measurement of the cell the UE is currently camping in.

[0360] 3> If available, set measResultNeighCells in descending order of the ranking-criterion used for cell reselection, and include the measurement results of neighbor cells that became available during the previous logging interval according to the following.

[0361] 4> For NR serving frequencies, include measurement results for up to 6 neighboring cells, and for each NR neighbor frequency, include measurement results for up to 3 cells according to the following.

[0362] 5> If interFreqTargetInfo is included in VarLogMeasConfig:

[0363] 6> If earlyMeasIndication is included in VarLogMeasConfig:

[0364] 7> Includes measurement results for NR neighbor frequencies included in both interFreqTargetInfo and measIdleCarrierListNR (in VarMeasIdleConfig) or SIB4.

[0365] 6> Other cases:

[0366] 7> Includes measurement results for NR neighbor frequencies included in both interFreqTargetInfo and SIB4.

[0367] 5> Other cases:

[0368] 6> If earlyMeasIndication is included in VarLogMeasConfig:

[0369] 7> Includes measurement results for NR neighbor frequencies included in measIdleCarrierListNR(in VarMeasIdleConfig) or SIB4.

[0370] 6> Other cases:

[0371] 7> Includes measurement results for NR neighbor frequencies included in SIB4.

[0372] 4> For inter-RAT frequency, measurement results for up to 3 neighboring cells are included according to the following.

[0373] 5> If earlyMeasIndication is included in VarLogMeasConfig:

[0374] 6> Includes measurement results for inter-RAT neighbor frequencies included in measIdleCarrierListEUTRA (in VarMeasIdleConfig) or SIB5.

[0375] 5> Other cases:

[0376] 6> Includes measurement results for inter-RAT frequencies included in SIB5.

[0377] 4> For each neighboring cell included, include available optional fields.

[0378] For specific details regarding the above-described Logged Measurement setup procedure and Logged Measurement procedure, refer to Sections 5.5a.1 and 5.5c.3 of TS 38.331 V19.

[0379] AI / ML-based CSI compression and CSI prediction

[0380] Figure 17 is a diagram illustrating an inference method during AI / ML-based CSI compression, and Figure 18 is a diagram illustrating a method for performing AI / ML-based CSI prediction.

[0381] Due to the advancement of computational processing technology and AI (artificial intelligence) / ML (machine learning) technologies as described above, the nodes and terminals constituting wireless communication networks are becoming more intelligent and sophisticated. In particular, due to the intelligence of the network, it is expected that various network decision parameter values ​​can be rapidly optimized, derived, and applied according to various network environment parameters (e.g., distribution / location of base stations, distribution / location / material of buildings / furniture, location / movement direction / speed of terminals, weather information, etc.). Here, these various network decision parameter values ​​may include the transmit / receive power of each base station, the transmit power of each terminal, the precoders and beams of base stations and terminals, time / frequency resource allocation for each terminal, and the duplex method of each base station.

[0382] In the Rel-18 AI / ML study item, discussions were held regarding CSI compression based on AI / ML models to improve CSI accuracy and reduce feedback overhead in existing NR systems. As illustrated in Fig. 17, CSI compression can be operated / performed based on two-sided models. For example, a terminal can generate compressed channel information by performing inference based on a CSI generation submodel using channel information or channel state information measured based on CSI-RS as input data, and can quantize the compressed channel information and feed it back to the base station. The base station can restore CSI (e.g., channel information measured by the terminal based on CSI-RS) by performing inference based on a CSI reconstruction submodel using information obtained by de-quantizing feedback bits (e.g., quantized compressed channel information) received from the terminal as input data.

[0383] AI / ML models have a structural characteristic in which input and output dimensions are fixed. Therefore, multiple configuration-specific models may be required to perform CSI reporting for various CSI-RS resources, and such multiple configuration-specific models can cause storage issues for terminals, base stations, and networks. NR CSI reporting measurement / reporting can be performed based on CSI-RS(s) of configured N-ports ({1,2,4,8,16,24,32,48,64,128}, N_max=128) and M-subbands ({1,...,19}, M_max=19). In this case, a total of 10*19=190 configuration-specific models may be required to perform CSI reporting for all CSI-RS resources. Moreover, considering the massive MIMO (e.g., N_max=256, 512, etc.) and wide bandwidth environments of 6G, including Upper mid-band (e.g., 7-24GHz) and Sub-Thz (e.g., 90-300GHz), it is expected that even more models will be needed.

[0384] At Rel-18, three major use cases for NR wireless interfaces (air interfaces) using AI / ML were discussed as study items: CSI feedback enhancement, beam management, and positioning accuracy enhancement.

[0385] Specifically, referring to FIG. 17, CSI compression is operated based on a two-sided model (in terms of inference) in which AI / ML models are provided at the terminal and the base station, respectively, and operate as a pair; for convenience, the terminal-side model can be defined as an AI-encoder and the base station-side model as an AI-decoder. As illustrated in FIG. 17, the terminal applies channel information (e.g., raw channel matrix or precoder-type channel information vector (e.g., eigenvector)) measured / estimated (or, if necessary, pre-processing may be performed) as input to the AI-encoder and can generate / obtain output information from the AI-encoder. The terminal can quantize the output information and feed it back to the base station as AI-CSI. In this case, the base station can generate / acquire the output CSI of the AI-decoder by applying the de-quantized information of the feedbacked AI-CSI as input to the AI-decoder. Since the channel information to be actually sent is compressed and fed back through an AI / ML-based model through this process, the feedback overhead can be reduced, so this is called CSI compression.

[0386] Referring to FIG. 18, a UE-side model is illustrated that performs model inference in the sense that the CSI prediction is equipped with an AI / ML model only on the terminal-side. For example, the CSI prediction may be an AI / ML-based channel estimation method that applies a plurality of historical measurements as input to the AI / ML (or AL / ML model) and estimates at least one future CSI (or at least one time point) as the output of the AI / ML model.

[0387] Logging interval determination

[0388] The following section assumes a scenario where wireless communication services are supported by AI / ML to support advanced network / base station-based dynamic systems, and explains in detail the data collection methods for model training to perform operations such as beam management, CSI reporting, and positioning based on AI / ML. For example, regarding network-side data collection, methods utilizing data collection procedures based on mechanisms such as Minimization of Drive Test (MDT) are being discussed. Instead of directly measuring network performance indicators (e.g., channel status) or terminal performance indicators (e.g., throughput) through drive tests, MDT allows the terminal to report information measured by itself to the network. In this case, there is an advantage in saving the cost and time associated with drive tests. Such MDTs can be broadly divided into immediate MDTs and logged MDTs. An immediate MDT refers to the transmission of collected data to the network in (near) real-time, while a logged MDT refers to a method where the terminal stores the measured data and periodically transmits the stored data.

[0389] Below, we explain in detail how to effectively set the logging interval for data logging when logging data / datasets for network-side data collection based on a mechanism similar to this MDT.

[0390] For one-sided models, data collection is generally discussed in two main directions: network-side data collection and UE-side data collection. Network-side data collection is primarily used for training network-side models, while UE-side data collection is typically used for training UE-side models; however, if operations such as model transfer are additionally considered, the training side / node and the inference side / node may differ.

[0391] Regarding network-side data collection, the points discussed in Tables 5 and 6 below may be considered.

[0392] NW side data collectionAgreements1 For the NW-side data collection related to beam management use cases, RAN2 to consider gNB-centric and OAM-centric approaches2 We aim that the same measurement framework is applied to both gNB-centric data collection and OAM-centric data collection for NW-side data collection.3RAN2 supports enhancements to MDT for data collection framework for training. FSS Whether to enhance logged or immediate MDTAgreements on NW side data collection @ RAN2#126Agreements for beam management1. For gNB centric and OAM centric (for RRC signaling between UE and gNB), reporting multiple instances of logged L1 measurement result from UE to gNB via a RRC message as configured by gNB is an optional feature. FFS how to handle case when single RRC message is not sufficient. FFS if there will be any further enhancement needed pending RAN1 agreement.2. Immediate MDT is the baseline framework for OAM-centric data collection for the training of a network-sided model3.Enhance the immediate MDT framework to support periodical reporting. FFS whether and what event-based reporting is supported and FFS on network request reportingAgreements1 As the baseline approach, the UE receives the measurement configuration for AI / ML-enabled features / FGsfor data collection and logging of measurements. The network can explicitly configure the UE whether the corresponding data collection and logging (if supported) should be immediately started. FFS if multiple configurations can be provided to the UE. FFS if dynamic activation / deactivation is support.2 UE stores the logged training data at AS layer with a minimum AS layer memory size supported by the UE. FFS on the memory size. This is across all use cases3 When UE reaches its buffer limitation the UE stops measurement for data collection purposes and logging.4 Measurements for data collection purposes and logging based can be controlled based on power state of the UE.It is up to UE implementation how the UE determines power state. FFS whether the UE stops autonomously or if it reports to the network.5 FFS whether AS buffer event based reporting is supported. FFS if we send availability indication or full report if it is supported6 FFS on event based data collection / logging7 On-demand request from the network is supported. FFS details on signallingAgreements1 The UE implementation can determine how many entries to include in the list radio measurements information, such that the maximum PDCP SDU size is not exceeded. No standardized RRC segmentation procedure is needed (as for the logged MDT measurements)2 Data collection report will not be transmitted over SRB1. FFS which SRB is used.

[0393] Agreements on NW side data collection1 Periodic logging is supported for training data collection procedure in R192 Event-triggered data logging will be supported. At least radio condition based event triggered logging will be supported. FFS the details of radio condition based event. FFS if other events are supported.3 Periodic reporting of logged data is not supported.4 On-demand reporting of the logged measurements will be specified5 UEInformationRequest / UEInformationResponse is used for on-demand reporting of AI / ML training data collection. FFS of details of the message6 The UE can indicates the availability of logged data to the network to assist network to trigger UEInformationRequest. FFS trigger / definition of availability indication. and FFS how data availability indication is sent to the network.7 Low priority SRB will be used.FFS new SRB or use of SRB48 For data collection for both NW-sided / UE sided BM model training, at least L1-RSRPs and / or beam-IDs needs to be collected by UE. FFS if other data needs to be collected based on RAN1 progress.Agreements on NW side data collection1. Focus on the following three radio condition event based logging- L3 serving cell measurement based (e.g. X1 / X2 similar to A1 / A2)- Beam based events (e.g. beam becomes top-1 beam and number of measurements is less than configured value)- L1 beam level measurement2. Measurements on aperiodic CSI resources are not reported for NW sided data collection.3. Data collection is controlled by the network. The UE will not autonomously stop when low power state is detected.4. The UE reports to the network when the power state is low. We will not specify how the UE determines low power state. The network should de-configure the data collection (this can be captured in stage 2).5.The UE reports to the network when buffer is or may become full. FFS when it reports (before and / or after).The UE can report the reason for triggering of indication for the status (e.g. low power state, low memory). FFS how this is signalled and if the reporting can be part of availability indication.All agreements for NW side data collection1. Support the use of L3 measurement event triggered (i.e. L3 serving cell measurements becoming worse / better than a threshold for TTT) to determine whether the UE performs logging or not. L1 measurement event triggered will not be supported.2. Low power bit indication is supported3. Data availability indication is supported. FFS when this would be triggered4. As baseline, the UEInformationResponse contains one or more logged measurement entries in chronological order (i.e. starting from the oldest measurement entries stored in the UE memory), and an availability indication if there are further data available for transmission.Same principles as for logged MDT.5. UE retains logged data during handover (HO). FFS if there is scenarios where the UE needs to release the data and how does the UE know and if control from network is needed6. UE indicates availability of logged data during handover (ie, within the RRCReconfigurationComplete message) (if data is retained in the UE).7. FFS how to handle idle / inactive and RLF cases and whether we have a unified.

[0394] Referring to the agreements described in Tables 5 and 6, standardization is underway for data collection methods based on legacy MDT for network-side data collection for one-sided models. Additionally, as defined in Table 7 below (refer to TS 38.331 V19), the terminal may be instructed to set up logged measurement for the current MDT.

[0395] -- ASN1START-- TAG-LOGGEDMEASUREMENTCONFIGURATION-STARTLoggedMeasurementConfiguration-r16 ::= SEQUENCE {criticalExtensions CHOICE {loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16-IEs,criticalExtensionsFuture SEQUENCE {}}}LoggedMeasurementConfiguration-r16-IEs ::= SEQUENCE {traceReference-r16 TraceReference-r16,traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)),tce-Id-r16 OCTET STRING (SIZE (1)),absoluteTimeInfo-r16 AbsoluteTimeInfo-r16,areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, --Need Rplmn-IdentityList-r16 PLMN-IdentityList2-r16 OPTIONAL, --Need Rbt-NameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, --Need Mwlan-NameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, --Need Msensor-NameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, --Need MloggingDuration-r16 LoggingDuration-r16,reportType CHOICE {periodical LoggedPeriodicalReportConfig-r16,eventTriggered LoggedEventTriggerConfig-r16,...},lateNonCriticalExtension OCTET STRING OPTIONAL,nonCriticalExtension LoggedMeasurementConfiguration-v1700-IEs OPTIONAL}LoggedMeasurementConfiguration-v1700-IEs ::= SEQUENCE {sigLoggedMeasType-r17 ENUMERATED {true} OPTIONAL, -- Need RearlyMeasIndication-r17 ENUMERATED {true} OPTIONAL, -- Need RareaConfiguration-r17 AreaConfiguration-r17 OPTIONAL, --Need RnonCriticalExtension LoggedMeasurementConfiguration-v1800-IEs OPTIONAL}LoggedMeasurementConfiguration-v1800-IEs ::= SEQUENCE {areaConfiguration-v1800 AreaConfiguration-v1800 OPTIONAL, --Need RnonCriticalExtension SEQUENCE {} OPTIONAL}LoggedPeriodicalReportConfig-r16 ::= SEQUENCE {loggingInterval-r16LoggingInterval-r16,...}LoggedEventTriggerConfig-r16 ::= SEQUENCE {eventType-r16 EventType-r16,loggingInterval-r16 LoggingInterval-r16,...}EventType-r16 ::= CHOICE {outOfCoverage NULL,eventL1 SEQUENCE {l1-Threshold MeasTriggerQuantity,hysteresis Hysteresis,timeToTrigger TimeToTrigger},...}-- TAG-LOGGEDMEASUREMENTCONFIGURATION-STOP-- ASN1STOP.

[0396] As defined in Table 7, in legacy MDT operations, when the report type is periodic (LoggedPeriodicalreportConfig-r16), the logging interval for measurement logging (or log measurement) can be set via “logginghInterval-r16”. Here, the logging interval may refer to the period for logging MDT measurements. Therefore, when performing periodic / semi-persistent logging, the logging interval can be explicitly specified / set. If the logging interval is specified to the terminal, the terminal can perform data / dataset logging based on the specified logging interval. However, such information regarding the logging interval is optional, and information regarding the logging interval may not be specified to the terminal. In this case, it may be ambiguous when the terminal should log the data / dataset. Therefore, it may be necessary to determine / set the logging interval according to the following methods.

[0397] 1. Proposal 1

[0398] When data / dataset logging is performed periodically or semi-continuously for data collection, information regarding the logging interval may not be explicitly indicated to the node / device (e.g., UE) performing the logging of the data / dataset. Taking this case into consideration, Proposal 1 proposes a method for implicitly determining the logging interval, and at least one of the following Option 1 and Option 2 may be considered.

[0399] (1) Option 1

[0400] The above logging interval may be determined based on the periodicity of the RSs configured in association for logging the data / dataset. For example, the logging interval may be set to an SSB (e.g., ssb-Periodicity), the periodicity of the CSI-RS resource (e.g., CSI-ResourcePeriodicityAndOffset in the CSI-report config), the PRS (e.g., PRS Resource periodicity and time-offset of a PRS Resource set), and / or an integer multiple of the resource periodicity of the RS periods. The integer value of the integer multiple may be a value agreed upon / configured in advance or determined based on UE capabilities. For example, the logging interval may be set based on at least one of the SSB period, the CSI-RS resource periodicity, and the period of the PRS resource (e.g., the period of the PRS resource and the time-offset of the PRS resource set). Alternatively, the logging interval may be set to an integer multiple of at least one of the SSB period, CSI-RS resource periodicity, and PRS resource period. Here, the integer value corresponding to the integer multiple may be predefined or adaptively determined based on the UE's capability information. Alternatively, the integer multiple may be indicated by being included in the logging configuration information.

[0401] For example, if the logging setting information for data collection does not include information regarding the logging interval or the logging period, the logging interval may be determined based on the periodicity or period of the measurement logging resource or the resources associated with the logging resource setting within the logging setting information (e.g., CSI-RS resources or SSB). For example, the logging setting information (or CSI log measurement setting) may include resource setting information that indicates / sets the resources on which logging is performed, and the resource setting information may indicate an ID for one CSI resource setting among the CSI resource settings, and multiple resources included in the one CSI resource setting may be set / determined as resources associated with the logging. Meanwhile, the resource setting information may be considered / interpreted as setting / indicating only the NZP CSI-RS resources and / or SSB resources among the multiple resources included in the CSI resource setting as resources associated with the logging. In addition, the logging may be performed at regular time intervals (e.g., logging intervals) according to the period of the resources associated with the logging, or at regular time intervals according to integer multiples of the period of the resources associated with the logging. For example, the logging may be performed at every period of the resources or at every integer multiple of the period of the resources.

[0402] (2) Option 2

[0403] For Option 2, the logging interval may be determined based on the CSI reporting periodicity information associated with the logging of the data / dataset. It may be set to a reporting period set within the CSI-report config or PRS measurement reporting period (e.g., CSI-reportPeriodicityAndOffset) or an integer multiple of the reporting periodicity. The integer value corresponding to the integer multiple may be a pre-agreed / set value or determined based on UE capabilities.

[0404] For example, the logging interval for logging data and / or datasets may be determined based on the associated CSI reporting periodicity information. Specifically, the logging interval may be set to the report periodicity set in the CSI-report configuration and / or PRS measurement reporting configuration, for example, the period set by CSI-ReportPeriodicityAndOffset, or an integer multiple of said report periodicity. In this case, the integer value may be a pre-agreed value or may be determined based on UE capabilities.

[0405] As described above, the explicit indication of the logging interval / logging period in Proposal 1 is optional and may not always be a value indicated to the terminal. In the case of the CSI-RS used in Proposal 1, the time domain behavior may be Periodic / semi-persistent CSI-RS. For example, if the reference signal associated with logging in Proposal 1 is a CSI-RS, the time domain behavior of the CSI-RS may be periodic CSI-RS or semi-persistent CSI-RS.

[0406] In the case of Option 1 of Proposal 1 above, the logging interval / logging period may be determined based on period information such as RS (e.g., P / SP CSI-RS, SSB) for or associated with data collection. If set to an integer multiple of the period information, the following data logging operation may be considered.

[0407] - Alt 1-1: The first / last measurement values ​​within the logging interval can be logged.

[0408] - Alt 1-2: Representative values ​​(e.g., average) of RSs transmitted within a logging interval may be logged. Additionally, a filtering value (e.g., L1-filtering) may be defined regarding which representative value is logged. Alternatively, the representative value may be determined and logged by the terminal implementation. For example, for multiple RSs received within a logging interval, a representative value (e.g., average) for the multiple RSs may be logged. Furthermore, a filtering value (e.g., L1-filtering value) may be defined regarding which representative value is logged. Alternatively, the representative value may be determined and logged according to the terminal implementation.

[0409] In the case of Option 2 of Proposal 1 above, the logging interval / logging period may be determined based on periodic information such as CSI-Report or PRS measurement report for data collection. In this case, the terminal may consider / perform the following additional operations.

[0410] - Alt 2-1: Within the reporting time of beam / CSI-related information calculated according to the reporting cycle (e.g., CSI-Report or PRS measurement Report cycle), or measurement information measured based on PRS, (valid) measurement values ​​can be logged.

[0411] - Alt 2-2: Beam / CSI related information calculated according to the reporting cycle (e.g., CSI-Report or PRS measurement report cycle) can be logged.

[0412] The difference between Alt 2-1 and 2-2 above may be whether the measurement results are considered as collected / logged data, or whether values ​​that have undergone specific processing are considered as collected / logged data. This may be a value indicated / set by the collected data format, etc. For example, in Proposal 1, the measurement value may be L1-RSRP (Layer 1 Reference Signal Received Power) and / or L1-SINR (Layer 1 Signal to Interference plus Noise Ratio) in the case of BM (beam management), raw channel matrix and / or CSI (e.g., CRI (Channel State Information-Reference Signal Resource Indicator), RI (Rank Indicator), CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator)) in the case of CSI, and PRS-based measurement, RSRP, timing info, TOA (Time of Arrival), TDOA (Time Difference of Arrival) and / or RTT (Round Trip Time), etc. in the case of Positioning.

[0413] For example, the difference between the above Alt 2-1 and Alt 2-2 can be distinguished based on whether the logging target is the valid measurement value itself obtained at the measurement points, or a processed value calculated according to the reporting cycle based on said measurement values. Specifically, in Alt 2-1, the valid measurement values ​​themselves obtained within the CSI-Report or PRS measurement reporting cycle may be considered as collected data and / or log data. On the other hand, in Alt 2-2, beam-related information, CSI-related information, and / or measurement information calculated or generated from multiple measurement values ​​according to the reporting cycle may be considered as log data.

[0414] Additionally, the frequency granularity and / or frequency range values ​​of measurements for log data / datasets may be indicated to the terminal via a separate indicator. Here, the frequency granularity may be RE, RB, RB group (e.g., subband), and / or wideband within the bandwidth where the measurement RSs are set, and the frequency range may be set / indicated as the granularity or an index of the frequency granularity, etc., as range information of the frequency band where the measurement is performed. In the absence of such additional signaling, the frequency granularity / frequency range values ​​indicated in the RS settings or reporting settings may be applied and used for data / dataset logging. For example, in the absence of separate signaling / setting, the frequency granularity and / or frequency range of measurements for data / dataset logging may be determined based on the frequency granularity / frequency range indicated in the RS settings or reporting settings. For example, the frequency granularity and / or frequency range of the measurements for the above data / data set logging may be the same as the frequency granularity / frequency range indicated in the RS setting or reporting setting, or determined as an integer multiple of the frequency granularity / frequency range indicated in the RS setting or reporting setting.

[0415] In order to establish a linkage between the logging configuration and the measurement RS (and / or, reporting configuration) in Proposal 1 above, a specific CSI report config ID or RS ID (e.g., CSI resource configuration ID) may be configured within the logging measurement configuration (e.g., LoggedMeasurementConfiguration message). For instance, if there are multiple RSs connected to the logging configuration (or multiple CSI reports / CSI report configurations connected to the P / SP CSI-RS or SSB), it may be ambiguous which RS or report cycle the logging interval should follow. In this case, through explicit signaling, the resource ID (or CSI resource configuration ID) related to the determination of the logging interval among the multiple RS (or multiple RS resource) IDs, or the report ID related to the determination of the logging interval among the multiple CSI reports / CSI report configuration IDs, may be indicated. For instance, the resource / CSI report ID may be indicated directly, or a specific order in which multiple RSs or multiple CSI reports configured / included within the logging measurement configuration are configured may be indicated. For example, by explicit signaling, a resource ID among the plurality of RS or plurality of RS resource IDs related to the determination of the logging interval may be indicated, or a report ID among the plurality of CSI report or CSI report setting IDs related to the determination of the logging interval may be indicated. For example, the resource ID or CSI report ID may be indicated directly, or the position / order of the RS or CSI report related to the determination of the logging interval may be indicated indirectly based on the setting order or setting listing order of the plurality of RS or plurality of CSI reports included in the logging settings. Alternatively, if there is no explicit indication, the logging interval may be implicitly determined / set on a rule basis.For example, the smallest or largest period value among the periods for multiple resources (e.g., CSI-RS resources or SSBs) or CSI reports may be considered as the logging interval. Alternatively, the period of the resource or report with the lowest or highest index / ID among the resource IDs (or CSI resource configuration IDs) and / or report IDs linked or configured for logging in the logging configuration information may be considered as the logging interval. Alternatively, the logging interval may be determined based on the order in which they are configured in the logging configuration information (or the order in which the RS IDs or report IDs included in the logging configuration information are listed). For example, the period of the first resource / report ID configured within the logging configuration or logging configuration information may be determined as the logging interval.

[0416] Alternatively, the logging interval may be determined by the reporting cycle of a CSI report configured not to be reported among the CSI reports connected to the P / SP CSI-RS or SSB, or by the resource cycle configured in said CSI report. Here, a CSI report configured not to be reported may be a CSI report with a Report quantity set to 'none', or a CSI report with a specified purpose in the RS configuration, such as an RS configured for data collection purposes. Alternatively, as shown in Table 8 below, if “ReportConfigType = none” is configured for a CSI report, the terminal may recognize that said CSI report is a CSI report configuration configured for data collection purposes and operate accordingly. In this case, the terminal may determine the logging interval based on the resource cycle configured in the corresponding CSI report configuration (report config). The advantage of such a configuration method (e.g., a method for determining / setting implicit logging intervals) is that, previously, time domain behavior related to reporting was necessarily set, and when the terminal recognized a CSI report set for data collection purposes, whether based on an explicit method or an implicit method, it had to ignore the reporting method set as a CSI report setting (report Config) set for data collection purposes; however, the introduction of the new parameter above has the advantage of eliminating this unnecessary process. For example, referring to Table 8, the proposed method has the advantage of not requiring the additional introduction or definition of a separate parameter to explicitly indicate that the CSI report is for data collection purposes, by causing the terminal to recognize or regard a CSI report set with “ReportConfigType = none” as a CSI report for data collection purposes.

[0417] CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId, carrier ServCellIndex OPTIONAL, -- Need S resourcesForChannelMeasurement CSI-ResourceConfigId, csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R reportConfigType CHOICE { periodic SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUCCH SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUSCH SEQUENCE { reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320}, reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32), p0alpha P0-PUSCH-AlphaSetId }, aperiodic SEQUENCE { reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32) } }, reportQuantity CHOICE { none NULL, cri-RI-PMI-CQI NULL, cri-RI-i1 NULL, cri-RI-i1-CQI SEQUENCE { pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S }, cri-RI-CQI NULL, cri-RSRP NULL, ssb-Index-RSRP NULL, cri-RI-LI-PMI-CQI NULL },. <skip>[[ reportConfigType-v19 CHOICE { none NULL, ...,} ]]reportConfigTypeTime domain behavior of reporting configuration.If the field reportConfigType-r19 is present, UE shall ignore reportConfigType (without suffix).

[0418] For example, regarding the logging mechanism, it is necessary to determine when to start logging and how to perform the logging. Regarding the initiation of logging, in conventional CSI reporting, periodic CSI reporting can be triggered when the UE receives a CSI setting. Similarly, logging of periodic CSI-RS can be triggered / initiated when the UE receives a logging setting associated with said periodic CSI-RS. In other words, for periodic CSI-RS, logging can be initiated when a logging setting associated with the periodic CSI-RS is received.

[0419] In contrast, according to TS 38.214, semi-persistent CSI-RS does not support periodic CSI reporting, so additional DCI (Downlink Control Information) or MAC CE (Medium Access Control Element) may be required for reporting. When CSI-ReportConfig is used to configure resources for data collection purposes without CSI reporting, an intuitive approach to enabling logging may be to utilize existing signaling by reusing the existing DCI or MAC CE for CSI reporting. When a UE receives a DCI or MAC CE for CSI reporting, the UE can decide whether to log or report Layer 1 measurement results based on its logging requirements. In this regard, Table 9 below defines CSI-RS configurations that can trigger / enable CSI reporting.

[0420] CSI-RS ConfigurationPeriodic CSI ReportingSemi-Persistent CSI ReportingAperiodic CSI ReportingPeriodic CSI-RSNo dynamic triggering / activationFor reporting on PUCCH, the UE receives an activation command, as described in clause 6.1.3.16 of [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCITriggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1.Semi-Persistent CSI-RSNot SupportedFor reporting on PUCCH, the UE receives an activation command, as described in clause 6.1.3.16 of [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCITriggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1.Aperiodic CSI-RSNot SupportedNot SupportedTriggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1.

[0421] For example, for a semi-persistent CSI-RS, logging may be initiated when a DCI (Downlink Control Information) or MAC CE (Medium Access Control Element) for CSI reporting is received, as in the existing CSI reporting mechanism.

[0422] Periodic / event-based logging can be performed as follows. In the existing MDT (Minimization of Drive Tests) operation, if the reporting type is periodic, the UE can log data at configured logging intervals. Similarly, for periodic or semi-persistent CSI-RS logging, the UE can log data at each logging interval, and the minimum logging interval can be the CSI-RS transmission periodicity.

[0423] For example, regarding periodic logging, the UE can perform logging at each logging interval. The logging interval can be set through the logging configuration. Otherwise (if the logging interval is not set through the logging configuration), the logging interval may follow the CSI-RS transmission configuration / CSI-RS resource configuration in the time domain.

[0424] Meanwhile, although the above-described Proposal 1 is described as being applicable to AI / ML-based beam management and / or CSI reporting, its scope of application is not limited thereto. For example, the above Proposal 1 can also be applied to positioning use cases or CSI compression based on two-sided models. Furthermore, although the above Proposal 1 has been described with a focus on data collection on the network side, it can be applied to data collection on the UE side using the same principles or in a corresponding manner.

[0425] FIGS. 19 and 20 are drawings for explaining a signaling method related to a logging procedure between a terminal and a base station according to one embodiment.

[0426] Referring to FIG. 19 (a), the terminal may receive periodic measurement logging setting information (or CSI log measurement setting information) from the NW, and may receive CSI resource setting information (or measurement RS resource setting information), and / or CSI reporting setting information (S191-1). Based on the logging setting information, the terminal may receive a measurement RS for configuring logging data / datasets (e.g., an SSB, CSI-RS, or PRS based on the CSI resource setting information) (S193-1). Based on the logging setting information, the terminal may perform a measurement on the measurement RS and perform data / dataset logging for the measurement results (S195-1). Based on the CSI log measurement setting information, the terminal may report information about the logged or logged data / datasets to the base station (S197-1). Meanwhile, some of these steps may be omitted as necessary.

[0427] Referring to FIG. 19 (b), the base station / NW receives periodic measurement logging setting information (or CSI log measurement setting information) from the terminal and can transmit CSI resource setting information (or measurement RS resource setting information) and / or CSI reporting setting information (S191-2). The base station can transmit measurement RS (e.g., SSB, CSI-RS, or PRS) for configuring logging data / datasets to the terminal (S193-2). The base station can receive information (e.g., CSI measurement log information) from the terminal regarding logs or logged data / datasets based on the logging setting information (S195-2). Meanwhile, some of these steps may be omitted as necessary. For example, the base station can request the UE to report the logged CSI measurement log information by sending a UEInformationRequest message to the UE, and can obtain the CSI measurement log information from the UEInformationResponse message in response to this.

[0428] Alternatively, referring to FIG. 20, the terminal may receive logging setting information from a base station, receive CSI resource setting information (or measurement RS resource setting information), receive CSI reporting setting information (or measurement reporting setting information), receive measurement RS, and report CSI measurement log information to the base station that includes data / data set logged for measurement results based on measurement RS. Alternatively, the base station may transmit logging setting information to the terminal, transmit measurement reporting setting information, transmit measurement RS to the terminal, and receive CSI measurement log information that includes data / data set logged for measurement results based on measurement RS.

[0429] Figure 21 is a diagram illustrating how a UE performs logging based on log measurement settings.

[0430] Referring to FIG. 21, the UE may receive information regarding CSI resource settings or CSI resource setting information (e.g., including a plurality of CSI resource settings) (S211). The CSI resource settings may include setting information for one or more resources for channel measurement. Specifically, the CSI resource settings may include information regarding at least one CSI resource setting ID and information regarding a list of NZP (Non-Zero Power) CSI-RS resource sets and / or a list of SSB resource sets related to CSI measurement corresponding to each of the at least one resource setting ID. The CSI resource settings may include information regarding the ID (identifier) ​​of each resource / resource set, transmission characteristics in the time domain, and the periodicity of the resource.

[0431] The UE may receive information regarding a logged measurement setting (or, CSI logged measurement setting) for collecting network-side data (S213). The logged measurement setting (or, CSI logged measurement setting) may be a logging-related setting for the network to collect a dataset from the UE, and may include log resource information (e.g., log resource setting information or CSI log resource setting information) that directs / sets resources associated with logging based on the CSI resource setting.

[0432] For example, the above log measurement setting or CSI log measurement setting may be a logging-related setting for a network to collect a dataset from a UE, and may include information (e.g., log resource setting information) that indicates / sets resources associated with logging based on the above CSI resource setting. For example, the above log resource setting information may be information that indicates / sets resources for which the UE performs channel measurements, among at least one set of resources or at least one resource included in the above CSI resource setting, while being associated with measurement results logged by the UE. Alternatively, the above log resource setting information may indicate / set resources associated with logging by indicating / setting an ID for the CSI resource setting related to the performance of logging. Meanwhile, the UE may interpret only CSI-RS (e.g., NZP CSI-RS) and / or SSB resources among the plurality of resources corresponding to the CSI resource setting ID indicated by the above log resource setting information as resources associated with logging. Additionally, the above log measurement setting may further include log period information regarding logging period / periodism. As described above, the log period information may be optional information that may or may not be included in the log measurement settings.

[0433] As described above, the UE may determine the time interval at which logging is performed differently depending on whether information regarding the log period is included in the log measurement setting information. For example, if information regarding the log period is included in the log setting information, the UE may determine / set the time interval according to the log period. Conversely, if logging period information is not included in the log measurement setting, the UE may determine / set the logging time interval based on the period of resources associated with logging. For example, even if the logging period is not separately specified, the time interval for performing the logging may be implicitly derived from the periodicity of the resources indicated by the log measurement setting. For example, the UE may perform logging at time intervals according to the period of the resources. The time interval or logging interval may be determined by the transmission period of the resources themselves. Alternatively, the UE may perform logging at time intervals corresponding to n times the period of the resources (where n is an integer). Here, the value of n may be set / defined in advance, or determined based on the UE's capability. For example, the value of n can be determined based on the UE's measurement processing performance, storage capacity, power consumption characteristics, or supported logging resolution.

[0434] If there is only one cycle associated with the resources indicated by the above log measurement settings, the UE may apply that cycle or an integer multiple (e.g., n) of that cycle as the logging interval. Alternatively, if there are multiple cycles associated with the resources, the UE may determine the logging interval in a rule-based manner. For example, the UE may perform logging at time intervals corresponding to the shortest cycle among the multiple cycles of the resources. In this case, data collection with relatively high temporal resolution may be possible. Alternatively, the UE may perform logging at time intervals corresponding to the longest cycle among the multiple cycles of the resources. In this case, representative measurement data can be collected while reducing the memory storage and processing burden on the UE. Alternatively, rules based on the IDs of each of the multiple resources may be applied. For example, the UE may determine the logging interval based on the cycle of the resource with the lowest ID, or based on the cycle of the resource with the highest ID. Such a method allows the logging interval to be determined consistently without explicit logging cycle indication, even when multiple resources are linked.

[0435] Alternatively, the information regarding the log period included in the log measurement setting may be for the value of n. For example, the log measurement setting information may include information regarding the log period for the value of n (e.g., 2, 3). In this case, the logging may be performed at time intervals or logging intervals corresponding to a value obtained by multiplying the transmission period of the resources by n.

[0436] Alternatively, the UE may perform logging for resources for channel measurements associated with logging (e.g., NZP CSI-RS resources and / or SSB resources) based on the log measurement settings according to the time interval determined as above (S215). Here, the logging may be an operation of storing a measurement value obtained from the resources or a dataset generated based on the measurement values ​​for data collection at each logging interval. For example, the UE may log the first measurement value obtained within each time interval. Or, the UE may log the last measurement value obtained within each time interval. This may correspond to a method of recording the state at the start or end point of the logging interval as a representative value. Or, the UE may log a representative value for multiple measurement values ​​obtained within each time interval. For example, the representative value may be an average value. The UE may accumulate or filter the measurement results for multiple CSI-RS or SSB received within a single logging interval and then include the average value in the logged dataset. In this case, which representative value is used, or what filtering is applied before calculating the average value, can be determined by predefined rules, upper-layer settings, or UE implementations. For example, the representative measurement value can be determined based on L1 filtering values.

[0437] And / or, the UE may report CSI logging data to the base station, including the logged data or the logged dataset generated by the performance of the logging. For example, the UE may receive a UEInformationRequest message from the base station and, in response, transmit a UEInformationResponse message to the base station that includes the logged data or the CSI logging data. The logged data or the CSI logging data may include a log measurement setting ID (or, CSI logging setting ID), the serving cell ID where the measurement was performed, the measurement value by CSI-RS resource ID (L1-RSRP), and / or the measurement value by SSB index (L1-RSRP). Here, the measurement value may be the first or last measurement value within each time interval as described above. Alternatively, the measurement value may include the average value of the measurements within the time interval. The logged data or the CSI logging data reported by the UE may be utilized for network-side data collection, such as AI / ML-based beam management or CSI-related learning purposes.

[0438] In this way, even when logging period information is not explicitly included in the log measurement settings, the proposed invention allows the UE to implicitly determine the logging interval based on the periods of CSI resources associated with the log measurement settings and perform channel measurement logging accordingly.

[0439] FIG. 22 is a diagram illustrating how a base station receives CSI logging data logged from a UE.

[0440] Referring to FIG. 22, the base station may transmit information regarding CSI resource configuration to the UE (S221). The CSI resource configuration may include configuration information for one or more resources for channel measurement, for example, may include configuration information for CSI-RS resources and / or SSB resources. For example, the CSI resource configuration may include resource configuration information for an NZP CSI-Rs resource set list and / or an SSB resource set list related to CSI measurement. The CSI resource configuration may include information regarding the ID (identifier) ​​of each resource / resource set, transmission characteristics in the time domain, and the periodicity of the resource. Here, the information regarding the CSI resource configuration may be a CSI-MeasConfig containing information for configuring a plurality of CSI resource configurations, and the CSI resource configuration may be a CSI-ResourceConfig.

[0441] The base station may transmit information regarding logged measurement settings for network-side data collection to the UE (S223). The logged measurement settings (or CSI logged measurement settings) may be logging-related settings for the network to collect a dataset from the UE, and may include information that directs / sets resources associated with logging based on the CSI resource settings (e.g., log resource setting information or CSI log resource setting information).

[0442] For example, the above log measurement setting (or, CSI log measurement setting) may be a logging-related setting for a network to collect a dataset from a UE, and may include log resource setting information (or, CSI log resource setting information) that indicates / sets resources associated with logging based on the above CSI resource setting. For example, the above log resource setting information may be information that indicates / sets resources for which the UE performs channel measurements, among at least one set of resources or at least one resource included in the above CSI resource setting, while being associated with measurement results logged by the UE. Alternatively, the above log resource setting information may indicate / set resources associated with logging by indicating / setting an ID for the CSI resource setting related to the performance of logging. Meanwhile, the UE may interpret only CSI-RS (e.g., NZP CSI-RS) and / or SSB resources among a plurality of resources corresponding to the CSI resource setting ID indicated / set by the above log resource setting information as resources associated with logging. Additionally, the above log measurement setting may further include log period information regarding logging periodicity / periodism. As described above, the log period information may be optional information that may or may not be included in the log measurement settings.

[0443] Specifically, the log measurement setting may not explicitly include information regarding the logging period or logging interval. For example, even if the base station does not instruct the UE to separate logging period information, it may designate / configure the logging target resources through the log resource setting information of the log measurement setting. In this case, based on the fact that the log measurement setting does not include logging period information, the UE may implicitly determine the logging time interval based on the period of the resources indicated in the log resource setting information. In other words, the logging time interval may be the periodicity of the resources indicated in the log resource setting information itself, or may be determined as an integer multiple of the periodicity. This method corresponds to Option 1 of Proposal 1 and may imply a configuration in which the logging interval is determined based on the period of the resources associated with logging itself, rather than the reporting period.

[0444] The base station may receive CSI logging data for resources for channel measurement associated with logging from the UE based on the log measurement settings (S225). The CSI logging data may include measurements logged for the resources at time intervals based on the period of the resources, based on the fact that logging period information is not included in the log measurement settings. For example, the CSI logging data may include measurements acquired at each time interval, and more specifically, may include the first measurement, the last measurement, or a representative value for multiple measurements within each time interval. The representative value may be an average value and may be composed of filtered values ​​as needed.

[0445] Alternatively, if there are multiple cycles associated with the resources indicated by the log measurement settings, the UE may determine a logging interval among the multiple cycles according to a predetermined rule, and the base station may receive CSI logging data generated according to the logging interval thus determined. For example, the CSI logging data may include measurements logged at a time interval corresponding to the shortest or longest cycle among the cycles of the multiple resources. Alternatively, the CSI logging data may include measurements logged at a time interval corresponding to the cycle of the resource having the lowest ID or the highest ID among the IDs of the multiple resources. In this way, the base station may configure the UE to perform logging based on the logging target resource and its periodicity, even without separately specifying the logging cycle.

[0446] Thus, the proposed invention can effectively resolve ambiguity in logging execution that may occur when logging period information is not explicitly included, by enabling the UE to implicitly determine the logging interval based on the period of CSI resources or reference signal resources associated with logging. Furthermore, the proposed invention enables the UE to clearly determine the logging time by allowing the logging interval to be implicitly determined based on the periods of resources associated with logging, even if logging period information is not explicitly included in the log measurement settings. Additionally, by ensuring that the logging interval is determined in conjunction with the resource period, the proposed invention can improve the consistency between the time when actual measurements are performed and the time when log data is generated, and effectively reduce the possibility of unnecessary duplicate logging or omitted measurements. Moreover, the proposed invention enables the implementation of a logging mechanism by utilizing existing CSI resource settings, CSI reporting settings, and related signaling structures, thereby minimizing the introduction of new parameters or separate complex control procedures and increasing compatibility with existing systems.

[0447] Example of a communication system to which the invention is applied

[0448] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of the invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0449] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.

[0450] FIG. 23 illustrates a communication system to which the present invention is applied.

[0451] Referring to FIG. 23, the communication system (1) to which the present invention applies includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and can be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0452] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0453] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present invention, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0454] Example of a wireless device to which the present invention is applied

[0455] FIG. 24 illustrates a wireless device that can be applied to the present invention.

[0456] Referring to FIG. 24, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 23.

[0457] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present invention, the wireless device may refer to a communication modem / circuit / chipset.

[0458] Specifically, the first wireless device or UE (100) may include a processor (102) connected to a transceiver (106) and a memory (104). The memory (104) may include at least one program capable of performing operations related to the embodiments described in the section “Logging interval determination” with reference to FIGS. 17 through 22. The operations include controlling the RF transceiver to receive information regarding CSI (channel state information) resource settings, receiving information regarding logged measurement settings for network-side data collection, and performing logging for resources for channel measurement associated with logging based on said logged measurement settings, wherein said logged measurement settings include information indicating said resources based on said CSI resource settings, and based on said logged measurement settings not including logging period information, said logging may be performed at time intervals based on the period of said resources.

[0459] Alternatively, a processing device may be configured including a processor (102) and a memory (104) that controls the UE. In this case, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions that perform operations when executed by the at least one processor. The operations include causing the UE to: receive information regarding a CSI (channel state information) resource setting; receive information regarding a logged measurement setting for network-side data collection; and perform logging for resources for channel measurement associated with logging based on the logged measurement setting, wherein the logged measurement setting includes information indicating the resources based on the CSI resource setting, and the logging may be performed at time intervals based on the period of the resources based on the fact that the logged measurement setting does not include logging period information.

[0460] Alternatively, at least one non-transient computer-readable medium may be configured, in which a program / instruction for performing the above-described operations is stored.

[0461] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In the present invention, the wireless device may refer to a communication modem / circuit / chip.

[0462] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver or RF transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in the section “Logging interval determination” with reference to FIGS. 17 through 22. The operations include controlling the RF transceiver (206) to transmit information regarding CSI (channel state information) resource settings to a UE (User Equipment), transmitting information regarding logged measurement settings for network-side data collection to the UE, and receiving CSI logging data for resources for channel measurement associated with logging based on said logged measurement settings, wherein said logged measurement settings include information indicating said resources based on said CSI resource settings, and based on said logged measurement settings not including logging period information, said CSI logging data may include measurements logged for said resources at time intervals based on the period of said resources.

[0463] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0464] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For 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 one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0465] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0466] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0467] Examples of wireless device applications to which the present invention is applied

[0468] FIG. 25 illustrates another example of a wireless device to which the present invention applies. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 23).

[0469] Referring to FIG. 25, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 24 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 25. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 24. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0470] The additional element (140) can be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 23, 100a), a vehicle (Fig. 23, 100b-1, 100b-2), an XR device (Fig. 23, 100c), a portable device (Fig. 23, 100d), a home appliance (Fig. 23, 100e), an IoT device (Fig. 23, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 23, 400), a base station (Fig. 23, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0471] In FIG. 25, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least partially connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be connected via a wire, and the control unit (120) and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0472] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0473] FIG. 26 illustrates a vehicle or autonomous vehicle to which the present invention applies. The vehicle or autonomous vehicle may be implemented as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0474] Referring to FIG. 26, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 25, respectively.

[0475] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, roadside base stations (Roadside units), etc.), and servers. The control unit (120) can perform various operations by controlling elements of the vehicle or autonomous vehicle (100). The control unit (120) may include an Electronic Control Unit (ECU). The driving unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The driving unit (140a) may include an engine, motor, power train, wheels, brakes, steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and may include wired / wireless charging circuits, batteries, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement technologies such as maintaining the driving lane, technologies for automatically adjusting speed such as adaptive cruise control, technologies for automatically driving along a predetermined path, and technologies for automatically setting a path and driving when a destination is set.

[0476] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving path and a driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or the autonomous vehicle (100) moves along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can acquire the latest traffic information data from an external server non-periodically and can acquire surrounding traffic information data from surrounding vehicles. Additionally, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving path and the driving plan based on the newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving path, driving plan, etc. to an external server. An external server can predict traffic information data in advance using AI technology, etc., based on information collected from vehicles or autonomous vehicles, and can provide the predicted traffic information data to vehicles or autonomous vehicles.

[0477] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0478] The embodiments described above are combinations of the components and features of the present invention in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that do not have an explicit citation relationship in the claims, or that new claims may be included by amendment after filing.

[0479] In this document, embodiments of the present invention are described primarily with a focus on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is extended in the same or similar manner to signal transmission and reception between a terminal and a relay or between a base station and a relay. Specific operations described in this document as being performed by a base station may, in some cases, be performed by an upper node. That is, it is self-evident that various operations performed for communication with a terminal in a network consisting of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. Additionally, the terminal may be replaced by terms such as User Equipment (UE), Mobile Station (MS), and Mobile Subscriber Station (MSS).

[0480] Embodiments according to the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, one embodiment of the present invention may be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

[0481] In the case of implementation by firmware or software, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc., that performs the functions or operations described above. Software code may be stored in a memory unit and executed by a processor. The memory unit may be located inside or outside the processor and may exchange data with the processor by various means already known.

[0482] It is obvious to those skilled in the art that the present invention may be embodied in other specific forms without departing from the features of the invention. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects but should be considered exemplary. The scope of the invention shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the invention are included within the scope of the invention.

[0483] The embodiments of the present invention as described above can be applied to various mobile communication systems.< / skip>

Claims

1. In a method using UE (User Equipment), Step of receiving information regarding CSI (channel state information) resource configuration; A step of receiving information on logged measurement settings for network-side data collection; and The method includes the step of performing logging for resources for channel measurements associated with logging based on the above log measurement settings, and The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and A method in which, based on the fact that the log measurement setting above does not include logging period information, the logging is performed at time intervals based on the period of the resources.

2. In Paragraph 1, The above logging is performed at time intervals according to the period of the above resources, a method.

3. In Paragraph 1, A method in which the above logging is performed at time intervals corresponding to n times the period of the above resources (where n is an integer).

4. In Paragraph 3, A method in which the value of n is determined or preset based on the capability of the UE.

5. In Paragraph 1, A method in which the above resources include only a CSI-RS (channel state information-reference signal) resource or an SSB (synchronization signal block) resource among a plurality of resources included in the above CSI resource configuration.

6. In Paragraph 1, A method based on the fact that there are multiple cycles associated with the above resources, wherein the logging is performed at time intervals corresponding to the shortest or longest cycle among the multiple cycles of the above resources.

7. In Paragraph 1, A method in which, based on the fact that there are multiple cycles associated with the above resources, the logging is performed at time intervals corresponding to the cycle of the resource having the lowest ID or the highest ID among the IDs (identifiers) of the above resources.

8. In Paragraph 1, It further includes the step of reporting information about the dataset logged by performing the above logging to the base station, A method in which the above-mentioned logged dataset includes the first measurement or the last measurement within the above-mentioned time interval.

9. In Paragraph 1, The method further includes the step of reporting the dataset logged by performing the above logging to the base station, A method in which the above-mentioned logged dataset includes the average value of measurements within the above-mentioned time interval.

10. In at least one non-transient computer-readable recording medium, Includes instructions that perform operations when executed by at least one processor, The above operations are, Receive information regarding CSI (channel state information) resource configuration; Receive information on logged measurement settings for network-side data collection; and It includes performing logging for resources for channel measurements associated with logging based on the above log measurement settings, and The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and Based on the fact that the log measurement setting above does not include logging period information, the logging is performed at time intervals based on the period of the resources, at least one non-transient computer-readable recording medium.

11. Regarding UE (User Equipment), RF (Radio Frequency) transceiver; and It includes a processor connected to the above RF transceiver, and The above processor controls the RF transceiver to receive information regarding CSI (channel state information) resource settings and receives information regarding logged measurement settings for network-side data collection, and performs logging for resources for channel measurements associated with logging based on the logged measurement settings. The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and Based on the fact that the log measurement settings above do not include logging period information, the logging is performed at time intervals based on the periods of the resources, UE.

12. In Paragraph 11, The above logging is performed at time intervals according to the cycle of the resources, UE.

13. In a processing device for controlling UE (User Equipment), At least one processor; and It includes at least one memory that stores instructions connected to the above at least one processor and performing operations when executed by the at least one processor, The above operations cause the UE to: Receive information regarding CSI (channel state information) resource configuration; Receive information on logged measurement settings for network-side data collection; and It includes performing logging for resources for channel measurements associated with logging based on the above log measurement settings, and The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and A processing device in which, based on the fact that the log measurement setting above does not include logging period information, the logging is performed at time intervals based on the period of the resources.

14. In the method using a base station, A step of transmitting information regarding CSI (channel state information) resource configuration to UE (User Equipment); A step of transmitting information to the above UE regarding logged measurement settings for network-side data collection; and The method includes the step of receiving CSI logging data for resources for channel measurements associated with logging based on the above log measurement settings, and The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and A method in which, based on the fact that the log measurement setting above does not include logging period information, the CSI logging data includes measurements logged for the resources at time intervals based on the period of the resources.

15. Regarding base stations, RF (Radio Frequency) transceiver; and It includes a processor connected to the above RF transceiver, and The above processor controls the RF transceiver to transmit information regarding CSI (channel state information) resource settings to the UE (User Equipment), transmits information regarding logged measurement settings for network-side data collection to the UE, and receives CSI logging data for resources for channel measurement associated with logging based on the logged measurement settings. The above log measurement setting includes information indicating the resources based on the above CSI resource setting, and Based on the fact that the log measurement setting above does not include logging period information, the base station, wherein the CSI logging data includes measurements logged for the resources at time intervals based on the period of the resources.

Images