Method and apparatus for reporting channel state information on basis of synchronization signal block outside active band in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to operations of a terminal and a base station in a wireless communication system, and, specifically, to a method for transmitting and receiving an uplink reference signal in a wireless communication system, and an apparatus capable of performing same. The present disclosure provides an apparatus and a method capable of effectively providing services in a mobile communication system.

Description

Method and apparatus for reporting channel state information based on a synchronization signal block outside the active band in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for reporting channel state information based on a synchronization signal block outside the active band in a wireless communication system and an apparatus capable of performing the same.

[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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0009] The present invention, for solving the above-mentioned problems, comprises a method performed by a terminal in a wireless communication system, the method comprising: transmitting a terminal capability information message including first terminal capability information and second terminal capability information to a base station; receiving a radio resource control (RRC) message from the base station including a trigger state list for non-periodic channel state information (CSI) reporting; receiving downlink control information (DCI) from the base station including a field indicating a trigger state of one of the trigger state lists; and, if the reference signal associated with the indicated trigger state is a synchronization signal block (SSB) transmitted in an inactive downlink bandwidth portion, transmitting a CSI report determined based on the SSB to the base station.

[0010] In addition, the present invention, for solving the above-mentioned problems, comprises a method performed by a base station in a wireless communication system, the method comprising: receiving a terminal capability information message from a terminal including first terminal capability information and second terminal capability information; transmitting a radio resource control (RRC) message to the terminal including a trigger state list for non-periodic channel state information (CSI) reporting; transmitting downlink control information (DCI) to the terminal including a field indicating a trigger state of one of the trigger state lists; and receiving a CSI report determined based on the SSB from the terminal when the reference signal associated with the indicated trigger state is an SSB transmitted in an inactive downlink bandwidth portion.

[0011] In addition, the present invention for solving the above-mentioned problems comprises, in a terminal of a wireless communication system, at least one transceiver; at least one processor connected to the at least one transceiver so as to be able to communicate with the at least one transceiver; and a memory connected to the at least one processor so as to be able to communicate with the at least one processor and capable of executing the at least one processor individually or in any combination thereof, wherein the terminal transmits a terminal capability information message including first terminal capability information and second terminal capability information to a base station, receives a radio resource control (RRC) message including a trigger state list for non-periodic channel state information (CSI) reporting from the base station, receives downlink control information (DCI) from the base station including a field indicating a trigger state among the trigger state lists, and stores an instruction to transmit a CSI report determined based on the SSB to the base station when the reference signal associated with the indicated trigger state is an SSB transmitted in an inactive downlink bandwidth portion.

[0012] In addition, the present invention for solving the above-mentioned problems comprises, in a base station of a wireless communication system, at least one transceiver; at least one processor connected to the at least one transceiver so as to be able to communicate; and a memory that stores an instruction in which the base station receives a terminal capability information message including first terminal capability information and second terminal capability information from a terminal, transmits a radio resource control (RRC) message including a trigger state list for non-periodic channel state information (CSI) reporting to the terminal, transmits downlink control information (DCI) including a field indicating one of the trigger state lists to the terminal, and, when the reference signal associated with the indicated trigger state is a synchronization signal block (SSB) transmitted in a disabled downlink bandwidth portion, receives a CSI report determined based on the SSB from the terminal.

[0013] The disclosed embodiments provide an apparatus and method capable of effectively providing services in a mobile communication system.

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

[0015] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

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

[0018] FIG. 5 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 6 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure.

[0020] Figure 7 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0021] FIG. 8 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 9 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 10 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 11 is a diagram illustrating an example of time-axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 12 is a diagram illustrating a method for determining an available slot when transmitting a PUSCH repetition type A of a terminal in a 5G system according to one embodiment of the present disclosure.

[0026] FIG. 13 is a diagram showing a non-periodic CSI report signaling structure that a terminal according to one embodiment of the present disclosure can receive as an upper layer signaling.

[0027] FIG. 14 is a diagram showing non-periodic CSI report and non-periodic CSI-RS triggering situations and constraints according to one embodiment of the present disclosure.

[0028] FIG. 15A is a diagram illustrating an example of a non-periodic CSI report signaling structure based on terminal capabilities according to one embodiment of the present disclosure.

[0029] FIG. 15B is a diagram illustrating an example of a non-periodic CSI report signaling structure based on terminal capabilities according to one embodiment of the present disclosure.

[0030] FIG. 16 is a diagram showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0031] FIG. 17 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0032] FIG. 18 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0033] FIG. 19 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0034] FIG. 20 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0035] FIG. 21 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

[0037] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0038] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0039] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0040] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may 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 made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0041] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0042] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0043] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0044] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 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.

[0045] As a representative example of the above-mentioned broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to 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 refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

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

[0047] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0048] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0049] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0050] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

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

[0052] [NR Time-Frequency Resources]

[0053] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

[0054] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain where data or control channels are transmitted in a 5G system.

[0055] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104). In the time axis, a single subframe (110) may contain multiple OFDM symbols (102). For example, the length of one subframe may be 1 ms.

[0056] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0057] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( = 14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by [Table 1] below.

[0058] [Table 1]

[0059]

[0060] [Bandwidth Section (BWP)]

[0061] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0062] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0063] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the information in [Table 2] below for each bandwidth portion.

[0064] [Table 2]

[0065]

[0066] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to the above configuration information. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. At least one of the configured bandwidth portions may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via DCI.

[0067] According to some embodiments, prior to the RRC connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a PDCCH can be transmitted to receive system information required for initial connection (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and monitoring occasion for Control Resource Set #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0068] The settings for the bandwidth portion supported by the above 5G can be used for various purposes.

[0069] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth portion setting. For example, by setting the frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0070] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed (FDM), and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0071] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz can be very inefficient in terms of power consumption. To reduce the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0072] In the method for configuring the above bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part (Initial BWP) through the MIB during the initial connection phase. More specifically, the terminal can receive a configuration of a control area (i.e., CORESET) for a downlink control channel through which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control area configured by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which the SIB is transmitted. In addition to the purpose of receiving the SIB, the Initial Bandwidth Part may also be utilized for other system information (OSI), paging, and random access.

[0073] [Bandwidth Section (BWP) Change]

[0074] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may instruct the terminal to Bandwidth Part #2 (302) using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0075] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been specified and can be defined, for example, as shown in [Table 3] below.

[0076] [Table 3]

[0077]

[0078] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0079] In accordance with the aforementioned requirements for the bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be performed at a time no later than the new bandwidth portion, and transmission and reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (TBWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0080] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the said DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the said DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the said DCI 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).

[0081] [CA / DC Related]

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

[0083] Referring to Fig. 4, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (Service Data Adaptation Protocol 425, 470), NR PDCP (Packet Data Convergence Protocol 430, 465), NR RLC (Radio Link Control 435, 460), and NR MAC (Medium Access Control 440, 455) at the terminal and the NR base station, respectively.

[0084] The main functions of NR SDAP (425, 470) may include some of the following functions.

[0085] - User data transfer function (transfer of user plane data)

[0086] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

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

[0088] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0089] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is set, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers to the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support smooth service.

[0090] The main functions of NR PDCP (430, 465) may include some of the following functions.

[0091] - Header compression and decompression features (ROHC only)

[0092] - User data transfer function (Transfer of user data)

[0093] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0095] - Reordering function (PDCP PDU reordering for reception)

[0096] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0097] - Retransmission of PDCP SDUs

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

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

[0100] In the above, the reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function that transmits data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

[0101] The main functions of NR RLC (435, 460) may include some of the following functions.

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

[0103] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

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

[0106] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0107] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0108] - Reordering function (Reordering of RLC data PDUs)

[0109] - Duplicate detection

[0110] - Error detection function (Protocol error detection)

[0111] - RLC SDU discard function

[0112] RLC re-establishment function

[0113] In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering the RLC SDUs when the original RLC SDU is received divided into multiple RLC SDUs, a function of rearranging the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, or a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs described above may be processed in the order they are received (regardless of the order of sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0114] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering RLC SDUs when a single RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0115] The NR MAC (440, 455) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

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

[0117] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0118] - Scheduling information reporting function

[0119] - HARQ function (Error correction through HARQ)

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

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

[0122] - MBMS service identification function

[0123] - Transport format selection function

[0124] - Padding

[0125] The NR PHY layer (445, 450) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0126] The detailed structure of the above wireless protocol structure may vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, as shown in 400. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in 410, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in 420, but multiplexes the PHY layer through the MAC layer.

[0127] [Unified TCI state]

[0128] The following describes a method for directing and activating a single TCI state based on the unified TCI scheme. The unified TCI scheme refers to a method of managing transmit and receive beams by integrating the TCI state method used for downlink reception and the spatial relation info method used for uplink transmission, which were distinguished in the existing Rel-15 and Rel-16, into a single TCI state. Therefore, when a terminal receives a directive from a base station based on the unified TCI scheme, it can perform beam management using the TCI state for uplink transmission as well. If the terminal receives a TCI-State from the base station, which is a higher-layer signaling with the tci-stateId-r17, the terminal can perform operations based on the unified TCI scheme using that TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0129] The first form is a joint TCI state, and the terminal can receive instructions from the base station regarding the TCI state to be applied for both uplink transmission and downlink reception through a single TCI-State. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 within the joint TCI state-based TCI-State, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used as an uplink transmission beam or transmission filter using the RS corresponding to qcl-Type2 within the joint DL / UL TCI state-based TCI-State. In this case, if the terminal receives a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0130] The second form is a separate TCI state, and the terminal can individually receive instructions from the base station for an UL TCI state to be applied for uplink transmission and a DL TCI state to be applied for downlink reception. If the terminal is instructed with an UL TCI state, the terminal can be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state. If the terminal is instructed with a DL TCI state, the terminal can be instructed with parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2.

[0131] If the terminal is instructed with both a DL TCI state and a UL TCI state, the terminal may be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state, parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2. In this case, if the reference RS or source RS set within the DL TCI state and the UL TCI state instructed to the terminal are different, the terminal may apply beams individually to uplink transmission and downlink reception, respectively, based on the instructed UL TCI state and DL TCI state.

[0132] A terminal can receive up to 128 upper-layer signalings for each specific bandwidth part within a specific cell from the base station for joint TCI states, and among the separate TCI states, DL TCI states can be received as upper-layer signalings for each specific bandwidth part within a specific cell, up to 64 or 128 based on terminal capability reports, and among the separate TCI states, DL TCI states and joint TCI states can use the same upper-layer signaling structure. For example, if 128 joint TCI states are set and 64 DL TCI states are set among the separate TCI states, the 64 DL TCI states can be included in the 128 joint TCI states.

[0133] Among the separate TCI states, the UL TCI state can be configured with up to 32 or 64 upper layer signalings for each specific bandwidth part within a specific cell based on terminal capability reporting, and like the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCIs may also use the same upper layer signaling structure, or the UL TCI state among the separate TCIs may use a different upper layer signaling structure from the joint TCI state and the DL TCI state among the separate TCIs.

[0134] Using different or identical upper-layer signaling structures in this way may be defined in the specifications, or may be distinguished through another upper-layer signaling configured by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0135] The terminal can receive instructions regarding transmit / receive beams in an integrated TCI manner by utilizing one of the joint TCI state and separate TCI state configured by the base station. The terminal can receive a configuration from the base station via upper-layer signaling regarding whether to use one of the joint TCI state or separate TCI state.

[0136] The terminal receives instructions related to the transmit / receive beam using one of the selected methods among the joint TCI state and the separate TCI state through upper layer signaling, and at this time, there may be two types of transmit / receive beam instructions from the base station: a MAC-CE based instruction method and a MAC-CE based activation and DCI based instruction method.

[0137] If a terminal receives instructions related to transmit / receive beams using the joint TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE indicating the joint TCI state from the base station, and the base station can schedule the terminal to receive a PDSCH containing the corresponding MAC-CE through the PDCCH. If there is only one joint TCI state included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the indicated joint TCI state starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful. If there are two or more joint TCI states included in the MAC-CE, the terminal can confirm that the multiple joint TCI states indicated by the MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful, and activate the indicated joint TCI states. Subsequently, the terminal can receive DCI format 1_1 or 1_2 and apply the one joint TCI state indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0138] If a terminal receives instructions regarding transmit / receive beams using a separate TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE from the base station that indicates a separate TCI state, and the base station can schedule the terminal to receive a PDSCH containing the MAC-CE via a PDCCH. If there is only one set of separate TCI states included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter by using the separate TCI states included in the indicated set of separate TCI states starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether the PDSCH was successfully received. At this time, a separate TCI state set may refer to a single or multiple separate TCI states that a single code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a separate TCI state set may include one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. If there are two or more separate TCI state sets included by MAC-CE, the terminal may confirm that the multiple separate TCI state sets indicated by MAC-CE correspond to each code point of the TCI state field in DCI format 1_1 or 1_2 starting 3 ms after a PUCCH transmission containing HARQ-ACK information indicating whether the PDSCH was successfully received, and activate the indicated separate TCI state sets.In this case, each code point in the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal receives DCI format 1_1 or 1_2 and can apply the separate set of TCI states indicated by the TCI state field within the corresponding DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0139] FIG. 5 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure. As described above, the terminal receives DCI format 1_1 or 1_2 from a base station that includes downlink data channel scheduling information (with DL assignment) or does not include it (without DL assignment), and can apply one joint TCI state or a set of separate TCI states indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams.

[0140] - DCI format 1_1 or 1_2 with DL assignment (5-00): If a terminal receives DCI format 1_1 or 1_2 containing downlink data channel scheduling information from a base station (5-01) and indicates a set of one joint TCI state or separate TCI state based on the integrated TCI method, the terminal receives a PDSCH scheduled based on the received DCI (5-05) and can transmit a PUCCH containing a HARQ-ACK indicating whether the DCI and PDSCH were successfully received (5-10). At this time, the HARQ-ACK may include the meaning of whether the DCI and PDSCH were successfully received, and if at least one of the DCI and PDSCH is not received, the terminal can transmit a NACK, and if both are successfully received, the terminal can transmit an ACK.

[0141] - DCI format 1_1 or 1_2 without DL assignment (5-50): If a terminal receives DCI format 1_1 or 1_2 from a base station that does not include downlink data channel scheduling information (5-55) and indicates one joint TCI state or a separate set of TCI states based on a unified TCI scheme, the terminal may assume at least one combination of the following for the DCI.

[0142] ■ Includes scrambled CRC using CS-RNTI.

[0143] ■ The value of all bits assigned to all fields used as RV (Redundancy Version) fields is 1.

[0144] ■ The value of all bits assigned to all fields used as MCS (Modulation and Coding Scheme) fields is 1.

[0145] ■ The value of all bits assigned to all fields used as NDI (New Data Indication) fields is 0.

[0146] ■ For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits allocated to the FDRA field is 0; for FDRA Type 1, the value of all bits allocated to the FDRA field is 1; and for the FDRA method dynamicSwitch, the value of all bits allocated to the FDRA field is 0.

[0147] The terminal may transmit a PUCCH containing a HARQ-ACK indicating whether reception of DCI format 1_1 or 1_2, in which the above-described items are assumed, was successful (5-60).

[0148] - For both DCI format 1_1 or 1_2 with DL assignment (5-00) and without DL assignment (5-50), if the new TCI state indicated via DCI (5-01, 5-55) is the same as the TCI state that was previously indicated and applied to the uplink transmit and downlink receive beams, the terminal may maintain the previously applied TCI state; if the new TCI state is different from the previously indicated TCI state, the terminal may determine the application time of the joint TCI state or separate TCI state set indicated by the TCI state field included in the DCI as (5-30, 5-80) after the first slot (5-20, 5-70) after a time equal to BAT (beam application time, 5-15, 5-65) following PUCCH transmission, and may use the previously indicated TCI state until (5-25, 5-75) prior to that slot (5-20, 5-70). there is.

[0149] - For both DCI format 1_1 or 1_2 with DL assignment (5-00) and without DL assignment (5-50), BAT can be set to upper layer signaling based on terminal capability reporting information as a specific number of OFDM symbols, and the numerology for BAT and the first slot after BAT can be determined based on the smallest numerology among all cells to which the joint TCI state or separate TCI state set indicated through DCI is applied.

[0150] A terminal can apply a single joint TCI state indicated via MAC-CE or DCI to the reception of control resource sets connected to all terminal-specific search spaces, the reception of PDSCH scheduled to PDCCH transmitted from said control resource set, the transmission of PUSCH, and the transmission of all PUCCH resources.

[0151] If a separate set of TCI states indicated via MAC-CE or DCI includes a DL TCI state, the terminal can apply the separate set of TCI states to the reception of control resource sets connected to all terminal-specific search spaces, and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and can apply it to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

[0152] If a separate set of TCI states indicated via MAC-CE or DCI includes one UL TCI state, the terminal can apply it to all PUSCH and PUCCH resources, and based on the previously indicated DL TCI state, it can apply it to receiving control resource sets connected to all terminal-specific search spaces, and receiving PDSCH scheduled to PDCCH transmitted from said control resource set.

[0153] If a separate set of TCI states indicated by MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to the reception of control resource sets connected to all terminal-specific search spaces and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0154] [Unified TCI state MAC-CE]

[0155] The following describes a single TCI state instruction and activation method based on an integrated TCI method. A terminal receives a PDSCH containing the following MAC-CE from a base station and, starting from the third slot after transmitting a HARQ-ACK for the PDSCH to the base station, can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information within the MAC-CE received from the base station. That is, the terminal can activate each entry of the MAC-CE received from the base station to each code point of the TCI state field in DCI format 1_1 or 1_2.

[0156] FIG. 6 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure. The meaning of each field within the MAC-CE structure may be as follows.

[0157] - Serving Cell ID (6-00): This field may indicate which serving cell the MAC-CE is to be applied to. The length of this field may be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signalings simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE may be applied to all serving cells included in one or more of the lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 that contain the serving cell indicated by this field.

[0158] - DL BWP ID (6-05): This field may indicate which DL BWP the corresponding MAC-CE applies to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator within the DCI. The length of this field may be 2 bits.

[0159] - UL BWP ID (6-10): This field may indicate which UL BWP the MAC-CE applies to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator within the DCI. The length of this field may be 2 bits.

[0160] - P i (6-15): This field can indicate whether each code point of the TCI state field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state. If P i If the value of is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the code point can include a separate DL TCI state and a separate UL TCI state. If P i If the value of is 0, it means that the corresponding i-th code point has a single TCI state, which means that the code point may contain one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0161] - D / U (6-20): This field may indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet may be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet may be a separate UL TCI state.

[0162] - TCI state ID (6-25): This field indicates a TCI state that can be identified by the upper layer signaling TCI-StateId. If the D / U field is set to 1, this field can be used to represent the TCI-StateId, which can be represented by 7 bits. If the D / U field is set to 0, the MSB (most significant bit) of this field can be considered a reserved bit, and the remaining 6 bits can be used to represent the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be enabled is 8 for joint TCI states and 16 for separate DL or UL TCI states.

[0163] - R: Represents a reserved bit and can be set to 0.

[0164] Regarding the MAC-CE structure of FIG. 6 described above, the terminal may include a third octet containing fields P1, P2, ..., P8 in FIG. 6 within the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal may perform TCI state activation using a fixed MAC-CE structure, regardless of the upper layer signaling received from the base station. As another example, regarding the MAC-CE structure of FIG. 6 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal may omit the third octet containing fields P1, P2, ..., P8 in FIG. 6. In this case, the terminal can save up to 8 bits of the payload of the corresponding MAC-CE according to the upper layer signaling set by the base station. Additionally, all D / U fields located from the fourth octet to the first bit in FIG. 6 can be considered as R fields, and all corresponding R fields can be set to 0 bits.

[0165] [CSI resource configuration]

[0166] NR has a CSI framework for directing the measurement and reporting of channel state information (CSI) from a terminal at a base station. The CSI framework of NR can be composed of at least two elements: a resource setting and a report setting, and the report setting can have a connection relationship with the resource setting by referencing at least one ID of the resource setting.

[0167] According to one embodiment of the present disclosure, a resource setting may include information related to a reference signal (RS) for a terminal to measure channel state information. A base station may set at least one resource setting for the terminal. For example, the base station and the terminal may exchange signaling information such as [Table 4] to transmit information regarding the resource setting.

[0168] [Table 4]

[0169]

[0170] In [Table 4], the signaling information CSI-ResourceConfig contains information for each resource setting. According to the signaling information, each resource setting may include a resource setting index (csi-ResourceConfigId), a BWP index (bwp-ID), a resource time-axis transmission setting (resourceType), or a resource set list (csi-RS-ResourceSetList) containing at least one resource set. The resource time-axis transmission setting may be set to aperioditic transmission, semi-persistent transmission, or periodic transmission. The resource set list may be a set containing resource sets for channel measurement or a set containing resource sets for interference measurement. If the resource set list is a set containing resource sets for channel measurement, each resource set may include at least one resource, which may be a CSI reference signal (CSI-RS) resource or an index of a synchronous / broadcast channel block (SS / PBCH block, SSB). If the resource set list is a set containing resource sets for interference measurement, each resource set may include at least one interference measurement resource (CSI interference measurement, CSI-IM).

[0171] For example, if the resource set includes CSI-RS, the base station and the terminal can exchange signaling information such as [Table 5] to transmit information about the resource set.

[0172] [Table 5]

[0173]

[0174] [Table 5] The signaling information NZP-CSI-RS-ResourceSet contains information for each resource set. According to the signaling information, each resource set contains at least information regarding the resource set index (nzp-CSI-ResourceSetId) or the set of indices of the included CSI-RS (nzp-CSI-RS-Resources), and may include information regarding the spatial domain transmission filter of the included CSI-RS resource (repetition) or part of whether the included CSI-RS resource is used for tracking (trs-Info).

[0175] CSI-RS can be the most representative reference signal included in the resource set. The base station and the terminal can exchange signaling information such as [Table 6] to transmit information regarding the CSI-RS resource.

[0176] [Table 6]

[0177]

[0178] In [Table 6], the signaling information NZP-CSI-RS-Resource contains information for each CSI-RS. The information included in the above signaling information NZP-CSI-RS-Resource may have the following meanings.

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

[0180] - resourceMapping: Resource mapping information of CSI-RS resources

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

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

[0183] - scramblingID: Scrambling index of the CSI-RS sequence

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

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

[0186] The resourceMapping included in the above signaling information NZP-CSI-RS-Resource represents resource mapping information of the CSI-RS resource and may include frequency resource element (RE) mapping, number of ports, symbol mapping, CDM type, frequency resource density, and frequency band mapping information. The number of ports, frequency resource density, CDM type, and time-frequency axis RE mapping that can be configured through this may have a value set in one of the rows of [Table 7] below.

[0187] [Table 7]

[0188]

[0189] [Table 7] shows the frequency resource density, CDM type, frequency axis, and time axis start position of the CSI-RS component RE pattern configurable according to the number of CSI-RS ports (X). ), represents the number of frequency axis REs (k') and the number of time axis REs (l') of the CSI-RS component RE pattern. The aforementioned CSI-RS component RE pattern may be a basic unit constituting a CSI-RS resource. Through Y=1+max(k') REs on the frequency axis and Z=1+max(l') REs on the time axis, the CSI-RS component RE pattern may be composed of YZ REs. When the number of CSI-RS ports is 1 port, the CSI-RS RE location can be specified without subcarrier restrictions within the PRB (Physical Resource Block), and the CSI-RS RE location can be specified by a 12-bit bitmap. When the number of CSI-RS ports is {2, 4, 8, 12, 16, 24, 32} ports and Y=2, CSI-RS RE locations can be assigned for every two subcarriers within the PRB and can be assigned by a 6-bit bitmap. When the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE locations can be assigned for every four subcarriers within the PRB and can be assigned by a 3-bit bitmap. Similarly, time axis RE locations can be assigned by a total of 14-bit bitmaps.

[0190] [CSI report configuration]

[0191] According to one embodiment of the present disclosure, a report setting may have a connection relationship with a resource setting by referencing at least one ID of the resource setting, and the resource setting(s) having a connection relationship with the report setting provide setting information including information about a reference signal for measuring channel information. When the resource setting(s) having a connection relationship with the report setting are used for measuring channel information, the measured channel information may be used for channel information reporting according to a reporting method set in the report setting having a connection relationship.

[0192] According to one embodiment of the present disclosure, the report setting may include setting information related to the CSI reporting method. For example, a base station and a terminal may exchange signaling information such as [Table 8] to transmit information regarding the report setting.

[0193] [Table 8]

[0194]

[0195]

[0196] In [Table 8], the signaling information CSI-ReportConfig contains information for each report setting. The information included in the above signaling information CSI-ReportConfig may have the following meanings.

[0197] - reportConfigId: report setting index

[0198] - carrier: Serving cell index

[0199] - resourcesForChannelMeasurement: Resource setting index for channel measurement linked to report setting

[0200] - csi-IM-ResourcesForInterference: Resource setting index containing CSI-IM resources for interference measurement that have a connection with the report setting

[0201] - nzp-CSI-RS-ResourcesForInterference: Resource setting index containing CSI-RS resources for interference measurement that have a relationship with the report setting

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

[0203] - reportQuantity: Indicates the type of channel information being reported, and may have the type of channel information when no channel report is transmitted ('none') or when channel report is transmitted ('cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RI-LI-PMI-CQI'). Here, the elements included in the type of channel information refer to 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).

[0204] - reportFreqConfiguration: Indicates whether the reported channel information includes only wideband information or information for each subband; if information for each subband is included, it can have configuration information for the subband containing the channel information.

[0205] - timeRestrictionForChannelMeasurements: Whether there are time axis constraints on the reference signal for channel measurement among the reference signals referenced by the reported channel information.

[0206] - timeRestrictionForInterferenceMeasurements: Whether there are time axis constraints on the reference signal for interference measurement among the reference signals referenced by the reporting channel information.

[0207] - codebookConfig: Codebook information referenced by the reporting channel information

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

[0209] - cqi-Table: CQI table index referenced by the reporting channel information

[0210] - subbandSize: An index indicating the subband size of the channel information

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

[0212] When a base station instructs a channel information report through upper layer signaling or L1 signaling, the terminal can perform the channel information report by referring to the above-mentioned setting information included in the instructed report setting.

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

[0214] For example, a base station may instruct a terminal to report aperiodic channel information (CSI report) via upper layer signaling or DCI using DCI format 0_1. The base station sets parameters for the terminal's aperiodic CSI report, or a plurality of CSI report trigger states, which include parameters for the CSI report, via upper layer signaling. The parameters for the CSI report or the CSI report trigger states may include a slot interval or a set of possible slot intervals between a PDCCH containing DCI and a PUSCH containing the CSI report, a reference signal ID for measuring channel state, and the type of channel information included. When the base station instructs some of the plurality of CSI report trigger states to the terminal via DCI, the terminal reports channel information according to the CSI report settings of the report settings configured in the instructed CSI report trigger states. The channel information reporting may be performed via a PUSCH scheduled in DCI format 0_1. The time-domain resource allocation of a PUSCH containing a terminal's CSI report can be achieved through the slot interval with the PDCCH indicated via the DCI, and the indication of the starting symbol and symbol length within the slot for the time-domain resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated via the slot interval with the PDCCH indicated via the DCI, and the starting symbol and symbol length within the slot can be indicated via the time domain resource assignment field of the aforementioned DCI.

[0215] For example, a base station may instruct a terminal to send a semi-persistent CSI report via PUSCH using a DCI format 0_1. The base station may activate or deactivate the semi-persistent CSI report sent via PUSCH using a DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station establishes multiple CSI report trigger states containing parameters for the terminal's semi-persistent CSI report or parameters for the semi-persistent CSI report through upper layer signaling. Parameters for a CSI report, or CSI report trigger states, may include a set of possible slot intervals or slot intervals between a PDCCH containing a DCI directing a CSI report and a PUSCH containing a CSI report, a slot interval between a slot where an upper-layer signaling directing a CSI report is activated and a PUSCH containing a CSI report, a slot interval period of the CSI report, and the type of channel information 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 via upper-layer signaling or DCI, the terminal may report channel information according to the report setting included in the directed CSI report trigger state or the CSI report setting configured in the activated report setting.The above channel information reporting can be performed through a PUSCH that is semi-continuously scheduled in DCI format 0_1 ​​scrambled with SP-CSI-RNTI. Time-axis resource allocation for a PUSCH containing a terminal's CSI report can be achieved through the slot interval period of the CSI report, the slot interval with the slot where upper-layer signaling is activated, the slot interval with the PDCCH indicated via DCI, and the indication of the start symbol and symbol length within the slot for time-axis resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated through the slot interval with the PDCCH indicated via 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.

[0216] For example, a base station may instruct a terminal to transmit a semi-persistent CSI report via PUCCH through upper-layer signaling such as MAC-CE. Through the MAC-CE signaling, the base station may activate or deactivate the semi-persistent CSI report transmitted via PUCCH. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station sets parameters for the terminal's semi-persistent CSI report through upper-layer signaling. The parameters for the CSI report may include the PUCCH resource to which the CSI report is transmitted, the slot interval period of the CSI report, and the type of channel information included. The terminal may transmit the CSI report via PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted via the PUSCH. The location of the PUCCH transmission slot containing the CSI report is indicated by the slot interval period of the CSI report set through upper-layer signaling, and the slot interval between the slot where the upper-layer signaling is activated and the PUCCH containing the CSI report. The starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper-layer signaling.

[0217] For example, a base station may instruct a terminal to issue a periodic CSI report via upper-layer signaling. The base station may enable or disable the periodic CSI report via upper-layer signaling, including RRC signaling. When the periodic CSI report is enabled, the terminal may report channel information periodically according to the set slot interval. When the periodic CSI report is disabled, the terminal may stop the periodic channel information reporting that was enabled. The base station establishes a report setting via upper-layer signaling that includes parameters for the terminal's periodic CSI report. The parameters for the CSI report may include the PUCCH resource setting for the CSI report, the slot interval between the slot where the upper-layer signaling instructing the CSI report is enabled and the PUCCH containing the CSI report, the slot interval period of the CSI report, a reference signal ID for measuring channel state, and the type of channel information included. The terminal may transmit the CSI report via the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted via the PUSCH. The slot location where the PUCCH containing the CSI report is transmitted is indicated by the slot interval period of the CSI report set through upper-layer signaling, and the slot interval between the slot where the upper-layer signaling is activated and the PUCCH containing the CSI report; furthermore, the starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper-layer signaling.

[0218] Regarding the aforementioned CSI report settings (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with a single downlink (DL) bandwidth portion identified by the upper-layer parameter bandwidth portion identifier (bwp-id) given by the CSI-ResourceConfig, which is associated with the corresponding report setting. As for the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, and these can be configured from the base station to the terminal by the reportConfigType parameter set from the upper layer. Semi-Persistent CSI reporting methods support 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. In the case of a periodic or semi-continuous CSI reporting method, the terminal may receive a PUCCH or PUSCH resource to transmit the CSI from the base station via upper layer signaling. The period and slot offset of the PUCCH or PUSCH resource to transmit the CSI may be given as the numerology of the uplink (UL) bandwidth portion configured for transmitting the CSI report. In the case of a non-periodic CSI reporting method, the terminal may receive a PUSCH resource to transmit the CSI scheduled from the base station via L1 signaling (the aforementioned DCI format 0_1).

[0219] Regarding the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig is S( 1) It may include CSI resource sets (given by the upper-level parameter csi-RS-ResourceSetList). The CSI resource set list may consist of non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or may consist of CSI-interference measurement (CSI-IM) resource sets. Each CSI resource setting may be located in a downlink (DL) bandwidth portion identified by the upper-level parameter bwp-id, and the CSI resource setting may be associated with a CSI reporting setting in the same downlink bandwidth portion. The time domain operation of the CSI-RS resources within the CSI resource setting may be set to one of 'non-periodic', 'periodic', or 'semi-continuous' by the upper-level parameter resourceType. For periodic or semi-continuous CSI resource settings, the number of CSI-RS resource sets may be limited to S=1, and the set period and slot offset may be given by the numerology of the downlink bandwidth portion identified by bwp-id. The terminal may receive one or more CSI resource settings for channel or interference measurement from the base station via upper layer signaling, and may include, for example, the following CSI resources.

[0220] - CSI-IM resources for interference measurement

[0221] - NZP CSI-RS resources for interference measurement

[0222] - NZP CSI-RS resources for channel measurement

[0223] For CSI-RS resource sets associated with a resource setting where the upper-level parameter resourceType is set to 'Aperiodic', 'Periodic', or 'Semi-persistent', the Trigger State for a CSI reporting setting where reportType is set to 'Aperiodic' and the resource setting for channel or interference measurements for one or more component cells (CC) can be set as the upper-level parameter CSI-AperiodicTriggerStateList.

[0224] Non-periodic CSI reporting of the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-continuous CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after being activated by the MAC control element (MAC CE). As described above, CSI resource settings can also be configured non-periodic, periodic, or semi-continuous. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 9] below.

[0225] [Table 9] Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations

[0226]

[0227] Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1, which corresponds to the scheduling DCI for PUSCH. The terminal can monitor PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicators for PUSCH. The CSI request indicator can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by the upper layer signaling (reportTriggerSize). One trigger state among one or more aperiodic CSI reporting trigger states that can be set by the upper layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0228] - If all bits of the CSI request field are 0, this may mean that a CSI report is not requested.

[0229] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, then M CSI trigger states can be mapped to 2NTs-1 according to the selected mapping relationship, and one of the trigger states of 2NTs-1 can be indicated as a CSI request field.

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

[0231] The following [Table 10] shows an example of the relationship between CSI request indicators and CSI trigger states that can be indicated by those indicators.

[0232] [Table 10]

[0233]

[0234] For a CSI resource within a CSI trigger state triggered by a CSI request field, the terminal can perform a measurement and generate a CSI therefrom (including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP, etc.). The terminal can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the uplink data (UL-SCH) and the acquired CSI can be multiplexed and transmitted to the PUSCH resource scheduled by DCI format 0_1. If the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", CSI can be mapped and transmitted without uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0235] Figure 7 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0236] In one example (700) of FIG. 7, the terminal can monitor the PDCCH (701) to obtain the DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (705). The terminal can obtain resource information for the CSI-RS (702) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform a measurement on the CSI-RS (702) resource being transmitted based on the time when it receives the DCI format 0_1 ​​and the parameter for the offset within the CSI resource set setting (e.g., the aperiodicTriggeringOffset mentioned above) in the NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet). More specifically, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set setting as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the aperiodic CSI report is received and the slot in which the 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.

[0237] [Table 11]

[0238]

[0239] In one example (700) of FIG. 7, an example is shown in which the aforementioned offset value is set to X=0. In this case, the terminal can receive CSI-RS (702) in a slot (corresponding to slot 0 (706) in FIG. 7) that receives DCI format 0_1 ​​that triggers a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (705). The terminal can obtain scheduling information for PUSCH (705) for CSI reporting (information corresponding to each field of the aforementioned DCI format 0_1) from DCI format 0_1. For example, the terminal can obtain information about the slot to transmit PUSCH (705) from the aforementioned time domain resource allocation information for PUSCH (705) included in DCI format 0_1. In one example (700) of FIG. 7, the terminal obtains a K2 (704) value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and accordingly, at the time when PUSCH (705) receives PDCCH (701), it can be transmitted from slot 3 (709), which is 3 slots away from slot 0 (706).

[0240] In one example (710) of FIG. 7, the terminal can monitor PDCCH (711) in slot 0 (716) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (715). The terminal can obtain resource information for CSI-RS (712) to be measured from the received CSI request indicator. One example (710) of FIG. 7 shows an example in which the offset (713) value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive CSI-RS (712) in the next slot (corresponding to slot 1 (717) in FIG. 7) of the slot in which DCI format 0_1 ​​triggering a non-periodic CSI report was received, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (715).

[0241] Aperiodic CSI reports may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI reports are transmitted via PUSCH, they may be multiplexed with the transport block. For multiplexing, a CRC is inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The above 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 during the multiplexing of CSI part 1 or CSI part 2 included in the aperiodic CSI reports can be calculated as shown in [Table 12] below.

[0242] [Table 12]

[0243]

[0244]

[0245] In particular, for PUSCH repetition transmission methods A and B, the terminal can transmit aperiodic CSI reports by multiplexing them only during the first repetition of the PUSCH repetition. This is because the aperiodic CSI report information being multiplexed is encoded in a polar code format, and for it to be multiplexed across multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. Specifically, in the case of PUSCH repetition type B, since each actual repetition can have a different OFDM symbol length, the aperiodic CSI reports can be multiplexed and transmitted only during the first PUSCH repetition.

[0246] Additionally, for PUSCH repeat transmission method B, if the terminal receives a DCI that schedules aperiodic CSI reporting without scheduling for the transport block or enables semi-continuous CSI reporting, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repeat transmissions set by the upper layer signaling is greater than 1. Additionally, if the terminal schedules or enables aperiodic or semi-continuous CSI reporting without scheduling for the transport block based on PUSCH repeat transmission method B, the terminal may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including semi-continuous CSI based on PUSCH repeat transmission method B without scheduling for the DCI after semi-continuous CSI reporting is enabled by the DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0247] [CSI computation time]

[0248] When a base station instructs a terminal to provide an aperiodic CSI report or a semi-persistent CSI report via DCI, the terminal can determine whether it can perform a valid channel report through the instructed CSI report by considering the channel computation time required for the CSI report. For the aperiodic CSI report or semi-persistent CSI report instructed via DCI, the terminal can perform a valid CSI report starting from the uplink symbol after the Z symbol, after the last symbol included in the PDCCH containing the DCI instructing the CSI report has ended. The aforementioned Z symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH containing the DCI instructing the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type or characteristics of the channel information reported in the CSI report (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.). In other words, for a CSI report to be determined as a valid CSI report (for the CSI report to be valid), the uplink transmission of the CSI report, including the timing advance, must not be performed before the Zref symbol. In this case, the Zref symbol is time from the moment the last symbol of the aforementioned triggering PDCCH ends. It is an uplink symbol that initiates the CP (cyclic prefix). Here, the detailed value of Z follows the explanation below, , Hz, , , and is numerology. At this time Is The largest of them It can be promised to use something that causes a value, is the subcarrier interval used for PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, can refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example Is The largest of them It is also possible to promise to use something that causes a value. and Refer to the explanation above for the definition. For convenience of future explanation, satisfying the above conditions will be referred to as satisfying CSI reporting validity condition 1.

[0249] Furthermore, if the reference signal for channel measurement regarding the aperiodic CSI report instructed to the terminal via the DCI is an aperiodic reference signal, a valid CSI report can be executed starting from the uplink symbol following the Z' symbol after the end of the last symbol containing the reference signal. The aforementioned Z' symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH containing the DCI instructing the CSI report, the numerology of the bandwidth corresponding to the reference signal for channel measurement regarding the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type or characteristics of the channel information reported in the CSI report (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.). In other words, for a CSI report to be determined as a valid CSI report (for the CSI report to be a valid CSI report), the uplink transmission of the CSI report, including the timing advance, must not be executed before the Zref' symbol. At this time, the Zref' symbol is time from the moment the last symbol of the non-periodic CSI-RS or non-periodic CSI-IM triggered by the aforementioned triggering PDCCH ends. It is an uplink symbol that initiates the CP (cyclic prefix). Here, the detailed value of Z' follows the explanation below, , Hz, , , and is numerology. At this time Is The largest of them It can be promised to use something that causes a value, is the subcarrier interval used for triggering PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, can refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example, Is The largest of them It can be promised to use what causes a value. In this case, and Refer to the explanation above for the definition. For convenience of future explanation, satisfying the above conditions will be referred to as satisfying CSI reporting validity condition 2.

[0250] If a base station instructs a terminal to perform an aperiodic CSI report on an aperiodic reference signal via DCI, the terminal may perform a valid CSI report starting from the first uplink symbol that satisfies both the time point Z after the end of the last symbol included in the PDCCH containing the DCI instructing the CSI report and the time point Z' after the end of the last symbol containing the reference signal. That is, in the case of aperiodic CSI reporting based on an aperiodic reference signal, it is determined to be a valid CSI report only if it satisfies both CSI reporting validity conditions 1 and 2.

[0251] If the timing of the CSI report instructed by the base station does not satisfy the CSI computation time requirements, the terminal may determine that the CSI report is invalid and not consider updating the channel information status for the CSI report.

[0252] The Z and Z' symbols for the aforementioned CSI computation time calculation follow [Table 13] and [Table 14] below. For example, if the channel information reported in the CSI report includes only wideband information, the number of reference signal ports is 4 or less, there is one reference signal resource, the codebook type is 'type I-SinglePanel', or the type of reported channel information (report quantity) is 'cri-RI-CQI', the Z and Z' symbols are those in [Table 14]. It follows the value. This will be named Delay Requirement 2 in the future. In addition, if the PUSCH containing the CSI report does not contain a TB or HARQ-ACK and the terminal's CPU occupation is 0, the Z and Z' symbols are from [Table 13]. It follows the value and is named Delay Requirement 1. The explanation regarding the aforementioned CPU occupation is described in detail below. Additionally, if the report quantity is 'cri-RSRP' or 'ssb-Index-RSRP', the Z and Z' symbols are from [Table 14]. Follows the values. X1, X2, X3, and X4 in [Table 14] represent the terminal's capability (UE capability) regarding beam reporting time, and KB1 and KB2 in [Table 14] represent the terminal's capability regarding beam switching time. In cases where the type or characteristic of channel information reported in the aforementioned CSI report does not apply, the Z and Z' symbols are [Table 14] Follows the value.

[0253] [Table 13]

[0254]

[0255] [Table 14]

[0256]

[0257] [CSI reference resource]

[0258] When a base station instructs a terminal to issue an aperiodic / semi-persistent / periodic CSI report, it may set a CSI reference resource to determine the reference time and frequency for the channel to be reported in the CSI report. The frequency of the CSI reference resource may be the carrier and subband information to be measured for the CSI, as specified in the CSI report configuration, and may correspond to the carrier and reportFreqConfiguration, respectively, within the upper-layer signaling CSI-ReportConfig. The time of the CSI reference resource may be defined based on the time at which the CSI report is transmitted. For example, if 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 for CSI report #X may be defined as the downlink slot n-nCSI-ref of the carrier and BWP measuring the CSI. When downlink slot n is named μDL for the numerology of the carrier and BWP measuring CSI, and μUL for the numerology of the carrier and BWP transmitting CSI report #X It is calculated as follows. nCSI-ref, the slot interval between downlink slot n and the CSI reference signal, depends 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, if a single CSI-RS / SSB resource is connected to the said CSI report If it follows and multiple CSI-RS / SSB resources are connected to the relevant CSI report Follows. If the CSI report #X transmitted in uplink slot n' is an aperiodic CSI report, considering the CSI computation time Z' for channel measurement It is calculated as. The aforementioned is the number of symbols included in a slot, and in NR Assume =14.

[0259] When a base station instructs a terminal to transmit a CSI report in uplink slot n' via upper layer signaling or DCI, the terminal may report a CSI by performing channel measurement or interference measurement on a CSI-RS resource, CSI-IM resource, or SSB resource associated with the CSI report that is transmitted no later than the CSI reference resource slot of the CSI report transmitted in uplink slot n'. The CSI-RS resource, CSI-IM resource, or SSB resource associated with the above-mentioned CSI report may refer to 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, or a CSI-RS resource, CSI-IM resource, or SSB resource referenced by a CSI report trigger state containing parameters for the CSI report, or a CSI-RS resource, CSI-IM resource, or SSB resource pointed to by an ID of a reference signal (RS) set.

[0260] In embodiments of the present disclosure, a CSI-RS / CSI-IM / SSB occasion refers to the transmission time of a CSI-RS / CSI-IM / SSB resource(s) determined by an upper layer setting or a combination of an upper layer setting and DCI triggering. For example, for a semi-persistent or periodic CSI-RS resource, the slot to be transmitted is determined by the slot period and slot offset set by the upper layer signaling, and the transmitted symbol(s) within the slot are determined by the resource mapping information. For another example, for an aperiodic CSI-RS resource, the slot to be transmitted is determined by the slot offset with the PDCCH containing the DCI indicating channel reporting set by the upper layer signaling, and the transmitted symbol(s) within the slot are determined by the resource mapping information.

[0261] The aforementioned CSI-RS occasion can 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 the resource set; accordingly, the following two interpretations are possible for the CSI-RS occasion according to each resource set setting.

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

[0263] - Interpretation 1-2: Among all CSI-RS resources included in the resource set(s) configured in the resource setting referenced by the report setting configured for the CSI report, from the start time of the earliest symbol transmitted by the earliest transmitted CSI-RS resource to the end time of the latest symbol transmitted by the latest transmitted CSI-RS resource

[0264] In the embodiments of the present disclosure below, it is possible to individually apply both interpretations of the CSI-RS occasion. Additionally, while it is possible to consider both interpretations for the CSI-IM occasion and the SSB occasion, just as with the CSI-RS occasion, the principle is similar to the explanation above, so redundant explanations will be omitted below.

[0265] In embodiments of the present disclosure, 'CSI-RS / CSI-IM / SSB occasion for CSI report #X transmitted in uplink slot n'' refers to a set of CSI-RS occasions, CSI-IM occasions, and SSB occasions among the CSI-RS resource, CSI-IM resource, and SSB resource CSI-RS occasions, CSI-IM occasions, and SSB occasions included in the resource set of the resource setting referenced by the report setting set for CSI report #X, which are not later than the CSI reference resource of CSI report #X transmitted in uplink slot n'.

[0266] 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 be interpreted in the following two ways.

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

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

[0269] In the embodiments of the present disclosure below, it is possible to apply individually by considering 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’. Additionally, when considering the two interpretations (interpretation 1-1, interpretation 1-2) described above for the CSI-RS occasion, CSI-IM occasion, and SSB occasion, 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 be applied individually by considering all 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).

[0270] The base station may instruct a CSI report by considering the amount of channel information that the terminal can simultaneously calculate for the CSI report, that is, the number of the terminal's channel information processing units (CSI processing units, CPUs). The number of channel information processing units that the terminal can simultaneously calculate If so, the terminal If you do not expect CSI report instructions from base stations that require more channel information calculations, or Updates to channel information that require more channel information calculations may not be considered. The terminal can report to the base station via upper layer signaling, or the base station can set it via upper layer signaling.

[0271] The CSI report instructed by the base station to the terminal is the total number of channel information that the terminal can calculate simultaneously. It is assumed that some or all of the CPU is occupied for channel information calculation. For each CSI report, for example, CSI report The number of channel information calculation units required for If so, the number of channel information calculation units required for a total of N CSI reports is It can be said that the calculation unit of channel information required per reportQuantity set in the CSI report can be set as follows [Table 15].

[0272] [Table 15]

[0273]

[0274] The number of channel information calculations required by the terminal for multiple CSI reports at a specific point in time is the number of channel information calculation units that the terminal can calculate simultaneously. In more cases, the terminal may not consider updating channel information for some CSI reports. Among multiple directed CSI reports, the CSI reports for which channel information updates are not considered are determined by taking into account at least the time the calculation of channel information required for the CSI report occupies the CPU and the priority of the reported channel information. For example, it may not consider updating channel information for a CSI report where the calculation of channel information required for the CSI report starts at the latest time, and it is possible to prioritize not considering channel information updates for CSI reports with lower channel information priority.

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

[0276] [Table 16]

[0277]

[0278] The CSI priority for a CSI report is determined by the priority value PriiCSI(y,k,c,s) in [Table 16]. Referring to [Table 16], the CSI priority value is determined by the type of channel information included in the CSI report, the time-axis reporting characteristics of the CSI report (aperiodic, semi-persistent, periodic), the channel through which the CSI report is transmitted (PUSCH, PUCCH), the serving cell index, and the CSI report configuration index. The CSI priority for a CSI report is determined by comparing the priority value PriiCSI(y,k,c,s) and judging that the CSI report with the smaller priority value has a higher CSI priority.

[0279] If CPU occupation time is defined as the time the CPU is occupied by calculating channel information required for the CSI report instructed by the base station to the terminal, then CPU occupation time is determined by considering 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 slots or symbols occupied by the upper-layer signaling or DCI instructing the CSI report, and part or all of the slots or symbols occupied by the reference signal for channel state measurement.

[0280] [PDCCH: DCI related]

[0281] Next, we will explain downlink control information (DCI) in 5G systems in detail.

[0282] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0283] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

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

[0285] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 17] below.

[0286] [Table 17]

[0287]

[0288] DCI format 0_1 ​​can be used as a non-defense 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 may include, for example, the information in [Table 18] below.

[0289] [Table 18]

[0290]

[0291]

[0292] DCI format 1_0 can be used as a countermeasure 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 may include, for example, the information in [Table 19] below.

[0293] [Table 19]

[0294]

[0295] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 20] below.

[0296] [Table 20]

[0297]

[0298]

[0299] [PDCCH: CORESET, REG, CCE, Search Space]

[0300] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0301] FIG. 8 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 8 illustrates an example in which two control resources (control resource #1 (801), control resource #2 (802)) are set within a terminal bandwidth part (UE bandwidth part) (810) on the frequency axis and one slot (820) on the time axis. The control resources (801, 802) can be set in a specific frequency resource (803) within the entire terminal bandwidth part (810) on the frequency axis. On the time axis, they can be set with one or more OFDM symbols and can be defined as the control resource set duration (Control Resource Set Duration, 804). Referring to the example illustrated in FIG. 8, control resource #1 (801) is set with a control resource length of 2 symbols, and control resource #2 (802) is set with a control resource length of 1 symbol.

[0302] The control domain 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 domain to the terminal means providing information such as the control domain identifier (Identity), the frequency location of the control domain, and the symbol length of the control domain. For example, it may include the information in [Table 21] below.

[0303] [Table 21]

[0304]

[0305] 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 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 area.

[0306] FIG. 9 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. According to FIG. 9, the basic unit of time and frequency resources that constitute a control channel can be called a REG (Resource Element Group, 903), and the REG (903) can be defined as 1 OFDM symbol (901) on the time axis and 1 PRB (Physical Resource Block, 902) on the frequency axis, that is, 12 subcarriers. A base station can concatenate REGs (903) to form a downlink control channel allocation unit.

[0307] As illustrated in FIG. 9, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 904), then 1 CCE (904) can be composed of multiple REGs (903). For example, if the REG (903) illustrated in FIG. 9 is described, the REG (903) can be composed of 12 REs, and if 1 CCE (904) is composed of 6 REGs (903), then 1 CCE (904) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (904), and a specific downlink control channel can be mapped to one or multiple CCEs (904) and transmitted according to the Aggregation Level (AL) within the control area. The CCEs (904) in the control area are distinguished by numbers, and the numbers of the CCEs (904) can be assigned according to a logical mapping method.

[0308] The basic unit of the downlink control channel, namely the REG (903) illustrated in FIG. 9, may include both the REs to which the DCI is mapped and the DMRS (905), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 9, three DMRS (905) may be transmitted within one REG (903). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the Aggregation Level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode at a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0309] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a pre-arranged set of CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0310] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control domain index to be monitored in the search space. For example, the information in [Table 22] below may be included.

[0311] [Table 22]

[0312]

[0313]

[0314] According to the configuration information, the base station may set one or multiple sets of search spaces for the terminal. According to some embodiments, the base station may set search space set 1 and search space set 2 for the terminal, and may set DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and may set DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in a terminal-specific search space.

[0315] According to the configuration information, one or more sets of search spaces 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 configured as a common search space, and Search Space Set #3 and Search Space Set #4 may be configured as a terminal-specific search space.

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

[0317] - 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

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

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

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

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

[0322] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

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

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

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

[0326] - C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0327] - TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0328] - CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0329] - RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

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

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

[0332] - INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing.

[0333] - TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0334] - TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0335] - TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

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

[0337] [Table 23]

[0338]

[0339] In 5G, the search space of aggregation level L in the control domain p and search space set s can be expressed as [Equation 1] below.

[0340] [Mathematical Formula 1]

[0341]

[0342] The value may be 0 for the common search space.

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

[0344] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., parameters in [Table 22]), the set of search space sets monitored by the terminal at each point in time may vary. For example, if search space set #1 is configured for an X-slot period and search space set #2 is configured for a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0345] [PDSCH / PUSCH: Regarding Frequency Resource Allocation]

[0346] Next, Frequency Domain Resource Assignment (FDRA) for PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) in NR is explained.

[0347] FIG. 10 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.

[0348] FIG. 10 is a diagram illustrating three frequency axis resource allocation methods, FDRA type 0 (1000), FDRA type 1 (1005), and dynamic switch (1010), which can be configured through an upper layer in an NR wireless communication system.

[0349] Referring to FIG. 10, if the terminal is configured to use only FDRA type 0 through upper layer signaling (1000), some downlink control information (DCI) for scheduling PDSCH or PUSCH to the terminal is N RBGIt includes a bitmap composed of bits. The conditions for this will be explained again later. In this case, N RBG This refers to the number of RBGs (resource block groups) determined as shown in [Table 24] below, based on the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0350] [Table 24]

[0351]

[0352] The size of the frequency resource in the bandwidth portion can be defined by the number of RBs included in the bandwidth portion. More specifically, if a terminal is instructed to allocate an FDRA type-0 resource, the length of the FDRA field of the DCI received by the terminal is the number of RBGs (N) within the bandwidth portion. RBG It is the same as ), is. Here, the first RBG within the bandwidth portion is It includes RBs, and the last RBG within the bandwidth portion is If, Includes RBs, and otherwise, It includes RBs. The remaining RBGs within the bandwidth portion include P RBs. Here, P is the number of nominal RBGs determined according to [Table 24] above.

[0353] If the terminal is configured to use only FDRA type 1 through upper layer signaling (1005), the DCI that assigns PDSCH or PUSCH to the terminal is It includes frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the bandwidth portion. Through this, the base station can set the starting VRB (1020) and the length (1025) of the frequency axis resources continuously allocated from it.

[0354] If the terminal is configured to use both FDRA type-0 resource allocation and FDRA type-1 resource allocation through upper layer signaling (1010), some DCIs that allocate PDSCH / PUSCH to the terminal include frequency axis resource allocation information consisting of bits of the larger value (1035) of the payload (1015) for setting FDRA type-0 resource allocation and the payload (1020, 1025) for setting FDRA type-1 resource allocation. The conditions for this will be explained later. At this time, one bit (1030) may be added to the first part (MSB) of the frequency axis resource allocation information within the DCI, and if the bit has a value of '0', it indicates that FDRA type-0 resource allocation is used, and if it has a value of '1', it indicates that FDRA type-1 resource allocation is used.

[0355] If the terminal has received an FDRA type-2 resource allocation method through upper layer signaling, the terminal may receive instructions from the base station regarding the FDRA type-2 resource allocation method according to the following method.

[0356] The terminal can receive RB allocation information from the base station in the form of M interlace index sets.

[0357] Interlaced index is common RB It can be composed of , and M can be defined as in [Table 25].

[0358] [Table 25]

[0359]

[0360] RB in interlaced m and bandwidth portion i and common RB The relationship with can be defined as follows.

[0361] ■

[0362] ■ where is the common resource block where bandwidth part starts relative to common resource block 0. u is subcarrier spacing index

[0363] When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlaced set can be notified from the base station to the terminal using m0 + l indices. Additionally, the resource allocation field can be composed of a Resource Inclusion Value (RIV). The Resource Inclusion Value , When, the starting interlace m0 and consecutive interlace numbers It can be composed of, and the value is as follows.

[0364]

[0365] The resource indicator value When that, the resource indicator value consists of the start interlaced index m0 and l values ​​and can be configured as shown in [Table 26].

[0366] [Table 26]

[0367]

[0368] When the subcarrier spacing is 30 kHz (u=1), RB allocation information can be notified from the base station to the terminal in the form of a bitmap indicating the interlaces allocated to the terminal. The size of the bitmap is M, and each bit of the bitmap corresponds to an interlace. The order of the interlace bitmap can be mapped from the MSB to the LSB from interlace index 0 to M-1.

[0369] In addition, the least significant bit (LSB) of the FDRA field for 15kHz and 30kHz can represent a consecutive set of RBs of PUSCH scheduled in DCI format 0_1. The Y bit can be composed of a resource indication value (RIVRBset). , In this case, the RIVRBset value is the starting RB set ( ) and the number of consecutive RB sets ( It can be determined as ). The RIVRBset value can be defined as follows.

[0370]

[0371] represents the number of RB sets included within the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set to upper signaling (or pre-set).

[0372] [PDSCH / PUSCH: Time Resource Allocation]

[0373] The following describes a time-domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems).

[0374] The base station may set a table for time domain resource allocation information for the downlink data channel (PDSCH) and uplink data channel (PUSCH) for the terminal using upper layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of a maximum of maxNrofDL-Allocations = 16 entries may be set, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 16 entries may be set. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the starting symbol for which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH or PUSCH. For example, information such as [Table 27] or [Table 28] below may be transmitted from the base station to the terminal.

[0375] [Table 27]

[0376]

[0377] [Table 28]

[0378]

[0379] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

[0380] FIG. 11 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0381] Referring to FIG. 11, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and control channel. PDSCH , μ PDCCH The time axis position of the PDSCH resource can be indicated according to the scheduling offset (K0) value, and the OFDM symbol start position (1100) and length (1105) within one slot (1110) that are dynamically indicated through DCI.

[0382] [PUSCH: Regarding transmission method]

[0383] Next, the scheduling method for PUSCH transfers is described. PUSCH transfers can be dynamically scheduled by UL grants within the DCI, or operated by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transfers can be provided in DCI format 0_0 or 0_1.

[0384] Configured grant Type 1 PUSCH transmissions can be semi-statically configured by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 29], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 29], through the upper signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied through configuredGrantConfig, the upper signaling of [Table 29], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 30]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 29], the terminal applies tp-pi2BPSK in pusch-Config of [Table 30] to PUSCH transmissions operated by the configured grant.

[0385] [Table 29]

[0386]

[0387]

[0388] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config in [Table 30], the upper signaling, is 'codebook' or 'nonCodebook'.

[0389] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured by a configured grant. If a terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the terminal-specific PUCCH resource corresponding to the minimum ID within the active uplink BWP in the serving cell, wherein the PUSCH transmission is based on a single antenna port. The terminal does not expect scheduling for a PUSCH transmission via DCI format 0_0 within a BWP where the PUCCH resource containing pucch-spatialRelationInfo is not configured. If the terminal has not been configured with txConfig in pusch-Config of [Table 30], the terminal does not expect to be scheduled via DCI format 0_1.

[0390] [Table 30]

[0391]

[0392] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured via a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the terminal determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (number of PUSCH transmission layers).

[0393] In this case, the SRI can be configured via the SRS resource indicator field within the DCI or via the higher-level signaling srs-ResourceIndicator. When transmitting a codebook-based PUSCH, the terminal receives at least one SRS resource and can receive up to two. When the terminal receives an SRI via the DCI, the SRS resource indicated by that SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing that SRI. Additionally, the TPMI and transmission rank can be configured via the precoding information and number of layers field within the DCI or via the higher-level signaling precodingAndNumberOfLayers. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the terminal receives one SRS resource, the TPMI is used to indicate the precoder to be applied from that one configured SRS resource. If the terminal is configured with multiple SRS resources, TPMI is used to specify the precoder to be applied to the SRS resource indicated by SRI.

[0394] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0395] A terminal may receive one SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set may be indicated via SRI. If multiple SRS resources are set in the SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0396] The terminal transmits one or more SRS resources included in an SRS resource set in which the usage value is set to 'codebook' according to the upper signaling to the base station, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, the SRI is used as information to select the index of one SRS resource, and the said SRI is included in the DCI. Additionally, the base station includes information in the DCI that instructs the terminal to use the TPMI and rank for PUSCH transmission. The terminal performs PUSCH transmission using the SRS resource instructed by the said SRI, by applying the instructed rank based on the transmit beam of the corresponding SRS resource and the precoder instructed by the TPMI.

[0397] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can be semi-statically configured by configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission scheduled via DCI format 0_1.

[0398] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than 42 symbols, the terminal does not expect the information for the precoder for SRS transmission to be updated.

[0399] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the corresponding DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

[0400] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal does not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

[0401] When a terminal is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI. In this case, the SRI can be indicated via the field SRS resource indicator within the DCI or configured via the higher-level signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously within the same symbol in a single SRS resource set, as well as the maximum number of SRS resources, are determined based on the UE capability reported by the terminal to the base station. In this case, SRS resources transmitted simultaneously by the terminal occupy the same RB. The terminal configures one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0402] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result of measuring the received NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, it applies the calculated precoder, and the base station selects one or more SRS resources from among the received one or more SRS resources. At this time, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the SRI is included within the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied for SRS resource transmission to each layer.

[0403] [PUSCH: Preparation Process Time]

[0404] Next, the PUSCH preparation procedure time is described. When a base station schedules a terminal to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the terminal may require PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method specified through the DCI (transmission precoding method of the SRS resource, number of transmission layers, spatial domain transmission filter). In NR, the PUSCH preparation procedure time has been defined taking this into account. The terminal's PUSCH preparation procedure time may follow [Equation 2] below.

[0405] [Mathematical Formula 2]

[0406]

[0407] T mentioned above in [Mathematical Formula 2] proc,2 In this, each variable can have the following meanings.

[0408] - N2: A number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the terminal's capability. If the terminal processing capability is reported as 1 according to the terminal's capability report, it has the value of [Table 31], and if the terminal processing capability is reported as 2 and the ability to use terminal processing capability 2 is set through upper layer signaling, it may have the value of [Table 32].

[0409] [Table 31]

[0410]

[0411] [Table 32]

[0412]

[0413] - d 2,1 : The number of symbols determined as 0 if the resource elements of the first OFDM symbol of the PUSCH transmission are all configured to consist only of DM-RS, and 1 otherwise.

[0414] - : 64

[0415] - μ: or Middle, T proc,2 It follows the value that becomes larger. represents the numerology of the downlink through which a PDCCH containing a DCI that schedules the PUSCH is transmitted, and represents the numerology of the uplink through which PUSCH is transmitted.

[0416] - T c : , Hz, has.

[0417] - d 2,2 : If the DCI scheduling PUSCH directs BWP switching, follow the BWP switching time; otherwise, have 0.

[0418] - d2: If the OFDM symbols of PUCCH, PUSCH with a higher priority index, and PUCCH with a lower priority index overlap in time, the d2 value of PUSCH with the higher priority index is used. Otherwise, d2 is 0.

[0419] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext It can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0420] - T switch : T when the uplink switching interval is triggered switch is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0421] When the base station and terminal consider the time-axis resource mapping information of the PUSCH scheduled via DCI and the influence of uplink-downlink timing advances, from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, T proc,2 Subsequently, if the first symbol of the PUSCH starts before the first uplink symbol initiated by the CP, it is determined that the PUSCH preparation time is insufficient. Otherwise, the base station and the terminal determine that the PUSCH preparation time is sufficient. If the preparation time is sufficient, the terminal transmits the PUSCH; if the preparation time is insufficient, it may ignore the DCI scheduling the PUSCH.

[0422] [PUSCH: Repetitive transmission related]

[0423] The following describes in detail the repetitive transmission of uplink data channels in 5G systems. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can receive either PUSCH repetitive transmission type A or B as a setting for upper layer signaling.

[0424] 1. PUSCH Repeated Transmission Type A

[0425] - As described above, the symbol length of the uplink data channel and the position of the start symbol are determined by a time domain resource allocation method within a single slot, and the base station can notify the terminal of the number of repeated transmissions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0426] - Based on the number of repeated transmissions received from the base station, the terminal may repeatedly transmit an uplink data channel in consecutive slots that has the same length and starting symbol as the uplink data channel configured. In this case, if the slot configured by the base station for the terminal as a downlink, or if at least one of the symbols of the uplink data channel configured for the terminal is configured as a downlink, the terminal omits the transmission of the uplink data channel, but counts the number of repeated transmissions of the uplink data channel. That is, the uplink data channel may not be transmitted, even though it is included in the number of repeated transmissions of the uplink data channel. On the other hand, a terminal supporting Rel-17 uplink data repeated transmission determines a slot where uplink data repeated transmission is possible as an available slot, and can count the number of transmissions when the uplink data channel is repeatedly transmitted in a slot determined to be an available slot. If the uplink data channel repeated transmission is omitted in a slot determined to be an available slot, the terminal may not count the omitted repeated transmission and may perform the uplink transmission after postponing it until the next available slot.

[0427] - The following method may be used to determine the above available slot. If at least one symbol set for time domain resource allocation (TDRA) for PUSCH in a slot for PUSCH transmission overlaps with a symbol for a purpose other than uplink transmission (e.g., a downlink symbol), the slot is determined to be an unavailable slot (e.g., a slot that is not an available slot and is determined to be unavailable for PUSCH transmission). Additionally, the available slot may be considered as an uplink resource for determining the resources for PUSCH transmission and the transport block size (TBoMS) in repeated PUSCH transmission and multi-slot PUSCH transmission consisting of a single TB.

[0428] 2. PUSCH Repeated Transmission Type B

[0429] - As described above, the start symbol and length of the uplink data channel are determined by a time domain resource allocation method within a single slot, and the base station can notify the terminal of the number of repetitions through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0430] - Based on the start symbol and length of the uplink data channel configured first, the nominal repetition of the uplink data channel is determined as follows. The slot where the nth nominal repetition starts is The symbol given by and starting in that slot is It is given by. The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is It is given by, where n=0,..., numberofrepetitions-1 and S represents the starting symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel. indicates the slot where the PUSCH transmission starts. represents the number of symbols per slot.

[0431] - For PUSCH repeat transmission type B, the terminal may determine a specific OFDM symbol as an invalid symbol in the following cases.

[0432] ○ Symbols configured for downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated may be determined as invalid symbols for PUSCH repeat transmission type B.

[0433] ○ Symbols designated as ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, which is an upper layer signaling, for receiving SSB in the unpaired spectrum (TDD spectrum) may be determined as invalid symbols for PUSCH repeated transmission type B.

[0434] ○ Symbols indicated by pdcch-ConfigSIB1 within the MIB to transmit a control resource set associated with a Type0-PDCCH CSS set in the unpaired spectrum (TDD spectrum) may be determined as invalid symbols for PUSCH repeat transmission type B.

[0435] ○ In the unpaired spectrum (TDD spectrum), if the upper layer signaling numberOfInvalidSymbolsForDL-UL-Switching is configured, the symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated may be determined as invalid symbols for numberOfInvalidSymbolsForDL-UL-Switching.

[0436] - Additionally, an invalid symbol may be set in an upper layer parameter (e.g., InvalidSymbolPattern). The upper layer parameter (e.g., InvalidSymbolPattern) may provide a symbol-level bitmap spanning one or two slots, and an invalid symbol may be set based on the upper layer parameter (e.g., InvalidSymbolPattern). In the bitmap, 1 represents an invalid symbol. Additionally, the periodicity and pattern of the bitmap may be set through an upper layer parameter (e.g., periodicityAndPattern). If the upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If a higher-level parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies an invalid symbol pattern.

[0437] After an invalid symbol is determined, for each nominal repetition, the terminal may consider symbols other than the invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition contains a consecutive set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot. If the OFDM symbol length of the nominal repetition is not 1, and the length of the actual repetition becomes 1, the terminal may ignore transmission for that actual repetition.

[0438] FIG. 12 is a diagram illustrating a method for determining an available slot when transmitting a PUSCH repetition type A of a terminal in a 5G system according to one embodiment of the present disclosure.

[0439] When a base station sets uplink resources through upper layer signaling (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) or L1 signaling (e.g., dynamic slot format indicator), the base station and the terminal can determine available slots for the set uplink resources according to the following two methods.

[0440] - Method for determining available slots based on TDD configuration

[0441] - Method for determining available slots considering TDD configuration, time domain resource allocation (TDRA), CG (Configured Grant) configuration, or activation DCI

[0442] As an example of a method for determining available slots based on TDD configuration, in FIG. 12, when the TDD configuration is set to 'DDFUU' through upper layer signaling, the base station and the terminal can determine slot #3 and slot #4, which are set as uplink 'U' based on the TDD configuration, as available slots (1201). At this time, slot #2 (1202), which is set as flexible slot 'F' based on the TDD configuration, can be determined as an unavailable slot or an available slot, and can be predefined, for example, through base station configuration.

[0443] As an example of a method for determining available slots considering TDD configuration, time domain resource allocation (TDRA), CG configuration, or activation DCI, in FIG. 12, when the TDD configuration is set to 'UUUUU' through upper layer signaling and the SLIV (start and length indicator value) of PUSCH transmission is set to {S: 2, L: 12 symbols} through L1 signaling, the base station and the terminal can determine slot #0, slot #1, slot #3, and slot #4, which satisfy the PUSCH SLIV, as available slots for the set uplink slot 'U'. At this time, the base station and the terminal determine slot #2 ('L=9'), which does not satisfy the SLIV, which is the TDRA condition for PUSCH transmission. SLIV 'L=12') can be identified as an unavailable slot (1203). This is for illustrative purposes only and is not limited to PUSCH transmissions; it can also be applied to PUCCH transmissions, PUSCH / PUCCH repeated transmissions, nominal repetition of PUSCH repetition type B, and TBoMS.

[0444] [PUSCH: Frequency Hopping Process]

[0445] The following describes frequency hopping of the uplink data channel (PUSCH) in a 5G system in detail.

[0446] In 5G, two methods are supported for the frequency hopping of the uplink data channel for each PUSCH repeat transmission type. First, PUSCH repeat transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, and PUSCH repeat transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

[0447] The intra-slot frequency hopping method supported by PUSCH repeat transmission type A is a method in which a terminal transmits by changing the allocated resources in the frequency domain by a set frequency offset at two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be represented by [Equation 3].

[0448] [Mathematical Formula 3]

[0449]

[0450] In [Equation 3], i=0 and i=1 represent the first hop and the second hop, respectively, and represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method. It represents the frequency offset between two hops through the upper-layer parameters. The number of symbols in the first hop is It can be represented as, and the number of symbols for the second hop is It can be represented as. is the length of PUSCH transmission within one slot, represented by the number of OFDM symbols.

[0451] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal transmits by changing the allocated resource in the frequency domain by a set frequency offset for each slot. In inter-slot frequency hopping The starting RB during the slot can be represented through [Equation 4].

[0452] [Mathematical Formula 4]

[0453]

[0454] In [Mathematical Formula 4], is the current slot number in a multi-slot PUSCH transfer, represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method. It represents the frequency offset between two hops through the upper layer parameters.

[0455] Next, the inter-repetition frequency hopping method supported by PUSCH repeat transmission type B transmits resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. In the frequency domain for one or more actual repetitions within the n-th nominal repetition, RB, which is the index of the starting RB, start (n) can follow [Equation 5] below.

[0456] [Mathematical Formula 5]

[0457]

[0458] In [Equation 5], n is the index of the nominal repetition, represents the RB offset between two hops through the upper layer parameter.

[0459] [PUSCH: Regarding transmission power]

[0460] The following describes in detail how to determine the transmission power of an uplink data channel in a 5G system.

[0461] In a 5G system, the transmission power of the uplink data channel can be determined through the following [Equation 6].

[0462] [Mathematical Formula 6]

[0463]

[0464] In [Equation 6], j represents the PUSCH grant type; specifically, j=0 is a PUSCH grant for random access response, j=1 is a configured grant, j {2,3,...,J-1} represents a dynamic grant. represents the maximum output power set at the terminal for the carrier f of the supporting cell c for the PUSCH transmission occasion i. is set as a higher-level parameter and can be determined through upper layer settings and SRI (in the case of dynamic grant PUSCH) It is a parameter composed of the sum of represents the bandwidth for resource allocation expressed as the number of resource blocks for PUSCH transmission occasion i, and represents a value determined by the type of information transmitted via MCS (Modulation Coding Scheme) and PUSCH (e.g., whether UL-SCH is included or CSI is included, etc.). is a value for compensating for path loss, which can be determined through upper layer settings and SRI (SRS Resource Indicator) (in the case of dynamic grant PUSCH). The reference signal index is q d It refers to the downlink path loss estimate calculated by the terminal using the reference signal, and the reference signal index q dThe terminal can determine this through upper layer settings and SRI (in the case of dynamic grant PUSCH or ConfiguredGrantConfig-based configured grant PUSCH (type 2 configured grant PUSCH) that does not include upper layer settings rrc-ConfiguredUplinkGrant) or through upper layer settings. is a closed-loop power adjustment value that can be supported in accumulation and absolute modes. If the upper-layer parameter tpc-Accumulation is not set on the terminal, the closed-loop power adjustment value can be determined using the accumulation method. In this case, is to transmit PUSCH transmission occasion i-i0 to the closed-loop power adjustment value for the previous PUSCH transmission occasion i-i0 K PUSCH Transmitting PUSCH transmission occasion i from (i-i0)-1 symbols K PUSCH (i) Between symbols, the sum of TPC command values ​​for closed-loop index l received via DCI It is determined as follows. If the upper layer parameter tpc-Accumulation is set on the terminal, is the TPC command value for closed-loop index l received via DCI It is determined as follows. The closed-loop index l can be set to 0 or 1 if the upper-layer parameter twoPUSCH-PC-AdjustmentStates is configured on the terminal, and its value can be determined through the upper-layer configuration and SRI (in the case of dynamic grant PUSCH). The TPC command field and TPC value within the DCI according to the accumulation method and the absolute method. The mapping relationship can be defined as shown in [Table 33] below.

[0465] TPC command field Accumulated [dB]Absolute [dB]0-1-410-1211334

[0466] [PUSCH: Regarding TPMI]

[0467] Next, we will explain the TPMI (Transmit Precoding Matrix Indicator) indicated by the DCI from the base station during codebook-based PUSCH transmission.

[0468] If the terminal is configured to receive a 1-layer transmission via DCI or higher layer signaling from the base station using a single PUSCH antenna port, the TPMI can be defined as W=1; otherwise, that is, if the terminal is configured to receive a PUSCH scheduling of 1-layer or more via DCI or higher layer signaling from the base station using multiple PUSCH antenna ports, the TPMI W can be defined through [Table 34] to [Table 40] below.

[0469] [Table 34]

[0470]

[0471] [Table 34] above shows TPMI in 1-layer when the terminal has two PUSCH antenna ports. In [Table 34] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may instruct the terminal to select one of TPMI index 0 and 1, and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may instruct the terminal to select one of TPMI index 0 to 5.

[0472] [Table 35]

[0473]

[0474] [Table 35] above describes a 1-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is used (i.e., when DFTS-OFDM waveforms are used). In [Table 35] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 3; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 11; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 27.

[0475] [Table 36]

[0476]

[0477] [Table 36] above describes a 1-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In [Table 36] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 3; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 11; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 27.

[0478] [Table 37]

[0479]

[0480] [Table 37] above describes a 2-layer TPMI in which the terminal has two PUSCH antenna ports and transform precoding is not used (i.e., when a CP-OFDM waveform is used). In [Table 37] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0, and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2.

[0481] [Table 38]

[0482]

[0483] Table 38 above describes a 2-layer TPMI in which the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In Table 38 above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 5; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 13; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 21.

[0484] [Table 39]

[0485]

[0486] Table 39 above describes a 3-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In Table 39 above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 6.

[0487] [Table 40]

[0488]

[0489] [Table 40] above describes a 4-layer TPMI where the terminal has 4 PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In [Table 40] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 4.

[0490] [Regarding Terminal Capability Reporting]

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

[0492] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions when necessary.

[0493] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. The method by which the terminal configures the UE capability in the NR system is summarized below.

[0494] 1. If the terminal receives a list of LTE and / or NR bands from the base station via a UE capability request, the terminal configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it constructs a candidate list of BCs for EN-DC and NR SA based on the bands requested from the base station via FreqBandList. Additionally, the bands have priority in the order listed in FreqBandList.

[0495] 2. If the base station requests a UE capability report by setting the “eutra-nr-only” flag or the “eutra” flag, the terminal completely removes NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

[0496] 3. Subsequently, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC; this step can be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step applies to MR-DC as well, meaning it applies to LTE bands. The BCs remaining after this step constitute the final "candidate BC list."

[0497] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal constructs the supportedBandCombinationList in a predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" 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.

[0498] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations is included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is included only in UE-NR-Capabilities.

[0499] After the terminal capability is configured, the terminal transmits a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station subsequently performs appropriate scheduling and transmission / reception management for the terminal.

[0500]

[0501] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The contents of the present disclosure are applicable to FDD and TDD systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a physical layer downlink data channel, or from a terminal to a base station using a physical layer uplink data channel, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC CE).

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

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

[0504] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that 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 described uniformly as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.

[0505] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above will be referred to as the NC-JT case.

[0506] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, gNB, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. 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 similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included therein. Accordingly, 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 judged by a person skilled in the art. The contents of the present disclosure are applicable to FDD and TDD systems.

[0507] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0508] In describing the present disclosure below, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0509] - MIB (Master Information Block)

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

[0511] - RRC (Radio Resource Control)

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

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

[0514] - PDCCH (Physical Downlink Control Channel)

[0515] - DCI (Downlink Control Information)

[0516] - Terminal-specific (UE-specific) DCI

[0517] - Group common DCI

[0518] - Common DCI

[0519] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

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

[0521] - PUCCH (Physical Uplink Control Channel)

[0522] - UCI (Uplink Control Information)

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

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

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

[0526] As an embodiment of the present disclosure, a method for setting CSI reports and CSI resources at a terminal and a base station is described. This embodiment may be operated in combination with other embodiments within the present disclosure.

[0527] FIG. 13 is a diagram showing a non-periodic CSI report signaling structure that a terminal according to one embodiment of the present disclosure can receive as an upper layer signaling.

[0528] The terminal can receive up to 128 CSI-AperiodicTriggerStates (13-00), which are upper-layer signalings, from the base station, and one CSI-AperiodicTriggerState can be mapped to a code point in the CSI request field within the DCI. The terminal can receive reportTriggerSize, which is an upper-layer signaling related to the number of code points in the CSI request, from the base station, and reportTriggerSize can be one integer from 0 to 6. When the reportTriggerSize value is denoted as NTs, the terminal 2 for the CSI request field NTs It can be expected that there are code points. However, the maximum number of CSI-AperiodicTriggerStates and the value of reportTriggerSize are merely examples of the present disclosure, and the maximum number of CSI-AperiodicTriggerStates may be greater than 128, and the maximum value of reportTriggerSize may also be set to a value greater than 6.

[0529] - If all bits of the CSI request field in the DCI received by the terminal are 0, the terminal may determine (or consider) that there is no information to trigger the transmission of a non-periodic CSI report (in addition, the reception of a non-periodic CSI-RS may also be indicated).

[0530] - If the number of CSI-AperiodicTriggerStates configured for the terminal's upper layer signaling is 2 NTsIf it is greater than -1, the terminal selects 2 out of multiple CSI-AperiodicTriggerStates configured for upper-layer signaling from the base station. NTs -1 can receive the selected MAC-CE. That is, the MAC CE can receive up to 2 of the multiple CSI-AperiodicTriggerStates configured for upper layer signaling. NTs - Information about one CSI-AperiodicTriggerState may be included.

[0531] - If the number of CSI-AperiodicTriggerStates configured for the terminal in upper layer signaling is 2 NTs If it is less than or equal to -1, the terminal can use multiple CSI-AperiodicTriggerStates configured as upper-layer signaling by sequentially connecting them to the code points of each CSI request field. For example, assume that the terminal receives 32 CSI-AperiodicTriggerStates configured as upper-layer signaling and receives the upper-layer signaling reportTriggerSize set to 6. If reportTriggerSize is 6, 2 6 -1=63 code points of the CSI request field can be used for triggering non-periodic CSI reports. Since the number of configured CSI-AperiodicTriggerStates (32) is less than the number of code points (63) of the CSI request field, the terminal can map the configured CSI-AperiodicTriggerStates to the code points of the CSI request in ascending order.

[0532] The terminal can receive at least one, and up to 16, CSI-AssociatedReportConfigInfos within the upper layer signaling CSI-AperiodicTriggerState (13-05). One CSI-AssociatedReportConfigInfo configuration information may contain one CSI-ReportConfig (13-10), and one CSI-ReportConfig may contain CSI-ResourceConfig (13-25). For non-periodic CSI reports, one or more, and up to 16, NZP-CSI-RS-ResourceSets (13-30) may be included within CSI-ResourceConfig. Additionally, the CSI-AssociatedReportConfigInfo configuration information may include resourceForChannel (13-15), and through the parameter nzp-CSI-RS (13-20) which can be configured, one of the multiple NZP-CSI-RS-ResourceSets that can be included in CSI-ResourceConfig for aperiodic CSI reports can be selected. That is, even if aperiodic CSI reports are connected to multiple NZP-CSI-RS-ResourceSets, for one CSI-AssociatedReportConfigInfo, one aperiodic CSI-RS resource set connected to one aperiodic CSI report configuration can be considered.

[0533] The following describes the relationship between the CSI report and the CSI-RS resource set based on the time domain behavior of the CSI report and the CSI-RS resource.

[0534] - When considering the periodic CSI report, the terminal can expect that there is one periodic CSI-RS resource set that can be connected to and used with the periodic CSI report.

[0535] - When considering a semi-continuous CSI report, the terminal can expect that there is one periodic or semi-continuous CSI-RS resource set that can be connected to and used with the semi-continuous CSI report.

[0536] - When considering a non-periodic CSI report, if the non-periodic CSI report is connected to a periodic and semi-continuous 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, and if the non-periodic CSI report is connected to a non-periodic CSI-RS resource set, the number of NZP-CSI-RS-ResourceSets that can be included in the upper layer signaling CSI-ResourceConfig may be up to 16, but for one CSI-AssociatedReportConfigInfo, one non-periodic CSI-RS resource set connected to one non-periodic CSI report setting can be considered through the upper layer signaling resourceForChannel.

[0537] FIG. 14 is a diagram showing non-periodic CSI report and non-periodic CSI-RS triggering situations and constraints according to one embodiment of the present disclosure.

[0538] A terminal may not expect to receive multiple DCIs containing a CSI request field containing information that triggers the transmission of an aperiodic CSI report (which may additionally also indicate the reception of an aperiodic CSI-RS) within a single slot in a cell. Referring to FIG. 14, if both PDCCH 1 (14-00) and PDCCH 2 (14-01) contain a CSI request field containing information that triggers the transmission of an aperiodic CSI report (which may additionally indicate the reception of an aperiodic CSI-RS), the terminal may not expect PDCCH 1 (14-00) and PDCCH 2 (14-01) to be received within a single slot. Therefore, if a base station wants to transmit multiple PDCCHs to a terminal that have a CSI request field containing information that triggers an aperiodic CSI report transmission (which may additionally also instruct an aperiodic CSI-RS reception), the base station may transmit each PDCCH (14-05, 14-06) in two different slots. Thus, the terminal may receive each PDCCH (14-05, 14-06) that triggers an aperiodic CSI report in two different slots. If the terminal receives a DCI containing a CSI request field containing information that triggers an aperiodic CSI report transmission (which may additionally instruct an aperiodic CSI-RS reception) in a specific slot within the same cell group, it may not expect to receive another DCI containing a CSI request field containing information that triggers an aperiodic CSI report transmission (which may additionally instruct an aperiodic CSI-RS reception) in any other slot within the same cell group that overlaps with that slot.

[0539] The terminal can transmit to the base station constraints on the number of CSI-RS resources that can be simultaneously activated per cell and constraints on the number of CSI-RS ports that can be simultaneously activated per cell through terminal capability reporting. The terminal can report to the base station a value of 1 to 32 as the number of CSI-RS resources that can be simultaneously activated per cell. Additionally, the terminal can report to the base station a value that is a multiple of 8, of 8 to 128, as the number of CSI-RS ports that can be simultaneously activated per cell. When the terminal receives multiple non-periodic CSI-RS resources in one slot or receives one non-periodic CSI-RS resource per slot, it can receive non-periodic CSI-RS resources (14-10, 14-15, 14-20) triggered via PDCCH from the base station under the constraints on the number of CSI-RS resources and the number of CSI-RS ports.

[0540] The terminal does not expect multiple non-periodic CSI reports to be transmitted in the same slot within a cell via a single PDCCH. The terminal may not expect multiple non-periodic CSI reports located in a single slot to be triggered by a single PDCCH. For example, if non-periodic CSI report 1 (14-35), non-periodic CSI report 2 (14-40), non-periodic CSI report 3 (14-45), and non-periodic CSI report 4 (14-50) are triggered based on a single PDCCH (14-30), the terminal does not expect non-periodic CSI report 1 (14-35) and non-periodic CSI report 2 (14-40) located in a single slot to be triggered based on a single PDCCH (14-30). Additionally, a CSI report triggered based on a single PDCCH (14-30) may be allowed to be triggered in different slots, such as a non-periodic CSI report 3 (14-45) and a non-periodic CSI report 4 (14-50).

[0541] It may be allowed for non-periodic CSI reports triggered by different PDCCHs to exist in the same slot, or for only one non-periodic CSI report triggered by different PDCCHs to exist in each slot. For example, it may be allowed for non-periodic CSI report 1 (14-70) triggered by PDCCH 1 (14-60) and non-periodic CSI report 2 (14-75) triggered by PDCCH 2 (14-65) to exist in the same slot, or for each CSI report to exist only one in each slot, such as non-periodic CSI report 3 (14-80) triggered by PDCCH 1 (14-60) and non-periodic CSI report 2 (14-85) triggered by PDCCH 2 (14-65).

[0542] FIGS. 15A and FIGS. 15B are drawings illustrating examples of a non-periodic CSI report signaling structure based on terminal capabilities according to one embodiment of the present disclosure.

[0543] The terminal may report the terminal capability csi-TriggerStateNon-ActiveBWP to the base station. The terminal capability csi-TriggerStateNon-ActiveBWP may include information regarding whether the terminal can receive a trigger for an aperiodic CSI report connected to a disabled downlink bandwidth portion when the terminal receives one or more aperiodic CSI reports triggered from the base station through the CSI request field in the DCI. The terminal capability csi-TriggerStateNon-ActiveBWP may indicate that an aperiodic CSI report connected to an aperiodic CSI-RS transmitted through the disabled bandwidth portion can be triggered through the CSI request field included in the DCI received by the terminal from the base station.

[0544] For example, if the terminal does not report csi-TriggerStateNon-ActiveBWP to the base station through terminal capabilities, the terminal may receive a higher layer signaling related to non-periodic CSI reporting from the base station as shown in FIG. 15A.

[0545] - The terminal may receive two upper layer signalings, CSI-AperiodicTriggerState, and CSI-AperiodicTriggerState#1 (15-00) may include CSI-AssociatedReportConfigInfo#1 (15-01) and CSI-AssociatedReportConfigInfo#2 (15-11). CSI-AssociatedReportConfigInfo#1 (15-01) and CSI-AssociatedReportConfigInfo#2 (15-11) may each include CSI-ReportConfig#1 (15-02) and CSI-ReportConfig#2 (15-12). CSI-ReportConfig#1 (15-02) and CSI-ReportConfig#2 (15-12) may each be connected to CSI-ResourceConfig#1 (15-03) and CSI-ResourceConfig#2 (15-23). CSI-ResourceConfig#1 (15-03) and CSI-ResourceConfig#2 (15-23) can both receive the upper layer signaling bwp-Id set to 1 (15-04, 15-14).

[0546] - Additionally, CSI-AperiodicTriggerState#2 (15-20) may include CSI-AssociatedReportConfigInfo#3 (15-21) and CSI-AssociatedReportConfigInfo#4 (15-31). CSI-AssociatedReportConfigInfo#3 (15-21) and CSI-AssociatedReportConfigInfo#4 (15-31) may each include CSI-ReportConfig#3 (15-22) and CSI-ReportConfig#4 (15-32). CSI-ReportConfig#3 (15-22) and CSI-ReportConfig#4 (15-32) may each be connected to CSI-ResourceConfig#3 (15-23) and CSI-ResourceConfig#4 (15-33). CSI-ResourceConfig#3 (15-23) and CSI-ResourceConfig#4 (15-33) can both receive the upper layer signaling bwp-Id set to 2 (15-24, 15-34).

[0547] - The terminal can be instructed to a code point corresponding to CSI-AperiodicTriggerState#1 (15-00) through the CSI request field in the DCI within the active downlink bandwidth portion with index 1 (downlink bandwidth portion with bwp-id 1). Additionally, the terminal can be instructed to a code point corresponding to CSI-AperiodicTriggerState#2 (15-20) through the CSI request field in the DCI within the active downlink bandwidth portion with index 2 (downlink bandwidth portion with bwp-id 2).

[0548] - The terminal cannot be instructed to a code point corresponding to CSI-AperiodicTriggerState#1 (15-00) through the CSI request field in the DCI within an active downlink bandwidth portion where index is not 1. Additionally, the terminal cannot be instructed to a code point corresponding to CSI-AperiodicTriggerState#2 (15-20) through the CSI request field in the DCI within an active downlink bandwidth portion where index is not 2.

[0549] - In other words, through a single code point of the CSI request field in the DCI, a non-periodic CSI report connected to a CSI-RS existing in an inactive downlink bandwidth portion may not be triggered. In the following, a CSI-RS (or SSB) existing in a downlink bandwidth portion may mean a CSI-RS (or SSB) in the downlink bandwidth portion (CSI-RS (or SSB) is in the DL BWP) or a CSI-RS (or SSB) received through the downlink bandwidth portion.

[0550] Therefore, the terminal can expect that all non-periodic CSI reports triggered through a single code point of the CSI request field within the DCI are connected to a reference signal (CSI-RS or SSB) existing in the active downlink bandwidth.

[0551] Therefore, the terminal may not expect that at least one of all non-periodic CSI reports triggered through a single code point of the CSI request field within the DCI will be connected to a reference signal (CSI-RS or SSB) existing in the disabled downlink bandwidth portion.

[0552] Therefore, the terminal can assume that one or more specific code points in the CSI request field within the DCI can be used only when a specific downlink bandwidth portion is active, and expect that such one or more specific code points will not be triggered in other downlink bandwidth portions.

[0553] Therefore, if the terminal operates within a specific downlink bandwidth, the number of code points that the terminal can be instructed to via the CSI request field within the DCI may be limited.

[0554] If the terminal reports a csi-TriggerStateNon-ActiveBWP to the base station through terminal capabilities, the terminal may receive a higher-layer signaling related to the non-periodic CSI report from the base station, for example as shown in Fig. 15B.

[0555] - The terminal may receive two upper layer signalings, CSI-AperiodicTriggerState, and CSI-AperiodicTriggerState#1 (15-50) may include CSI-AssociatedReportConfigInfo#1 (15-51) and CSI-AssociatedReportConfigInfo#2 (15-61). CSI-AssociatedReportConfigInfo#1 (15-51) and CSI-AssociatedReportConfigInfo#2 (15-61) may each include CSI-ReportConfig#1 (15-52) and CSI-ReportConfig#2 (15-62). CSI-ReportConfig#1 (15-52) and CSI-ReportConfig#2 (15-62) may each be connected to CSI-ResourceConfig#1 (15-53) and CSI-ResourceConfig#2 (15-63). CSI-ResourceConfig#1 (15-53) and CSI-ResourceConfig#2 (15-63) can each receive upper layer signaling bwp-Ids set to 1 and 2, respectively (15-54, 15-64).

[0556] - Additionally, CSI-AperiodicTriggerState#2 (15-70) may include CSI-AssociatedReportConfigInfo#3 (15-71) and CSI-AssociatedReportConfigInfo#4 (15-81). CSI-AssociatedReportConfigInfo#3 (15-71) and CSI-AssociatedReportConfigInfo#4 (15-81) may each include CSI-ReportConfig#3 (15-72) and CSI-ReportConfig#4 (15-82). CSI-ReportConfig#3 (15-72) and CSI-ReportConfig#4 (15-82) may each be connected to CSI-ResourceConfig#3 (15-73) and CSI-ResourceConfig#4 (15-83). CSI-ResourceConfig#3 (15-73) and CSI-ResourceConfig#4 (15-83) can each receive the upper layer signaling bwp-Id set to 1 and 2, respectively (15-74, 15-84).

[0557] - The terminal can be instructed to a code point corresponding to CSI-AperiodicTriggerState#1 (15-50) through the CSI request field in the DCI within the active downlink bandwidth portion with index 1 (downlink bandwidth portion with bwp-id 1). Upon receiving such instructions, the terminal may perform CSI reporting only for CSI-ReportConfig#1 (15-52), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#1 (15-53), bwp-Id set to 1 (15-54)) present in the active downlink bandwidth portion among CSI-AperiodicTriggerState#1 (15-50) and may not perform CSI reporting for CSI-ReportConfig#2 (15-62), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#1 (15-63), bwp-Id set to 2 (15-64)) present in the inactive downlink bandwidth portion, and may not perform CSI reporting for CSI-ReportConfig#2 (15-62), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#1 (15-63), bwp-Id set to 2 (15-64)) and the corresponding CSI reporting It can be ignored. Additionally, if the reference signal present in the above-mentioned disabled downlink bandwidth portion (CSI-RS or SSB, the upper layer signaling bwp-Id in CSI-ResourceConfig#1 (15-63) is set to 2 (15-64)) is aperiodic CSI-RS, the terminal may not expect to receive the aperiodic CSI-RS.

[0558] - In addition, within the active downlink bandwidth portion with index 2 (downlink bandwidth portion with bwp-id 2), the terminal can be instructed to a code point corresponding to CSI-AperiodicTriggerState#2 (15-70) through the CSI request field in the DCI. Upon receiving such instructions, the terminal may perform CSI reporting only for CSI-ReportConfig#4 (15-82), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#4 (15-83), bwp-Id set to 2 (15-84)) present in the active downlink bandwidth portion among CSI-AperiodicTriggerState#2 (15-70) and may not perform CSI reporting for CSI-ReportConfig#3 (15-72), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#3 (15-73), bwp-Id set to 1 (15-74)) present in the inactive downlink bandwidth portion, and may not perform CSI reporting for CSI-ReportConfig#3 (15-72), which is connected to the reference signal (CSI-RS or SSB, the upper layer signaling within CSI-ResourceConfig#3 (15-73), bwp-Id set to 1 (15-74)). It can be ignored. Additionally, if the reference signal present in the above-mentioned disabled downlink bandwidth portion (CSI-RS or SSB, the upper layer signaling bwp-Id in CSI-ResourceConfig#3 (15-73) is set to 1 (15-74)) is aperiodic CSI-RS, the terminal may not expect to receive the aperiodic CSI-RS.

[0559] In other words, through a single code point of the CSI request field within the DCI, not only can a non-periodic CSI report connected to a reference signal (CSI-RS or SSB) existing in the active downlink bandwidth be triggered, but a non-periodic CSI report connected to a CSI-RS existing in the inactive downlink bandwidth can also be triggered. However, among the one or more triggered non-periodic CSI reports, the terminal does not report to the base station the non-periodic CSI report connected to a reference signal (CSI-RS or SSB) existing in the inactive downlink bandwidth, and in this case, if the reference signal (CSI-RS or SSB) is a non-periodic CSI-RS, the terminal may not expect to receive the corresponding non-periodic CSI-RS.

[0560] When upper-layer signaling is configured in this manner, the terminal can use all code points of the CSI request field within the DCI without restriction within a specific downlink bandwidth. Therefore, a base station receiving such terminal capability reports can configure upper-layer signaling related to non-periodic CSI reports for the terminal with greater freedom, and the number of code points available for use within a single downlink bandwidth may be greater compared to a situation where terminal capability is not received.

[0561] When operating within the active downlink bandwidth, the terminal may operate without including an SSB within that bandwidth. That is, the terminal can perform at least one of Radio Link Monitoring (RLM), Beam Management (BM), and Beam Failure Detection (BFD) through an SSB located outside the active downlink bandwidth (out of active BWP). The terminal may not only receive signals transmitted in the frequency band corresponding to the active downlink bandwidth through the receiver, but may also receive and detect signals in a frequency band wider than the frequency band corresponding to the active downlink bandwidth (or a frequency band outside the frequency band corresponding to the active downlink bandwidth), thereby supporting the aforementioned functions. The terminal may notify the base station that such operation is possible through a terminal capability report, and upon receiving such terminal capability, the base station may transmit downlink bandwidth configuration information to the terminal that excludes the frequency band containing the SSB. The SSB (or CSI-RS) existing outside the active downlink bandwidth portion below may mean an SSB (or CSI-RS) located outside the downlink bandwidth portion (SSB or CSI-RS is outside active DL BWP) or an SSB (or CSI-RS) received through outside the downlink bandwidth portion.

[0562] The following [Table 41] defines the terminal capabilities for performing RLM, BM, and BFD using the SSB outside the downlink bandwidth portion described above.

[0563] FG (Feature Group) 53-1 may mean that RLM, BM, BFD, and L3 intra-frequency measurements can be performed without interrupt time via a CD-SSB (Cell Defined SSB) located outside the downlink bandwidth portion where the terminal is active. Unless otherwise indicated, the SSB described below may be considered a CD-SSB.

[0564] FG (Feature Group) 53-3 means that for RLM, BM, and BFD, it can be performed through NCD-SSB (Non-cell Defined SSB) located within the downlink bandwidth portion where the terminal is active.

[0565] FG (Feature Group) 53-4 means that if the SSB is located outside the downlink bandwidth portion where it is active, the RLM, BM, and BFD can be performed through the CSI-RS located inside the downlink bandwidth portion where the terminal is active.

[0566] [Table 41]

[0567]

[0568]

[0569] Meanwhile, as described in the explanation of the terminal capability mentioned in Fig. 16 above, the terminal can be triggered by a non-periodic CSI report connected to a reference signal existing in the deactivated downlink bandwidth portion from the base station. Additionally, as described in the explanation of the terminal capability mentioned in [Table 41] above, the terminal can perform BM through an SSB existing outside the activated downlink bandwidth portion according to a specific terminal capability report. As part of the BM operation, the terminal can receive and measure L1-RSRP for a specific reference signal and report it to the base station in the form of a CSI. Therefore, although the terminal capability mentioned in Fig. 16 above and the terminal capability mentioned in [Table 41] above are unrelated in terms of background and motivation for introduction, they may be related regarding the operation and function of the terminal and the base station. In the following, the terminal capability mentioned in Fig. 16 above may be named as FG 14-8, the first terminal capability, or csi-TriggerStateNon-ActiveBWP, and all of them can be considered to have the same meaning.

[0570] In addition, the terminal capability mentioned in [Table 41] above may be named as at least one combination of FG 53-1, FG 53-3, FG 53-4, or a second terminal capability, or bwpOperationMeasWithoutInterrupt, and all of them may be considered to have the same meaning.

[0571] The terminal may consider the following four cases ([Case 1] to [Case 4]) for which it can report to the base station regarding the first terminal capability and the second terminal capability, and the terminal operation in each case may be as described below.

[0572] [Case 1]

[0573] If the terminal does not report both the first terminal capability and the second terminal capability, the terminal may not expect to be triggered to receive an aperiodic CSI report associated with a reference signal (CSI-RS or SSB) existing outside the inactive downlink bandwidth or the active downlink bandwidth within the active downlink bandwidth. This method of triggering an aperiodic CSI report may be named the "first aperiodic CSI report trigger method," and for this purpose, the upper-layer signaling configuration received by the terminal from the base station may be named the "first CSI report upper-layer signaling configuration." Additionally, the terminal may expect that an SSB is included when receiving the active downlink bandwidth configuration from the base station. In other words, the terminal may not expect that an SSB exists outside the active downlink bandwidth from the base station. This configuration of setting the downlink bandwidth may be named the "first downlink bandwidth configuration."

[0574] [Case 2]

[0575] If the terminal reports the first terminal capability but does not report the second terminal capability, the terminal may be triggered to receive an aperiodic CSI report connected to a reference signal (CSI-RS or SSB) existing outside the inactive downlink bandwidth or the active downlink bandwidth in the active downlink bandwidth portion. However, the terminal may expect the SSB to be included when receiving the active downlink bandwidth configuration from the base station. In other words, the terminal may not expect the SSB to exist outside the active downlink bandwidth from the base station. Such a downlink bandwidth configuration configuration may be referred to as the "first downlink bandwidth configuration configuration" as described above. Therefore, if the terminal is triggered to receive an aperiodic CSI report connected to a reference signal existing outside the inactive downlink bandwidth or the active downlink bandwidth portion as described above, the terminal may expect that the reference signal connected to the aperiodic CSI report is a CSI-RS existing outside the inactive downlink bandwidth or the active downlink bandwidth portion. If a terminal receives a trigger from a base station for an aperiodic CSI report connected to a CSI-RS existing in a deactivated downlink bandwidth portion, it may ignore the said aperiodic CSI report without transmitting it to the base station. Additionally, if the said CSI-RS is an aperiodic CSI-RS, the terminal may not expect to receive the said aperiodic CSI-RS. Such an aperiodic CSI report trigger method may be named the "second aperiodic CSI report trigger method," and for this purpose, the upper-layer signaling configuration received by the terminal from the base station may be named the "second CSI report upper-layer signaling configuration."

[0576] [Case 3]

[0577] If the terminal has not reported the first terminal capability but has reported the second terminal capability, when the terminal receives the active downlink bandwidth portion from the base station, the said configuration may or may not include an SSB. In other words, if an SSB exists outside the active downlink bandwidth portion from the base station, the terminal can perform RLM, BM, and BFD operations using the said SSB, and can operate even if an SSB exists outside the active downlink bandwidth portion. Such a downlink bandwidth portion configuration can be named the "second downlink bandwidth portion configuration."

[0578] Additionally, when the terminal receives a trigger for an aperiodic CSI report from the base station in the active downlink bandwidth, it may not expect to receive a trigger for an aperiodic CSI report connected to a reference signal (CSI-RS or SSB) existing outside the inactive downlink bandwidth or the active downlink bandwidth, except for an aperiodic CSI report setting connected to an SSB existing outside the active downlink bandwidth. Therefore, the terminal may exceptionally receive triggering for an aperiodic CSI report connected to an SSB existing outside the active downlink bandwidth, even though it has not reported the first terminal capability. In addition, unlike the operation when the terminal reports the first terminal capability (ignoring and not reporting to the base station even if it receives a trigger for an aperiodic CSI report connected to a reference signal (SSB or CSI-RS) existing in the disabled downlink bandwidth, and not expecting reception of the aperiodic CSI-RS if the reference signal is an aperiodic CSI-RS), the terminal may transmit the aperiodic CSI report to the base station when it receives a trigger for an aperiodic CSI report connected to an SSB existing outside the enabled downlink bandwidth. This method of triggering an aperiodic CSI report may be named the "third aperiodic CSI report trigger method," and for this purpose, the upper layer signaling configuration received by the terminal from the base station may be named the "third CSI report upper layer signaling configuration."

[0579] [Case 4]

[0580] If the terminal reports a first terminal capability and a second terminal capability, when the terminal receives an active downlink bandwidth portion from the base station, the said configuration may or may not include an SSB. In other words, if an SSB exists outside the active downlink bandwidth portion from the base station, the terminal can perform RLM, BM, and BFD operations using the SSB, and can operate even if an SSB exists outside the active downlink bandwidth portion. Such a downlink bandwidth portion configuration can be named the "second downlink bandwidth portion configuration."

[0581] Additionally, the terminal may receive a trigger for an aperiodic CSI report associated with a reference signal (CSI-RS or SSB) located outside the disabled downlink bandwidth or the disabled downlink bandwidth, in the active downlink bandwidth portion. If the terminal receives a trigger for an aperiodic CSI report associated with a reference signal located outside the disabled downlink bandwidth or the active downlink bandwidth portion as described above, the terminal may expect that the reference signal associated with said aperiodic CSI report is a CSI-RS or SSB located outside the disabled downlink bandwidth or the active downlink bandwidth portion. If the terminal receives a trigger from the base station for an aperiodic CSI report associated with a CSI-RS located in the disabled downlink bandwidth portion, it may ignore said aperiodic CSI report without transmitting it to the base station. Additionally, if said CSI-RS is an aperiodic CSI-RS, the terminal may not expect to receive said aperiodic CSI-RS. Additionally, if the terminal receives a trigger from the base station regarding an aperiodic CSI report connected to an SSB existing outside the downlink bandwidth portion activated in this way, the terminal may transmit the said aperiodic CSI report to the base station. Such an aperiodic CSI report trigger method may be named the "fourth aperiodic CSI report trigger method," and for this purpose, the upper layer signaling configuration received by the terminal from the base station may be named the "fourth CSI report upper layer signaling configuration."

[0582] FIG. 16 is a diagram showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0583] When configuring non-periodic CSI reporting operation (16-00), the terminal and base station can be determined based on whether the first terminal capability and the second terminal capability report.

[0584] - If the terminal does not report the first terminal capability (16-05) and does not report the second terminal capability (16-15), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 1] (16-35), and may follow the first non-periodic CSI reporting trigger method, the first CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0585] - If the terminal does not report the first terminal capability (16-05) and reports the second terminal capability (16-15), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 3] above (16-30), and may follow the third non-periodic CSI reporting trigger method, the third CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0586] - If the terminal reports the first terminal capability (16-05) and does not report the second terminal capability (16-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 2] (16-25), and may follow the second non-periodic CSI reporting trigger method, the second CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0587] - If the terminal reports the first terminal capability (16-05) and the second terminal capability (16-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 4] (16-20), and may follow the fourth non-periodic CSI reporting trigger method, the fourth CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0588] FIG. 17 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0589] When configuring non-periodic CSI reporting operation (17-00), the terminal and base station can be determined based on whether the first terminal capability and the second terminal capability report.

[0590] - If the terminal does not report the first terminal capability (17-05), the terminal may not report the second terminal capability (17-15). That is, the terminal may not expect the case where the first terminal capability is not reported and the second terminal capability is reported, and the above-described [Case 3] may be considered not to occur. If the terminal reports that RLM, BM, and BFD operations are possible using an SSB located outside the active downlink bandwidth, it may need to perform L1-RSRP reporting using an SSB located outside the active downlink bandwidth for at least BM, but if the terminal does not report the first terminal capability, it may be determined (or considered) that the terminal reports that such operations are impossible. Therefore, the terminal may establish a relationship between the reported values ​​of the first terminal capability and the second terminal capability and consider that if the first terminal capability is not reported, the second terminal capability is always not reported. In such cases, the terminal and the base station may determine (or consider) that the situation corresponds to [Case 1] (17-30), and may follow the first non-periodic CSI reporting trigger method, the first CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0591] - If the terminal has reported the first terminal capability (17-05) and has not reported the second terminal capability (17-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 2] (17-25), and may follow the second non-periodic CSI reporting trigger method, the second CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0592] - If the terminal reports the first terminal capability (17-05) and the second terminal capability (17-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 4] (17-20), and may follow the fourth non-periodic CSI reporting trigger method, the fourth CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0593] FIG. 18 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0594] When configuring non-periodic CSI reporting operation (18-00), the terminal and base station can be determined based on whether the first terminal capability and the second terminal capability report.

[0595] - If the terminal does not report the second terminal capability (18-05) and does not report the first terminal capability (18-15), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 1] (18-35), and may follow the first non-periodic CSI reporting trigger method, the first CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0596] - If the terminal does not report the second terminal capability (18-05) and reports the first terminal capability (18-15), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 2] above (18-30), and may follow the second non-periodic CSI reporting trigger method, the second CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0597] - If the terminal reports the second terminal capability (18-05) and does not report the first terminal capability (18-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 3] above (18-25), and may follow the third non-periodic CSI reporting trigger method, the third CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0598] - If the terminal reports a second terminal capability (18-05) and a first terminal capability (18-10), the terminal and the base station may determine (or consider) that the situation corresponds to [Case 4] above (18-20), and may follow the fourth non-periodic CSI reporting trigger method, the fourth CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0599] FIG. 19 is another drawing showing the operation of a terminal and a base station according to one embodiment of the present disclosure.

[0600] When configuring non-periodic CSI reporting operation (19-00), the terminal and base station can be determined based on whether the first terminal capability and the second terminal capability report.

[0601] - If the terminal does not report the second terminal capability (19-05) and does not report the first terminal capability (19-15), the terminal and the base station may consider the situation as corresponding to [Case 1] (19-30), and may follow the first non-periodic CSI reporting trigger method, the first CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0602] - If the terminal does not report the second terminal capability (19-05) and reports the first terminal capability (19-15), the terminal and the base station may consider the situation to correspond to [Case 2] above (19-30), and may follow the second non-periodic CSI reporting trigger method, the second CSI reporting upper layer signaling configuration, and the first downlink bandwidth portion setting configuration as described above.

[0603] - If the terminal reports the second terminal capability (19-05), the terminal may report the first terminal capability (19-10). That is, the terminal may not expect the case where the second terminal capability is reported and the first terminal capability is not reported, and the above-described [Case 3] may be considered not to occur. If the terminal reports that RLM, BM, and BFD operations are possible using an SSB located outside the active downlink bandwidth, it may need to perform L1-RSRP reporting using an SSB located outside the active downlink bandwidth for at least BM, because if the terminal does not report the first terminal capability, it may be determined (or considered) that the terminal reports that such operations are impossible. Therefore, the terminal may establish a relationship between the reported values ​​of the first terminal capability and the second terminal capability and consider that when the second terminal capability is reported, the first terminal capability is always reported. In such cases, the terminal and the base station may determine (or consider) that the situation corresponds to [Case 4] above (19-20), and may follow the fourth non-periodic CSI reporting trigger method, the fourth CSI reporting upper layer signaling configuration, and the second downlink bandwidth portion setting configuration as described above.

[0604] Although the above points were explained using non-periodic CSI reporting, they can be similarly applied to semi-continuous and periodic CSI reporting.

[0605] FIG. 20 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0606] Referring to FIG. 20, the terminal may include a transceiver (referring to a terminal receiver (20-00) and a terminal transmitter (20-10)), a memory (not shown), and a terminal processing unit (20-05, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (20-00, 20-10), memory, and terminal processing unit (20-05) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0607] The transceiver can transmit and receive signals with a base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts its frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0608] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

[0609] Memory can store programs and data necessary for the operation of the terminal. Additionally, memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0610] In addition, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.

[0611] FIG. 21 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0612] Referring to FIG. 21, the base station may include a transceiver unit, a memory (not shown), and a base station processing unit (21-05, or a base station control unit or processor), which refer to a base station receiver (21-00) and a base station transmitter (21-10). Depending on the communication method of the base station described above, the transceiver unit (21-00, 21-10), the memory, and the base station processing unit (21-05) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. Furthermore, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0613] The transceiver can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts its frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0614] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

[0615] Memory can store programs and data necessary for the operation of the base station. Additionally, memory can store control information or data included in signals transmitted and received by the base station. Memory can be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0616] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.

[0617] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0618] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0619] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0620] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wireless LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.

[0621] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0622] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

[0623] Meanwhile, the order of description in the drawings illustrating the method of the present invention does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.

[0624] Alternatively, drawings describing the method of the present invention may omit some components and include only some components to the extent that the essence of the present invention is not compromised.

[0625] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not impair the essence of the invention.

[0626] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will understand that modifications can be easily made to other specific forms without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and their equivalents should be interpreted as being included within the scope of the present disclosure.

Claims

1. A method performed by a terminal in a wireless communication system, A step of transmitting a terminal capability information message including first terminal capability information and second terminal capability information to a base station; A step of receiving an RRC (radio resource control) message containing a trigger state list for non-periodic CSI (channel state information) reporting from the base station; A step of receiving DCI (downlink control information) from the base station including a field indicating a trigger state of one of the trigger state lists above; and A method characterized by including the step of transmitting a CSI report determined based on the SSB to the base station when the reference signal associated with the above-mentioned trigger state is an SSB (synchronization signal block) transmitted in the disabled downlink bandwidth portion.

2. In Paragraph 1, The above first terminal capability information indicates that the terminal supports a trigger state including the disabled downlink bandwidth portion being included in the trigger state list, and A method characterized in that the second terminal capability information indicates that the terminal can perform a measurement of the SSB transmitted in the inactive bandwidth portion.

3. In Paragraph 1, A method characterized in that, when the above reference signal is a CSI-RS (CSI-reference signal) transmitted in the above deactivated downlink bandwidth portion, the terminal omits CSI reporting.

4. In Paragraph 3, A method characterized in that, when the reference signal is a non-periodic CSI-RS, the terminal does not expect to receive the non-periodic CSI-RS.

5. In a method performed by a base station in a wireless communication system, A step of receiving a terminal capability information message from a terminal including first terminal capability information and second terminal capability information; A step of transmitting an RRC (radio resource control) message containing a trigger state list for non-periodic CSI (channel state information) reporting to the above terminal; A step of transmitting DCI (downlink control information) to the terminal, including a field indicating a trigger state of one of the trigger state lists above; and A method characterized by including the step of receiving a CSI report determined based on the SSB from the terminal when the reference signal associated with the above-mentioned trigger state is an SSB (synchronization signal block) transmitted in the disabled downlink bandwidth portion.

6. In Paragraph 5, The above first terminal capability information indicates that the terminal supports a trigger state including the disabled downlink bandwidth portion being included in the trigger state list, and A method characterized in that the second terminal capability information indicates that the terminal can perform a measurement of the SSB transmitted in the inactive bandwidth portion.

7. In Paragraph 5, A method characterized by omitting CSI reporting when the above reference signal is a CSI-RS (CSI-reference signal) transmitted in the above deactivated downlink bandwidth portion.

8. In a terminal of a wireless communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The terminal is connected to communicate with at least one processor and is capable of executing individually or in any combination of the at least one processor, so that the terminal, Transmit a terminal capability information message including first terminal capability information and second terminal capability information to a base station, and Receive an RRC (radio resource control) message from the above base station containing a trigger state list for non-periodic CSI (channel state information) reporting, and Receive DCI (downlink control information) from the base station including a field indicating a trigger state of one of the above trigger state lists, and A terminal characterized by including a memory that stores a command to transmit a CSI report determined based on the SSB to the base station when the reference signal associated with the above-mentioned trigger state is an SSB (synchronization signal block) transmitted in the disabled downlink bandwidth portion.

9. In Paragraph 8, The above first terminal capability information indicates that the terminal supports a trigger state including the disabled downlink bandwidth portion being included in the trigger state list, and A terminal characterized in that the second terminal capability information indicates that the terminal can perform a measurement of the SSB transmitted in the inactive bandwidth portion.

10. In Paragraph 9, A terminal characterized by omitting CSI reporting when the above reference signal is a CSI-RS (CSI-reference signal) transmitted in the above deactivated downlink bandwidth portion.

11. In Paragraph 10, A terminal characterized in that, when the above reference signal is a non-periodic CSI-RS, the terminal does not expect reception of the non-periodic CSI-RS.

12. In a base station of a wireless communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The base station is connected to communicate with at least one processor and is capable of executing individually or in any combination of the at least one processor, and, A terminal capability information message including first terminal capability information and second terminal capability information is received from a terminal, and Transmit an RRC (radio resource control) message containing a trigger state list for non-periodic CSI (channel state information) reporting to the above terminal, and Transmit DCI (downlink control information) including a field indicating the trigger state of one of the above trigger state lists to the terminal, and A base station characterized by including a memory that stores a command to receive a CSI report determined based on the SSB from the terminal when the reference signal associated with the above-mentioned trigger state is an SSB (synchronization signal block) transmitted in the disabled downlink bandwidth portion.

13. In Paragraph 12, The above first terminal capability information indicates that the terminal supports a trigger state including the disabled downlink bandwidth portion being included in the trigger state list, and A base station characterized by the above second terminal capability information indicating that the terminal can perform a measurement of the SSB transmitted in the above inactive bandwidth portion.

14. In Paragraph 12, A base station characterized by omitting CSI reporting when the above reference signal is a CSI-RS (CSI-reference signal) transmitted in the above deactivated downlink bandwidth portion.

Images