Method and device for requesting channel state information for saving network energy in wireless communication system

The method enables user equipment to receive and selectively transmit CSI reports based on configurations from the base station, optimizing energy usage and latency in high-frequency wireless communication systems, addressing the challenges of energy saving and performance in current systems.

WO2024237766A1PCT designated stage expired Publication Date: 2024-11-21SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/095809
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-17
Filing Date
2024-05-17
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently managing channel state information (CSI) reporting to optimize network energy saving, particularly in high-frequency bands where energy consumption is high and latency is critical, especially for services like eMBB, URLLC, and mMTC.

Method used

A method and apparatus that allow user equipment (UE) to receive configurations for CSI reporting from a base station, enabling the UE to selectively transmit CSI reports based on sub-configurations, optimizing energy usage and reporting frequency.

Benefits of technology

This approach enhances network energy efficiency by reducing unnecessary CSI reporting, thereby lowering energy consumption and improving latency performance across various wireless communication services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024095809_21112024_PF_FP_ABST
    Figure KR2024095809_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a user equipment (UE) in a wireless communication system comprises the steps of: receiving first information including information about at least one configuration for a channel state information (CSI) report from a base station, wherein the information about the at least one configuration includes information about sub-configurations; receiving second information for the CSI report from the base station, wherein at least one sub-configuration among the sub-configurations is indicated on the basis of the second information; and transmitting the CSI report about the at least one sub-configuration to the base station.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for requesting channel state information for network energy saving in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for requesting channel state information for network energy saving in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a mobile communication system are provided.

[0009] According to one embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include the steps of: receiving, from a base station, first information including information on at least one configuration for channel state information (CSI) reporting; the information on the at least one configuration including information on sub-configurations; receiving, from the base station, second information for the CSI reporting; indicating at least one sub-configuration among the sub-configurations based on the second information; and transmitting, to the base station, the CSI report for the at least one sub-configuration.

[0010] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to one embodiment.

[0013] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment.

[0014] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment.

[0015] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to one embodiment.

[0016] FIG. 5 is a diagram illustrating an example of an aperiodic CSI reporting method according to one embodiment.

[0017] FIG. 6 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to one embodiment.

[0018] FIG. 7 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment.

[0019] FIG. 8 is a diagram illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment.

[0020] FIG. 9 is a diagram illustrating an example of configuring downlink control information (DCI) for cooperative communication in a wireless communication system according to one embodiment.

[0021] FIG. 10 is a diagram illustrating an aperiodic CSI report signaling structure that a terminal can set as upper layer signaling according to one embodiment.

[0022] FIG. 11 is a diagram illustrating aperiodic CSI report and aperiodic CSI-RS triggering situations and constraints according to one embodiment.

[0023] FIG. 12 is a diagram illustrating a MAC-CE structure that indicates activation or deactivation of a semi-persistent CSI report transmitted on a PUCCH according to one embodiment.

[0024] FIG. 13 is a diagram illustrating a situation in which multiple overlapping CSI-RS resources are transmitted according to one embodiment.

[0025] FIG. 14 is a diagram illustrating a MAC-CE structure that indicates activation or deactivation of a PUCCH-based semi-persistent CSI report considering detailed CSI report settings according to one embodiment.

[0026] FIG. 15 is a diagram illustrating another MAC-CE structure for indicating activation or deactivation of a PUCCH-based semi-persistent CSI report considering detailed CSI report settings according to one embodiment.

[0027] Fig. 16 is a diagram showing the operation of a terminal according to one embodiment.

[0028] Figure 17 is a diagram illustrating the operation of a base station according to one embodiment.

[0029] FIG. 18 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment.

[0030] FIG. 19 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment.

[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0032] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0033] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure. The present disclosure is defined only by the scope of the claims. Like reference numerals may refer to like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the specification.

[0035] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include at least one of a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, the downlink (DL) may be referred to as a wireless transmission path of a signal transmitted from the base station to the terminal, and the uplink (UL) may be referred to as a wireless transmission path of a signal transmitted from the terminal to the base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0036] It can be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. The computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment can create a means for performing the functions described in the flowchart block(s). The computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement a function in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes an instruction means for performing the functions described in the flowchart block(s). Computer program instructions may also be installed on a computer or other programmable data processing device, such that a series of operational steps may be performed on the computer or other programmable data processing device to produce a computer-executable process, and instructions that the computer or other programmable data processing device executes may provide steps for performing the functions described in the flowchart block(s).

[0037] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0038] According to one embodiment, the term '~ unit' used in the present disclosure may refer to a software or hardware component such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the '~ unit' may perform certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' may include components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card. In addition, the '~parts' in the present disclosure may include one or more processors.

[0039] According to one embodiment, wireless communication systems are evolving from providing initial voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0040] According to one embodiment, as a representative example of a broadband wireless communication system, in the LTE system, the downlink (DL) uses the OFDM (Orthogonal Frequency Division Multiplexing) method. The uplink (UL) may employ the SC-FDMA (Single Carrier Frequency Division Multiple Access) method. The uplink may be referred to as a wireless link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink may be referred to as a wireless link through which a base station transmits data or control signals to a terminal. The multiple access method typically allocates and operates time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality, thereby distinguishing data or control information for each user.

[0041] According to one embodiment, as a future communication system after LTE, i.e., 5G communication system, must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that simultaneously satisfy various requirements must be supported. Services being considered for 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0042] In one embodiment, eMBB may aim to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. In addition, the 5G communication system should provide an increased user-perceived data rate while providing the peak data rate. To meet these requirements, improvements in various transmission and reception technologies, including further improved multi-input multi-output (MIMO) transmission technology, may be required. In addition, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission rates required by the 5G communication system by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz frequency band.

[0043] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, which may require even wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, extremely long battery lifespans, such as 10 to 15 years, may be required.

[0044] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of 10-5 or lower. Therefore, for URLLC-enabled services, 5G systems must provide shorter Transmit Time Intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0045] In one embodiment, three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. Different transmission and reception techniques and parameters can be used to meet the different requirements of each service. Of course, 5G is not limited to the three services described above.

[0046] Hereinafter, a / b can be understood as at least one of a or b.

[0047] [NR time-frequency resources]

[0048] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

[0049] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted, in a 5G system according to one embodiment.

[0050] Referring to Figure 1, the horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM symbol (102) in the time axis and 1 subcarrier (103) in the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB, 104). One subframe (110) on the time axis can include multiple OFDM symbols (102). For example, the length of one subframe can be 1 ms.

[0051] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment.

[0052] Referring to FIG. 2, FIG. 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and / or a slot (Slot, 202). One frame (200) may be defined as 10 ms. One subframe (201) may be defined as 1 ms, and thus one frame (200) may be composed of a total of 10 subframes (201).

[0053] According to one embodiment, one slot (202, 203) may be defined as 14 OFDM symbols. For example, the number of symbols per slot is =14 can be referenced. 1 subframe (201) can be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) can vary depending on the setting value μ(204, 205) for the subcarrier spacing.

[0054] In an example of FIG. 2, cases where the subcarrier spacing setting value is μ=0(204) and μ=1(205) are illustrated. When μ=0(204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1(205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0055]

[0056] [Bandwidth Part (BWP)]

[0057] Below, the bandwidth part (BWP) setting in the 5G communication system is specifically described with reference to the drawing.

[0058] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment.

[0059] Referring to FIG. 3, an example is described in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set the information in [Table 2] below for each bandwidth portion.

[0060]

[0061] The information configured for the terminal is not limited to the above examples, and in addition to the configuration information in [Table 2], various parameters related to the bandwidth portion may be configured for the terminal. The configuration information may be transmitted from the base station to the terminal via upper layer signaling (e.g., RRC (Radio Resource Control) signaling). At least one bandwidth portion among one or more bandwidth portions configured for the terminal may be activated. Whether or not the bandwidth portion configured for the terminal is activated may be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (downlink control information).

[0062] According to one embodiment, a terminal prior to RRC connection can receive configuration information for an initial bandwidth portion (Initial BWP) for initial access from a base station via a Master Information Block (MIB). For example, during the initial access phase, the terminal can receive configuration information for a Control Resource Set (CORESET) and a Search Space, through the MIB, where a PDCCH for receiving system information required for initial access (e.g., Remaining System Information (RMSI) and / or System Information Block 1 (SIB1)) can be transmitted.

[0063] According to one embodiment, the control region and search space set by the MIB may each be identified or regarded as an identifier (ID) 0. The base station may notify or set configuration information such as frequency allocation information, time allocation information, and / or numerology for the control region #0 to the terminal through the MIB. In addition, the base station may notify or set configuration information for the monitoring cycle and monitoring occasion for the control region #0, i.e., configuration information for the search space #0, to the terminal through the MIB. The terminal may identify or regard the frequency region set as the control region #0 obtained from the MIB as an initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion may be regarded as 0.

[0064] According to one embodiment, the settings for the bandwidth portion supported by 5G can be used for various purposes.

[0065] In one embodiment, when the bandwidth supported by the terminal is smaller than the system bandwidth, the base station can support the terminal's data communication by configuring the bandwidth portion. For example, the base station can configure the frequency position (configuration information 2) of the bandwidth portion for the terminal, and the terminal can transmit and / or receive data at a specific frequency position (e.g., the configured frequency position) within the system bandwidth.

[0066] In one embodiment, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support both data transmission and reception using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz for a given terminal, the base station may configure two bandwidth segments for the given terminal, each with a subcarrier spacing of 15 kHz and 30 kHz. The different bandwidth segments may be frequency-division multiplexed (FDM), and when data is to be transmitted and / or received using a specific subcarrier spacing, the bandwidth segment configured with the subcarrier spacing may be activated.

[0067] In one embodiment, for the purpose of reducing power consumption of a terminal, a base station may configure bandwidth portions with different bandwidth sizes for the terminal. For example, if a terminal supports a very large bandwidth (e.g., 100 MHz bandwidth) and always transmits and / or receives data within the supported bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a traffic-free environment may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth (e.g., 20 MHz bandwidth portion) for the terminal. In a traffic-free environment, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and / or receive data in the 100 MHz bandwidth portion according to an indication from the base station.

[0068] According to one embodiment, in a method for configuring a bandwidth portion, terminals prior to an RRC connection (Connected) can receive configuration information regarding an initial bandwidth portion (Initial BWP) through an MIB during an initial access phase. For example, the terminal can configure a control region (i.e., CORESET) for a downlink control channel on which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of a Physical Broadcast Channel (PBCH). The bandwidth of the control region configured by the MIB can be identified, determined, or regarded as the initial bandwidth portion, and the terminal can receive a Physical Downlink Shared Channel (PDSCH) on which the SIB is transmitted through the configured initial bandwidth portion. In addition to receiving the SIB, the initial bandwidth portion can also be utilized for other system information (OSI), paging, and / or random access.

[0069] According to one embodiment, when one or more bandwidth part values ​​are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part value using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station may instruct the terminal to use the bandwidth part indicator in the DCI to use bandwidth part #2 (302), and the terminal may perform a bandwidth part change (or switching) to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0070] As described above, since DCI-based bandwidth part changes can be indicated by DCI scheduling PDSCH or PUSCH, when a UE receives a bandwidth part change request, it must be able to seamlessly receive or transmit data in the changed bandwidth part on the PDSCH or PUSCH scheduled by the received DCI. To this end, the standard specifies requirements for the delay time (TBWP) required when changing the bandwidth part, which can be defined, for example, as shown in [Table 3] below.

[0071]

[0072] According to one embodiment, the requirement for bandwidth part change delay time may support type 1 or type 2 depending on the capability of the terminal. The terminal may report to the base station the type of bandwidth part change delay time that it can support. For example, the bandwidth part change delay time may vary depending on the capability of the terminal, and the terminal may report to the base station the type of bandwidth part change delay time determined based on the capability of the terminal. The bandwidth part delay time type may indicate the bandwidth part change delay time.

[0073] According to one embodiment, when a terminal receives a DCI including a bandwidth portion change indicator in slot n, according to (or based on) a requirement for a bandwidth portion change delay time, the terminal can complete a change to a new bandwidth portion indicated by the bandwidth portion change indicator at a time not later than slot n+TBWP, and the terminal can perform transmission and / or reception for a data channel scheduled by the DCI in the changed new bandwidth portion.

[0074] According to one embodiment, when a base station wants to schedule a data channel with a new bandwidth portion, it may determine the time domain resource allocation for the data channel based on the bandwidth portion change delay time (TBWP) of the terminal. That is, when the base station schedules a data channel with a new bandwidth portion, it may schedule the data channel after the bandwidth portion change delay time when determining the time domain resource allocation for the data channel. Accordingly, the terminal may not expect the DCI indicating the bandwidth portion change to indicate a slot offset (K0 or K2) value smaller than the bandwidth portion change delay time (TBWP).

[0075] According to one embodiment, when a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth part change, the terminal may not perform any transmission or reception during a time period from the third symbol of a slot in which a PDCCH including the DCI indicating a bandwidth part change is received to the start point of the slot indicated by the slot offset (K0 or K2) value. For example, the slot offset (K0 or K2) value may be indicated by a time domain resource allocation indicator field in the DCI.

[0076] For example, if a terminal receives a DCI indicating a bandwidth change in slot n, and the slot offset value indicated by the DCI indicating the bandwidth change is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0077] [CA / DC related]

[0078] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and / or dual connectivity situation according to one embodiment.

[0079] Referring to FIG. 4, the wireless protocol of the mobile communication system according to one embodiment may be composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and / or NR MAC (Medium Access Control S40, S55) in the terminal and the NR base station, respectively.

[0080] According to one embodiment, the main functions of the NR SDAP (S25, S70) may include at least some of the following functions:

[0081] - Transfer of user plane data

[0082] - Mapping function between QoS flow and data bearer for both DL and UL

[0083] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0084] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0085] According to one embodiment, for an SDAP layer device, a terminal can be configured by an RRC message for each PDCP layer device, per bearer, or per logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device. When the SDAP header is configured, the SDAP layer device can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink in the NAS reflective QoS configuration 1-bit indicator (NAS reflective QoS) and the AS reflective QoS configuration 1-bit indicator (AS reflective QoS) of the SDAP header. For example, the SDAP header can include QoS flow ID information indicating QoS. For example, the QoS information can be used as data processing priority and / or scheduling information to support a desired service.

[0086] The main functions of NR PDCP (S30, S65) may include at least some of the following functions:

[0087] - Header compression and decompression (ROHC only)

[0088] - User data transfer function

[0089] - In-sequence delivery of upper layer PDUs

[0090] - Out-of-sequence delivery of upper layer PDUs

[0091] - PDCP PDU reordering for reception

[0092] - Duplicate detection of lower layer SDUs

[0093] - Retransmission function (Retransmission of PDCP SDUs)

[0094] - Encryption and decryption functions (Ciphering and deciphering)

[0095] - Timer-based SDU discard in uplink.

[0096] According to one embodiment, the reordering function of the NR PDCP device may be referred to as a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP SN (sequence number), and the reordering function of the NR PDCP device may include a function of transmitting data to an upper layer in the reordered order.

[0097] In one embodiment, the reordering function of the NR PDCP device may include the ability to forward PDCP PDUs without considering the order and the ability to record lost PDCP PDUs by reordering them. The reordering function of the NR PDCP device may include the ability to report status of lost PDCP PDUs to the transmitter and the ability to request retransmission of lost PDCP PDUs.

[0098] The main functions of NR RLC (S35, S60) may include at least some of the following functions:

[0099] - Data transfer function (Transfer of upper layer PDUs)

[0100] - In-sequence delivery of upper layer PDUs

[0101] - Out-of-sequence delivery of upper layer PDUs

[0102] - ARQ function (Error Correction through ARQ)

[0103] - Concatenation, segmentation and reassembly of RLC SDUs

[0104] - Re-segmentation of RLC data PDUs

[0105] - Reordering of RLC data PDUs

[0106] - Duplicate detection function

[0107] - Protocol error detection

[0108] - RLC SDU discard function

[0109] - RLC re-establishment function

[0110] According to one embodiment, the in-sequence delivery function of an NR RLC device may be referred to as a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of an NR RLC device may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs. The in-sequence delivery function of an NR RLC device may include a function of reordering received RLC PDUs based on an RLC SN (sequence number) or a PDCP SN (sequence number), and may include a function of recording lost RLC PDUs by rearranging the order. The in-sequence delivery function of an NR RLC device may include a function of reporting a status on lost RLC PDUs to a transmitting side, and may include a function of requesting retransmission of lost RLC PDUs.

[0111] According to one embodiment, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to an upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to an upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to an upper layer all RLC SDUs received up to the present time if a predetermined timer has expired even if there is a lost RLC SDU. In addition, the in-sequence delivery function of an NR RLC device may process RLC PDUs in the order they are received (in the order of arrival, regardless of the order of sequence numbers) and deliver them to a PDCP device regardless of the order (out-of-sequence delivery). The sequential forwarding function of the NR RLC device can receive segments that are stored in the buffer or will be received later, reassemble them into a complete RLC PDU, process them, and forward them to the PDCP device. The NR RLC layer may not include a concatenation function, and the function can be performed in the NR MAC layer or replaced with the multiplexing function of the NR MAC layer.

[0112] According to one embodiment, the out-of-sequence delivery function of an NR RLC device may be referred to as a function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order. The out-of-sequence delivery function of an NR RLC device may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs, and a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.

[0113] According to one embodiment, the NR MAC (S40, S55) may be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include at least some of the following functions.

[0114] - Mapping function (Mapping between logical channels and transport channels)

[0115] - Multiplexing / demultiplexing of MAC SDUs

[0116] - Scheduling information reporting function

[0117] - HARQ (hybrid automatic repeat request) function (Error correction through HARQ)

[0118] - Priority handling between logical channels of one UE

[0119] - Priority handling between UEs by means of dynamic scheduling

[0120] - MBMS service identification function

[0121] - Transport format selection function

[0122] - Padding function

[0123] According to one embodiment, the NR PHY layer (S45, S50) may perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0124] According to one embodiment, the detailed structure of the wireless protocol structure may be changed in various ways depending on the carrier (or cell) operation method. For example, in the case that the base station transmits data to the terminal based on a single carrier (or cell), the base station and the terminal can use a protocol structure that has a single structure for each layer, such as S00. On the other hand, in the case that the base station transmits data to the terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal can use a protocol structure that has a single structure up to RLC but multiplexes the PHY layer through the MAC layer, such as S10. For example, in the case that the base station transmits data to the terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal can use a protocol structure that has a single structure up to RLC but multiplexes the PHY layer through the MAC layer, such as S20.

[0125] [CSI resource configuration]

[0126] According to one embodiment, NR may have a channel state information (CSI) framework for directing a base station to measure and report channel state information (CSI) of a terminal. For example, the NR CSI framework may consist of at least two elements: a resource setting and a report setting. For example, a report setting may have a connection relationship with at least one resource setting ID by referencing it.

[0127] According to one embodiment, the resource setting may include information related to a reference signal (RS) for measuring channel state information by the terminal. For example, the base station may set at least one resource setting for the terminal. For example, the base station and the terminal may exchange at least some of the signaling information included in [Table 4] to convey information regarding resource settings.

[0128]

[0129] According to one embodiment, the signaling information CSI-ResourceConfig in [Table 4] may include information about each resource setting. Based on the signaling information in [Table 4], each resource setting may include a resource setting index (csi-ResourceConfigId) or a BWP index (bwp-ID) or a time axis transmission configuration of the resource (resourceType) or a resource set list (csi-RS-ResourceSetList) including at least one resource set.

[0130] According to one embodiment, the time axis transmission setting of the resource can be set to aperiodic transmission, semi-persistent transmission, or periodic transmission.

[0131] According to one embodiment, the resource set list may be a set including resource sets for channel measurement or a set including resource sets for interference measurement. For example, if the resource set list is a set including resource sets for channel measurement, each resource set may include at least one resource. The at least one resource may be an index of a CSI reference signal (CSI-RS) resource or a synchronization / broadcast channel block (SS / PBCH block, SSB (synchronization signal block)). For example, if the resource set list is a set including resource sets for interference measurement, each resource set may include at least one interference measurement resource (CSI interference measurement, CSI-IM).

[0132] According to one embodiment, when a resource set includes a CSI-RS, the base station and the terminal may exchange at least some of the signaling information included in [Table 5] to convey information about the resource set.

[0133]

[0134] According to one embodiment, the signaling information NZP-CSI-RS-ResourceSet in [Table 5] may include information about each resource set. Based on the signaling information in [Table 5], each resource set includes at least information about a resource set index (nzp-CSI-ResourceSetId) or a set of indices of CSI-RS included in the resource set (nzp-CSI-RS-Resources), and may include part of information about a spatial domain transmission filter of a CSI-RS resource included in the resource set (repetition) or whether the CSI-RS resource included in the resource set is used for tracking (trs-Info).

[0135] According to one embodiment, the CSI-RS may be the most representative reference signal included in the resource set. The base station and the terminal may exchange at least some of the signaling information included in [Table 6] to convey information regarding the CSI-RS resource.

[0136]

[0137] According to one embodiment, the signaling information NZP-CSI-RS-Resource in [Table 6] contains information about each CSI-RS. The information contained in the signaling information NZP-CSI-RS-Resource in [Table 6] may have the following meaning or may include the following information.

[0138] - nzp-CSI-RS-ResourceId: CSI-RS resource index

[0139] - resourceMapping: Resource mapping information for CSI-RS resources

[0140] - powerControlOffset: Ratio between PDSCH EPRE (Energy Per RE) and CSI-RS EPRE

[0141] - powerControlOffsetSS: Ratio between SS / PBCH block EPRE and CSI-RS EPRE

[0142] - scramblingID: scrambling index of the CSI-RS sequence

[0143] - periodicityAndOffset: Transmission period and slot offset of the CSI-RS resource

[0144] - qcl-InfoPeriodicCSI-RS: TCI-state information if the CSI-RS is a periodic CSI-RS.

[0145] According to one embodiment, resourceMapping included in the signaling information NZP-CSI-RS-Resource indicates resource mapping information of a CSI-RS resource, and the signaling information NZP-CSI-RS-Resource may include frequency resource resource element (RE) mapping, number of ports, symbol mapping, CDM type, frequency resource density, and / or frequency band mapping information. The number of ports, frequency resource density, CDM type, and / or time-frequency axis RE mapping that can be set through the signaling information NZP-CSI-RS-Resource may have a value set in one of the rows of the following [Table 7].

[0146]

[0147]

[0148] According to one embodiment, [Table 7] shows the frequency resource density (density), CDM type, frequency axis of CSI-RS component RE pattern (pattern) that can be set according to the number of CSI-RS ports (X), and the start position of the time axis ( ), the number of frequency-axis REs (k') and / or the number of time-axis REs (l') of the CSI-RS component RE pattern may be indicated. The aforementioned CSI-RS component RE pattern may be a basic unit configuring a CSI-RS resource. Through Y=1+max(k') REs in the frequency axis and Z=1+max(l') REs in the time axis, the CSI-RS component RE pattern may be composed of YZ REs.

[0149] For example, when the number of CSI-RS ports is 1 port, the CSI-RS RE position can be specified without limitation of subcarriers within a PRB (Physical Resource Block), and the CSI-RS RE position can be specified by a 12-bit bitmap.

[0150] For example, when the number of CSI-RS ports is {2, 4, 8, 12, 16, 24, 32} ports and Y=2, CSI-RS RE positions can be specified for every two subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 6-bit bitmap. For example, when the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE positions can be specified for every four subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 3-bit bitmap. Similarly, time axis RE positions can be specified by a bitmap of a total of 14 bits.

[0151] [CSI report configuration]

[0152] According to one embodiment, a report setting may have a connection relationship with at least one ID of a resource setting by referencing each other, and the resource setting(s) having a connection relationship with the report setting may provide configuration information including information on a reference signal for measuring channel information. For example, when the resource setting(s) having a connection relationship (or mapping relationship) with the report setting are used for measuring channel information, the measured channel information may be used for reporting channel information according to the reporting method set in the report setting having the connection relationship.

[0153] According to one embodiment, the report setting may include configuration information related to the CSI reporting method. For example, the base station and the terminal may exchange at least some of the signaling information included in [Table 8] to convey information regarding the report setting.

[0154]

[0155]

[0156]

[0157] According to one embodiment, the signaling information CSI-ReportConfig included in [Table 8] may include information about each report setting. The information included in the signaling information CSI-ReportConfig may have the following meaning or include the following information.

[0158] - reportConfigId: report setting index

[0159] - carrier: serving cell index

[0160] - resourcesForChannelMeasurement: resource setting index for channel measurement that has a connection (or mapping) relationship with report setting.

[0161] - csi-IM-ResourcesForInterference: Resource setting index containing CSI-IM resources for interference measurement that have a relationship with report settings.

[0162] - nzp-CSI-RS-ResourcesForInterference: Resource setting index containing CSI-RS resources for interference measurement that are linked to report settings.

[0163] - reportConfigType: Indicates the time axis transmission settings and transmission channel of the channel report, and may have aperiodic transmission or semi-persistent PUCCH (Physical Uplink Control Channel) transmission or semi-periodic PUSCH transmission or periodic transmission settings.

[0164] - reportQuantity: Indicates the type of channel information to be reported. It can have the types of channel information ('cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RI-LI-PMI-CQI') when no channel report is transmitted and when a channel report is transmitted. Here, the elements included in the types of channel information mean CQI (Channel Quality Indicator), PMI (Precoding Matric Indicator), CRI (CSI-RS Resource Indicator), SSBRI (SS / PBCH block Resource Indicator), Layer Indicator(LI), Rank Indicator(RI), and / or L1-RSRP (Reference Signal Received Power).

[0165] - reportFreqConfiguration: Indicates whether the reported channel information includes only information about the entire wideband or information about each subband. If it includes information about each subband, it can have configuration information about the subband that contains the channel information.

[0166] - timeRestrictionForChannelMeasurements: Whether the reference signal for channel measurement among the reference signals referenced by the reported channel information has a time axis restriction.

[0167] - timeRestrictionForInterferenceMeasurements: Whether the time axis of the reference signal for interference measurement is restricted among the reference signals referenced by the reported channel information.

[0168] - codebookConfig: Codebook information referenced by the channel information being reported

[0169] - groupBasedBeamReporting: Whether to group beams in channel reporting

[0170] - cqi-Table: CQI table index referenced by the reported channel information

[0171] - subbandSize: Index indicating the subband size of channel information

[0172] - non-PMI-PortIndication: Port mapping information referenced when reporting non-PMI channel information.

[0173] According to one embodiment, when a base station instructs channel information reporting through upper layer signaling or L1 signaling, a terminal may perform channel information reporting based on configuration information included in the instructed report setting.

[0174] According to one embodiment, the base station may instruct the terminal to report channel state information (CSI) through upper layer signaling including Radio Resource Control (RRC) signaling or Medium Access Control (MAC) Control Element (CE) signaling, or L1 signaling (e.g., common DCI, group-common DCI, terminal-specific DCI).

[0175] For example, a base station can instruct a terminal to report aperiodic channel information (CSI) report via higher layer signaling or DCI using DCI format 0_1. The base station can set parameters for aperiodic CSI report of the terminal, or multiple CSI report trigger states including parameters for CSI report, via higher layer signaling. For example, parameters for CSI report or CSI report trigger states can include a set including slot interval or possible slot interval between a PDCCH including DCI and a PUSCH including CSI report, a reference signal ID for channel state measurement, and / or a type of channel information.

[0176] In one example, when a base station indicates some of multiple CSI report trigger states to a terminal via DCI, the terminal reports channel information according to the CSI report settings of the report settings set in the indicated CSI report trigger states. For example, the channel information reporting of the terminal may be performed via a PUSCH scheduled with DCI format 0_1. For example, the time domain resource allocation of the PUSCH including the CSI report of the terminal may be performed based on the slot interval with respect to the PDCCH indicated via the DCI, the start symbol and / or symbol length indication within the slot for the time domain resource allocation of the PUSCH, etc. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted may be indicated via the slot interval with respect to the PDCCH indicated via the DCI, and the start symbol and symbol length within the slot may be indicated via the time domain resource assignment field of the DCI described above.

[0177] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report on the PUSCH via DCI using DCI format 0_1. The base station can activate or deactivate the semi-persistent CSI report transmitted on the PUSCH via DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station can configure multiple CSI report trigger states including parameters for the terminal's semi-persistent CSI report or parameters for the semi-persistent CSI report via upper layer signaling.

[0178] According to one embodiment, parameters for a CSI report, or a CSI report trigger state, may include a slot interval or a set including possible slot intervals between a PDCCH including DCI indicating a CSI report and a PUSCH including the CSI report, a slot interval between a slot in which upper layer signaling indicating a CSI report is activated and a PUSCH including the CSI report, a slot interval period of the CSI report, and / or a type of channel information to be included. When a base station activates some of a plurality of CSI report trigger states or some of a plurality of report settings to a terminal through upper layer signaling or DCI, the terminal may report channel information according to a report setting included in the indicated CSI report trigger state or a CSI report setting set in the activated report setting. The channel information reporting may be performed through a PUSCH that is semi-persistently scheduled in DCI format 0_1 ​​scrambled with SP-CSI-RNTI. The time domain resource allocation of the PUSCH including the CSI report of the terminal can be performed through the slot interval period of the CSI report, the slot interval with respect to the slot in which upper layer signaling is activated, the slot interval with respect to the PDCCH indicated through DCI, and / or the start symbol and symbol length indication within the slot for the time domain resource allocation of the PUSCH. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted can be indicated through the slot interval with respect to the PDCCH indicated through DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the aforementioned DCI format 0_1.

[0179] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report on the PUCCH through upper layer signaling such as MAC-CE. Through MAC-CE signaling, the base station can activate or deactivate the semi-persistent CSI report transmitted on the PUCCH.

[0180] In one example, when the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station can configure parameters for the semi-persistent CSI report of the terminal through upper layer signaling. The parameters for the CSI report can include a PUCCH resource on which the CSI report is transmitted, a slot interval period of the CSI report, and / or a type of channel information. The terminal can transmit the CSI report through the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the terminal can transmit the CSI report through the PUSCH.

[0181] For example, the location of a PUCCH transmission slot including a CSI report may be indicated by a slot interval period of the CSI report set via higher layer signaling, and / or a slot interval between a slot in which higher layer signaling is activated and a PUCCH including the CSI report. The start symbol and symbol length within a slot may be indicated by a start symbol and symbol length to which a PUCCH resource is allocated, set via higher layer signaling.

[0182] For example, a base station can instruct a terminal to perform periodic CSI reporting through upper layer signaling. The base station can activate or deactivate periodic CSI reporting through upper layer signaling, including RRC signaling. When periodic CSI reporting is activated, the terminal can periodically report channel information according to a configured slot interval. When periodic CSI reporting is deactivated, the terminal can stop the activated periodic channel information reporting. The base station can configure report settings including parameters for the terminal's periodic CSI reporting through upper layer signaling.

[0183] For example, parameters for a CSI report may include PUCCH resource settings for the CSI report, slot spacing between slots in which upper layer signaling indicating the CSI report is activated and the PUCCH containing the CSI report, slot spacing period of the CSI report, reference signal ID for channel state measurement, and / or type of channel information.

[0184] According to one embodiment, the terminal may transmit the CSI report via PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the terminal may transmit the CSI report via the PUSCH. For example, the position of the slot in which the PUCCH including the CSI report is transmitted may be indicated by the slot interval period of the CSI report configured through higher layer signaling, and / or the slot interval between the slot in which the higher layer signaling is activated and the PUCCH including the CSI report. The start symbol and symbol length within the slot may be indicated by the start symbol and symbol length to which the PUCCH resource is allocated, configured through higher layer signaling.

[0185] According to one embodiment, for a CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig may be associated with a CSI resource setting associated with the report setting, and / or one downlink (DL) bandwidth portion identified by a higher layer parameter bandwidth portion identifier (bwp-id) given to CSI-ResourceConfig.

[0186] According to one embodiment, for each report setting CSI-ReportConfig, time domain reporting behaviors of 'Aperiodic', 'Semi-Persistent', and 'Periodic' may be supported, and the reporting method (e.g., Aperiodic, Semi-Persistent, and Periodic) may be set from the base station to the terminal by the reportConfigType parameter set from the upper layer.

[0187] For example, the semi-persistent CSI reporting method may support or include 'semi-PersistentOnPUCCH' and 'semi-PersistentOnPUSCH'. For example, in the periodic or semi-persistent CSI reporting method, the terminal may be configured with PUCCH or PUSCH resources to transmit CSI from the base station through upper layer signaling. The period and slot offset of the PUCCH or PUSCH resources to transmit CSI may be given as a numerology of the uplink (UL) bandwidth portion in which the CSI report is configured to be transmitted. For example, in the aperiodic CSI reporting method, the terminal may be scheduled with PUSCH resources to transmit CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

[0188] According to one embodiment, for a CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig may include S (≥1) CSI resource sets (given by the upper layer parameter csi-RS-ResourceSetList). For example, the CSI resource set list may be composed of a non-zero power (NZP) CSI-RS resource set and a SS / PBCH block set, or a CSI-interference measurement (CSI-IM) resource set.

[0189] According to one embodiment, each CSI resource setting may be located in a downlink (DL) bandwidth portion identified by a higher layer parameter bwp-id, and the CSI resource setting may be linked (or mapped, corresponded) to a CSI reporting setting of the same downlink bandwidth portion.

[0190] According to one embodiment, the time domain operation of CSI-RS resources within a CSI resource setting can be set to one of 'aperiodic', 'periodic', or 'semi-persistent' from the upper layer parameter resourceType. For periodic or semi-persistent CSI resource setting, the number of CSI-RS resource sets can be limited to S=1, and the set period and slot offset can be given as a numerology of a downlink bandwidth portion identified by bwp-id. A terminal can receive one or more CSI resource settings for channel or interference measurement from a base station through upper layer signaling. For example, a CSI resource setting set for a terminal can include at least one of the following CSI resources.

[0191] - CSI-IM resources for interference measurements

[0192] - NZP CSI-RS resources for interference measurements

[0193] - NZP CSI-RS resources for channel measurements

[0194] According to one embodiment, for CSI-RS resource sets associated with resource settings where the upper layer parameter resourceType is set to 'aperiodic', 'periodic', or 'semi-persistent', a trigger state for a CSI report setting where reportType is set to 'aperiodic' and a resource setting for channel or interference measurement for one or more component cells (CC) may be set to the upper layer parameter CSI-AperiodicTriggerStateList.

[0195] According to one embodiment, a terminal may use PUSCH when performing aperiodic CSI reporting, a terminal may use PUCCH when performing periodic CSI reporting, a terminal may use PUSCH when triggered or activated by DCI when performing semi-persistent CSI reporting, and a terminal may use PUCCH after being activated by a MAC control element (MAC CE) when performing semi-persistent CSI reporting. As described above, CSI resource settings may also be configured as aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings may be supported based on [Table 9] below.

[0196]

[0197] Table 5.2.1.4-1: Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations.

[0198] According to one embodiment, aperiodic CSI reporting may be triggered by the “CSI request” field of the aforementioned DCI format 0_1 ​​corresponding to scheduling DCI for PUSCH. The UE may monitor the PDCCH, acquire the DCI format 0_1, and acquire scheduling information and a CSI request indicator for the PUSCH. The CSI request indicator may be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and may be determined by higher layer signaling (reportTriggerSize). One of one or more aperiodic CSI reporting trigger states that may be set by higher layer signaling (CSI-AperiodicTriggerStateList) may be triggered by the CSI request indicator.

[0199] - If all bits in the CSI request field are 0, this may mean that no CSI report is requested.

[0200] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateList is greater than 2NTs-1, M CSI trigger states can be mapped to 2NTs-1 according to the mapping relationship defined, and one of the trigger states of 2NTs-1 can be indicated by the CSI request field.

[0201] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateList is less than or equal to 2NTs-1, one of the M CSI trigger states may be indicated by the CSI request field.

[0202] According to one embodiment, [Table 10] describes an example of a relationship between a CSI request indicator and a CSI trigger state that may be indicated by the indicator.

[0203]

[0204] According to one embodiment, a terminal may perform measurements on CSI resources within a CSI trigger state triggered by a CSI request field, from which the terminal may generate CSI (e.g., including at least one of CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP).

[0205] According to one embodiment, the terminal may transmit the acquired CSI using the PUSCH scheduled by the corresponding DCI format 0_1. If 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 ​​indicates “1”, the terminal may multiplex and transmit the acquired CSI with uplink data (UL-SCH (shared channel)) on the PUSCH resource scheduled by the DCI format 0_1. If 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 ​​indicates “0”, the terminal may map and transmit only the CSI without uplink data (UL-SCH) on the PUSCH resource scheduled by the DCI format 0_1.

[0206] FIG. 5 is a diagram illustrating an example of an aperiodic CSI reporting method according to one embodiment.

[0207] Referring to FIG. 5, in an example (500) of FIG. 5, a terminal can monitor a PDCCH (501) to obtain DCI format 0_1, and can obtain scheduling information and CSI request information for a PUSCH (505) based on the obtained DCI.

[0208] According to one embodiment, the terminal can obtain resource information on the CSI-RS (502) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform measurement on the transmitted CSI-RS (502) resource based on the time point of receiving DCI format 0_1 ​​and a parameter (e.g., aperiodicTriggeringOffset) for an offset in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). That is, the terminal can determine the time point of CSI-RS resource measurement based on the time point of receiving DCI format 0_1 ​​and the CSI resource set configuration.

[0209] For example, the terminal may receive an offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station through upper layer signaling. For example, the configured offset value X may mean an offset between a slot in which a DCI triggering aperiodic CSI reporting is received and a slot in which a CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in [Table 11] below.

[0210]

[0211] According to one embodiment, an example (500) of FIG. 5 shows an example in which the aforementioned offset value is set to X=0. In this case, the terminal can receive a CSI-RS (502) in a slot (e.g., slot 0 (506) of FIG. 5) in which a DCI format 0_1 ​​that triggers aperiodic CSI reporting is received, and can report CSI information measured with the received CSI-RS to the base station through a PUSCH (505).

[0212] According to one embodiment, the terminal can obtain scheduling information (e.g., information corresponding to each field of the DCI format 0_1) for the PUSCH (505) for CSI reporting from the DCI format 0_1. For example, the terminal can obtain information on a slot in which the PUSCH (505) is to be transmitted from the aforementioned time domain resource allocation information for the PUSCH (505) in the DCI format 0_1. For example, in an example (500) of FIG. 5, the terminal can obtain a K2 value corresponding to a slot offset value for PDCCH-to-PUSCH as 3, and the PUSCH (505) can be transmitted in slot 3 (509), which is 3 slots away from slot 0 (506), which corresponds to the time point at which the PDCCH (501) is received.

[0213] In an example (510) of FIG. 5, the terminal can monitor the PDCCH (511) to obtain DCI format 0_1, and can obtain scheduling information and CSI request information for the PUSCH (515) from the obtained DCI (or, DCI format 0_1). The terminal can obtain resource information for the CSI-RS (512) to be measured from the received CSI request indicator. An example (510) of FIG. 5 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. The terminal can receive the CSI-RS (512) in a slot (e.g., slot 0 (516) of FIG. 5) in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received, and the terminal can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (515).

[0214] According to one embodiment, an aperiodic CSI report may include at least one or both of CSI part 1 and CSI part 2, and when the aperiodic CSI report is transmitted via a PUSCH, the aperiodic CSI report may be multiplexed with a transport block. For multiplexing with a transport block, the aperiodic CSI report may be encoded and rate-matched, and then mapped to a resource element in a PUSCH in a specific pattern and transmitted. The CRC insertion may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching when multiplexing CSI Part 1 or CSI part 2 included in the aperiodic CSI report may be calculated as shown in [Table 12] below.

[0215]

[0216]

[0217] According to one embodiment, in the case of PUSCH repetition transmission schemes A and B, the UE may multiplex and transmit an aperiodic CSI report only on the first repetition transmission among the PUSCH repetition transmissions. This is because the aperiodic CSI report information to be multiplexed is encoded in a polar code manner, and in this case, in order for the aperiodic CSI report information to be multiplexed on multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, each actual repetition may have a different OFDM symbol length, and therefore the aperiodic CSI report may be multiplexed and transmitted only on the first PUSCH repetition.

[0218] According to one embodiment, for PUSCH repetition transmission scheme B, if a UE schedules aperiodic CSI reporting without scheduling a transport block or receives a DCI activating semi-persistent CSI reporting, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repetition transmissions configured by upper layer signaling is greater than 1. Furthermore, if the UE schedules or activates aperiodic or semi-persistent CSI reporting without scheduling a transport block based on PUSCH repetition transmission scheme B, the UE may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including semi-persistent CSI based on PUSCH repetition transmission scheme B without scheduling a DCI after semi-persistent CSI reporting is activated by DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0219] According to one embodiment, when a base station instructs a terminal to perform an aperiodic CSI report or a semi-persistent CSI report through DCI, the terminal can determine or identify whether it can perform a valid channel report through the instructed CSI report by considering the channel computation time required for the CSI report.

[0220] According to one embodiment, for an aperiodic CSI report or a semi-persistent CSI report indicated through DCI, the terminal may perform a valid CSI report starting from the uplink symbol after the Z symbol after the last symbol included in the PDCCH including the DCI indicating the CSI report.

[0221] For example, the Z symbol can be determined based on the numerology of the downlink bandwidth part corresponding to the PDCCH including the DCI indicating the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type and / or characteristics (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.) of the channel information reported in the CSI report. That is, in order for a CSI report to be determined as a valid CSI report (or, in order for a CSI report to be a valid CSI report), the uplink transmission of the CSI report must not be performed before the Zref symbol, including the timing advance. In this case, the Zref symbol is determined based on the time T from the moment when the last symbol of the triggering PDCCH ends. proc,CSI =(Z)(2048+144)·κ2 -μ ·T C It may be an uplink symbol that starts a CP (cyclic prefix).

[0222] In one embodiment, the detailed value of Z is as described below, and T c =1 / (△f max ·N f ), △f max =480·10 3 Hz, N f =4096, κ=64, and μ is the numerology. Here, μ is (μ PDCCH ,μ CSI-RS,μ UL ) is the largest T proc,CSI It can be promised that something that causes a value will be used.

[0223] μ PDCCH can be referred to as the subcarrier spacing used for PDCCH transmission, μ CSI-RS can be referred to as the subcarrier spacing used for CSI-RS transmission, μ UL can be referred to as the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. For example, μ is (μ PDCCH ,μ UL ) The largest T among proc,CSI It may cause the value to be μ PDCCH and μ UL The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 1.

[0224] According to one embodiment, when a reference signal for channel measurement for an aperiodic CSI report instructed to a terminal through DCI is an aperiodic reference signal, the terminal can perform a valid CSI report starting from an uplink symbol after the Z' symbol after the last symbol including the reference signal ends.

[0225] For example, the aforementioned Z' symbol can be determined based on the numerology of the downlink bandwidth part corresponding to the PDCCH including the DCI indicating the CSI report, the numerology of the bandwidth corresponding to the reference signal for channel measurement for the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type and / or characteristics of the channel information reported in the CSI report (e.g., report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.). That is, in order for a CSI report to be determined as a valid CSI report (for a CSI report to be a valid CSI report), the uplink transmission of the corresponding CSI report must not be performed prior to the Zref' symbol, including the timing advance.

[0226] For example, the Zref' symbol starts at the time T' from the moment when the last symbol of the aperiodic CSI-RS or aperiodic CSI-IM triggered by the triggering PDCCH ends. proc,CSI =(Z')(2048+144)·κ2 -μ )·T C It may be an uplink symbol that starts CP (cyclic prefix). Here, the detailed value of Z' is as described below, and T c =1 / (△f max ·N f ), △f max =480·10 3 Hz, N f =4096, κ=64, and μ is numerology.

[0227] At this time, μ is (μ PDCCH ,μ CSI-RS ,μ UL ) is the largest T proc,CSI It can be promised that the value that causes it to be used is μ PDCCHcan be referred to as the subcarrier interval used for triggering PDCCH transmission, μ CSI-RS can be referred to as the subcarrier spacing used for CSI-RS transmission, μ UL may be referred to as the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. For example, μ is (μ PDCCH ,μ UL ) is the largest T proc,CSI It can be promised that the value will be used. In this case, μ PDCCH and μ UL The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 2.

[0228] According to one embodiment, when a base station instructs a terminal to perform an aperiodic CSI report for an aperiodic reference signal through DCI, the terminal can perform a valid CSI report starting from the first uplink symbol that satisfies both the time point Z symbol after the last symbol included in the PDCCH including the DCI instructing the CSI report and the time point Z' symbol after the last symbol including the reference signal. That is, in the case of aperiodic CSI reporting based on an aperiodic reference signal, the terminal determines that the CSI report is valid only when both CSI reporting validity conditions 1 and 2 are satisfied.

[0229] According to one embodiment, if the CSI report time indicated by the base station does not satisfy the CSI computation time requirement, the terminal may determine the CSI report to be invalid and may not consider updating the channel information status for the CSI report.

[0230] According to one embodiment, the Z, Z' symbols for calculating the CSI computation time may be based on [Table 13] and [Table 14] below. For example, if the channel information reported in the CSI report includes only wideband information, the number of ports of the reference signal is 4 or less, there is one reference signal resource, and the codebook type is 'typeI-SinglePanel' or the type of channel information to be reported (report quantity) is 'cri-RI-CQI', the Z, Z' symbols may be based on [Table 14]. Follow the value. This will be referred to as delay requirement 2 in the future.

[0231] In addition, if the PUSCH including the CSI report does not include TB or HARQ-ACK and the CPU occupation of the terminal is 0, the Z and Z' symbols are as in [Table 13]. The value is followed and is named as delay requirement 1. The description of the CPU occupation mentioned above is described in detail below. In addition, when the report quantity is 'cri-RSRP' or 'ssb-Index-RSRP', the Z, Z' symbols are as shown in [Table 14]. Follow the values. X1, X2, X3, and X4 in [Table 14] represent the UE capability for beam reporting time, and KB1 and KB2 in [Table 14] represent the UE capability for beam change time. If it does not correspond to the type or characteristic of channel information reported in the CSI report, the Z and Z' symbols are used in [Table 14]. Follow the value.

[0232]

[0233] [CSI reference resource]

[0234] According to one embodiment, when a base station instructs a terminal to perform an aperiodic / semi-persistent / periodic CSI report, the base station may set a CSI reference resource to determine a reference time and frequency for a channel to be reported in the CSI report.

[0235] For example, the frequency of the CSI reference resource may be the carrier and subband information for measuring CSI, which are indicated in the CSI report configuration, and the carrier information and subband information may correspond to carrier and reportFreqConfiguration in the upper layer signaling, CSI-ReportConfig, respectively.

[0236] According to one embodiment, the time of the CSI reference resource may be defined based on the time at which the CSI report is transmitted. For example, when CSI report #X is instructed to be transmitted in the uplink slot n' of the carrier and BWP to which the CSI report is to be transmitted, the time of the CSI reference resource of the CSI report #X may be defined as the downlink slot n-nCSI-ref of the carrier and BWP on which the CSI is measured. Downlink slot n is named as μDL when the numerology of the carrier and BWP on which the CSI is measured is named μUL, and the numerology of the carrier and BWP on which the CSI report #X is transmitted is named μDL. is calculated as

[0237] According to one embodiment, nCSI-ref, which is a slot interval between downlink slot n and a CSI reference signal, may be determined based on the number of CSI-RS / SSB resources for channel measurement when CSI report #X transmitted in uplink slot n' is a semi-persistent or periodic CSI report. For example, nCSI-ref, which is a slot interval between downlink slot n and a CSI reference signal, may be determined when a single CSI-RS / SSB resource is associated (or mapped, corresponded) to a CSI report. , and if multiple CSI-RS / SSB resources are connected to a CSI report. can follow. If the CSI report #X transmitted in uplink slot n' is an aperiodic CSI report, the CSI computation time Z' for channel measurement is considered. is calculated as mentioned above is the number of symbols contained in one slot, and in NR =14 is assumed.

[0238] According to one embodiment, when a base station instructs a terminal to transmit a CSI report in uplink slot n' through upper layer signaling or DCI, the terminal may report CSI by performing channel measurement or interference measurement on a CSI-RS resource, CSI-IM resource, or SSB resource that is transmitted no later than a CSI reference resource slot of the CSI report transmitted in uplink slot n' among CSI-RS resources, CSI-IM resources, or SSB resources associated (or mapped, corresponding) with the CSI report.

[0239] For example, a CSI-RS resource, CSI-IM resource, or SSB resource associated with (or mapped to, corresponding to) a CSI report may be a CSI-RS resource, CSI-IM resource, or SSB resource included in a resource set configured in a resource setting referenced by a report setting for a CSI report of a terminal configured through upper layer signaling. A CSI-RS resource, CSI-IM resource, or SSB resource associated with a CSI report may be a CSI-RS resource, CSI-IM resource, or SSB resource referenced by a CSI report trigger state including parameters for a CSI report. A CSI-RS resource, CSI-IM resource, or SSB resource associated with a CSI report may be a CSI-RS resource, CSI-IM resource, or SSB resource indicated by an ID of a reference signal (RS) set.

[0240] According to one embodiment, a CSI-RS / CSI-IM / SSB occasion may be referred to as a transmission time of CSI-RS / CSI-IM / SSB resource(s) determined by a higher layer configuration or a combination of the higher layer configuration and DCI triggering. For example, a semi-persistent or periodic CSI-RS resource may determine a slot to be transmitted according to a slot period and slot offset configured by higher layer signaling, and the transmission symbol(s) within the slot may be determined according to resource mapping information (resourceMapping). As another example, an aperiodic CSI-RS resource may determine a slot to be transmitted according to a slot offset from a PDCCH including a DCI indicating channel reporting configured by higher layer signaling, and the transmission symbol(s) within the slot may be determined according to resourceMapping information.

[0241] According to one embodiment, a CSI-RS occasion may be determined by independently considering the transmission time of each CSI-RS resource or by comprehensively considering the transmission time of one or more CSI-RS resource(s) included in a resource set, and accordingly, the following two interpretations are possible for the CSI-RS occasion according to each resource set configuration.

[0242] - Interpretation 1-1: From the start time of the earliest symbol to the end time of the latest symbol in which one or more specific resources among the CSI-RS resources included in the resource set(s) set in the resource setting referenced by the report setting set for the CSI report are transmitted.

[0243] - Interpretation 1-2: From the start time of the earliest symbol transmitted by the CSI-RS resource to the end time of the latest symbol transmitted by the CSI-RS resource among all CSI-RS resources included in the resource set(s) set in the resource setting referenced by the report setting set for the CSI report.

[0244] In the embodiments of the present disclosure below, it is possible to consider both interpretations of CSI-RS occasions and apply them individually. Furthermore, it is possible to consider both interpretations for CSI-IM occasions and SSB occasions, similar to CSI-RS occasions. However, since the principles are similar to those described above, any redundant explanation will be omitted below.

[0245] According to one embodiment, the 'CSI-RS / CSI-IM / SSB occasion' for CSI report #X transmitted in 'uplink slot n' may be referenced as a set of CSI-RS resources, CSI-IM resources, and SSB resources included in a resource set set in a resource setting referenced by a report setting set for CSI report #X, among CSI-RS occasions, CSI-IM occasions, and / or SSB occasions that are not later than the CSI reference resource of CSI report #X transmitted in 'uplink slot n'.

[0246] According to one embodiment, the latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in 'uplink slot n' can be interpreted in two ways as follows.

[0247] - Interpretation 2-1: A set of occasions including the latest CSI-RS occasion among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', the latest CSI-IM occasion among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', and the latest SSB occasion among the SSB occasions for CSI report #0 transmitted in uplink slot n'.

[0248] - Interpretation 2-2: The latest occasion among all CSI-RS occasions, CSI-IM occasions, and SSB occasions for CSI report #X transmitted in uplink slot n'

[0249] According to one embodiment, it is possible for both interpretations of the “latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in ‘uplink slot n’” to be applied individually. In addition, considering the two interpretations (Interpretation 1-1, Interpretation 1-2) for the CSI-RS occasion, CSI-IM occasion, and SSB occasion described above, in the embodiments of the present disclosure, the “latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in ‘uplink slot n’” can have four different interpretations (applying Interpretation 1-1 and Interpretation 2-1, applying Interpretation 1-1 and Interpretation 2-2, applying Interpretation 1-2 and Interpretation 2-1, applying Interpretation 1-2 and Interpretation 2-2) to be applied individually.

[0250] In one embodiment, the base station may instruct the CSI report based on the amount of channel information that the terminal can calculate simultaneously for the CSI report. For example, the base station may instruct the CSI report based on the number of channel information calculation units (CSI processing units, CPUs) of the terminal. The number of channel information calculation units that the terminal can calculate simultaneously is N. CPU If so, the terminal is N CPU Do not expect CSI report instructions from base stations that require more channel information calculations, or N CPU We may not consider updating channel information that requires more channel information calculations. N CPU The terminal can report to the base station through upper layer signaling or the base station can set it through upper layer signaling.

[0251] According to one embodiment, the CSI report instructed by the base station to the terminal is the total number N of channel information that the terminal can calculate simultaneously. CPU It can be assumed that some or all of the CPU is occupied for channel information calculation. For each CSI report, for example, the number of channel information calculation units required for CSI report n (n=0,1,…,N-1) is Then, the number of channel information calculation units required for a total of N CSI reports is It can be referenced as follows. The calculation unit of channel information required for each reportQuantity set in the CSI report can be set as shown in [Table 15] below.

[0252]

[0253] According to one embodiment, the number of channel information calculations required by a terminal for multiple CSI reports at a given point in time is the number N of channel information calculation units that the terminal can calculate simultaneously. CPU In more cases, the terminal may not consider or perform channel information updates for some CSI reports. Among the multiple indicated CSI reports, the CSI reports for which channel information updates are not considered or performed may be determined at least by considering the time that the channel information calculation required for the CSI report takes up the CPU and / or the priority of the channel information being reported. For example, the channel information update may not be considered or performed for the CSI report for which the channel information calculation required for the CSI report takes up the latest CPU time, and the channel information update may not be considered or performed preferentially for the CSI report with a lower priority.

[0254] The priority of channel information can be determined by referring to [Table 16] below.

[0255]

[0256] According to one embodiment, the CSI priority for a CSI report may be determined based on the priority value PriiCSI(y,k,c,s) of [Table 16]. Referring to [Table 16], the CSI priority value may be determined based on the type of channel information included in the CSI report, the time axis reporting characteristic of the CSI report (aperiodic, semi-persistent, periodic), the channel on which the CSI report is transmitted (PUSCH, PUCCH), the serving cell index, and / or the CSI report configuration index. With respect to the CSI priority for the CSI report, by comparing the priority values ​​PriiCSI(y,k,c,s), it may be determined that the CSI priority for a CSI report with a smaller priority value is higher.

[0257] According to one embodiment, if the time taken by the CPU to calculate channel information required for a CSI report instructed by the base station to the terminal is called CPU occupation time, the CPU occupation time may be determined based on the type of channel information included in the CSI report (report quantity), the time axis characteristics of the CSI report (aperiodic, semi-persistent, periodic), the slot or symbol occupied by the upper layer signaling or DCI instructing the CSI report, and / or a part or all of the slot or symbol occupied by the reference signal for channel state measurement.

[0258] [PDCCH: DCI related]

[0259] Below, downlink control information (DCI) in a 5G system is described in detail.

[0260] According to one embodiment, in a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) may be transmitted from a base station to a terminal via DCI. The terminal may monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format may be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0261] According to one embodiment, DCI may be transmitted through or on a Physical Downlink Control Channel (PDCCH) that is a physical downlink control channel after going through a channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC may be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control command, or random access response). That is, the RNTI may not be transmitted explicitly but may be included in the CRC calculation process and transmitted. When a UE receives a DCI message transmitted on the PDCCH, the UE verifies the CRC using the assigned RNTI, and if the CRC verification result is correct, the UE can identify or know that the DCI message has been transmitted to the UE.

[0262] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

[0263] In one embodiment, DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, wherein the CRC may be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, at least some of the information in [Table 17] below.

[0264]

[0265] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, at least some of the information in [Table 18] below.

[0266]

[0267]

[0268] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, at least some of the information in [Table 19] below.

[0269]

[0270] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, at least some of the information in [Table 20] below.

[0271]

[0272] A diagram is provided illustrating a downlink control channel in a 5G communication system.

[0273] Figure 5 is a diagram illustrating an example of an aperiodic CSI reporting method.

[0274] FIG. 6 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. Referring to FIG. 6, an example is illustrated in which two control regions (Control Region #1 (601), Control Region #2 (602)) are set within a UE bandwidth part (610) on the frequency axis and one slot (620) on the time axis. The control regions (601, 602) may be set to specific frequency resources (603) within the entire UE bandwidth part (610) on the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 604). Referring to FIG. 6, Control Region #1 (601) is set to a control region length of two symbols, and Control Region #2 (602) is set to a control region length of one symbol.

[0275] According to one embodiment, the control region in the aforementioned 5G can be configured by the base station to the terminal through upper layer signaling (e.g., system information, MIB (Master Information Block), RRC (Radio Resource Control) signaling). Configuring the control region for the terminal means providing information such as the control region identifier (Identity), the frequency location of the control region, and / or the symbol length of the control region. For example, the configuration information for the control region may include at least some of the information in [Table 21].

[0276]

[0277] In [Table 21], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices and / or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0278] Figure 7 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G.

[0279] Referring to Fig. 7, the basic unit of time and frequency resources constituting the control channel can be referred to as a REG (Resource Element Group, 703). A REG (703) can be defined as 1 OFDM symbol (701) on the time axis and 1 PRB (Physical Resource Block, 702) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (703) to form a downlink control channel allocation unit.

[0280] According to one embodiment, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 704), 1 CCE (704) may be composed of multiple REGs (703). Taking REG (703) illustrated in FIG. 7 as an example, REG (703) may be composed of 12 REs, and if 1 CCE (704) is composed of 6 REGs (703), 1 CCE (704) may be composed of 72 REs.

[0281] According to one embodiment, when a downlink control region is established, the downlink control region may be composed of a plurality of CCEs (704), and a specific downlink control channel may be mapped to one or a plurality of CCEs (704) and transmitted according to an aggregation level (AL) within the control region. The CCEs (704) within the control region are distinguished by numbers, and the numbers of the CCEs (704) may be assigned or indicated according to a logical mapping method.

[0282] The basic unit of the downlink control channel illustrated in Fig. 7, i.e., REG (703), may include both REs to which DCI is mapped and areas to which DMRS (705), which is a reference signal for decoding it, is mapped. As in Fig. 7, three DMRSs (705) may be transmitted within one REG (703).

[0283] According to one embodiment, the number of CCEs required to transmit a PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs can be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel can be transmitted through L CCEs. The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs for blind decoding is defined. The search space is a set of downlink control channel candidates consisting of CCEs that the terminal must attempt to decode on a given aggregation level, and since there are various aggregation levels that form a single bundle with 1, 2, 4, 8, or 16 CCEs, the terminal can have multiple search spaces. A search space set can be defined as the collection of search spaces at all established aggregation levels.

[0284] According to one embodiment, the search space may be classified into a common search space and a UE-specific search space. A certain group of UEs or all UEs may search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling for system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, may be received by searching the common search space of the PDCCH. For example, in the case of the common search space, since a certain group of UEs or all UEs must receive the PDCCH, it may be defined as a set of pre-arranged CCEs. UE-specific scheduling allocation information for the PDSCH or PUSCH may be received by searching the UE-specific search space of the PDCCH. The UE-specific search space may be defined UE-specifically as a function of the UE's identity and various system parameters.

[0285] According to one embodiment, in 5G, parameters for a search space for a PDCCH can be set from a base station to a terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can set to the terminal the number of PDCCH candidates at each aggregation level L, a monitoring period for the search space, a monitoring occasion per symbol within a slot for the search space, a search space type (common search space or terminal-specific search space), a combination of a DCI format and an RNTI to be monitored in the search space, and / or a control region index to be monitored in the search space. For example, the information set to the terminal may include at least some of the information in [Table 22].

[0286]

[0287]

[0288] According to one embodiment, based on the configuration information, the base station can configure one or more search space sets for the terminal. According to one embodiment, the base station can configure search space set 1 and search space set 2 for the terminal, and can configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and can configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0289] In one embodiment, according to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be set as a common search space, and search space set #3 and search space set #4 may be set as terminal-specific search spaces.

[0290] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these.

[0291] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0292] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0293] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0294] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0295] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0296] According to one embodiment, the following combination of DCI format and RNTI can be monitored in a terminal-specific search space, although the present invention is not limited to the following examples.

[0297] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0298] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0299] The RNTIs specified may follow the definitions and uses below.

[0300] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0301] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0302] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0303] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

[0304] P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.

[0305] SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.

[0306] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

[0307] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0308] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0309] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

[0310] The aforementioned specified DCI formats may follow the definitions in [Table 23] below.

[0311]

[0312] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in [Mathematical Formula 1] below.

[0313]

[0314] - L: Integration level

[0315] - n CI : Carrier Index

[0316] - N CCE,p : Total number of CCEs existing within the control region p

[0317] - : slot index

[0318] - : Number of PDCCH candidates for aggregation level L

[0319] - : PDCCH candidate index of aggregation level L

[0320] - i = 0, … , L -1

[0321] - , Y p,-1 =n RNTI ≠0, A p=39827 for pmod3=0, A p =39829 for pmod3=1, A p =39839 for pmod3=2, D=65537

[0322] - n RNTI : Terminal identifier

[0323] The value can be 0 for a common search space.

[0324] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set to the terminal by the base station) and the time index.

[0325] According to one embodiment, in 5G, since multiple search space sets can be set with different parameters (e.g., parameters in [Table 22]), the set of search space sets monitored by the terminal at each point in time can be different. For example, if search space set #1 is set with an X-slot period and search space set #2 is set with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, and the terminal can monitor either search space set #1 or search space set #2 in a specific slot.

[0326] [Regarding terminal capability reporting]

[0327] In LTE and NR, a terminal, while connected to a serving base station, can perform a procedure to report its supported capabilities to the base station. In the description below, this may be referred to as a UE capability report.

[0328] According to one embodiment, a base station may transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message may include a UE capability request for each radio access technology (RAT) type of the base station. The RAT type-specific request may include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types may be requested through a single RRC message container transmitted by the base station, or the base station may include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. In other words, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct a UE capability information message corresponding to the inquiry and report it multiple times.

[0329] According to one embodiment, a next-generation mobile communication system may request terminal capabilities for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Furthermore, while terminal capability inquiry messages are typically transmitted initially after a terminal connects to a base station, they may be requested under any conditions when a base station is needed.

[0330] In one embodiment, a terminal receiving a UE capability report request from a base station can configure terminal capability based on the RAT type and band information requested from the base station. Below is a summary of how a terminal configures UE capability in an NR system.

[0331] 1. When a UE receives a list of LTE and / or NR bands through a UE capability request from a base station, the UE can configure a band combination (BC) for EN-DC and NR stand-alone (SA). That is, a candidate list of BCs for EN-DC and NR SA can be configured based on the bands requested to the base station via FreqBandList. In addition, the band priorities can be prioritized in the order listed in FreqBandList.

[0332] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the UE may completely remove NR SA BCs from the candidate list of configured BCs. This action can only occur when the LTE base station (eNB) requests the "eutra" capability.

[0333] 3. Afterwards, the terminal can remove fallback BCs from the BC candidate list constructed in the above step. Here, a fallback BC can be referred to as a BC obtained by removing at least one band corresponding to an SCell from an arbitrary BC. Since the BC before removing the band corresponding to at least one SCell can already cover the fallback BC, this step can be omitted. This step also applies to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list."

[0334] 4. The terminal can select BCs to report by selecting BCs that match the requested RAT type from the final "candidate BC list" above. In this step, the terminal can construct the supportedBandCombinationList in a set order. That is, the terminal constructs BCs and UE capabilities to report according to the preset rat-Type order (nr -> eutra-nr -> eutra). In addition, the terminal can construct a featureSetCombination for the constructed supportedBandCombinationList, and construct a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0335] 5. Also, if the requested rat Type is eutra-nr and has influence, featureSetCombinations can be included in both containers, UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of NR can only be included in UE-NR-Capabilities.

[0336] In one embodiment, after terminal capabilities are configured, the terminal can transmit a terminal capability information message containing the terminal capabilities to the base station. Based on the terminal capabilities received from the terminal, the base station can then perform appropriate scheduling and transmission / reception management for the terminal.

[0337] [NC-JT related]

[0338] In one embodiment, Non-Coherent Joint Transmission (NC-JT) may be used for a terminal to receive PDSCH from multiple TRPs.

[0339] According to one embodiment, a 5G wireless communication system can support not only services requiring high transmission speeds, but also services with very short transmission delays and services requiring high connection density, unlike existing services. In a wireless communication network including multiple cells, transmission and reception points (TRPs), or beams, coordinated transmission between each cell, TRP, and / or beam can increase the strength of a signal received by a terminal or efficiently perform interference control between each cell, TRP, and / or beam, thereby satisfying various service requirements.

[0340] According to one embodiment, Joint Transmission (JT) is a representative transmission technology for the above-described cooperative communication, which increases the strength or processing rate of a signal received by a terminal by transmitting a signal to a single terminal through a plurality of different cells, TRPs, and / or beams. At this time, the channel between each cell, TRP, and / or beam and the terminal may have significantly different characteristics, and in particular, in the case of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP, and / or beam, individual precoding, MCS, resource allocation, TCI indication, etc. may be required depending on the channel characteristics of each link between each cell, TRP, or / and beam and the terminal.

[0341] The above-described NC-JT transmission can be applied to at least one channel among the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). When transmitting PDSCH, transmission information such as precoding, MCS, resource allocation, and / or TCI can be indicated as DL DCI. For NC-JT transmission, the transmission information must be independently indicated for each cell, TRP, and / or beam. This is a major factor that increases the payload required for DL ​​DCI transmission, which may adversely affect the reception performance of the PDCCH transmitting the DCI. Therefore, in order to support JT of PDSCH, it is necessary to carefully design a tradeoff between the amount of DCI information and the reception performance of control information.

[0342] FIG. 8 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting a PDSCH using cooperative communication in a wireless communication system according to one embodiment.

[0343] Referring to FIG. 8, examples for PDSCH transmission are explained for each technique of joint transmission (JT), and examples for allocating radio resources for each TRP are shown.

[0344] Referring to FIG. 8, an example (800) for coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP or / and beam is illustrated.

[0345] According to one embodiment, in the case of C-JT, TRP A (805) and TRP B (810) transmit a single data (PDSCH) to the terminal (815), and joint precoding can be performed on multiple TRPs. This may mean that TRP A (805) and TRP B (810) transmit the DMRS through the same DMRS (demodulation reference signal) ports in order to transmit the same PDSCH. For example, TRP A (805) and TRP B (810) may each transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal may receive one DCI information for receiving one PDSCH demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0346] FIG. 8 illustrates an example (820) of Non-Coherent Joint Transmission (NC-JT) supporting non-coherent precoding between each cell, TRP, or / and beam for PDSCH transmission according to one embodiment.

[0347] According to one embodiment, in the case of NC-JT, a PDSCH is transmitted to a terminal (835) for each cell, TRP, or / and beam, and individual precoding may be applied to each PDSCH. Each cell, TRP, and / or beam may transmit a different PDSCH or a different PDSCH layer to the terminal, thereby improving throughput compared to single cell, TRP, or / and beam transmission. In addition, each cell, TRP, and / or beam may repeatedly transmit the same PDSCH to the terminal, thereby improving reliability compared to single cell, TRP, and / or beam transmission. For convenience of explanation, a cell, TRP, and / or beam are collectively referred to as TRP hereinafter.

[0348] At this time, various wireless resource allocations can be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (840), when the frequency and time resources used by multiple TRPs do not overlap at all (845), and when some of the frequency and time resources used by multiple TRPs overlap (850).

[0349] To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal.

[0350] FIG. 9 is a diagram illustrating an example of a configuration of downlink control information (DCI) for NC-JT in which each TRP transmits a different PDSCH or a different PDSCH layer to a terminal in a wireless communication system according to one embodiment.

[0351] Referring to FIG. 9, case #1 (900) according to an embodiment is an example in which, in addition to a serving TRP (TRP#0) used for single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), control information for PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently from the control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). Formats between independent DCIs may be the same or different, and payloads between DCIs may also be the same or different. In the aforementioned case #1, each PDSCH control or allocation freedom can be fully guaranteed, but if each DCI is transmitted in different TRPs, coverage differences may occur for each DCI, which may deteriorate reception performance.

[0352] According to one embodiment, case #2 (905) shows an example in which, in addition to a serving TRP (TRP#0) used for single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), control information (DCI) for PDSCHs of the (N-1) additional TRPs is transmitted respectively, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0353] For example, in the case of DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but in the case of shortened DCI (hereinafter, sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it may include only some of the information elements of DCI format 1_0, DCI format 1_1, or DCI format 1_2. Therefore, SDCI, which transmits control information for PDSCHs transmitted from cooperative TRPs, may include reserved bits compared to nDCI because its payload is smaller than that of normal DCI (nDCI), which transmits PDSCH-related control information transmitted from a serving TRP.

[0354] According to one embodiment, case #2 may limit the degree of freedom of each PDSCH control or allocation depending on the content of the information elements included in sDCI, but since the reception performance of sDCI is superior to that of nDCI, the probability of a difference in coverage by DCI may be reduced.

[0355] According to one embodiment, case #3 (910) shows an example in which, in a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than a serving TRP (TRP#0) used for single PDSCH transmission, one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0356] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), may include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. In the case of control information for PDSCHs transmitted from cooperating TRPs (TRP#1 to TRP#(N-1)), only some of the information elements of DCI format 1_0, DCI format 1_1, D or CI format 1_2 may be gathered and transmitted in one 'secondary' DCI (sDCI). For example, sDCI may include at least one of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperating TRPs. In addition, information not included in sDCI, such as BWP (bandwidth part) indicator or carrier indicator, can be determined based on DCI (DCI#0, normal DCI, nDCI) of serving TRP.

[0357] According to one embodiment, case #3 (910) may limit the degree of freedom of each PDSCH control or allocation depending on the content of the information element included in sDCI, but may allow for control of the reception performance of sDCI and may reduce the complexity of DCI blind decoding of the terminal compared to case #1 (900) or case #2 (905).

[0358] According to one embodiment, case #4 (915) is an example in which, in a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for single PDSCH transmission, control information for PDSCHs transmitted from (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as the control information for PDSCHs transmitted from the serving TRP. That is, the terminal can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4 (915), the complexity of DCI blind decoding of the terminal may not increase, but the degree of freedom in PDSCH control or allocation may be low, such as because the number of cooperative TRPs is limited due to the long DCI payload limitation.

[0359] In the following description and examples, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI format 1_0 to 1_1 described above) containing PDSCH control information transmitted in a cooperative TRP, and unless a special limitation is specified, the description is similarly applicable to the various auxiliary DCIs described above.

[0360] In the following description and examples, the aforementioned cases #1 (900), #2 (905), and #3 (910), in which more than one DCI (PDCCH) is used to support NC-JT, can be distinguished as multiple PDCCH-based NC-JT. The aforementioned case #4 (915), in which a single DCI (PDCCH) is used to support NC-JT, can be distinguished as single PDCCH-based NC-JT. In PDSCH transmission based on multiple PDCCH, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCI of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled can be distinguished. As a method for distinguishing the CORESETs, there may be a method for distinguishing through an upper layer indicator for each CORESET, a method for distinguishing through beam setting for each CORESET, etc. Additionally, in single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH with multiple layers is scheduled, and the multiple layers described above can be transmitted from multiple Transmission Relays (TRPs). In this case, the connection relationship between a layer and the TRP transmitting the layer can be indicated through a Transmission Configuration Indicator (TCI) indication for the layer.

[0361] In the embodiments of the present disclosure, “cooperative TRP” may be replaced with various terms such as “cooperative panel” or “cooperative beam” in actual application.

[0362] In the embodiments of the present disclosure, “when NC-JT is applied” can be interpreted in various ways depending on the situation, such as “when a terminal simultaneously receives one or more PDSCHs in one BWP,” “when a terminal simultaneously receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications in one BWP,” or “when a PDSCH received by a terminal is associated with one or more DMRS port groups,” but is used as a single expression for convenience of explanation.

[0363] In the present invention, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) similar to S10 of FIG. 4 is possible. On the other hand, when the backhaul delay between cooperative TRPs is so large that it cannot be ignored (for example, when more than 2 ms is required for information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method (DC-like method) is possible to secure delay-robust characteristics by using an independent structure for each TRP starting from the RLC layer, similar to S20 of FIG. 4.

[0364] According to one embodiment, a terminal supporting C-JT and / or NC-JT may receive C-JT or / and NC-JT related parameters or setting values ​​from a higher layer configuration, and may set RRC parameters of the terminal based on the C-JT or / and NC-JT related parameters or setting values. For the higher layer configuration, the terminal may utilize a UE capability parameter, for example, tci-StatePDSCH. For example, the UE capability parameter (e.g., tci-StatePDSCH) may define TCI states for the purpose of PDSCH transmission. The number of TCI states may be set to 4, 8, 16, 32, 64, 128 in FR1, and to 64, 128 in FR2. Among the set number, up to 8 states may be set, which may be indicated by 3 bits of the TCI field of the DCI via a MAC CE message. The maximum value of 128 can be referenced as the value indicated by the maxNumberConfiguredTCIstatesPerCC parameter in the tci-StatePDSCH parameter included in the capability signaling of the terminal. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to a beamforming instruction or beamforming change command for at least one PDSCH in one TRP.

[0365] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD (frequency division duplex) and TDD (time division duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0366] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, a case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to the above is referred to as an NC-JT case.

[0367] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0368] In the following disclosure, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination.

[0369] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions, which can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be uniformly described as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state may be appropriately replaced with one of the above terms.

[0370] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, a case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to the above is referred to as an NC-JT case.

[0371] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure are applicable to FDD and TDD systems.

[0372] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

[0373] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0374] - MIB (Master Information Block)

[0375] - SIB (System Information Block) or SIB

[0376] - RRC (Radio Resource Control)

[0377] - MAC (Medium Access Control) CE (Control Element)

[0378] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the following physical layer channels or signaling.

[0379] - PDCCH (Physical Downlink Control Channel)

[0380] - DCI (Downlink Control Information)

[0381] - UE-specific DCI

[0382] - Group common DCI

[0383] - Common DCI

[0384] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

[0385] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)

[0386] - PUCCH (Physical Uplink Control Channel)

[0387] - UCI (Uplink Control Information)

[0388] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0389] The term “slot” used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a TTI (Transmit Time Interval), and may specifically mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0390] In the present disclosure, reception of a CSI-RS resource may be understood as reception of a CSI-RS corresponding to the CSI-RS resource. In addition, channel estimation or CSI calculation for a CSI-RS port may be understood as channel estimation and CSI calculation performed by measuring a CSI-RS corresponding to a CSI-RS antenna port.

[0391] In the following disclosure, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination.

[0392] According to one embodiment, a method for setting CSI reports and CSI resources for network energy saving is described.

[0393] As one embodiment of the present disclosure, a method for configuring CSI reports and CSI resources for network energy saving at a terminal and a base station is described. This embodiment can be operated in combination with other embodiments within the present disclosure.

[0394] FIG. 10 is a diagram illustrating an example of an aperiodic CSI report signaling structure that a terminal can set up with upper layer signaling according to one embodiment.

[0395] Referring to Figure 10, a terminal can receive up to 128 CSI-AperiodicTriggerStates (10-00), which are upper layer signalings, from a base station. One CSI-AperiodicTriggerState can be mapped to one code point of the CSI request field within DCI.

[0396] According to one embodiment, the terminal may receive from the base station the reportTriggerSize, which is an upper layer signaling related to the number of code points of the CSI request. The reportTriggerSize may be an integer from 0 to 6, and when this value is set to NTs, the terminal may set 2 for the CSI request field. NTs We can expect that there are code points for the dog.

[0397] - If all bits of the CSI request field in the DCI received by the terminal are 0, the terminal may consider or identify that there is no information to trigger aperiodic CSI report transmission (which may also indicate aperiodic CSI-RS reception).

[0398] - The number of CSI-AperiodicTriggerStates set by the terminal through upper layer signaling is 2. NTs If it is greater than -1, the terminal receives a MAC-CE from the base station, and the MAC CE is 2 of the multiple CSI-AperiodicTriggerStates set by upper layer signaling. NTs You can choose as much as -1.

[0399] - The number of CSI-AperiodicTriggerStates set by the terminal through upper layer signaling is 2.NTs If it is less than or equal to -1, multiple CSI-AperiodicTriggerStates set by upper layer signaling can be sequentially linked to the code points of each CSI request field. For example, if the terminal receives 32 CSI-AperiodicTriggerStates set by upper layer signaling and reportTriggerSize, which is an upper layer signaling, is set to 6, that is, the number of code points of the CSI request field is 2. 6 -1=If 63 can be used for aperiodic CSI report, the terminal can understand or identify that the number of CSI-AperiodicTriggerStates set is less than the number of code points in the CSI request field, and thus the code points of the CSI request are mapped in ascending order in the order of CSI-AperiodicTriggerStates.

[0400] According to one embodiment, the terminal may receive one or more, but up to 16 CSI-AssociatedReportConfigInfos configured within the upper layer signaling CSI-AperiodicTriggerState (10-00) (10-05). One CSI-AssociatedReportConfigInfo configuration information may include one CSI-ReportConfig (10-10), and the CSI-ReportConfig may include CSI-ResourceConfig (10-25), and in the case of an aperiodic CSI report, one or more, but up to 16 NZP-CSI-RS-ResourceSets (10-30) may be included within the CSI-ResourceConfig.

[0401] In one embodiment, the CSI-AssociatedReportConfigInfo configuration information may include resourceForChannel (10-15). In the case of an aperiodic CSI report, one of multiple NZP-CSI-RS-ResourceSets that may be included in the CSI-ResourceConfig may be selected through a parameter called nzp-CSI-RS (10-20), which may be set via a parameter (e.g., resourceForChannel) (10-35). That is, in the case of an aperiodic CSI report, even if it is connected (or mapped, corresponded) to multiple NZP-CSI-RS-ResourceSets, one aperiodic CSI-RS resource set connected to one aperiodic CSI report configuration may be considered for one CSI-AssociatedReportConfigInfo.

[0402] Below, the connection relationship (or mapping relationship) between a CSI report and a CSI-RS resource set is described according to the time domain behavior of the CSI report and the CSI-RS resource.

[0403] - When considering periodic CSI reports, the terminal can expect that there will be only one periodic CSI-RS resource set that can be connected and used.

[0404] - When considering a semi-persistent CSI report, the terminal can expect that there will be only one periodic or semi-persistent CSI-RS resource set that can be used by being connected (or mapped, corresponding) to the semi-persistent CSI report.

[0405] - When a terminal considers an aperiodic CSI report, if the aperiodic CSI report is associated with (or mapped to, corresponds to) a periodic and semi-persistent CSI-RS resource set, the number of NZP-CSI-RS-ResourceSets that can be included in the upper layer signaling CSI-ResourceConfig may be limited to 1. If the aperiodic CSI report is associated with (or mapped to, corresponds to) an aperiodic CSI-RS resource set, even if the number of NZP-CSI-RS-ResourceSets that can be included in the upper layer signaling CSI-ResourceConfig is multiple, up to a maximum of 16, the terminal may select and consider one aperiodic CSI-RS resource set associated with one aperiodic CSI report configuration through the upper layer signaling resourceForChannel for one CSI-AssociatedReportConfigInfo.

[0406] Below, a method for triggering and activating a base station for a terminal's semi-persistent CSI report is described.

[0407] According to one embodiment, for a semi-persistent CSI report transmitted via PUSCH, a terminal may be configured with a set of multiple trigger states from a base station via a higher layer signaling, CSI-SemiPersistentOnPUSCH-TriggerStateList. The terminal may be configured by the base station to include a setting for up to 64 (= maxNrOfSemiPersistentPUSCH-Triggers) semi-persistent CSI report trigger states in the CSI-SemiPersistentOnPUSCH-TriggerStateList. The terminal may be activated via a CSI request field in a DCI received from the base station for one of the multiple trigger states configured via CSI-SemiPersistentOnPUSCH-TriggerStateList, and at this time, the CRC of the DCI may be scrambled with SP-CSI-RNTI.

[0408] In one embodiment, the terminal may not expect to receive a DCI (the CRC of the DCI may be scrambled with SP-CSI-RNTI) that additionally activates a semi-persistent CSI report having the same ID (e.g., CSI-ReportConfigId) as an already activated semi-persistent CSI report via DCI received from the base station (the CRC of the DCI may be scrambled with SP-CSI-RNTI).

[0409] According to one embodiment, for a semi-persistent CSI report transmitted via PUCCH, the terminal can be configured with PUCCH resources to be used for reporting the semi-persistent CSI report via pucch-CSI-ResourceList in reportConfigType, which is a higher layer signaling. The maximum number of PUCCH resources can be 4, which is the maximum number of bandwidth portions that the terminal can be configured with via higher layer signaling from the base station.

[0410] According to one embodiment, a terminal may receive a MAC-CE including an activation command for a semi-persistent CSI report from a base station, and the received MAC-CE may notify or transfer one of a plurality of semi-persistent CSI report configurations to the terminal, and a semi-persistent CSI report corresponding to the notified semi-persistent CSI report configuration may be transmitted through the configured PUCCH resource. When the terminal receives a PDSCH including a MAC-CE including an activation command for a semi-persistent CSI report, the terminal may apply the semi-persistent CSI report configuration activated through the MAC-CE from the first slot appearing 3 ms after a slot in which a PUCCH including HARQ-ACK information for the PDSCH is transmitted.

[0411] According to one embodiment, each code point of a CSI request field in a DCI including a CRC scrambled with SP-CSI-RNTI may be associated with a trigger state of one semi-persistent CSI report. In this case, the association between the code point of the CSI request field and the trigger state of the semi-persistent CSI report may be associated in the order of a plurality of trigger states in the upper layer signaling CSI-SemiPersistentOnPUSCH-TriggerStateList. For example, the first code point of the CSI request field may be associated with the first trigger state among the plurality of trigger states in the upper layer signaling CSI-SemiPersistentOnPUSCH-TriggerStateList. When verifying the validity of activation or deactivation for a semi-persistent CSI report, the terminal may confirm or identify whether the following conditions for the DCI are satisfied.

[0412] - When the terminal verifies the validity of activation or deactivation of the semi-persistent CSI report, the terminal can check whether the CRC of the DCI is scrambled with SP-CSI-RNTI, which can be set as SP-CSI-RNTI, which is an upper layer signaling from the base station.

[0413] - When the terminal verifies the validity of activation of the semi-persistent CSI report, the terminal can check or identify whether all bits in the HARQ process number field (if present) in DCI format 0_1 ​​or 0_2 are indicated as 0, and / or whether all bits in the RV field (if present) in DCI format 0_1 ​​or 0_2 are indicated as 0.

[0414] - When the terminal verifies the validity of the deactivation of the semi-persistent CSI report, the terminal can check whether all bits in the HARQ process number field (if present) in DCI format 0_1 ​​or 0_2 are indicated as 0, whether all bits in the MCS field in DCI format 0_1 ​​or 0_2 are indicated as 1, whether all bits in the RV field (if present) in DCI format 0_1 ​​or 0_2 are indicated as 0, and / or whether the FDRA (Frequency Domain Resource Assignment field) field in DCI format 0_1 ​​or 0_2 satisfies the following:

[0415] ■ When the terminal receives FDRA type 0 from the base station through upper layer signaling, the terminal can check whether all bits in the FDRA field are set to 0.

[0416] ■ When the terminal receives FDRA type 1 from the base station through upper layer signaling, the terminal can check whether all bits in the FDRA field are set to 1.

[0417] ■ If the terminal is set to enable dynamic switching between FDRA types 0 and 1 through upper layer signaling from the base station and the MSB (Most Significant Bit) of the FDRA field is 0, the terminal can check whether all bits in the FDRA field are indicated as 0; otherwise (if the MSB of the FDRA field is 1), the terminal can check whether all bits in the FDRA field are indicated as 1.

[0418] ■ For DCI format 0_1, if the terminal receives FDRA type 2 from the base station through upper layer signaling and the subcarrier spacing is 15 kHz, the terminal can check or identify whether all bits in the FDRA field are indicated as 1, and if the subcarrier spacing is 30 kHz, the terminal can check or identify whether all bits in the FDRA field are indicated as 0.

[0419] FIG. 11 is a diagram illustrating an example of an aperiodic CSI report and an aperiodic CSI-RS triggering situation and constraints according to one embodiment.

[0420] Referring to FIG. 11, a terminal according to one embodiment may not expect to receive multiple DCIs having a CSI request field that includes information triggering aperiodic CSI report transmission within a slot within a cell. The information triggering aperiodic CSI report transmission may also indicate aperiodic CSI-RS reception.

[0421] Therefore, if both PDCCH 1 (1100) and PDCCH 2 (1101) have CSI request fields including information that triggers aperiodic CSI report transmission (which may additionally indicate aperiodic CSI-RS reception), the UE may not expect to receive both PDCCHs within one slot. Therefore, if the base station wants to transmit multiple PDCCHs to the UE, each having a CSI request field including information that triggers aperiodic CSI report transmission (which may additionally indicate aperiodic CSI-RS reception), the UE may receive each of the PDCCHs (1105, 1106) in two different slots.

[0422] In one embodiment, when a terminal receives a DCI having a CSI request field including information triggering aperiodic CSI report transmission (which may additionally also indicate aperiodic CSI-RS reception) in a particular slot within the same cell group, the terminal may not expect to receive another DCI having a CSI request field including information triggering aperiodic CSI report transmission (which may additionally also indicate aperiodic CSI-RS reception) in any other slot overlapping with the slot within the cell group.

[0423] According to one embodiment, the terminal may transmit to the base station, through the terminal capability report, constraints on the number of CSI-RS resources that can be activated simultaneously per cell and constraints on the number of CSI-RS ports that can be activated simultaneously per cell. The terminal may report to the base station a natural number from 1 to 32 as the number of CSI-RS resources that can be activated simultaneously per cell. The terminal may report to the base station a multiple of 8 from 8 to 128 as the number of CSI-RS ports that can be activated simultaneously per cell. Whether the terminal receives multiple aperiodic CSI-RS resources in one slot or one aperiodic CSI-RS resource per slot, the terminal may receive aperiodic CSI-RS resources (1110, 1115, 1120) triggered via the PDCCH from the base station under the constraints on the number of CSI-RS resources and the number of CSI-RS ports.

[0424] According to one embodiment, a terminal may transmit a PUSCH including all aperiodic CSI reports triggered through a single PDCCH within a cell, based on a slot offset corresponding to a largest value among the same or different slot offsets set by upper layer signaling for each of the plurality of aperiodic CSI reports. In this case, some or all of the aperiodic CSI reports triggered through the DCI may be included in the PUSCH, and whether or not each aperiodic CSI report is included may be determined based on the priority of each aperiodic CSI report and the resource capacity of the PUSCH. If aperiodic CSI report 1 (1135), aperiodic CSI report 2 (1135), aperiodic CSI report 3 (1145), and aperiodic CSI report 4 (1140) are triggered by a single PDCCH (1130), and the slot offset (1134) for aperiodic CSI reports 1 (1135) and 2 (1135) is 2 slots, the slot offset (1139) of aperiodic CSI report 4 (1140) is 4 slots, and the slot offset (1144) of aperiodic CSI report 3 (1145) is 5 slots, the terminal may transmit aperiodic CSI reports 1 to 4 in a PUSCH 5 slots after the PDCCH based on the 5 slots having the longest slot offset.

[0425] In one embodiment, the terminal may not expect that aperiodic CSI reports triggered from different PDCCHs exist within the same slot. For example, the terminal may not expect that aperiodic CSI report 1 (1170) triggered from PDCCH 1 (1160) and aperiodic CSI report 2 (1175) triggered from PDCCH 2 (1165) exist within the same slot.

[0426] In one embodiment, the terminal may expect that aperiodic CSI reports, each triggered by a different PDCCH, may be transmitted in different slots. For example, it may be acceptable for each CSI report to be transmitted only once in each slot, such as aperiodic CSI report 3 (1180) triggered by PDCCH 1 (1160) and aperiodic CSI report 4 (1185) triggered by PDCCH 2 (1165).

[0427] FIG. 12 is a diagram illustrating a MAC-CE structure that indicates activation or deactivation of a semi-persistent CSI report transmitted on a PUCCH according to one embodiment.

[0428] Referring to FIG. 12, a MAC-CE indicating activation or deactivation of a semi-persistent CSI report transmitted on a PUCCH according to an embodiment may be identified through a MAC subheader including an LCID (Logical Channel ID) and may have a fixed length of 16 bits. A description of each field of the MAC-CE may be as follows.

[0429] - Serving Cell ID (1200): This field can indicate the ID of the serving cell to which the MAC-CE is applied, and can be 5 bits long.

[0430] - BWP ID (1205): This field may indicate the uplink bandwidth portion to which the MAC-CE is to be applied, may mean a code point within the bandwidth portion indicator field within the DCI, and may be 2 bits long.

[0431] - S i(1210): This field may indicate the enable or disable status of the semi-persistent CSI report configuration within the upper layer signaling csi-ReportConfigToAddModList.

[0432] ■ The S0 field may mean a CSI report configuration having a type set to semiPersistentOnPUCCH and having the lowest ID (e.g., CSI-ReportConfigId) among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList, which includes a PUCCH resource connected to or included in the bandwidth portion indicated through the BWP ID field.

[0433] ■ The S1 field may mean a CSI report configuration having a PUCCH resource included in or connected to the bandwidth portion indicated by the BWP ID field, and having a type set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList and having the second lowest ID (e.g., CSI-ReportConfigId).

[0434] ■ The S2 and S3 fields can also be considered in this way.

[0435] ■ PUCCH resources connected to or included within a specific bandwidth portion may be PUCCH format 2, 3, or 4, and can be identified using the PUCCH resource ID set in PUCCH-Config, which is an upper layer signaling.

[0436] ■ If the type is set to semiPersistentOnPUCCH among the CSI-ReportConfig in the upper layer signaling csi-ReportConfigToAddModList and the number of semi-persistent CSI report configurations that are connected to the bandwidth part indicated by the BWP ID field or include PUCCH resources included in the bandwidth part is less than i+1, the UE may ignore the Si field. For example, if the number of semi-persistent CSI report configurations as described above is 2, the UE may interpret the S0 field and the S1 field, but may ignore the S2 field and the S3 field.

[0437] ■ If the Si field is set to 1, the terminal can understand that the corresponding semi-persistent CSI report setting should be activated.

[0438] ■ If the Si field is set to 0, the terminal can understand that the corresponding semi-persistent CSI report setting should be disabled.

[0439] - R: Indicates reserved bit and can be set to 0.

[0440] Through MAC-CE in Figure 12, a terminal can activate up to four semi-persistent CSI reports within a specific bandwidth segment.

[0441] In one embodiment, a base station may activate or deactivate some or all of the power amplifiers used for downlink transmission to save network energy. If the base station activates or deactivates some or all of the power amplifiers, this may impact the downlink performance of all terminals supported by the base station. Therefore, when adjusting the activation or deactivation of power amplifiers, the base station may consider the performance impact on the terminals.

[0442] To this end, the base station can transmit CSI-RSs with different numbers of ports to the terminal to check the performance difference in each case of activating or deactivating a specific number or area of ​​power amplifiers, and can expect the terminal to calculate and report a CSI report for each CSI-RS with different numbers of ports to the base station. The base station that receives the CSI report can determine the performance of the terminal for each CSI-RS with different numbers of ports, and the base station can collect and refer to reports from multiple terminals that can report CSI reports to ultimately determine which power amplifier to deactivate or activate.

[0443] According to one embodiment, a terminal may include multiple detailed CSI report configurations in a CSI-ReportConfig, which is an upper layer signaling configured by a base station, for the purpose of network energy saving. The terminal may report the CSI calculated by the terminal through a CSI report corresponding to each detailed CSI report configuration when the base station operates some or all antenna ports. In this case, when the terminal receives a CSI-ReportConfig including multiple detailed CSI report configurations from the base station, at least one combination of the following configuration methods may be possible.

[0444] - The terminal may include a configuration for PUCCH-based periodic CSI report in the CSI-ReportConfig containing multiple detailed CSI report configurations from the base station for network energy saving purposes.

[0445] - The terminal may include a configuration for PUCCH-based semi-persistent CSI report in CSI-ReportConfig, which includes multiple detailed CSI report configurations from the base station for network energy saving purposes.

[0446] - The terminal may include a configuration for PUSCH-based semi-persistent CSI reporting in the CSI-ReportConfig containing multiple detailed CSI report configurations from the base station for network energy saving purposes.

[0447] - The terminal may include a configuration for PUSCH-based aperiodic CSI report in CSI-ReportConfig, which includes multiple detailed CSI report configurations from the base station for network energy saving purposes.

[0448] For example, the terminal may combine all of the above items to include configuration or configuration information for at least one of a PUCCH-based periodic CSI report, a PUCCH-based semi-persistent CSI report, a PUSCH-based semi-persistent CSI report, or a PUSCH-based aperiodic CSI report in the CSI-ReportConfig, which includes multiple detailed CSI report configurations from the base station for the purpose of saving network energy. That is, the terminal may receive a CSI report configuration for saving network energy from the base station through the PUCCH-based periodic CSI report, the PUCCH-based semi-persistent CSI report, the PUSCH-based semi-persistent CSI report, or the PUSCH-based aperiodic CSI report, and the terminal may transmit the CSI report based on the received configuration. The possibility of all types of CSI reports may be to provide more flexible signaling for saving network energy between the terminal and the base station.

[0449] For example, among the above items, the terminal may include only the configuration for the PUSCH-based aperiodic CSI report in the CSI-ReportConfig, which includes multiple detailed CSI report configurations from the base station, for the purpose of network energy saving. That is, the terminal may not receive the PUCCH-based periodic CSI report, the PUCCH-based semi-persistent CSI report, and the PUSCH-based semi-persistent CSI report as the CSI report configuration for the purpose of network energy saving, and may only receive the configuration (or configuration information) for the PUSCH-based aperiodic CSI report. The reason why only the configuration for the PUSCH-based aperiodic CSI report is possible in this way is because the size of the CSI that the terminal must include in the CSI report according to the multiple detailed CSI report configurations for network energy saving may be large, and the amount of computation required for this may be burdensome, and therefore, it may be inefficient to periodically perform such CSI reports.

[0450] The above is only an example, and other combinations may be possible as described above.

[0451] FIG. 13 is a diagram illustrating an example of a situation in which multiple overlapping CSI-RS resources are transmitted according to an embodiment of the present disclosure.

[0452] Referring to FIG. 13, the terminal can be configured to have RE (resource element) mappings of two ports of CSI-RS resources (10-10), four ports of CSI-RS resources (10-11), and / or eight ports of CSI-RS resources (10-12) overlap with each other through upper layer signaling from the base station as shown in FIG. 13.

[0453] According to one embodiment, the CSI-RS resources of two ports can be defined based on Row 3 in [Table 7], and the terminal can receive l0=3 (10-00) and k0=0 (10-01) from the base station through upper layer signaling. Through this, the terminal can determine that the CSI-RS resources of two ports are mapped to the 3rd symbol among the symbol indices starting from 0 in the RB within a specific slot, the 0th RE and the 1st RE among the RE indices starting from 0 (10-10).

[0454] In addition, the CSI-RS resources of the four ports can be defined based on Row 4 in the above [Table 7], and the terminal can receive l0=3 (10-00) and k0=0 (10-01) from the base station through upper layer signaling. Through this, the terminal can determine that the CSI-RS resources of the four ports are mapped to the 3rd symbol among the symbol indices starting from 0 in the RB within a specific slot, and the 0th RE, 1st RE, 3rd RE, and 4th RE among the RE indices starting from 0 (10-11).

[0455] In addition, the CSI-RS resources of the 8 ports can be defined based on Row 6 in the above [Table 7], and the terminal can be set to l0=3 (10-00), k0=0 (10-01), k1=3 (10-02), k2=6 (10-03), and k3=9 (10-04) through upper layer signaling from the base station. Through this, the terminal can determine that the CSI-RS resources of the 4 ports are mapped to the 3rd symbol among the symbol indices starting from 0 in the RB within a specific slot, and the 0th RE, 1st RE, 3rd RE, 4th RE, 6th RE, 7th RE, 9th RE, and 10th RE among the RE indices starting from 0 (10-12).

[0456] Therefore, the terminal can expect that the three CSI-RS resources of the 2, 4, and 8 ports overlap in the 0th RE and the 1st RE of the 3rd symbol, and the terminal can expect that the two CSI-RS resources of the 4 and 8 ports overlap in the 3rd RE and the 4th RE of the 3rd symbol. In this way, when the base station transmits multiple different CSI-RS resources with different numbers of ports to the terminal in the same symbol, the base station can reduce energy consumption by avoiding CSI-RS resource transmission in different time resources.

[0457] However, in order for a terminal to report a CSI report for multiple CSI-RS resources having different numbers of CSI-RS ports to a base station in the form of an aperiodic CSI report, the terminal may need to set multiple CSI-AssociatedReportConfigInfos in CSI-AperiodicTriggerState, which is an upper layer signaling linked to one code point of a CSI request field in DCI receivable from the base station, and may need to set a CSI-ReportConfig and a CSI-RS resource set in each CSI-AssociatedReportConfigInfo, and each CSI-RS resource set linked to each CSI-ReportConfig may need to have a different number of CSI-RS ports.

[0458] For example, a terminal may receive three CSI-AssociatedReportConfigInfos set within a specific CSI-AperiodicTriggerState, and a CSI-RS resource set connected to a CSI-ReportConfig included within a first CSI-AssociatedReportConfigInfo may include CSI-RS resources of one or more two ports. A CSI-RS resource set connected to a CSI-ReportConfig included within a second CSI-AssociatedReportConfigInfo may include CSI-RS resources of one or more four ports. A CSI-RS resource set connected to a CSI-ReportConfig included within a third CSI-AssociatedReportConfigInfo may include CSI-RS resources of one or more eight ports.

[0459] In one example, under the above-described settings, if the terminal receives a CSI request field having a value of the corresponding code point through one DCI, the terminal cannot transmit more than two aperiodic CSI reports corresponding to the first, second, and third CSI-AssociatedReportConfigInfo in the same slot, and can report only a single CSI report in each slot.

[0460] In this way, even if the terminal receives multiple CSI-RS resources with some REs overlapping at the same symbol position as shown in FIG. 13, this operation may be inefficient in terms of time resource utilization because the CSI reports must be reported in different slots.

[0461] If these multiple CSI reports are to be reported as a single CSI report within the same slot, the terminal may need to receive two or more DCIs containing aperiodic CSI report trigger information, each in a different slot. Even in this case, the terminal may still be inefficient, as it must receive multiple DCIs and perform aperiodic CSI reporting accordingly.

[0462] Additionally, the terminal may not be able to transmit some or all of the aperiodic CSI reports triggered by the base station for network energy saving management due to priority rules such as ignoring lower priority CSI reports based on CPU (CSI Processing Unit) occupancy time or priority in cases where multiple CSI reports overlap in the time dimension. This may be inflexible and inefficient from the base station's scheduling perspective, as the terminal may have to perform network energy saving management without the information in the CSI report if the CSI report needs to be triggered again or if the CSI report is not received from the terminal within a certain time.

[0463] Accordingly, the base station can set flexible upper layer signaling so that the base station can transmit multiple CSI-RS resources having different numbers of ports (hereinafter, can be used interchangeably with antenna ports) to the terminal, and accordingly, can receive each CSI report for each CSI-RS resource having different numbers of ports from the terminal. To make this possible, the terminal can receive upper layer signaling configuration for the CSI report and the CSI-RS resource from the base station based on at least one combination of the following various methods.

[0464] [Method 1-1]

[0465] According to one embodiment, when a terminal receives a CSI report corresponding to CSI-RS resources having different numbers of ports from a base station for the purpose of network energy saving through upper layer signaling, the terminal may receive a plurality of CSI-ReportConfigs from the base station, and each of the plurality of CSI-ReportConfigs may be connected to a CSI-RS resource set including CSI-RS resources having different numbers of ports. In order to configure a CSI report corresponding to the CSI-RS resources having such different numbers of ports, the terminal may be configured by the base station to be connected to each other through upper layer signaling between the plurality of CSI-ReportConfigs. The signaling that connects the plurality of CSI-ReportConfigs in this way may be referred to as a linkage. The linkage that the terminal may receive through upper layer signaling may be configured through the following examples.

[0466] - In one way, it can be assumed that the terminal can configure multiple CSI-ReportConfigs within one CSI-AssociatedReportConfigInfo configuration. In this case, when multiple CSI-ReportConfigs are configured within one CSI-AssociatedReportConfigInfo, the multiple CSI-ReportConfigs can be considered or identified as being implicitly linked to each other, or an ID for linkage within the multiple CSI-ReportConfigs can be explicitly set through upper layer signaling, so that if two or more CSI-ReportConfigs have the same ID value, they can be considered or identified as being linked to each other. Additionally, since the terminal receives multiple CSI-ReportConfigs configured within a single CSI-AssociatedReportConfigInfo configuration, it can be assumed that the time domain behavior of the CSI-ReportConfigs is the same for all of them, and if all of the multiple CSI-ReportConfigs are for aperiodic CSI reports, the terminal can expect that the upper layer signaling resourceForChannel will be configured within the CSI-AssociatedReportConfigInfo configuration as many times as the number of CSI-ReportConfigs. The terminal can select one of multiple NZP-CSI-RS-ResourceSets that can be included in the CSI-ResourceConfig for each aperiodic CSI report by using the parameter called nzp-CSI-RS that can be configured through each resourceForChannel.

[0467] ■ For example, the terminal may receive the first to third CSI-ReportConfigs within one CSI-AssociatedReportConfigInfo setting, and a CSI-RS resource set including CSI-RS resources of two ports may be connected to the first CSI-ReportConfig, a CSI-RS resource set including CSI-RS resources of four ports may be connected to the second CSI-ReportConfig, and a CSI-RS resource set including CSI-RS resources of four ports may be connected to the third CSI-ReportConfig. In this case, since the three CSI-ReportConfigs are set within one CSI-AssociatedReportConfigInfo setting, the terminal may consider or identify that the three CSI-ReportConfigs are implicitly connected to each other even without additional upper layer signaling. Alternatively, if the terminal has set the linkage ID to 0 for each of the three CSI-ReportConfigs within a single CSI-AssociatedReportConfigInfo configuration, the three CSI-ReportConfigs can be considered to be explicitly linked to each other.

[0468] - Alternatively, the terminal may consider or identify that two or more CSI-AssociatedReportConfigInfo are linked to each other. In this case, the terminal may consider or identify that one CSI-ReportConfig is configured within each CSI-AssociatedReportConfigInfo. The terminal may receive multiple CSI-AssociatedReportConfigInfo configured within the upper layer signaling CSI-AperiodicTriggerState, and an ID for linkage within each of the multiple CSI-AssociatedReportConfigInfo may be explicitly configured through upper layer signaling. The terminal may consider or identify that two or more CSI-AssociatedReportConfigInfo having the same ID value are linked to each other. Alternatively, the terminal may expect that an additional upper layer signaling, such as CSI-linkedReportConfiglist, is established between the connection relationship between the upper layer signaling CSI-AperiodicTriggerState and CSI-AssociatedReportConfigInfo, such that CSI-linkedReportConfiglist is established within CSI-AperiodicTriggerState and multiple CSI-AssociatedReportConfigInfo are established within this CSI-linkedReportConfiglist. In this case, the terminal may consider or identify that the multiple CSI-AssociatedReportConfigInfos established within CSI-linkedReportConfiglist are implicitly linked to each other.

[0469] - For example, a terminal may consider or identify that two or more CSI-AperiodicTriggerStates are connected to each other. The terminal may receive DCI from a base station, and aperiodic CSI report transmission related to one of the multiple CSI-AperiodicTriggerStates may be triggered through a CSI request field in the DCI. In this case, if two or more CSI-AperiodicTriggerStates are connected to each other, even if aperiodic CSI report transmission related to one CSI-AperiodicTriggerState is triggered through the DCI, the terminal may consider or identify that a trigger instruction has been received from the base station for the connected CSI-AperiodicTriggerState. At this time, the terminal can expect that one or more CSI-AssociatedReportConfigInfo will be set within the upper layer signaling CSI-AperiodicTriggerState, and one CSI-ReportConfig will be set within each CSI-AssociatedReportConfigInfo. For a connection between two or more CSI-AperiodicTriggerStates, the terminal can explicitly set an ID for the linkage within each of the multiple CSI-AperiodicTriggerStates through upper layer signaling, so that the two or more CSI-AperiodicTriggerStates having the same ID value can be considered or identified as being connected to each other.

[0470] Alternatively, if the number of CSI-AperiodicTriggerStates set by upper layer signaling is greater than the number of code points of the CSI request field in the DCI by one less value, the terminal may link some of the entire CSI-AperiodicTriggerStates to the code points of the CSI request field through MAC-CE. In this case, two or more CSI-AperiodicTriggerStates may be linked to one code point of the CSI request field through MAC-CE. In this case, if two or more CSI-AperiodicTriggerStates are linked to one code point of the CSI request field, the terminal may consider or identify that these multiple CSI-AperiodicTriggerStates are linked to each other. Even if the number of CSI-AperiodicTriggerStates set by upper layer signaling is less than or equal to the number of code points of the CSI request field in the DCI by one less value, two or more CSI-AperiodicTriggerStates may be linked to one code point of the CSI request field by a specific rule. For example, if the ID for the linkage in two or more CSI-AperiodicTriggerStates is set to the same value, the terminal may determine that multiple CSI-AperiodicTriggerStates having the ID for the same linkage are linked to one code point of the CSI request field.

[0471] According to one embodiment, in order to configure a CSI report corresponding to a CSI-RS resource having a different number of ports, a terminal may be configured by a base station to be connected to each other through upper layer signaling between the plurality of CSI-ReportConfigs.

[0472] According to one embodiment, in order to configure a CSI report corresponding to a CSI-RS resource having a different number of CSI-RS ports, the terminal may connect multiple CSI-ReportConfigs from the base station, and for the multiple connected CSI-ReportConfigs, the terminal may perform CSI report transmission to the base station at the same time position (e.g., the same slot or / and the same symbol) even if triggered through one DCI.

[0473] According to one embodiment, a plurality of CSI-ReportConfigs may be connected, and CSI-RS resource sets within CSI-ResourceConfigs included in each CSI-ReportConfig may include CSI-RS resources having the same number of CSI-RS ports. For example, CSI-ReportConfigs such as first to third CSI-ReportConfigs may be connected through the various methods, and a CSI-RS resource set including CSI-RS resources of two ports may be connected to a first CSI-ReportConfig, a CSI-RS resource set including CSI-RS resources of four ports may be connected to a second CSI-ReportConfig, and a CSI-RS resource set including CSI-RS resources of four ports may be connected to a third CSI-ReportConfig.

[0474] However, if a base station sends CSI-RS resources having different numbers of CSI-RS ports to a terminal in an overlapping manner, i.e., if an RE corresponding to a CSI-RS resource having a small number of CSI-RS ports is included in an RE corresponding to a CSI-RS resource having a large number of CSI-RS ports, the following method may be used in addition to a method of individually defining CSI-RS resources having different numbers of CSI-RS ports.

[0475] According to one embodiment, a single CSI-RS resource having a largest value among different numbers of CSI-RS ports for which channel estimation is to be performed may be defined (e.g., if channels are to be estimated for CSI-RS ports 2, 4, and 8, the CSI-RS resource may be defined as a CSI-RS resource having 8 CSI-RS ports), and the terminal may use a method of estimating channel states according to different numbers of CSI-RS ports using some or all of the RE mappings of the resource. That is, the terminal may confirm or identify a single CSI-RS resource having a largest value among different numbers of CSI-RS ports for which channel estimation is to be performed, and may assume that the corresponding CSI-RS resource is commonly included in all CSI-RS resource sets included in the first to third CSI-ReportConfigs, respectively.

[0476] Although a CSI-RS resource has a specific number of CSI-RS ports by upper layer signaling (e.g., if channel estimation is to be performed for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource with 8 CSI-RS ports), depending on which CSI-ReportConfig it is connected to, the UE can be configured to perform channel estimation for some or all ports of the corresponding CSI-RS resource and report a CSI report for the estimated channel to the base station. Regarding the definition of the number of CSI-RS ports to be used for actual channel estimation, rather than the number of CSI-RS ports based on upper layer signaling configuration, the base station can configure for the UE in each CSI-RS resource set configuration, CSI-ReportConfig configuration, CSI-AssociatedReportConfigInfo configuration, or CSI-AperiodicTriggerState configuration.

[0477] [Method 1-2]

[0478] According to one embodiment, when a method of linking multiple CSI-ReportConfig configuration information is used, multiple CSI-ReportConfigs may be linked to one identical CSI-RS resource set, and the CSI-RS resource set may include multiple CSI-RS resources having different numbers of CSI-RS ports. For example, the terminal may receive first to third CSI-ReportConfigs in one CSI-AssociatedReportConfigInfo configuration, and all three CSI-ReportConfigs may be linked to one CSI-RS resource set, and the corresponding CSI-RS resource set may include CSI-RS resources of two ports, CSI-RS resources of four ports, and CSI-RS resources of eight ports.

[0479] If a linking method between the above multiple CSI-ReportConfig configuration information is used, the restriction that only CSI-RS resources with the same number of ports can be included in a single CSI-RS resource set is lifted, and the terminal can be configured by the base station through upper layer signaling to include multiple CSI-RS resources with different numbers of ports in a single CSI-RS resource set. In this case, since information related to a specific number of CSI-RS ports is configured as additional information in each CSI-ReportConfig through upper layer signaling, the terminal can calculate CSI based on information related to a specific number of CSI-RS ports through the CSI report configuration. For example, if additional information is set for CSI calculation for 2 ports in the first CSI-ReportConfig, and similarly, additional information is set for CSI calculation for 4 and 8 ports in the second and third CSI-ReportConfig, when the terminal calculates CSI to perform a CSI report based on the first CSI-ReportConfig, the second CSI-ReportConfig, and the third CSI-ReportConfig, the terminal may utilize CSI-RS resources having 2, 4, and 8 CSI-RS ports included in the same CSI-RS resource set to which the first CSI-ReportConfig to the third CSI-ReportConfig are connected, respectively.

[0480] According to one embodiment, when a base station transmits CSI-RS resources having different numbers of CSI-RS ports to a terminal in an overlapping manner, i.e., when an RE corresponding to a CSI-RS resource having a small number of CSI-RS ports is included in an RE corresponding to a CSI-RS resource having a large number of CSI-RS ports, a method described below may be used in addition to a method of individually defining CSI-RS resources having different numbers of CSI-RS ports.

[0481] According to one embodiment, a single CSI-RS resource having the largest value among different numbers of CSI-RS ports on which the terminal intends to perform channel estimation may be defined. For example, if the terminal intends to estimate channels for CSI-RS ports 2, 4, and 8, the CSI-RS resource may be defined as a CSI-RS resource having 8 CSI-RS ports. The terminal may also use a method of estimating channel states according to different numbers of CSI-RS ports by using some or all of the RE mappings of the defined CSI-RS resources. That is, the terminal may confirm or identify a single CSI-RS resource having the largest value among different numbers of CSI-RS ports on which the terminal intends to perform channel estimation, and may assume or identify that the CSI-RS resource having the largest value is included in the same CSI-RS resource set connected to the first CSI-ReportConfig to the third CSI-ReportConfig.

[0482] Although a CSI-RS resource has a specific number of CSI-RS ports by upper layer signaling (for example, if one wants to estimate channels for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource with 8 CSI-RS ports), depending on which CSI-ReportConfig it is connected to, the terminal can perform channel estimation for some or all ports of the corresponding CSI-RS resource and can be configured to transmit a CSI report for the estimated channel to the base station.

[0483] According to one embodiment, the base station may set or include information on the number of CSI-RS ports to be used in actual channel estimation, rather than the number of CSI-RS ports based on upper layer signaling settings, in each CSI-RS resource set configuration, in the CSI-ReportConfig configuration, in the CSI-AssociatedReportConfigInfo configuration, and / or in the CSI-AperiodicTriggerState configuration, and may set the CSI-RS port number information to the terminal. For example, the base station may set the information to the terminal based on each CSI-RS resource set configuration, the CSI-ReportConfig configuration, the CSI-AssociatedReportConfigInfo configuration, and / or the CSI-AperiodicTriggerState configuration.

[0484] According to one embodiment, in order to configure a CSI report corresponding to a plurality of CSI-RS resources having different numbers of CSI-RS ports, a plurality of CSI-ReportConfigs may be connected to each other, and the connected CSI-ReportConfigs may be connected to a single identical CSI-RS resource set, and the CSI-RS resource set may include a plurality of CSI-RS resources having different numbers of CSI-RS ports. For a plurality of CSI-ReportConfigs connected in this manner, a terminal may perform CSI report transmission to a base station at the same time position (e.g., the same slot or / and the same symbol) even if triggered through a single DCI.

[0485] [Method 1-3]

[0486] In one embodiment, the terminal may expect or identify that one CSI-ReportConfig is associated with multiple CSI-RS resource sets. For example, the terminal may expect or identify that one CSI-ReportConfig is configured in one CSI-AssociatedReportConfigInfo, which is an upper layer signaling, and that three CSI-RS resource sets are included in the CSI-ReportConfig. In this case, the CSI-RS resources included in the first CSI-RS resource set may have two CSI-RS ports, and the CSI-RS resources included in the second CSI-RS resource set and the third CSI-RS resource set may have four and eight CSI-RS ports, respectively. Through this, the terminal may include CSI for different numbers of CSI-RS ports in the CSI report through one CSI-ReportConfig and report it to the base station.

[0487] Multiple CSI-RS resource sets can be associated with a single CSI-ReportConfig when periodic and semi-persistent CSI-RS resource sets are associated. In the case of aperiodic CSI-RS resource sets, multiple resourceForChannels can be included in a single CSI-AssociatedReportConfigInfo, which is upper layer signaling, and the UE can select each CSI-RS resource set based on each resourceForChannel, and multiple CSI-RS resource sets can be associated with a single CSI-ReportConfig based on the selected CSI-RS resource set. The UE can select multiple associated CSI-RS resource sets and reflect them in the corresponding CSI report.

[0488] For example, if a new reportQuantity is defined and set in CSI-ReportConfig that can mean CSI calculation for different numbers of ports, the terminal can report CSI calculation and report by linking different CSI-RS resource sets in CSI-ReportConfig.

[0489] According to one embodiment, for [Method 1-3], a plurality of CSI-RS resource sets included in one CSI-ReportConfig may commonly include a CSI-RS resource having the same number of CSI-RS ports, and the CSI-RS resource may have the largest value among different numbers of CSI-RS ports.

[0490] That is, similarly to the method of setting up an additional CSI-RS resource described in the above-described [Method 1-1], one CSI-RS resource having the largest value among different numbers of CSI-RS ports for which channel estimation is to be performed can be defined (for example, if channels are to be estimated for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource having 8 CSI-RS ports), and the terminal can estimate the channel state according to different numbers of CSI-RS ports using some or all of the RE mapping of the resource.

[0491] That is, a single CSI-RS resource having the largest value among different numbers of CSI-RS ports for which channel estimation is to be performed can be defined, and the CSI-RS resource can be commonly included in multiple CSI-RS resource sets included in the corresponding CSI-ReportConfig.

[0492] Although a CSI-RS resource has a specific number of CSI-RS ports by upper layer signaling (for example, if a channel is to be estimated for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource having 8 CSI-RS ports), depending on which CSI-RS resource set the CSI-RS resource is included in, the UE can perform channel estimation for some or all ports of the CSI-RS resource and report a CSI report for the estimated channel to the base station. For example, for the CSI-RS resource of port 8 included in CSI-RS resource set 0, the UE can perform channel estimation for 8 ports, and for the same CSI-RS resource included in CSI-RS resource set 1, the UE can perform channel estimation for 4 ports. The base station can define the number of CSI-RS ports to be used for actual channel estimation, rather than the number of CSI-RS ports based on the upper layer signaling settings, within each CSI-RS resource set setting, within the CSI-ReportConfig setting, within the CSI-AssociatedReportConfigInfo setting, and / or within the CSI-AperiodicTriggerState setting for the terminal.

[0493] According to one embodiment, in order to configure a CSI report corresponding to multiple CSI-RS resources having different numbers of CSI-RS ports, a terminal may report a CSI report to a base station using multiple CSI-RS resource sets within one CSI-ReportConfig from the base station. Each CSI-RS resource set may include CSI-RS resources having different numbers of CSI-RS ports, or may include one CSI-RS resource having a largest value among the different numbers of CSI-RS ports. The terminal may perform CSI report transmission to the base station at the same time position (e.g., the same slot and / or the same symbol) using one CSI report for the CSI-ReportConfig.

[0494] According to one embodiment, for [Method 1-3], the terminal may receive one or more detailed CSI report configurations within one CSI-ReportConfig configuration through upper layer signaling. Each detailed CSI report configuration may be associated with one of the plurality of CSI-RS resource sets, and the number of detailed CSI report configurations may be equal to the number of the plurality of CSI-RS resource sets.

[0495] [Method 1-4]

[0496] According to one embodiment, the terminal may expect or identify that one CSI-ReportConfig is associated with one CSI-RS resource set including multiple CSI-RS resources having different numbers of ports. For example, one CSI-ReportConfig may be configured in one CSI-AssociatedReportConfigInfo, which is an upper layer signaling, and one CSI-RS resource set may be included in the CSI-ReportConfig, and a first CSI-RS resource having two CSI-RS ports may be included in the CSI-RS resource set, a second CSI-RS resource having four CSI-RS ports may be included in the CSI-RS resource set, and a third CSI-RS resource having eight CSI-RS ports may be included in the CSI-RS resource set. Based on the CSI-ReportConfig and the CSI-RS resource set, the terminal may calculate CSI according to different numbers of ports and report the same to the base station.

[0497] At this time, specific upper layer signaling configured within the CSI-AperiodicTriggerState, within the CSI-AssociatedReportConfigInfo, within the CSI-ReportConfig, and / or within the CSI-RS resource set may indicate that the CSI-RS resource set associated with the CSI-ReportConfig is allowed to include multiple CSI-RS resources, each having a different number of CSI-RS ports. This specific upper layer signaling may exist in various forms.

[0498] For example, if a specific upper layer signaling exists in CSI-ReportConfig, the specific upper layer signaling may exist in the form of a new reportQuantity. If a specific upper layer signaling exists in CSI-AperiodicTriggerState, the specific upper layer signaling may be defined as a new parameter to allow CSI calculation based on multiple CSI-RS resources having different numbers of CSI-RS ports, instead of selecting one of multiple CSI-RS resource sets connected to CSI-ReportConfig based on resourceForChannel. For example, the new parameter may be multipleNrofPortsForresourceForChannel. The names of the parameters described above are only examples and do not limit the present disclosure. Based on this, the terminal may select multiple CSI-RS resources having different numbers of ports connected to one CSI-ReportConfig and reflect them in CSI calculation and reporting.

[0499] According to one embodiment, in order to configure a CSI report corresponding to a CSI-RS resource having a different number of CSI-RS ports, a terminal may receive from a base station a connection to a single CSI-ReportConfig and a CSI-RS resource set, wherein the CSI-RS resource set may include a plurality of CSI-RS resources having different numbers of CSI-RS ports. Based on the CSI-ReportConfig connected to the CSI-RS resource set including the multiple CSI-RS resources having the different numbers of CSI-RS ports, the terminal may estimate a channel based on the different numbers of CSI-RS ports, calculate CSI for each channel, and then transmit a CSI report to the base station at the same time position (e.g., the same slot and / or symbol) for the estimated channel.

[0500] According to one embodiment, for [Method 1-4], the terminal may receive one or more detailed CSI report configurations configured through upper layer signaling within one CSI-ReportConfig configuration. Each detailed CSI report configuration may be associated with one of a plurality of CSI-RS resources having different numbers of ports configured within the one CSI-RS resource set, and the number of detailed CSI report configurations may be equal to the number of the plurality of CSI-RS resources having different numbers of ports configured within the one CSI-RS resource set.

[0501] [Method 1-5]

[0502] According to one embodiment, in order for a terminal to calculate CSI for multiple CSI-RS resources having different numbers of ports and to report the calculated CSI to a base station, the base station may set a CSI-RS resource having a largest port number among the different port numbers in one CSI-RS resource set, and the CSI-RS resource set may be connected to one CSI-ReportConfig.

[0503] That is, instead of individually defining CSI-RS resources having different numbers of CSI-RS ports, a single CSI-RS resource having the largest value among the different numbers of CSI-RS ports for which channel estimation is to be performed can be defined (for example, if a terminal wants to estimate channels for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource having 8 CSI-RS ports), and a method of estimating the different numbers of CSI-RS ports using some or all of the RE mappings of the resource can be used.

[0504] That is, a CSI-RS resource is included in one CSI-RS resource set included in CSI-ReportConfig, and although it is a CSI-RS resource having a specific number of CSI-RS ports through upper layer signaling (for example, if channels are to be estimated for CSI-RS ports 2, 4, and 8, the corresponding CSI-RS resource can be defined as a CSI-RS resource having 8 CSI-RS ports), the UE can estimate channels for some or all CSI-RS ports of the CSI-RS resource, and calculate and report individual CSI for the estimated channels.

[0505] According to one embodiment, in order to configure a CSI report corresponding to a CSI-RS resource having a different number of CSI-RS ports, a terminal may receive from a base station a connection to the single CSI-ReportConfig and a CSI-RS resource set. The CSI-RS resource set may include a CSI-RS resource having a largest value among the different numbers of CSI-RS ports. Based on these CSI-RS resources, the terminal may estimate channels for some or all of the CSI-RS ports, calculate individual CSI for each channel, and transmit a CSI report to the base station at the same time location (e.g., the same slot and / or symbol) for the calculated CSI.

[0506] According to one embodiment, for [Method 1-5], the terminal may receive one or more detailed CSI report configurations configured within one CSI-ReportConfig configuration through upper layer signaling. Each detailed CSI report configuration may be linked to one CSI-RS resource configured within the one CSI-RS resource set. The detailed CSI report configuration may include values ​​corresponding to some or all of the number of CSI-RS ports of the one connected CSI-RS resource. For example, if the number of CSI-RS ports of the one connected CSI-RS resource is eight and there are three detailed CSI report configurations, each detailed CSI report configuration may include CSI report configurations for the numbers of CSI-RS ports of two, four, and eight, respectively.

[0507] According to one embodiment, for the above-described [Method 1-3] to [Method 1-5], if there is one or more detailed CSI report configurations in the CSI-ReportConfig, the terminal may configure the upper layer signaling that can be configured in the CSI-ReportConfig, namely reportQuantity, reportFreqConfiguration, timeRestrictionForChannelMeasurements, timeRestrictionForInterferenceMeasurements, codebookConfig, dummy, groupBasedBeamReporting, cqi-Table, subbandSize, non-PMI-Port-Indication, semiPersistentOnPUSCH-v1530, semiPersistentOnPUSCH-v1610, aperiodic-v1610, reportQuantity-r16, codebookConfig-r16, cqi-BitsPerSubband-r17, groupBasedBeamReporting-v1710, codebookConfig-r17, sharedCMR-r17, For at least one of the configuration information among csi-ReportMode-r17, numberOfSingleTRP-CSI-Mode1-r17, reportQuantity-r17, semiPersistentOnPUSCH-v1720, aperiodic-v1720, or codebookConfig-v1730, the terminal can expect or discern that each detailed CSI report configuration exists individually, or for at least one configuration information, the terminal can expect or discern that a single configuration information is commonly applied to all detailed CSI report configurations.For example, reportQuantity, reportFreqConfiguration, cqi-Table, and / or subbandSize may be received through common configuration information for each detailed CSI report configuration, while other parameters may be received through configuration information individually for each detailed CSI report configuration.

[0508] According to one embodiment, the terminal may report as a terminal capability the maximum number of detailed CSI report configurations that can be set within one CSI-reportConfig for the detailed CSI report configurations that can be considered for the above-described [Method 1-3] to [Method 1-5]. For example, the maximum number may be one of the natural numbers less than or equal to 32. In addition, the terminal may report as a terminal capability the maximum value of the total number of detailed CSI report configurations that can be set within the entire CSI-ReportConfig.

[0509] According to one embodiment, for detailed CSI report settings that can be considered for the above-described [Method 1-3] to [Method 1-5], the terminal may receive one of the following items related to detailed CSI report settings from the base station through upper layer signaling.

[0510] - [Method 1-1-1] The terminal may arbitrarily select some or all of the detailed CSI report settings set by the base station and report them to the base station. In this case, the terminal may include information about the detailed CSI report settings selected by the terminal from among the detailed CSI report settings.

[0511] - [Method 1-1-2] The terminal can receive, through upper layer signaling from the base station, the number of detailed CSI report settings to be selected and reported to the base station by the terminal from among all detailed CSI report settings within one CSI-ReportConfig. In this case, the terminal can include information about the detailed CSI report settings selected by the terminal from among all detailed report settings within the CSI report.

[0512] - [Method 1-1-3] The terminal may receive an ID for a specific detailed CSI report setting to be reported to the base station from among all detailed CSI report settings within one CSI-ReportConfig from the base station through upper layer signaling. At this time, the terminal does not include the ID for the detailed CSI report setting set from the base station within the CSI report, and may include the CSI corresponding to each detailed CSI report setting within the CSI report in a specific order of the IDs for the detailed CSI report settings that the base station has set to be reported to the terminal. For example, if the terminal has received four detailed CSI report settings (e.g., ID1 to ID4) within one CSI-ReportConfig from the base station through upper layer signaling, and additionally has been set to report ID2 and ID3 from the base station, the terminal may include the CSI corresponding to detailed CSI report setting ID2 in ascending order of ID within the CSI report, and then include the CSI corresponding to detailed CSI report setting ID3 thereafter. At this time, if the CSI report for the detailed CSI report setting is divided into two parts, the terminal may include part 1 of the detailed CSI report setting ID2 and ID3 in the CSI report and place part 2 of the detailed CSI report setting ID2 and ID3 thereafter, or include part 1 and part 2 of the detailed CSI report setting ID2 in the CSI report and then include part 1 and part 2 of the detailed CSI report setting ID3 in the CSI report.

[0513] - [Method 1-1-4] The terminal can be configured through upper layer signaling from the base station for at least one combination of [Method 1-1-1] to [Method 1-1-3].

[0514] According to one embodiment, the terminal may report to the base station through terminal capability signaling whether it supports at least one combination of [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4]. The terminal may receive at least one combination of [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4] from the base station through upper layer signaling, activation through MAC-CE, instruction through L1 signaling, or notification through at least one combination of upper layer signaling, MAC-CE, and L1 signaling. Alternatively, the terminal may follow a method fixedly supported by the standard.

[0515] According to one embodiment, a method for requesting aperiodic channel state information based on PUSCH for network energy saving is described.

[0516] As one embodiment of the present disclosure, a method for requesting aperiodic channel state information (PUSCH) based on PUSCH for network energy saving at a terminal and a base station is described. This embodiment can be operated in combination with other embodiments within the present disclosure.

[0517] According to one embodiment, the terminal may report to the base station as terminal capabilities the maximum number of detailed CSI report configurations that the terminal may configure in CSI-ReportConfig, the maximum number of detailed CSI report configurations that the terminal may actually report in CSI-ReportConfig, and / or the maximum number of detailed CSI report configuration lists that the terminal may configure in CSI-ReportConfig. The terminal capabilities may be limited to aperiodic CSI reports, or may be values ​​that take into account all of aperiodic, semi-persistent, and periodic CSI reports.

[0518] According to one embodiment, a terminal may receive an aperiodic CSI report request from a base station via a CSI request field in DCI. If the terminal includes one or more detailed CSI report configurations in CSI-ReportConfig for network energy saving, the terminal may receive an aperiodic CSI report request based on a CSI-ReportConfig configuration including the detailed CSI report configurations from the base station using at least one of the following methods.

[0519] [Method 2-1]

[0520] According to one embodiment, the terminal may be configured to associate one or more CSI-AssociatedReportConfigInfo for each code point of the CSI request field in the DCI. The terminal may include one CSI-ReportConfig in one CSI-AssociatedReportConfigInfo through upper layer signaling. The terminal may receive multiple detailed CSI report configurations in one CSI-ReportConfig from the base station through upper layer signaling.

[0521] Under the upper layer signaling configuration, if a terminal is instructed by a base station to a specific codepoint through a CSI request field in DCI, the terminal may report aperiodic CSI reports to the base station for all multiple detailed CSI report configurations in CSI-ReportConfig included in CSI-AssociatedReportConfigInfo associated with the codepoint. That is, the terminal may have to report for all multiple detailed CSI report configurations that the base station configures in CSI-ReportConfig, and the base station may adjust the CSI calculation burden of the terminal by adjusting the number of detailed CSI report configurations configured in CSI-ReportConfig. However, a disadvantage may be that the adjustment by the base station can only be quasi-static.

[0522] According to one embodiment, the base station may configure two CSI-ReportConfigs with two different CSI-ReportConfigIds, with only the number of detailed CSI report settings being different among all configuration information, while keeping the remaining configuration information the same, to the terminal through upper layer signaling. Such two CSI-ReportConfigs may be linked to different CSI-AssociatedReportConfigInfos, and the different CSI-AssociatedReportConfigInfos may be linked to the same or different code points of CSI requests, and may be triggered through the same or different DCIs received from the base station.

[0523] For example, a terminal may be configured with a first CSI-ReportConfig and a second CSI-ReportConfig, and within the first CSI-ReportConfig, a total of four antenna ports, 2, 4, 8, and 16, may be configured as detailed CSI report settings. Within the second CSI-ReportConfig, a total of two antenna ports, 8 and 16, may be configured as detailed CSI report settings, and the remaining configuration information of the first CSI-ReportConfig and the second CSI-ReportConfig may be assumed to be all the same.

[0524] The first CSI-ReportConfig is connected to the first CSI-AssociatedReportConfigInfo, and the second CSI-ReportConfig is connected to the second CSI-AssociatedReportConfigInfo, and the first CSI-AssociatedReportConfigInfo and the second CSI-AssociatedReportConfigInfo may be connected to the same codepoint of the CSI request field, or may be connected to different codepoints. If connected to different codepoints, the base station may determine which of the detailed CSI report configurations of the CSI-ReportConfig to receive a CSI report from the terminal for, and which detailed CSI report configuration to cause the terminal to calculate and report, by transmitting a specific codepoint of the CSI request field to the terminal. This indication may have a trade-off between the CSI calculation overhead of the terminal and the information reception from the terminal for network energy saving at the base station. However, configuring different CSI-ReportConfigs that contain exactly the same configuration information except for the detailed CSI report settings may be an inefficient upper layer signaling configuration method considering the terminal's limitation that it can receive up to 48 different CSI-ReportConfig settings.

[0525] [Method 2-2]

[0526] According to one embodiment, the terminal may be configured to associate one or more CSI-AssociatedReportConfigInfo for each code point of the CSI request field in the DCI. The terminal may include one CSI-ReportConfig in one CSI-AssociatedReportConfigInfo through upper layer signaling. The terminal may be configured to configure multiple detailed CSI reports in one CSI-ReportConfig.

[0527] Under the upper layer signaling configuration, the terminal may expect or identify additional upper layer signaling configured within CSI-AssociatedReportConfigInfo associated with each code point of the CSI request field within the DCI. For example, the additional upper layer signaling may be a signaling that selects some or all of the multiple detailed CSI report configurations configured within the CSI-ReportConfig contained within CSI-AssociatedReportConfigInfo.

[0528] - For example, the terminal may assume that the first CSI-AssociatedReportConfigInfo is connected to the first code point of the CSI request field in the DCI, and that the second CSI-AssociatedReportConfigInfo is connected to the second code point. The same CSI-ReportConfig is configured in both the first CSI-AssociatedReportConfigInfo and the second CSI-AssociatedReportConfigInfo, and the CSI-ReportConfig may include four detailed CSI report settings. In this case, the terminal may expect that the first CSI-AssociatedReportConfigInfo connected to the first code point of the CSI request field includes configuration information for selecting some of the four detailed CSI report settings included in the corresponding CSI-ReportConfig (e.g., the first and second detailed CSI report settings). Additionally, the terminal may expect that the second CSI-AssociatedReportConfigInfo associated with the second code point of the CSI request field includes configuration information for selecting all of the four detailed CSI report configurations included in the corresponding CSI-ReportConfig (e.g., the first to fourth detailed CSI report configurations).

[0529] - For another example, the terminal may assume that the first CSI-AssociatedReportConfigInfo is connected to the first code point of the CSI request field in the DCI, and may assume that the second CSI-AssociatedReportConfigInfo is connected to the second code point. The same CSI-ReportConfig is set in both the first CSI-AssociatedReportConfigInfo and the second CSI-AssociatedReportConfigInfo, and the CSI-ReportConfig may include two detailed CSI report configuration lists. Each detailed CSI report configuration list may be referenced as a list including one or more detailed CSI report configurations. For example, if the CSI-ReportConfig includes four detailed CSI report configurations, the first detailed CSI report configuration list may include the first detailed CSI report configuration list and the second detailed CSI report configuration, and the second detailed CSI report configuration list may include the third and fourth detailed CSI report configurations. At this time, the terminal may expect that the first CSI-AssociatedReportConfigInfo linked to the first code point of the CSI request field includes configuration information for selecting a first list (e.g., including a first detailed CSI report configuration and a second detailed CSI report configuration) among the two detailed CSI report configuration lists included in the CSI-ReportConfig.Additionally, the terminal may expect that the second CSI-AssociatedReportConfigInfo associated with the second code point of the CSI request field includes configuration information for selecting a second list (including the third and fourth detailed CSI report configurations) from among the two detailed CSI report configuration lists included in the CSI-ReportConfig.

[0530] According to one embodiment, by introducing the upper layer signaling as above, the terminal and the base station can configure all of the multiple detailed CSI report configurations applicable to the corresponding CSI-ReportConfig within each CSI-ReportConfig, and then select some or all of the multiple detailed CSI report configurations using additional configuration information that can be included within the CSI-AssociatedReportConfigInfo linked to the CSI request codepoint. In this way, by using different CSI-AssociatedReportConfigInfo linked to the same CSI-ReportConfig, the base station can select different detailed CSI report configurations within the same CSI-ReportConfig for the terminal, thereby controlling the CSI calculation overhead at the terminal and the amount of information for network energy saving.

[0531] According to one embodiment, by introducing the upper layer signaling as above, similar to the method in which the terminal and the base station select one of multiple NZP-CSI-RS-ResourceSets configured in the CSI-ReportConfig for the aperiodic CSI report using the configuration information in the CSI-AssociatedReportConfigInfo, the terminal may set as much information as possible for multiple detailed CSI report settings that may exist in the CSI-ReportConfig, and may use a method of selectively selecting some of the multiple detailed CSI report settings when the base station triggers the aperiodic CSI report through the CSI request field.

[0532] [Method 2-3]

[0533] According to one embodiment, the terminal may be configured to associate one or more CSI-AssociatedReportConfigInfo for each code point of the CSI request field in the DCI. The terminal may include one CSI-ReportConfig in one CSI-AssociatedReportConfigInfo through upper layer signaling. The terminal may be configured to configure multiple detailed CSI reports in one CSI-ReportConfig.

[0534] Under the upper layer signaling configuration, the terminal may be instructed to select some or all of the detailed CSI report configurations configured in the CSI-ReportConfig, which are included in the CSI-AssociatedReportConfigInfo linked to the code point indicated by the CSI request field in the DCI, based on a new field defined in the same DCI or additional bits in the CSI request field. For example, the new field or additional bits in the CSI request field may be expressed in the form of a bitmap according to the maximum number of detailed CSI report configurations, or may be in a way that indicates a specific combination of all detailed CSI report configurations. It is also possible that new fields are defined based on other methods.

[0535] - In the case of bitmap format, if the maximum number of detailed CSI report settings that the terminal can set in CSI-ReportConfig is N, it can be represented by N bitmaps. In the case of representing in bitmap format, even if the maximum number M of detailed CSI report settings that the terminal can actually report in CSI-ReportConfig is smaller than the maximum number N of detailed CSI report settings that the terminal can set in CSI-ReportConfig, the length of the field in DCI must be N, not M, so overhead may increase. For example, if N is 4 and M is 2, the terminal can consider or identify 4 bits as a new field. At this time, even if the maximum number of detailed CSI report settings that the terminal can set in the CSI-ReportConfig is N, if the number of detailed CSI report settings set in a specific CSI-ReportConfig is less than N (for example, N'), the terminal can be instructed by the base station which detailed CSI report settings to report based on only N' bits from the MSB (or LSB) of the new field. For example, if N is 4 and N', which is the number of detailed CSI report settings set in the specific CSI-ReportConfig, is 3, the terminal can be instructed by the base station which detailed CSI report settings to report based on only 3 bits from the MSB (or LSB) of the new field consisting of 4 bits. In addition, the terminal can expect or identify that the number of bits having a value of 1 in the new field is less than or equal to M.

[0536] - In the case of a method of indicating a specific combination, if the maximum number of detailed CSI report settings that the terminal can set in CSI-ReportConfig is N, and the maximum number of detailed CSI report settings that the terminal can actually report in CSI-ReportConfig is M, the terminal can consider or identify a length of bits that can express the number of cases in which M is selected out of N as the length of the new field. For example, if N is 4 and M is 2, the terminal can consider or identify 3 bits that can express a total of 6 cases as the length of the new field. In this case, even if the maximum number of detailed CSI report settings that the terminal can set, N, is 4, if the number of detailed CSI report settings set in a specific CSI-ReportConfig is less than N (for example, N'), the terminal and the base station can assume that they will use only as many code points as the number of cases in which M is selected out of N' from the first code point of the new field, and can treat the remaining code points as reserved. For example, if N is 4, M is 2, and N', the number of detailed CSI report settings set in a specific CSI-ReportConfig, is 3, the terminal and base station can assume that they will use 3 code points, which is the number of cases in which M (=2) is selected from N' (=3) code points starting from the first code point, out of a total of 8 code points of the new field that can be expressed with 3 bits, and the remaining 5 code points can be processed as reserved.

[0537] - The terminal and the base station can expect to include at most E detailed CSI report configuration lists in the CSI-ReportConfig, and can perform a CSI report for the corresponding CSI-ReportConfig by selecting one of the E' (<=E) lists through the CSI request field in the DCI or through a new field. Each detailed CSI report configuration list can be referenced as a list including one or more detailed CSI report configurations. For example, if the terminal includes a total of 3 (=N') detailed CSI report configurations in a specific CSI-ReportConfig, and a total of 2 (=E') detailed CSI report configuration lists, the first detailed CSI report configuration list can include the first detailed CSI report configuration, the second detailed CSI report configuration, and the third detailed CSI report configuration. The second detailed CSI report configuration list can include the second and third detailed CSI report configurations. At this time, the terminal may be instructed to select one of two detailed CSI report configuration lists from the base station through an additional bit of the CSI request field in the DCI or a new field, and may report a CSI report corresponding to the detailed CSI report configurations included in the list to the base station. The bit length of the additional bit or new field in the CSI request field may be related to the value of E, and more specifically, may be the number of bits capable of expressing E (for example, it may be expressed as ceil(log2(E)), where ceil(.) is a rounding function and log2(.) is a logarithmic function with a base of 2).

[0538] According to one embodiment, the terminal may report to the base station as the terminal capability N (e.g., the maximum number of detailed CSI report configurations that the terminal can configure in CSI-ReportConfig), M (e.g., the maximum number of detailed CSI report configurations that the terminal can actually report in CSI-ReportConfig), or E (e.g., the maximum number of detailed CSI report configuration lists that the terminal can configure in CSI-ReportConfig).

[0539] In one embodiment, when a terminal uses a method of selecting some or all of the detailed CSI report settings in a CSI-ReportConfig for network energy saving by using a CSI request field in a DCI and additional bits or new fields in the CSI request field, the terminal can expect or identify that there is only one CSI-ReportConfig including the detailed CSI report settings among aperiodic CSI reports triggered through the DCI. If there are two or more CSI-ReportConfigs including the detailed CSI report settings among aperiodic CSI reports triggered through the DCI, the terminal can expect that the additional bits or new fields in the CSI request field defined above are commonly applied to all of the multiple CSI-ReportConfigs including the detailed CSI report settings triggered through the corresponding DCI.

[0540] If there are two or more CSI-ReportConfigs that include detailed CSI report settings among the aperiodic CSI reports triggered via DCI, the terminal may expect or identify that additional bits or new fields in the defined CSI request field are defined as the number of duplicate CSI-ReportConfigs that include detailed CSI report settings triggered via DCI and are applied to each CSI-ReportConfig.

[0541] According to one embodiment, when a terminal uses a method of selecting some or all of the detailed CSI report configurations in a CSI-ReportConfig for network energy saving by using a CSI request field in a DCI and additional bits or new fields in the CSI request field, the terminal may dynamically receive some or all of the multiple detailed CSI report configurations in the configured CSI-ReportConfig from the base station. Therefore, the terminal and the base station may use the fastest method in terms of signaling and consider low latency, but this may entail overhead of the DCI, and if the length of the additional bits or new fields in the CSI request field is restricted in consideration of the DCI overhead, some of the flexibility of the L1 signaling may be lost.

[0542] [Method 2-4]

[0543] According to one embodiment, a terminal may be configured to associate one or more CSI-AssociatedReportConfigInfo for each code point of a CSI request field in DCI. The terminal may include one CSI-ReportConfig in one CSI-AssociatedReportConfigInfo through upper layer signaling. The terminal may configure multiple detailed CSI reports in one CSI-ReportConfig. The terminal may be activated to report CSI reports for some or all of the multiple detailed CSI report configurations in one CSI-ReportConfig by receiving a MAC-CE from a base station.

[0544] For example, if there are five detailed CSI report configurations corresponding to antenna ports 2, 4, 8, 16, and 32 in one CSI-ReportConfig, the UE can receive activation information on which of the five detailed CSI report configurations to perform CSI reports for by receiving MAC-CE from the base station. For example, if three detailed CSI report configurations corresponding to antenna ports 2, 8, and 32 are activated through MAC-CE, and the UE is instructed through DCI the code point of the CSI request including the CSI-ReportConfig, the UE can report CSI reports for the three activated detailed CSI report configurations to the base station.

[0545] According to one embodiment, the terminal may activate CSI report reporting for some or all of the detailed CSI report settings through MAC-CE transmitted by the base station based on whether network energy saving is needed at the base station and the CSI calculation burden at the terminal, and may report the CSI report.

[0546] Although there may be a delay between the terminal receiving the MAC-CE from the base station and its activation, the situation in which the base station must change the amount of information requested from the terminal for network energy saving is unlikely to change dynamically as with DCI-based L1 (layer 1) signaling. Therefore, a method of selecting some or all of the detailed CSI report settings through MAC-CE can have appropriate signaling flexibility while not causing unnecessary overhead of the CSI-ReportConfig setting information as in [Method 2-1] above.

[0547] However, if it is possible to select only some or all of the detailed CSI report settings for one CSI-ReportConfig through one MAC-CE signaling, multiple MAC-CEs may be required when changes are needed for multiple CSI-ReportConfigs, and for this purpose, it may be possible to change the detailed CSI report settings of up to N CSI-ReportConfigs through one MAC-CE. In this case, N may be set by upper layer signaling or may be fixedly defined in the specification and may be related to the maximum length of the MAC-CE.

[0548] According to one embodiment, the terminal may report whether it supports at least one of [Method 2-1] to [Method 2-4] to the base station through terminal capability signaling. The terminal may be configured with at least one of [Method 2-1] to [Method 2-4] by the base station through upper layer signaling, activated through MAC-CE, instructed through L1 signaling, or notified through a combination of at least one of upper layer signaling, MAC-CE, and L1 signaling. Alternatively, the terminal may follow a method fixedly supported by the standard.

[0549] According to one embodiment, the terminal and the base station can use a combination of at least one of the above [Method 2-1] to [Method 2-4] and at least one of the above [Method 1-1-1] to [Method 1-1-4]. For example, the terminal can perform CSI reports to the base station only for a specific number of detailed CSI report settings among multiple detailed CSI report settings within a specific CSI-ReportConfig from the base station, as in the above [Method 1-1-2]. For example, if there are four detailed CSI report settings within a specific CSI-ReportConfig and the base station notifies the terminal to perform CSI reports for two of them, the terminal can arbitrarily select two detailed CSI report settings to be actually reported among the four. For this purpose, as a method of notifying the terminal from the base station, [Method 2-1] based on upper layer signaling, [Method 2-2] setting another upper layer signaling in CSI-AssociatedReportConfigInfo, [Method 2-3] indicating through a new field in DCI or an additional bit of the CSI request field, etc. may be considered.

[0550] For example, the terminal may additionally receive from the base station an upper layer signaling within CSI-AssociatedReportConfigInfo, which means to perform CSI reports for a specific number of detailed CSI report settings within a specific CSI-ReportConfig, as in [Method 2-2] above.

[0551] According to one embodiment, a method for requesting PUSCH-based semi-persistent channel state information for network energy saving is described.

[0552] As one embodiment of the present disclosure, a method for requesting PUSCH-based semi-persistent channel state information for network energy saving at a terminal and a base station is described. This embodiment can be operated in combination with other embodiments within the present disclosure.

[0553] According to one embodiment, the terminal may report to the base station as the terminal capability the maximum number of detailed CSI report configurations that the terminal may configure in the CSI-ReportConfig, the maximum number of detailed CSI report configurations that the terminal may actually report in the CSI-ReportConfig, and / or the maximum number of detailed CSI report configuration lists that the terminal may configure in the CSI-ReportConfig. The terminal capability may be limited to PUSCH-based semi-persistent CSI reports, or may be a value that considers all of aperiodic, semi-persistent, and periodic CSI reports.

[0554] According to one embodiment, a terminal may receive a PUSCH-based semi-persistent CSI report request from a base station through a CSI request field in DCI. If the terminal configures one or more detailed CSI report configurations in CSI-ReportConfig for network energy saving, the terminal may receive a PUSCH-based semi-persistent CSI report request based on a CSI-ReportConfig configuration including the detailed CSI report configurations from the base station by using at least one or more combinations of the following methods.

[0555] [Method 3-1]

[0556] According to one embodiment, the terminal may be configured to associate one CSI-SemiPersistentOnPUSCH-TriggerState for each code point of the CSI request field in the DCI, and the terminal may expect one CSI-ReportConfigId to be included in one CSI-SemiPersistentOnPUSCH-TriggerState. Accordingly, one CSI-ReportConfig may be indicated through one code point of the CSI request field. The terminal may receive multiple detailed CSI report configurations from the base station through upper layer signaling in one CSI-ReportConfig.

[0557] According to one embodiment, under the upper layer signaling configuration, if a terminal is instructed by a base station through a CSI request field in DCI for a specific codepoint, the terminal may report a PUSCH-based semi-persistent CSI report to the base station for all multiple detailed CSI report configurations in the CSI-ReportConfig connected to the CSI-SemiPersistentOnPUSCH-TriggerState connected to the codepoint. That is, the terminal must report for all multiple detailed CSI report configurations that the base station configures in the CSI-ReportConfig, and the base station may adjust the CSI calculation burden of the terminal by adjusting the number of detailed CSI report configurations configured in the CSI-ReportConfig. However, a disadvantage may be that the adjustment by the base station cannot be helped but be quasi-static.

[0558] According to one embodiment, the base station may set only the number of detailed CSI report settings among all configuration information of two CSI-ReportConfigs having two different CSI-ReportConfigIds, while keeping the remaining configuration information the same, and configure them to the terminal through upper layer signaling. Such two CSI-ReportConfigs are each linked to different CSI-SemiPersistentOnPUSCH-TriggerStates, and the different CSI-SemiPersistentOnPUSCH-TriggerStates are linked to different codepoints of CSI requests, and thus may be triggered from the base station through different DCIs. For example, the terminal may be configured with a first CSI-ReportConfig and a second CSI-ReportConfig, and within the first CSI-ReportConfig, a total of four antenna ports, namely 2, 4, 8, and 16, may be configured as detailed CSI report settings. In the second CSI-ReportConfig, two types of detailed CSI report settings, 8 and 16 antenna ports, can be configured, and the remaining configuration information of the first CSI-ReportConfig and the second CSI-ReportConfig can be assumed to be the same. The first CSI-ReportConfig is connected to the first CSI-SemiPersistentOnPUSCH-TriggerState, the second CSI-ReportConfig is connected to the second CSI-SemiPersistentOnPUSCH-TriggerState, and the first CSI-SemiPersistentOnPUSCH-TriggerState and the second CSI-SemiPersistentOnPUSCH-TriggerState can be connected to different codepoints.

[0559] At this time, the base station can determine which of the detailed CSI report configurations of the corresponding CSI-ReportConfig to receive a CSI report for from the terminal and which detailed CSI report configuration to have the terminal calculate and report by transmitting a specific code point of the CSI request field to the terminal. This instruction may have a trade-off between the CSI calculation overhead of the terminal and the reception of information from the terminal for network energy saving at the base station. However, receiving different CSI-ReportConfigs that contain the same configuration information except for the detailed CSI report configuration may be an inefficient upper layer signaling configuration method, considering the terminal's limitation that it can receive up to 48 different CSI-ReportConfig configurations and that the maximum number of CSI-SemiPersistentOnPUSCH-TriggerStates is 64 and only one CSI-ReportConfig can be associated with one CSI-SemiPersistentOnPUSCH-TriggerState.

[0560] [Method 3-2]

[0561] According to one embodiment, the terminal may be configured to associate one CSI-SemiPersistentOnPUSCH-TriggerState for each code point of the CSI request field in the DCI, and the terminal may expect one CSI-ReportConfigId to be included in one CSI-SemiPersistentOnPUSCH-TriggerState. Accordingly, one CSI-ReportConfig may be indicated through one code point of the CSI request field. The terminal may receive multiple detailed CSI report configurations configured in one CSI-ReportConfig from the base station through upper layer signaling.

[0562] In one embodiment, under the higher layer signaling configuration, the terminal may expect additional higher layer signaling to be configured within CSI-SemiPersistentOnPUSCH-TriggerState associated with each code point of the CSI request field within the DCI. The additional higher layer signaling may be a signaling for selecting some or all of a plurality of detailed CSI report configurations configured within CSI-ReportConfig associated with CSI-SemiPersistentOnPUSCH-TriggerState.

[0563] - For example, the terminal may assume that the first CSI-SemiPersistentOnPUSCH-TriggerState is connected to the first code point of the CSI request field in the DCI, and may assume that the second CSI-SemiPersistentOnPUSCH-TriggerState is connected to the second code point. The same CSI-ReportConfig is set for both the first CSI-SemiPersistentOnPUSCH-TriggerState and the second CSI-SemiPersistentOnPUSCH-TriggerState, and the CSI-ReportConfig may include four detailed CSI report settings. In this case, the terminal may expect that the first CSI-SemiPersistentOnPUSCH-TriggerState connected to the first code point of the CSI request field includes configuration information for selecting some of the four detailed CSI report settings included in the CSI-ReportConfig (e.g., the first and second detailed CSI report settings). Additionally, the terminal may expect that the second CSI-SemiPersistentOnPUSCH-TriggerState associated with the second code point of the CSI request field includes configuration information for selecting all of the four detailed CSI report settings included in the CSI-ReportConfig (e.g., the first CSI report setting to the fourth detailed CSI report setting).

[0564] - For another example, the terminal may assume that the first CSI-SemiPersistentOnPUSCH-TriggerState is connected to the first codepoint of the CSI request field in the DCI, and may assume that the second CSI-SemiPersistentOnPUSCH-TriggerState is connected to the second codepoint. The same CSI-ReportConfig is set for both the first CSI-SemiPersistentOnPUSCH-TriggerState and the second CSI-SemiPersistentOnPUSCH-TriggerState, and the CSI-ReportConfig may include two detailed CSI report configuration lists. Each detailed CSI report configuration list may be referenced as a list including one or more detailed CSI report configurations. For example, if the CSI-ReportConfig includes four detailed CSI report configurations, the first detailed CSI report configuration list may include the first detailed CSI report configuration and the second detailed CSI report configuration. The second detailed CSI report configuration list may include a third detailed CSI report configuration and a fourth detailed CSI report configuration. At this time, the terminal may expect or identify that configuration information for selecting a first list (e.g., including the first and second detailed CSI report configurations) among the two detailed CSI report configuration lists included in CSI-ReportConfig is included in the first CSI-SemiPersistentOnPUSCH-TriggerState linked to the first code point of the CSI request field.Additionally, the terminal may expect or identify that the second CSI-SemiPersistentOnPUSCH-TriggerState associated with the second code point of the CSI request field includes configuration information for selecting a second list (e.g., including the third and fourth detailed CSI report configurations) among the two detailed CSI report configuration lists included in the CSI-ReportConfig.

[0565] According to one embodiment, by introducing upper layer signaling, the terminal and the base station can configure all of the multiple detailed CSI report configurations applicable to the corresponding CSI-ReportConfig within each CSI-ReportConfig, and then select some or all of the multiple detailed CSI report configurations using additional configuration information that can be included within the CSI-SemiPersistentOnPUSCH-TriggerState linked to the CSI request codepoint. In this way, by using different CSI-SemiPersistentOnPUSCH-TriggerStates linked to the same CSI-ReportConfig, the base station can select different detailed CSI report configurations within the same CSI-ReportConfig for the terminal, thereby controlling the CSI calculation overhead at the terminal and the amount of information for network energy saving.

[0566] [Method 3-3]

[0567] According to one embodiment, the terminal may be configured to associate one CSI-SemiPersistentOnPUSCH-TriggerState for each code point of the CSI request field in the DCI, and may expect or identify that one CSI-ReportConfigId is included within one CSI-SemiPersistentOnPUSCH-TriggerState. Accordingly, one CSI-ReportConfig may be indicated through one code point of the CSI request field. The terminal may receive multiple detailed CSI report configurations within one CSI-ReportConfig from the base station through upper layer signaling.

[0568] According to one embodiment, under the upper layer signaling configuration, the terminal may be instructed to select some or all of the detailed CSI report configurations configured in the CSI-ReportConfig linked to the CSI-SemiPersistentOnPUSCH-TriggerState linked to the code point indicated by the CSI request field in the DCI, based on defining a new field in the same DCI or additional bits in the CSI request field. For example, the new field or the additional bits in the CSI request field may be expressed in the form of a bitmap according to the maximum number of detailed CSI report configurations, or may be in a manner indicating a specific combination of all detailed CSI report configurations. It is also possible that a new field may be defined based on a different method.

[0569] - In the case of bitmap format, if the maximum number of detailed CSI report settings that the terminal can set in CSI-ReportConfig is N, it can be represented by N bitmaps. In the case of representing in bitmap format, even if the maximum number M of detailed CSI report settings that the terminal can actually report in CSI-ReportConfig is smaller than the maximum number N of detailed CSI report settings that the terminal can set in CSI-ReportConfig, the length of the field in DCI must be N, not M, so overhead may increase. For example, if N is 4 and M is 2, the terminal can consider or identify 4 bits as a new field. At this time, even if the maximum number of detailed CSI report settings that the terminal can set in CSI-ReportConfig is N, if the number of detailed CSI report settings set in a specific CSI-ReportConfig is less than N (e.g., N'), the terminal can be instructed by the base station which detailed CSI report settings to report based on only N' bits from the MSB (or LSB) of the new field. For example, if N is 4 and N', which is the number of detailed CSI report settings set in a specific CSI-ReportConfig, is 3, the terminal can be instructed by the base station which detailed CSI report settings to report based on only 3 bits from the MSB (or LSB) of the new field consisting of 4 bits. In addition, the terminal can expect or identify that the number of bits having a value of 1 in the new field is less than or equal to M.

[0570] - In the case of a method of indicating a specific combination, if the maximum number of detailed CSI report settings that the terminal can set in CSI-ReportConfig is N, and the maximum number of detailed CSI report settings that the terminal can actually report in CSI-ReportConfig is M, the terminal can consider a length of bits that can express the number of cases in which M is selected out of N as the length of the new field. For example, if N is 4 and M is 2, the terminal can consider or identify 3 bits that can express a total of 6 cases as the length of the new field. At this time, even if the maximum number of detailed CSI report settings that the terminal can set, N, is 4, if the number of detailed CSI report settings set in a specific CSI-ReportConfig is less than N (for example, N'), the terminal and the base station can assume that they will use only as many code points as the number of cases in which M is selected out of N' from the first code point of the new field, and can treat the remaining code points as reserved. For example, if N is 4, M is 2, and N', the number of detailed CSI report settings set in a specific CSI-ReportConfig, is 3, the terminal and base station can assume that they will use 3 code points, which is the number of cases in which M (=2) out of N' (=3) code points are selected from the first code point, out of a total of 8 code points of the new field that can be expressed with 3 bits, and the remaining 5 code points can be processed as reserved.

[0571] - The terminal and the base station can expect to include at most E detailed CSI report configuration lists in the CSI-ReportConfig, and can perform a CSI report for the corresponding CSI-ReportConfig by selecting one of the E' (<=E) lists through the CSI request field in the DCI or through a new field. Each detailed CSI report configuration list can be referenced as a list including one or more detailed CSI report configurations. For example, if the terminal includes a total of three (=N') detailed CSI report configurations in a specific CSI-ReportConfig, and includes a total of two (=E') detailed CSI report configuration lists, the first detailed CSI report configuration list can include the first detailed CSI report configuration, the second detailed CSI report configuration, and / or the third detailed CSI report configuration. The second detailed CSI report configuration list can include the second and third detailed CSI report configurations. At this time, the terminal can be instructed by the base station to select one of two detailed CSI report configuration lists through an additional bit of the CSI request field in the DCI or a new field. The terminal can report a CSI report corresponding to the detailed CSI report configurations included in the list to the base station. The bit length of the additional bit or new field in the CSI request field may be related to the value of E, and more specifically, may be the number of bits capable of expressing E (for example, it may be expressed as ceil(log2(E)), where ceil(.) is a rounding function and log2(.) is a logarithmic function with a base of 2).

[0572] According to one embodiment, the terminal may report to the base station as the terminal capability for N (e.g., the maximum number of detailed CSI report configurations that the terminal can configure in CSI-ReportConfig), M (e.g., the maximum number of detailed CSI report configurations that the terminal can actually report in CSI-ReportConfig), and / or E (e.g., the maximum number of detailed CSI report configuration lists that the terminal can configure in CSI-ReportConfig).

[0573] In one embodiment, when a terminal uses a method of selecting some or all of the detailed CSI report settings in a CSI-ReportConfig for network energy saving by using a CSI request field in a DCI and additional bits or new fields in the CSI request field, the terminal may expect or identify that there is only one CSI-ReportConfig that includes the detailed CSI report settings among the aperiodic CSI reports triggered through the DCI.

[0574] If there are two or more CSI-ReportConfigs including detailed CSI report settings among the aperiodic CSI reports triggered through DCI, the terminal can expect or discern that additional bits or new fields in the defined CSI request field are commonly applied to all of the multiple CSI-ReportConfigs including detailed CSI report settings triggered through DCI. If there are two or more CSI-ReportConfigs including detailed CSI report settings among the aperiodic CSI reports triggered through the DCI, the terminal can expect or discern that additional bits or new fields in the defined CSI request field are defined as many as the number of the multiple CSI-ReportConfigs including detailed CSI report settings triggered through the DCI and are applied to each CSI-ReportConfig.

[0575] According to one embodiment, when a terminal uses a method of selecting some or all of the detailed CSI report configurations in a CSI-ReportConfig for network energy saving by using a CSI request field in DCI and additional bits or new fields in the CSI request field, the terminal may dynamically receive some or all of the multiple detailed CSI report configurations in the configured CSI-ReportConfig from the base station. Therefore, the terminal and the base station may use the fastest method in terms of signaling and consider low latency, but this may entail overhead of the DCI, and if the length of the additional bits or new fields in the CSI request field is restricted in consideration of the DCI overhead, the terminal and the base station may lose some of the flexibility of the L1 signaling.

[0576] [Method 3-4]

[0577] According to one embodiment, the terminal may be configured to associate one CSI-SemiPersistentOnPUSCH-TriggerState for each code point of the CSI request field in the DCI, and may expect or identify that one CSI-ReportConfigId is included within one CSI-SemiPersistentOnPUSCH-TriggerState. Accordingly, one CSI-ReportConfig may be indicated through one code point of the CSI request field. The terminal may receive multiple detailed CSI report configurations within one CSI-ReportConfig from the base station through upper layer signaling.

[0578] According to one embodiment, the terminal may be activated to report CSI reports for some or all of a plurality of detailed CSI report configurations within a single CSI-ReportConfig by receiving a MAC-CE from the base station. For example, if there are five detailed CSI report configurations corresponding to antenna ports 2, 4, 8, 16, and 32 within a single CSI-ReportConfig, the terminal may receive activation information regarding which of the five detailed CSI report configurations will perform CSI reports by receiving a MAC-CE from the base station. For example, if three detailed CSI report configurations corresponding to antenna ports 2, 8, and 32 are activated via the MAC-CE, and the terminal is instructed via DCI the codepoint of the CSI request including the corresponding CSI-ReportConfig, the terminal may report CSI reports for the three activated detailed CSI report configurations to the base station.

[0579] According to one embodiment, the terminal can activate CSI report reporting for some or all of the detailed CSI report configurations through MAC-CE transmitted by the base station based on whether the base station needs network energy saving and the CSI calculation burden of the terminal, and report the CSI report. Although there may be a delay between the terminal receiving the MAC-CE from the base station and its activation, the situation in which the base station needs to change the amount of information requested from the terminal for network energy saving is likely not to change dynamically like DCI-based L1 signaling. Therefore, the method of selecting some or all of the detailed CSI report configurations through MAC-CE can have appropriate signaling flexibility while not causing unnecessary overhead of the CSI-ReportConfig configuration information as in [Method 3-1].

[0580] However, if only some or all of the detailed CSI report settings for one CSI-ReportConfig can be selected through one MAC-CE signaling, multiple MAC-CEs may be required when changes to multiple CSI-ReportConfigs are required, and for this purpose, it may be possible to change the detailed CSI report settings of up to N CSI-ReportConfigs through one MAC-CE. In this case, N may be set by upper layer signaling or may be fixedly defined in the specification and may be related to the maximum length of the MAC-CE.

[0581] According to one embodiment, the terminal may report to the base station whether it supports at least one combination of [Method 3-1] to [Method 3-4] through terminal capability signaling. The terminal may be configured with at least one combination of [Method 3-1] to [Method 3-4] by the base station through upper layer signaling, activated through MAC-CE, instructed through L1 signaling, or notified through at least one combination of upper layer signaling, MAC-CE, and L1 signaling. Alternatively, the terminal may follow a method fixedly supported by the standard.

[0582] According to one embodiment, the terminal and the base station can use a combination of at least one of the above [Method 3-1] to [Method 3-4] and at least one of the above [Method 1-1-1] to [Method 1-1-4]. For example, the terminal can transmit a CSI report to the base station only for a specific number of detailed CSI report settings among a plurality of detailed CSI report settings within a specific CSI-ReportConfig from the base station, as in the above [Method 1-1-2]. For example, if there are four detailed CSI report settings within a specific CSI-ReportConfig and the base station notifies the terminal to perform CSI reports for two of them, the terminal can arbitrarily select two detailed CSI report settings to be actually reported among the four. For this, as a method of notifying the terminal from the base station, [Method 3-1] based on upper layer signaling, [Method 3-2] setting another upper layer signaling in CSI-SemiPersistentOnPUSCH-TriggerState, [Method 3-3] indicating through a new field in DCI or an additional bit of the CSI request field, etc. can be considered. For example, the terminal can additionally receive upper layer signaling from the base station in CSI-SemiPersistentOnPUSCH-TriggerState, which means to perform CSI reports for a specific number of all detailed CSI report settings in a specific CSI-ReportConfig, as in [Method 3-2] above.

[0583] According to one embodiment, the terminal may receive p0alpha within semiPersistentOnPUSCH within CSI-ReportConfig, which is an upper layer signaling, from the base station, and the configured p0alpha (e.g., P0-PUSCH-AlphaSetId) may mean p0 and alpha values ​​used for power control of PUSCH transmitted from the terminal, including a semi-persistent CSI report.

[0584] According to one embodiment, when a terminal receives the unified TCI state set for a specific serving cell from a base station through upper layer signaling, i.e., when the upper layer signaling unifiedTCI-StateType is set for the corresponding serving cell, the terminal may use the p0, alpha, and closedLoopIndex values ​​that can be set through p0AlphaSetforPUSCH-r17 included in the upper layer signaling ul-powerControl-r17 included in the integrated TCI state (e.g., joint TCI (TCI-State) or separate UL TCI (TCI-UL-State)) indicated to the terminal when controlling power of a PUSCH transmitted from the terminal within the same serving cell.

[0585] Accordingly, when the terminal receives the integrated TCI state set for a specific serving cell through upper layer signaling from the base station, i.e., when the upper layer signaling unifiedTCI-StateType is set for the serving cell, at least one of the following combinations may be considered as a method for processing p0alpha in semiPersistentOnPUSCH in CSI-ReportConfig.

[0586] - Use P0alpha (even if it is UTCI)

[0587] ■ Regardless of whether the upper layer signaling unifiedTCI-StateType is set or not for the serving cell, if reportConfigType in CSI-ReportConfig is set to semiPersistentOnPUSCH, the UE can always receive p0alpha from the base station in semiPersistentOnPUSCH. If the upper layer signaling unifiedTCI-StateType is not set for the serving cell, the UE can use p0alpha as a power control parameter when transmitting a PUSCH including a semi-persistent CSI report. Additionally, the terminal may not use the p0, alpha, and closedLoopIndex values ​​that can be set through p0AlphaSetforPUSCH-r17 included in the upper layer signaling ul-powerControl-r17 included in the integrated TCI state indicated to the terminal (e.g., joint TCI (TCI-State) or separate UL TCI (TCI-UL-State)), even when the upper layer signaling unifiedTCI-StateType is set to the serving cell, and may use p0alpha as a power control parameter used when transmitting a PUSCH including a semi-persistent CSI report.

[0588] - Ignore P0alpha (modify description, set unconditionally)

[0589] ■ Regardless of whether the upper layer signaling unifiedTCI-StateType is set or not for the serving cell, if reportConfigType in CSI-ReportConfig is set to semiPersistentOnPUSCH, the UE can always receive p0alpha from the base station in semiPersistentOnPUSCH. If the upper layer signaling unifiedTCI-StateType is set for the serving cell, the UE may ignore p0alpha and instead use the p0, alpha, and closedLoopIndex values ​​that can be set via p0AlphaSetforPUSCH-r17 included in the upper layer signaling ul-powerControl-r17 included in the integrated TCI state indicated to the UE (e.g., joint TCI (TCI-State) or separate UL TCI (TCI-UL-State)) as power control parameters when transmitting a PUSCH including a semi-persistent CSI report. The terminal may use p0alpha as a power control parameter used when transmitting a PUSCH containing a semi-persistent CSI report, if the upper layer signaling unifiedTCI-StateType is not set for the serving cell.

[0590] - Changed P0alpha setting conditions (Cond NoUnifiedTCI, OPTIONAL set)

[0591] ■ The terminal may consider the setting condition of the above p0alpha depending on whether the unified TCI state is set. This condition may be named Cond NoUnifiedTCI (OPTIONAL, Need R), and the terminal may selectively set the above p0alpha to (OPTIONAL, Need R) according to a specific condition. If the upper layer signaling unifiedTCI-StateType is set to the corresponding serving cell and / or if the reportConfigType in CSI-ReportConfig is set to semiPersistentOnPUSCH, the terminal may not set p0alpha in semiPersistentOnPUSCH from the base station. At this time, the terminal can use the values ​​of p0, alpha, and closedLoopIndex, which can be set via p0AlphaSetforPUSCH-r17 included in ul-powerControl-r17, which is an upper layer signaling included in the integrated TCI state indicated to the terminal (e.g., joint TCI (TCI-State) or separate UL TCI (TCI-UL-State)), as power control parameters used when transmitting PUSCH including semi-persistent CSI report. If the upper layer signaling unifiedTCI-StateType is not set for the corresponding serving cell and / or if reportConfigType in CSI-ReportConfig is set to semiPersistentOnPUSCH, the terminal can expect to receive the setting of p0alpha, and can use p0alpha as a power control parameter used when transmitting PUSCH including semi-persistent CSI report.

[0592] According to one embodiment, a method for requesting PUCCH-based semi-persistent channel state information for network energy saving is described.

[0593] As one embodiment of the present disclosure, a method for requesting semi-persistent channel state information based on PUCCH for network energy saving at a terminal and a base station is described. This embodiment can be operated in combination with other embodiments within the present disclosure.

[0594] According to one embodiment, the terminal may report to the base station as the terminal capability the maximum number of detailed CSI report configurations that the terminal can configure in the CSI-ReportConfig, the maximum number of detailed CSI report configurations that the terminal can actually report in the CSI-ReportConfig, and / or the maximum number of detailed CSI report configuration lists that the terminal can configure in the CSI-ReportConfig. The terminal capability may be limited to PUCCH-based semi-persistent CSI reports, or may be a value that takes into account all of aperiodic, semi-persistent, and periodic CSI reports.

[0595] A terminal can receive a PUCCH-based semi-persistent CSI report request from a base station through MAC-CE. For a PUCCH-based semi-persistent CSI report, the terminal can have the reportConfigType in CSI-ReportConfig, which is an upper layer signaling, set to semiPersistentOnPUCCH. If the terminal includes one or more detailed CSI report configurations in CSI-ReportConfig as in the above embodiment for network energy saving, the terminal can receive a PUCCH-based semi-persistent CSI report request based on a CSI-ReportConfig configuration including the detailed CSI report configurations by using a combination of at least one of the following methods from the base station.

[0596] [Method 4-1]

[0597] According to one embodiment, a terminal may perform PUCCH-based semi-persistent CSI report reporting by receiving the MAC-CE of FIG. 12 from a base station. That is, the terminal must perform CSI report reporting for all CSI-ReportConfigs activated through the MAC-CE, and the terminal may also report to the base station all detailed CSI report settings configured within each CSI-ReportConfig. That is, the terminal must report for all multiple detailed CSI report settings that the base station configures within the CSI-ReportConfig, and the base station may adjust the CSI calculation burden of the terminal by adjusting the number of detailed CSI report settings configured within the CSI-ReportConfig. However, a disadvantage may be that the adjustment by the base station cannot be helped but be quasi-static.

[0598] According to one embodiment, a terminal can receive up to four PUCCH-based semi-persistent CSI report activations within a single bandwidth segment using a CSI-ReportConfig without detailed CSI report settings. When a terminal receives PUCCH-based semi-persistent CSI report activations within a single bandwidth segment using a CSI-ReportConfig with detailed CSI report settings, the terminal can report, as a terminal capability, the maximum number of PUCCH-based semi-persistent CSI report activations that can be received.

[0599] According to one embodiment, the base station may configure two CSI-ReportConfigs having two different CSI-ReportConfigIds, with only the number of detailed CSI report settings being different among all configuration information, and the remaining configuration information being the same (in this case, reportSlotConfig and / or pucch-CSI-ResourceList may be different), to the terminal through upper layer signaling. Such two CSI-ReportConfigs may be delivered to the terminal through the same or different MAC-CEs. For example, the terminal may be configured with a first CSI-ReportConfig and a second CSI-ReportConfig, and in the first CSI-ReportConfig, a total of four antenna ports, namely 2, 4, 8, and 16, may be configured as detailed CSI report settings. In the second CSI-ReportConfig, a total of two antenna ports, namely 8 and 16, may be configured as detailed CSI report settings. The remaining configuration information of the first CSI-ReportConfig and the second CSI-ReportConfig can be assumed to be the same. The first CSI-ReportConfig and the second CSI-ReportConfig can be indicated through the same or different MAC-CEs. In this case, the base station can determine which of the detailed CSI report settings of the corresponding CSI-ReportConfig will receive a CSI report from the terminal and / or which detailed CSI report setting will be calculated and reported by the terminal by adjusting the BWP ID field and CSI-ReportConfigId through the same or different MAC-CEs.

[0600] These instructions may present a trade-off between the CSI calculation overhead at the terminal and the network energy savings at the base station by receiving information from the terminal. However, configuring different CSI-ReportConfigs containing identical configuration information except for the detailed CSI report configuration may be an inefficient upper-layer signaling configuration method, considering the terminal's limitation of being able to receive up to 48 different CSI-ReportConfig configurations.

[0601] [Method 4-2]

[0602] According to one embodiment, a terminal can perform PUCCH-based semi-persistent CSI report reporting by receiving a MAC-CE from a base station, and the MAC-CE can have some parts identical to the structure of FIG. 12, or can have a different form. If multiple detailed CSI report settings are included in the CSI-ReportConfig indicated by the MAC-CE from the base station, the terminal can be notified by the base station through a specific field in the MAC-CE which detailed CSI report setting among the multiple detailed CSI report settings in the indicated CSI-ReportConfig will be used to perform PUCCH-based semi-persistent CSI report reporting.

[0603] For example, the terminal may define a MAC-CE including a total of four fields for each Si, in addition to the two Octets as in FIG. 12, which indicate which of the multiple detailed CSI report settings in the CSI-ReportConfig to use based on the maximum number of detailed CSI report settings that the terminal can set in the CSI-ReportConfig.

[0604] If the maximum number of detailed CSI report settings that can be set in CSI-ReportConfig is less than or equal to 4, the terminal may include 2 more octets in addition to the 2 octets in the MAC-CE of FIG. 12, and may configure each field of 4 bits to correspond to each Si field. The terminal may be instructed to perform PUCCH-based semi-persistent CSI reporting by considering which of all detailed CSI report settings included in CSI-ReportConfig corresponding to each Si through each 4-bit field. For example, if the maximum number of detailed CSI report settings that can be set in CSI-ReportConfig is 8, the terminal can include 4 octets in addition to 2 octets in the MAC-CE of FIG. 12, and the terminal can correspond a field composed of N (<=8) bits from the right bit of each additional octet to each Si field, and the terminal can be instructed to perform PUCCH-based semi-persistent CSI reporting based on which detailed CSI report setting among all detailed CSI report settings included in CSI-ReportConfig corresponding to each Si through each N (<=8) bit field.

[0605] FIG. 14 is a diagram illustrating a MAC-CE structure that indicates activation or deactivation of a PUCCH-based semi-persistent CSI report considering detailed CSI report settings according to one embodiment.

[0606] Referring to FIG. 14, a MAC-CE indicating activation or deactivation of a semi-persistent CSI report transmitted on a PUCCH based on a detailed CSI report configuration according to an embodiment may be identified or determined through a MAC subheader including an LCID or an extended LCID (eLCID). The MAC-CE indicating activation or deactivation of a CSI report may have a fixed length of 32 or 48 bits. The description of each field of the MAC-CE may be as follows.

[0607] - Serving Cell ID (1400, 1450): This field can indicate the ID of the serving cell to which the corresponding MAC-CE is applied, and can be 5 bits long.

[0608] - BWP ID (1405, 1455): This field can indicate the uplink bandwidth portion to which the corresponding MAC-CE is applied, can mean a code point within the bandwidth portion indicator field within the DCI, and can be 2 bits long.

[0609] - S i (1410, 1460): This field can indicate the enable or disable status of the semi-persistent CSI report setting in the upper layer signaling csi-ReportConfigToAddModList.

[0610] ■ The S0 field may include a PUCCH resource that is connected to or included in the bandwidth portion indicated through the BWP ID field, and the S0 field may mean a CSI report configuration in which the type is set to semiPersistentOnPUCCH and has the lowest ID (e.g., CSI-ReportConfigId) among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList.

[0611] ■ The S1 field may include a PUCCH resource that is connected to or included in the bandwidth portion indicated by the BWP ID field, and the S1 field may mean a CSI report configuration in which the type is set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList and has the second lowest ID (e.g., CSI-ReportConfigId).

[0612] ■ The S2 and S3 fields can also be considered in this way.

[0613] ■ The PUCCH resource connected to or included in the above specific bandwidth portion may be PUCCH format 2, 3, or 4, and may be confirmed or identified using the ID of the PUCCH resource set in PUCCH-Config, which is upper layer signaling.

[0614] ■ If the type is set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList and the number of semi-persistent CSI report configurations that are connected to the bandwidth part indicated by the BWP ID field or include PUCCH resources included in the bandwidth part is less than i+1, the UE may ignore the Si field. For example, if the number of semi-persistent CSI report configurations is 2, the UE may interpret the S0 field and the S1 field, but may ignore the S2 field and the S3 field.

[0615] ■ If the Si field is set to 1, the terminal can understand that the corresponding semi-persistent CSI report setting should be activated.

[0616] ■ If the Si field is set to 0, the terminal can understand that the corresponding semi-persistent CSI report setting should be disabled.

[0617] - S s,i (1415, 1465): The Ss,i field may indicate activation or deactivation of any of multiple detailed CSI report settings included in CSI-ReportConfig, which indicates a semi-persistent CSI report setting in csi-ReportConfigToAddModList, which is an upper layer signaling. The length of the field may be set equal to the maximum number of detailed CSI report settings that can be set in CSI-ReportConfig in the case of bitmap form, and in the case of other forms, the length of the field may be shorter or longer than the field length in the bitmap form.

[0618] ■ For example, if the maximum number of detailed CSI report settings that can be configured in CSI-ReportConfig is 4, the terminal can configure the length of this field as one field of 4 bits each to correspond to each Si field (1415). The terminal can be instructed which detailed CSI report setting among all detailed CSI report settings included in CSI-ReportConfig corresponding to each Si should be considered for performing PUCCH-based semi-persistent CSI reporting through each 4-bit field. The field is in the form of a bitmap and can instruct the terminal which of 4 or fewer detailed CSI report settings should be activated or deactivated. For example, if the terminal receives 4 detailed CSI report settings from the base station in CSI-ReportConfig corresponding to the S0 field in MAC-CE, if the base station wants to activate or deactivate the 1st detailed CSI report and the 3rd detailed CSI report settings among the 4 detailed CSI report settings, the terminal can receive the S0 field in MAC-CE from the base station. s,0 (1415) Through the field, the terminal can expect the first and third bits from the MSB (or LSB) to be 1, and the terminal can expect the second and fourth bits to be 0.

[0619] ◆ If S i (1410) If the CSI-ReportConfig corresponding to the field does not contain detailed CSI report settings, the terminal shall s,i (1415) Fields can be ignored.

[0620] ■ As another example, if the maximum number of detailed CSI report settings that can be set in CSI-ReportConfig is 8, the terminal can correspond to each Si field by configuring the length of the field as one field of 8 bits each (1465), and the terminal can correspond to each S field through each 8-bit field. i The terminal may be instructed to perform PUCCH-based semi-persistent CSI reporting by considering which detailed CSI report settings among all detailed CSI report settings included in the CSI-ReportConfig corresponding to the S0 field in the MAC-CE. The field is in the form of a bitmap and may instruct the terminal which of 8 or fewer detailed CSI report settings are to be activated or deactivated. For example, if the terminal receives 8 detailed CSI report settings from the base station in the CSI-ReportConfig corresponding to the S0 field in the corresponding MAC-CE, and if the base station wants to activate or deactivate the first detailed CSI report setting and the third detailed CSI report setting among the 8 detailed CSI report settings, the terminal may instruct the base station to activate or deactivate the first detailed CSI report setting and the third detailed CSI report setting among the 8 detailed CSI report settings. s,0 (1415) Through the field, the terminal can expect the first and third bits from the MSB (or LSB) to be 1, and the terminal can expect the second and fourth bits to be 0.

[0621] ◆ If S i (1460) If the CSI-ReportConfig corresponding to the field does not contain detailed CSI report settings, the terminal shall s,i (1465) Fields can be ignored.

[0622] ■ As another example, in addition to the 4-bit or 8-bit bitmap, the terminal may assume that the MAC-CE includes a field indicating a specific combination of detailed CSI report settings as described above, and the terminal may assume that the MAC-CE includes a field selecting one of the detailed CSI report settings list set in CSI-ReportConfig. In this case, the S may be configured to indicate the combination or select one of the lists as described above. s,I When defining a field, it may consist of fewer or more bits than the above Ss,i field (1415, 1465).

[0623] - R: Indicates reserved bit and can be set to 0.

[0624] According to one embodiment, through the MAC-CE in FIG. 14, a terminal may activate up to four PUCCH-based semi-persistent CSI reports within a specific bandwidth portion, and each PUCCH-based semi-persistent CSI report may activate one or more detailed CSI report settings. In this case, the terminal may report to the base station as the terminal capability the maximum number of PUCCH-based semi-persistent CSI reports including one or more detailed CSI report settings among the PUCCH-based semi-persistent CSI reports that may be activated within the specific bandwidth portion.

[0625] In addition, the terminal can receive, as a response from the base station based on the terminal capability, a maximum number of PUCCH-based semi-persistent CSI reports that the base station can actually activate through upper layer signaling. In addition, the terminal can report, as a response from the base station based on the terminal capability, to the base station a maximum number of all detailed CSI report configurations included in all PUCCH-based semi-persistent CSI reports that can be activated within a specific bandwidth segment. In addition, the terminal can receive, as a response from the base station based on the terminal capability, a maximum number of all detailed CSI report configurations included in PUCCH-based semi-persistent CSI reports that the base station can actually activate through upper layer signaling. Depending on the upper layer signaling from the base station, the terminal can determine the total bit length of MAC-CE.

[0626] According to one embodiment, through the MAC-CE in FIG. 14, the terminal may receive, from the base station, a PUCCH resource that is connected to or included in the bandwidth portion indicated by the BWP ID field (1405, 1455) as an indication method of the Si field (1410, 1460), among the CSI-ReportConfigs in the csi-ReportConfigToAddModList, which is an upper layer signaling, and whose type is set to semiPersistentOnPUCCH and whose ID is the lowest (e.g., CSI-ReportConfigId) at most four. Accordingly, if the terminal receives at least four lowest IDs for one or more CSI-ReportConfigs that do not have detailed CSI report settings set by the upper layer signaling from the base station, the terminal may not be activated through the MAC-CE for the CSI-ReportConfigs in which detailed CSI report settings exist. Conversely, if the lowest ID is set for the CSI-ReportConfig that has detailed CSI report settings, the terminal may not be able to activate the CSI-ReportConfig that does not have detailed CSI report settings through MAC-CE, which may cause a CSI calculation burden on the terminal. Therefore, the terminal can appropriately set the ID of the CSI-ReportConfig that includes or does not include detailed CSI report settings from the base station and report the PUCCH-based semi-persistent CSI report to the base station through MAC-CE.

[0627] [Method 4-3]

[0628] In one embodiment, a terminal may receive an activation indication for a PUCCH-based semi-persistent CSI report including multiple detailed CSI report configurations by receiving a MAC-CE from a base station. For example, the MAC-CE may indicate to the terminal whether a PUCCH-based semi-persistent CSI report for which the terminal receives an activation indication from the base station includes detailed CSI report configurations, through a separate field within the MAC-CE.

[0629] FIG. 15 is a diagram illustrating another MAC-CE structure for indicating activation or deactivation of a PUCCH-based semi-persistent CSI report considering detailed CSI report settings according to one embodiment.

[0630] Referring to FIG. 15, a MAC-CE indicating activation or deactivation of a semi-persistent CSI report transmitted on a PUCCH considering detailed CSI report settings according to an embodiment can be determined or identified through a MAC subheader including an LCID or an eLCID (extended LCID), and the MAC-CE indicating activation or deactivation of a semi-persistent CSI report can have a variable bit length.

[0631] According to one embodiment, the MAC-CE represented at the top of FIG. 15 can individually indicate two things, through a specific field, whether the PUCCH-based semi-persistent CSI report to be activated or deactivated through the MAC-CE includes or does not include detailed CSI report settings, and only one of the CSI-ReportConfig including or not including detailed CSI report settings can be activated or deactivated through the MAC-CE.

[0632] - Serving Cell ID (1500): The Serving Cell ID field can indicate the ID of the serving cell to which the corresponding MAC-CE is applied, and can be 5 bits long.

[0633] - BWP ID (1505): The BWP ID field may indicate the uplink bandwidth portion to which the corresponding MAC-CE is to be applied, may mean a code point within the bandwidth portion indicator field within the DCI, and may be 2 bits long.

[0634] - S (1501): The S field can indicate to the terminal whether to enable or disable a CSI-ReportConfig that includes detailed CSI report settings, or to enable or disable a CSI-ReportConfig that does not include detailed CSI report settings. If the bit is 0, it can mean enable or disable a CSI-ReportConfig that does not include detailed CSI report settings, and if the bit is 1, it can mean that the CSI-ReportConfig includes detailed CSI report settings.

[0635] - S i (1510): The Si field may indicate the enable or disable status of the semi-persistent CSI report configuration within the upper layer signaling csi-ReportConfigToAddModList.

[0636] ■ If the above S field (1501) is 1, S iThe field may mean a CSI report configuration having the type set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList, which includes PUCCH resources associated with or included in the bandwidth portion indicated by the BWP ID field, and which includes detailed CSI report configurations, and which has the i+1th lowest ID (e.g., CSI-ReportConfigId).

[0637] ◆ If the type is set to semiPersistentOnPUCCH among the CSI-ReportConfig in the upper layer signaling csi-ReportConfigToAddModList and includes a PUCCH resource connected to or included in the bandwidth part indicated by the BWP ID field, and the number of semi-persistent CSI report configurations including detailed CSI report configurations is less than i+1, the terminal may ignore the Si field. For example, if the number of semi-persistent CSI report configurations is 2, the terminal may interpret the S0 field and the S1 field, but may ignore the S2 field and the S3 field.

[0638] ■ If the S field (1501) above is 0, the Si field may mean a CSI report configuration that is connected to the bandwidth portion indicated by the BWP ID field or includes a PUCCH resource included in the bandwidth portion, has the type set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList, does not include detailed CSI report configurations, and has the i+1th lowest ID (e.g., CSI-ReportConfigId).

[0639] ◆ If the type of CSI-ReportConfig in the upper layer signaling csi-ReportConfigToAddModList is set to semiPersistentOnPUCCH and includes PUCCH resources connected to or included in the bandwidth part indicated through the BWP ID field, and the number of semi-persistent CSI report configurations that do not include detailed CSI report configurations is less than i+1, the terminal sends S i Fields can be ignored. For example, if the number of semi-persistent CSI report settings is 2, the terminal can interpret the S0 and S1 fields, but ignore the S2 and S3 fields.

[0640] ■ PUCCH resources connected to or included within a specific bandwidth portion may be PUCCH format 2, 3, or 4, and can be confirmed or identified using the PUCCH resource ID set in PUCCH-Config, which is an upper layer signaling.

[0641] ■ If the Si field is set to 1, the terminal can understand that the corresponding semi-persistent CSI report setting should be activated.

[0642] ■ If the Si field is set to 0, the terminal can understand that the corresponding semi-persistent CSI report setting should be disabled.

[0643] - S s,i (1515): S s,iThe field may indicate activation or deactivation of a specific CSI report configuration among multiple detailed CSI report configurations included in CSI-ReportConfig, which represents a semi-persistent CSI report configuration in csi-ReportConfigToAddModList, which is an upper layer signaling, when the S field (1501) is 1. The length of the field may be set to be equal to the maximum number of detailed CSI report configurations that can be set in CSI-ReportConfig in the case of a bitmap form, and in other cases, the length of the field may be shorter or longer than the field length in the bitmap form. If the S field (1501) is 1, S s,i All Octets that have fields (1515) may not exist.

[0644] ■ For example, if the maximum number of detailed CSI report settings that can be configured in CSI-ReportConfig is 4, the terminal can configure the length of the field as one field of 4 bits each to correspond to each Si field (1515), and the terminal can be instructed to consider which detailed CSI report setting among all detailed CSI report settings included in CSI-ReportConfig corresponding to each Si through each 4-bit field to perform PUCCH-based semi-persistent CSI report. The field is in the form of a bitmap and can instruct the terminal which of 4 or fewer detailed CSI report settings is to be activated or deactivated. For example, if the terminal receives 4 detailed CSI report settings from the base station in CSI-ReportConfig corresponding to the S0 field in MAC-CE, if the base station wants to activate or deactivate the first detailed CSI report setting and the third detailed CSI report setting among the 4 detailed CSI report settings, the terminal can receive an S0 field in MAC-CE from the base station. s,0 (1515) Through the field, we can expect or identify that the first and third bits from the MSB (or LSB) will be 1, and the second and fourth bits will be 0.

[0645] ■ For another example, in addition to a 4-bit bitmap, an 8-bit bitmap may also be considered, and the terminal may assume that a field representing a specific combination of detailed CSI report settings is included in the MAC-CE, or the terminal may assume that a field selecting one of the detailed CSI report settings list set in CSI-ReportConfig is included in the MAC-CE. In this case, S may be used to indicate a combination or to select one of the lists. s,i If field (1515) is defined, the above Ss,i It may consist of fewer or more bits than the field (1515).

[0646] - R: Indicates reserved bit and can be set to 0.

[0647] The MAC-CE expressed at the bottom of Fig. 15 allows a terminal to receive PUCCH-based semi-persistent CSI report activation or deactivation from a base station by considering both CSI-ReportConfig including detailed CSI report settings and CSI-ReportConfig not including detailed CSI report settings.

[0648] - Serving Cell ID (1550): The Serving Cell ID field can indicate the ID of the serving cell to which the corresponding MAC-CE is applied, and can be 5 bits long.

[0649] - BWP ID (1555): The BWP ID field may indicate the uplink bandwidth portion to which MAC-CE is to be applied, may mean a code point within the bandwidth portion indicator field within the DCI, and may be 2 bits long.

[0650] - A i (1565) A i The field may indicate the enable or disable status of the semi-persistent CSI report configuration for a specific CSI-ReportConfig containing detailed CSI report configurations among the CSI-ReportConfigs within the upper layer signaling csi-ReportConfigToAddModList.

[0651] ■ A iThe field may mean a CSI report configuration having the type set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList, which includes PUCCH resources associated with or included in the bandwidth portion indicated by the BWP ID field, and which includes detailed CSI report configurations, and which has the i+1th lowest ID (e.g., CSI-ReportConfigId).

[0652] ■ PUCCH resources connected to or included within a specific bandwidth portion may be PUCCH format 2, 3, or 4, and can be identified using the PUCCH resource ID set in PUCCH-Config, which is an upper layer signaling.

[0653] ■ If the type is set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList and the number of semi-persistent CSI report configurations that include PUCCH resources included in the bandwidth portion indicated through the BWP ID field or that include detailed CSI report configurations is less than i+1, the terminal shall A i Fields can be ignored. For example, if the number of semi-persistent CSI report settings is 2, the terminal can interpret fields A0 and A1, but ignore fields A2 and A3.

[0654] ■ If A i If the field is set to 1, the terminal can understand that the semi-persistent CSI report setting should be enabled.

[0655] ■ If A iIf the field is set to 0, the terminal can understand that the semi-persistent CSI report setting should be disabled.

[0656] - A s,i (1570): A s,i The field may indicate whether to enable or disable any of the multiple detailed CSI report settings contained in the CSI-ReportConfig, which represents the semi-persistent CSI report settings in the upper layer signaling csi-ReportConfigToAddModList. The length of the field may be set equal to the maximum number of detailed CSI report settings that can be set in the CSI-ReportConfig in the case of bitmap form, and in other cases, the length of the field may be shorter or longer than the field length in the bitmap form. If all of the above A i If field (1570) is 0, A s,i All Octets that have fields (1570) may not exist.

[0657] ■ For example, if the maximum number of detailed CSI report settings that can be set in CSI-ReportConfig is 4, the terminal configures each field with a length of 4 bits and sets each A i It can be matched to the field (1565), and the terminal can correspond to each A through each 4-bit field. iThe terminal may be instructed to perform PUCCH-based semi-persistent CSI reporting by considering which detailed CSI report settings among all detailed CSI report settings included in the CSI-ReportConfig corresponding to the MAC-CE. The field is in the form of a bitmap and may instruct the terminal which of four or fewer detailed CSI report settings is to be activated or deactivated. For example, if the terminal receives from the base station four detailed CSI report settings in the CSI-ReportConfig corresponding to the A0 field in the MAC-CE, and if the base station wants to activate or deactivate the first and third detailed CSI report settings among the four detailed CSI report settings, the terminal may receive from the base station A in the MAC-CE s,0 (1570) Through the field, the terminal can expect the first and third bits from the MSB (or LSB) to be 1, and the terminal can expect the second and fourth bits to be 0.

[0658] ■ As another example, not only a 4-bit bitmap but also an 8-bit bitmap may be considered, and the terminal may assume that a field indicating a specific combination of detailed CSI report settings is included in the MAC-CE, or the terminal may assume that a field selecting one of the detailed CSI report settings list set in CSI-ReportConfig is included in the MAC-CE. In this case, A may be used to indicate the combination or to select one of the lists. s,i When defining field (1570), A s,i It may consist of fewer or more bits than the field (1570).

[0659] - S i (1570): S iThe field may indicate the enable or disable status of semi-persistent CSI report settings for a specific CSI-ReportConfig that does not contain detailed CSI report settings among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList.

[0660] ■ S i The field may mean a CSI report configuration having a type set to semiPersistentOnPUCCH among CSI-ReportConfigs in csi-ReportConfigToAddModList, which is an upper layer signaling, and which includes a PUCCH resource connected to or included in a bandwidth portion indicated through the BWP ID field, does not include a detailed CSI report configuration, and has the i+1th lowest ID (e.g., CSI-ReportConfigId).

[0661] ■ PUCCH resources connected to or included within a specific bandwidth portion may be PUCCH format 2, 3, or 4, and may be confirmed or identified using the PUCCH resource ID set in PUCCH-Config, which is an upper layer signaling.

[0662] ■ If the type is set to semiPersistentOnPUCCH among the CSI-ReportConfigs in the upper layer signaling csi-ReportConfigToAddModList and the number of semi-persistent CSI report configurations that are connected to the bandwidth part indicated through the BWP ID field or include PUCCH resources included in the bandwidth part is less than i+1, the terminal shall iFields can be ignored. For example, if the number of semi-persistent CSI report settings is 2, the terminal can interpret the S0 and S1 fields, but ignore the S2 and S3 fields.

[0663] ■ If S i If the field is set to 1, the terminal can understand that the corresponding semi-persistent CSI report setting should be activated.

[0664] ■ If S i If the field is set to 0, the terminal can understand that the corresponding semi-persistent CSI report setting should be disabled.

[0665] - R: Indicates reserved bit and can be set to 0.

[0666] According to one embodiment, through the MAC-CE at the top in FIG. 15, the terminal can activate up to 4 PUCCH-based semi-persistent CSI reports within a specific bandwidth portion, and all activated semi-persistent CSI reports may or may not include all detailed CSI report configurations. The base station can exclude a situation where the terminal is differentially activated or deactivated according to the CSI-ReportConfigId depending on whether or not the terminal includes such detailed CSI report configurations. In addition, the terminal can activate or deactivate all CSI-ReportConfigs that include or do not include detailed CSI report configurations through the MAC-CE at the bottom in FIG. 15. In this case, the terminal can report to the base station the maximum number of configurations for CSI-ReportConfigs that include or do not include detailed CSI report configurations, the maximum number of CSI reports that the terminal can actually report, etc. as terminal capabilities. Through such MAC-CE, a CSI-ReportConfig that includes or does not include detailed CSI report configurations can be activated or deactivated through a single MAC-CE.

[0667] [Method 4-4]

[0668] According to one embodiment, a terminal may be activated to report PUCCH-based semi-persistent CSI reports for some or all of multiple detailed CSI report configurations within a single CSI-ReportConfig by receiving a MAC-CE from a base station. For example, if there are five detailed CSI report configurations corresponding to antenna ports 2, 4, 8, 16, and 32 within a single CSI-ReportConfig, the terminal may receive activation information from the base station regarding which of the five detailed CSI report configurations will perform CSI reports. For example, if three detailed CSI report configurations corresponding to antenna ports 2, 8, and 32 are activated via the MAC-CE, and if the terminal is instructed via DCI by a codepoint of a CSI request including the corresponding CSI-ReportConfig, the terminal may report CSI reports for the three activated detailed CSI report configurations to the base station.

[0669] According to one embodiment, the terminal may activate CSI report reporting for some or all of the detailed CSI report configurations through MAC-CE transmitted by the base station, taking into account whether network energy saving is needed at the base station and the CSI calculation burden at the terminal, and report the CSI report. Although there may be a delay between the terminal receiving the MAC-CE from the base station and its activation, it is highly likely that the situation in which the base station needs to change the amount of information requested from the terminal for network energy saving will not change dynamically like DCI-based L1 signaling. Therefore, the method of selecting some or all of the detailed CSI report configurations through MAC-CE can have appropriate signaling flexibility without causing unnecessary overhead of the CSI-ReportConfig configuration information as in [Method 4-1]. However, if only some or all of the detailed CSI report settings for one CSI-ReportConfig can be selected through one MAC-CE signaling, multiple MAC-CEs may be required when changes to multiple CSI-ReportConfigs are required, and for this purpose, it may be possible to change the detailed CSI report settings of up to N CSI-ReportConfigs through one MAC-CE. In this case, N may be set by upper layer signaling or may be fixedly defined in the specification and may be related to the maximum length of the MAC-CE.

[0670] According to one embodiment, [Method 4-4] may also be applicable to PUCCH-based periodic CSI reports, wherein the PUCCH-based periodic CSI reports may include multiple detailed CSI report configurations. Accordingly, when applying [Method 4-4] to the PUCCH-based periodic CSI reports, the terminal may be activated through MAC-CE to perform CSI reporting for some or all of the detailed CSI report configurations among the multiple detailed CSI report configurations set in CSI-ReportConfig for the PUCCH-based periodic CSI reports from the base station.

[0671] For example, if there are five detailed CSI report configurations corresponding to antenna ports 2, 4, 8, 16, and 32 in the CSI-ReportConfig for PUCCH-based periodic CSI reporting of a terminal, the terminal can receive activation information on which of the five detailed CSI report configurations to perform CSI reporting for by receiving MAC-CE from the base station. For example, if three detailed CSI report configurations corresponding to antenna ports 2, 8, and 32 are activated through MAC-CE, the terminal can perform PUCCH-based periodic CSI reporting according to the three detailed CSI report configurations starting from 3 ms after transmitting a PUCCH including a HARQ-ACK corresponding to a PDSCH including the MAC-CE received from the base station.

[0672] According to one embodiment, the terminal may report to the base station through terminal capability signaling whether it supports at least one combination of [Method 4-1] to [Method 4-4]. The terminal may be configured with upper layer signaling from the base station for at least one combination of [Method 4-1] to [Method 4-4], activated with MAC-CE, instructed with L1 signaling, or notified with at least one combination of upper layer signaling, MAC-CE, and L1 signaling. Alternatively, the terminal may follow a method fixedly supported by the standard.

[0673] According to one embodiment, the terminal and the base station can use a combination of at least one of the [Method 4-1] to [Method 4-4] and at least one of the [Method 1-1-1] to [Method 1-1-4]. For example, the terminal can perform CSI reporting to the base station only for a specific number of detailed CSI report settings among multiple detailed CSI report settings within a specific CSI-ReportConfig from the base station, as in [Method 1-1-2]. For example, if there are four detailed CSI report settings within a specific CSI-ReportConfig and the base station notifies the terminal to perform CSI reporting for two of them, the terminal can arbitrarily select two detailed CSI report settings to be actually reported among the four. For this purpose, as a method of notifying the terminal from the base station, [Method 4-1] based on upper layer signaling, and [Method 4-2] to [Method 4-3] activating or deactivating based on a changed MAC-CE can be considered.

[0674] Fig. 16 is a diagram showing the operation of a terminal according to one embodiment.

[0675] Referring to FIG. 16, in step 1600 according to one embodiment, a terminal may transmit terminal capabilities to a base station. At this time, the terminal capabilities that the terminal may transmit may include a combination of at least one of the various CSI report and CSI-RS resource set configuration methods described above, the maximum number of CSI-RS ports per cell or per entire cell, the maximum number of CSI-RS resources per cell or per entire cell, [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4], [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0676] According to one embodiment, in step 1605, the terminal may receive upper layer signaling from the base station. At this time, the upper layer signaling that the terminal may receive from the base station may be configuration information including a combination of at least one of the various CSI report and CSI-RS resource set configuration methods described above, the maximum number of CSI-RS ports per cell or per entire cell, the maximum number of CSI-RS resources per cell or per entire cell, and [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4], [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0677] According to one embodiment, in step 1610, the terminal may receive from the base station a configuration, activation, and / or instruction for a CSI report for network energy saving. At this time, the terminal may receive from the base station a configuration, activation, and / or instruction for a CSI report for network energy saving through at least one combination of upper layer signaling, MAC-CE, and L1 signaling, which means a combination of at least one of [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0678] According to one embodiment, in step 1615, the terminal may receive a CSI-RS from the base station. At this time, the CSI-RS resource of the corresponding CSI-RS may be based on various CSI report and CSI-RS resource set configuration methods for the terminal from the base station as mentioned in the above embodiments. For example, the terminal may receive multiple CSI-RS resources having different numbers of ports, or the terminal may receive one CSI-RS resource, but perform channel estimation based on different numbers of CSI-RS ports for the corresponding CSI-RS resource through CSI report configuration, etc.

[0679] According to one embodiment, in step 1620, the terminal may transmit a CSI report to the base station. At this time, the terminal may determine whether to transmit some or all of the corresponding CSI reports to the base station according to the various CSI report and CSI-RS resource set configuration methods described above, and various CPU calculation methods. The UCI format for the CSI report may vary depending on the method of considering constraints in various CSI calculations. In addition, the terminal may perform channel estimation for CSI-RS resources corresponding to different numbers of CSI-RS ports and calculate and report the corresponding CSI. Although the terminal receives one CSI-RS resource, it may perform channel estimation for different numbers of CSI-RS ports for the corresponding CSI-RS resource through CSI report configuration, etc., and calculate and report the CSI corresponding to the estimated channel. The terminal may perform CSI report transmission by being notified of at least one combination of [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4] from the base station. The terminal may transmit the CSI report for scheduling and network operation for network energy saving of the base station, and the base station may perform scheduling and network operation for the purpose of network energy saving based on the information.

[0680] According to one embodiment, in step 1625, the terminal may receive base station signaling related to network energy saving from the base station. For example, the base station may receive the CSI report of the terminal and transmit the network energy saving related signaling. The base station may transmit the network energy saving related signaling to terminals that can report the CSI report as described above, or to all terminals in general. For example, the network energy saving related signaling may be a signaling that combines at least one of upper layer signaling, L1 signaling such as MAC-CE, and DCI, which means that the base station will adjust the downlink transmission power. The network energy saving related signaling may be terminal-specific or terminal-common. For another example, signaling that means that the base station power is cut off may not be excluded. A terminal that receives such signaling may understand that the base station is performing a network energy saving operation.

[0681] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts herein. For example, although depicted as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, steps may be omitted or replaced with other steps.

[0682] Figure 17 is a diagram illustrating the operation of a base station according to one embodiment.

[0683] According to one embodiment, in step 1700, the base station can receive terminal capabilities from the terminal. The terminal capabilities (e.g., information on terminal capabilities) that the base station can receive may include a combination of at least one of the CSI report and CSI-RS resource set configuration methods mentioned in the above embodiments, the maximum number of CSI-RS ports per cell or per entire cell, the maximum number of CSI-RS resources per cell or per entire cell, [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4], [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0684] According to one embodiment, in step 1705, the base station may transmit upper layer signaling to the terminal. At this time, the upper layer signaling that the base station may transmit to the terminal may be configuration information including a combination of at least one of the CSI report and CSI-RS resource set configuration methods mentioned in the above embodiments, the maximum number of CSI-RS ports per cell or per entire cell, the maximum number of CSI-RS resources per cell or per entire cell, [Method 1-1] to [Method 1-5], [Method 1-1-1] to [Method 1-1-4], [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0685] According to one embodiment, in step 1710, the base station can transmit to the terminal a configuration, activation, and / or instruction for a CSI report for network energy saving. At this time, the base station can transmit to the terminal a configuration, activation, and / or instruction for a CSI report for network energy saving through at least one combination of upper layer signaling, MAC-CE, and L1 signaling, which means at least one combination of [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4].

[0686] According to one embodiment, in step 1715, the base station may transmit a CSI-RS to the terminal. At this time, the CSI-RS resource of the corresponding CSI-RS may be based on a method of configuring a CSI report and CSI-RS resource set for the terminal from the base station. For example, the base station may transmit multiple CSI-RS resources having different numbers of ports, or the base station may transmit a single CSI-RS resource, but the terminal may perform channel estimation based on a different number of CSI-RS ports for the corresponding CSI-RS resource through CSI report configuration, etc.

[0687] According to one embodiment, in step 1720, the base station may receive a CSI report from the terminal. At this time, the CSI report may correspond to some or all of the CSI reports set as CSI reports determined by the terminal to be transmitted to the base station according to the CSI report and CSI-RS resource set setting method and CPU calculation method mentioned in the embodiments above. In addition, the form of UCI included in the CSI report may vary depending on the method of considering constraints in the CSI calculation. In addition, the CSI report may include CSI based on channel estimation for CSI-RS resources corresponding to different numbers of CSI-RS ports and / or CSI according to the result of performing channel estimation based on different numbers of CSI-RS ports for the corresponding CSI-RS resource, although one CSI-RS resource is transmitted, through CSI report setting, etc. The terminal may be notified of at least one combination of [Method 2-1] to [Method 2-4], [Method 3-1] to [Method 3-4], and [Method 4-1] to [Method 4-4] from the base station, and may perform CSI report transmission. The terminal may perform the corresponding CSI report for scheduling and network operation for network energy saving of the base station, and the base station may perform scheduling and network operation for the purpose of network energy saving based on the corresponding information.

[0688] According to one embodiment, in step 1725, the base station may transmit base station signaling related to network energy saving to the terminal. For example, the base station may receive a CSI report from the terminal and transmit a signaling combined with at least one of upper layer signaling, L1 signaling, such as MAC-CE, and DCI, which means to adjust downlink transmission power for terminals capable of reporting such CSI report or for all terminals in general. The signaling related to network energy saving may be terminal-specific or terminal-common. As another example, signaling meaning to cut off the power of the base station may not be excluded. A terminal receiving such signaling may understand that the base station is performing a network energy saving operation.

[0689] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the...

Claims

1. A method performed by a UE (user equipment) in a wireless communication system, A step of receiving, from a base station, first information including information on at least one configuration for reporting channel state information (CSI), wherein the information on the at least one configuration includes information on sub-configurations; A step of receiving second information for the CSI report from the base station, at least one sub-configuration among the sub-configurations being indicated based on the second information; and A method comprising the step of transmitting, to the base station, the CSI report for the at least one sub-configuration.

2. In claim 1, The first information includes information about at least one trigger state associated with a part of the sub-configurations, The second information includes DCI (downlink control information), and the DCI includes a CSI request field related to information about a trigger state corresponding to at least one sub-configuration among the at least one trigger state, A method wherein information about at least one trigger state corresponds to an aperiodic CSI report or a semi-persistent CSI report on a physical uplink shared channel (PUSCH).

3. In claim 1, The second information includes a MAC (medium access control) CE (control element) for reporting SP (semi-persistent) CSI on PUCCH (physical uplink control channel), The MAC CE includes a first field indicating whether at least one configuration for the CSI reporting is activated and a second field indicating whether sub-configurations included in the activated configuration among the at least one configuration are activated. A method wherein at least one of said sub-configurations is instructed to be activated based on said second field.

4. In claim 1, A method wherein the information about the sub-configurations is based on first capability information about a maximum number of sub-configurations set in the configuration for the CSI report, and second capability information about the number of CSI reports corresponding to the sub-configurations.

5. In a wireless communication system, in the UE (user equipment), transceiver; and A controller coupled with the above transceiver, The above controller: Receive first information from a base station, including information about at least one configuration for reporting CSI (channel state information), wherein the information about the at least one configuration includes information about sub-configurations; From the base station, second information for the CSI report is received, and at least one of the sub-configurations is indicated based on the second information. A UE configured to transmit, to the base station, the CSI report for the at least one sub-configuration.

6. In claim 5, The first information includes information about at least one trigger state associated with a part of the sub-configurations, The second information includes DCI (downlink control information), and the DCI includes a CSI request field related to information about a trigger state corresponding to at least one sub-configuration among the at least one trigger state, Information about at least one trigger state corresponds to aperiodic CSI reporting or semi-persistent CSI reporting on physical uplink shared channel (PUSCH).

7. In claim 5, The second information includes a MAC (medium access control) CE (control element) for reporting SP (semi-persistent) CSI on PUCCH (physical uplink control channel), The MAC CE includes a first field indicating whether at least one configuration for the CSI reporting is activated and a second field indicating whether sub-configurations included in the activated configuration among the at least one configuration are activated. A UE wherein at least one of the above sub-configurations is instructed to be activated based on the second field.

8. In claim 5, The information about the above sub-configurations is based on first capability information about the maximum number of sub-configurations set in the configuration for the CSI reporting, and second capability information about the number of CSI reports corresponding to the sub-configurations.

9. A method performed by a base station in a wireless communication system, A step of transmitting, to a UE (user equipment), first information including information on at least one configuration for reporting channel state information (CSI), wherein the information on the at least one configuration includes information on sub-configurations; A step of transmitting second information for the CSI report to the UE, wherein at least one of the sub-configurations is indicated based on the second information; and A method comprising the step of receiving, from said UE, said CSI report for said at least one sub-configuration.

10. In claim 9, The first information includes information about at least one trigger state associated with a part of the sub-configurations, The second information includes DCI (downlink control information), and the DCI includes a CSI request field related to information about a trigger state corresponding to at least one sub-configuration among the at least one trigger state, A method wherein information about at least one trigger state corresponds to an aperiodic CSI report or a semi-persistent CSI report on a physical uplink shared channel (PUSCH).

11. In claim 9, The second information includes a MAC (medium access control) CE (control element) for reporting SP (semi-persistent) CSI on PUCCH (physical uplink control channel), The MAC CE includes a first field indicating whether at least one configuration for the CSI reporting is activated and a second field indicating whether sub-configurations included in the activated configuration among the at least one configuration are activated. A method wherein at least one of said sub-configurations is instructed to be activated based on said second field.

12. In claim 9, A method wherein the information about the sub-configurations is based on first capability information about a maximum number of sub-configurations set in the configuration for the CSI report, and second capability information about the number of CSI reports corresponding to the sub-configurations.

13. In a base station in a wireless communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Transmitting first information including information about at least one configuration for reporting CSI (channel state information) to a UE (user equipment), wherein the information about the at least one configuration includes information about sub-configurations, To the UE, second information for the CSI report is transmitted, and at least one of the sub-configurations is indicated based on the second information. A base station configured to receive, from the UE, the CSI report for the at least one sub-configuration.

14. In claim 13, The first information includes information about at least one trigger state associated with a part of the sub-configurations, The second information includes DCI (downlink control information), and the DCI includes a CSI request field related to information about a trigger state corresponding to at least one sub-configuration among the at least one trigger state, A base station, wherein information about at least one trigger state corresponds to an aperiodic CSI report or a semi-persistent CSI report on a physical uplink shared channel (PUSCH).

15. In claim 13, The second information includes a MAC (medium access control) CE (control element) for reporting SP (semi-persistent) CSI on PUCCH (physical uplink control channel), The MAC CE includes a first field indicating whether at least one configuration for the CSI reporting is activated and a second field indicating whether sub-configurations included in the activated configuration among the at least one configuration are activated. A base station, wherein at least one of the above sub-configurations is instructed to be activated based on the second field.

Citation Information

Patent Citations

  • Reporting configurations for neural network-based processing at a ue

    WO2022040046A1