Method and device for reporting channel state information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The disclosure relates to a method performed by a terminal in a wireless communication system and a device for performing same, the method comprising the steps of: receiving, from a base station, higher layer signaling including first information for determining a table to be applied to the interpretation of a time domain resource assignment (TDRA) field; receiving, from the base station, downlink control information (DCI) for scheduling a channel state information (CSI) report through a physical uplink shared channel (PUSCH) that does not have a transport block (TB); determining, on the basis of the first information, the table to be applied to the interpretation of the TDRA field of the DCI; and, on the basis of the table and a resource identified on the basis of the TDRA field of the DCI, multiplexing the CSI report on the PUSCH that does not have the TB and transmitting same.

Description

Method and device for reporting channel state information 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 (CSI) in a wireless communication system and a device 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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

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

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

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

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

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

[0008] The technical problem to be solved in various embodiments of the present disclosure is to provide a device and method capable of effectively providing a service in a mobile communication system.

[0009] In addition, a technical problem to be achieved in various embodiments of the present disclosure is to provide an improved channel state information reporting method and a device capable of performing the same.

[0010] The technical problems to be achieved in the embodiments of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0011] The present disclosure for solving the above problems comprises a method performed by a terminal in a wireless communication system, the method comprising the steps of: receiving, from a base station, upper layer signaling including first information for determining a table to be applied to interpretation of a time domain resource assignment (TDRA) field; receiving, from the base station, downlink control information (DCI) for scheduling CSI (channel state information) reporting through a PUSCH (physical uplink shared channel) without a TB (transport block); determining, based on the first information, the table to be applied to interpretation of the TDRA field of the DCI; and multiplexing and transmitting the CSI reporting on the PUSCH without the TB based on resources identified based on the table and the TDRA field of the DCI.

[0012] In addition, the present disclosure provides a method performed by a base station in a wireless communication system, comprising the steps of: transmitting, to a terminal, upper layer signaling including first information for determining a table applicable to interpretation of a time domain resource assignment (TDRA) field; transmitting, to the terminal, downlink control information (DCI) for scheduling CSI (channel state information) reporting through a PUSCH (physical uplink shared channel) without a TB (transport block); and receiving, from the terminal, a CSI report multiplexed on the PUSCH without the TB based on the table applicable to interpretation of the TDRA field of the DCI determined based on the first information and a resource identified based on the TDRA field of the DCI.

[0013] In addition, the present disclosure provides a terminal of a wireless communication system, comprising: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; and a memory communicatively connected to the at least one processor, the memory storing instructions that are executable individually or in any combination by the at least one processor, such that the terminal receives, from the base station, upper layer signaling including first information for determining a table to be applied to the interpretation of a time domain resource assignment (TDRA) field, receives, from the base station, downlink control information (DCI) for scheduling a CSI (channel state information) report through a PUSCH (physical uplink shared channel) without a TB (transport block), determines the table to be applied to the interpretation of the TDRA field of the DCI based on the first information, and multiplexes and transmits the CSI report on the PUSCH without the TB based on a resource identified based on the table and the TDRA field of the DCI.

[0014] In addition, the present disclosure provides a base station of a wireless communication system, comprising: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; and a memory communicatively connected to the at least one processor, the memory including instructions executable individually or in any combination by the at least one processor, such that the base station transmits, to a terminal, upper layer signaling including first information for determining a table to be applied to the interpretation of a time domain resource assignment (TDRA) field, transmits, to the terminal, downlink control information (DCI) for scheduling a CSI (channel state information) report through a physical uplink shared channel (PUSCH) without a TB (transport block), and receives, from the terminal, a CSI report multiplexed on the PUSCH without a TB based on the table to be applied to the interpretation of the TDRA field of the DCI determined based on the first information and a resource identified based on the TDRA field of the DCI.

[0015] According to various embodiments of the present disclosure, a device and method for effectively providing a service in a mobile communication system can be provided.

[0016] In addition, according to various embodiments of the present disclosure, an improved channel state information reporting method and a device capable of performing the same can be provided.

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

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

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

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

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

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

[0023] FIG. 6 is a diagram illustrating another MAC-CE (medium access control - control element) structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to an embodiment of the present disclosure.

[0024] FIG. 7 is a diagram illustrating an example of an aperiodic CSI reporting method according to one embodiment of the present disclosure.

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

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

[0027] FIG. 10 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) in a wireless communication system according to one embodiment of the present disclosure.

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

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

[0030] FIG. 13 is a diagram illustrating an example of PUSCH repetition transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 14 is a diagram illustrating the operation of a terminal according to an embodiment of the present disclosure.

[0032] FIG. 15 is a diagram illustrating the operation of a base station according to an embodiment of the present disclosure.

[0033] FIG. 16 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0034] FIG. 17 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

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

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

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

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

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

[0040] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

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

[0042] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

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

[0045] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

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

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

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

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

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

[0051] [NR time-frequency resources]

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

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

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

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

[0056] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and therefore 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). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, cases where the subcarrier spacing setting value μ = 0 (204) and μ = 1 (205) are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of one slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of two slots (203). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0057] [Table 1]

[0058]

[0059] [Bandwidth Part (BWP)]

[0060] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

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

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

[0063] [Table 2]

[0064]

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

[0066] According to some embodiments, a terminal before RRC connection can be configured with an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive configuration information about a control resource set (CORESET) and a search space in which a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) and search space can be transmitted through the MIB during the initial access phase. The control space and search space configured by the MIB can each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control space #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and monitoring occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

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

[0068] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0069] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed (FDM), and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0070] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 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.

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

[0072] [Bandwidth Part (BWP) Change]

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

[0074] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in [Table 3] below, for example.

[0075] [Table 3]

[0076]

[0077] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0078] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP The completion can be done at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. When the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules the data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (TBWP ) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

[0079] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth change, the terminal may not perform any transmission or reception during the time period from the third symbol of the slot in which the PDCCH including the DCI is received to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth change in slot n and the slot offset value indicated by the 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).

[0080] [CA / DC related]

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

[0082] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system is composed 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) in the terminal and NR base station, respectively.

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

[0084] - Transfer of user plane data

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

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

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

[0088] For the above SDAP layer device, the terminal can be configured by an RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

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

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

[0091] - User data transfer function

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

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

[0094] - PDCP PDU reordering for reception

[0095] - Duplicate detection of lower layer SDUs

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

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

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

[0099] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

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

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

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

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

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

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

[0106] - Re-segmentation of RLC data PDUs

[0107] - Reordering of RLC data PDUs

[0108] - Duplicate detection function

[0109] - Protocol error detection

[0110] - RLC SDU discard function

[0111] - RLC re-establishment function

[0112] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the 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 an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

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

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

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

[0116] - Multiplexing / demultiplexing of MAC SDUs

[0117] - Scheduling information reporting function

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

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

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

[0121] - MBMS service identification function

[0122] - Transport format selection function

[0123] - Padding function

[0124] The NR PHY layer (445, 450) can perform an operation of channel coding and modulating upper layer data, converting it into an OFDM symbol and transmitting it through a wireless channel, or demodulating and channel decoding an OFDM symbol received through a wireless channel and transmitting it to a higher layer.

[0125] The above wireless protocol structure can have various detailed structures 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 having 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 CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, as shown in 410. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, as shown in 420.

[0126] [Unified TCI state]

[0127] Hereinafter, a single TCI state indication and activation method based on the unified TCI scheme is described. The unified TCI scheme can refer to a method of integrating and managing the transmission and reception beam management methods, which were distinguished into the TCI state method used for downlink reception of the terminal in the existing Rel-15 and 16 and the spatial relation info method used for uplink transmission, into a TCI state. Therefore, when the terminal is instructed by the base station based on the unified TCI scheme, it can perform beam management using the TCI state even for uplink transmission. If the terminal has set a TCI-State, which is an upper layer signaling with the tci-stateId-r17, which is an upper layer signaling, from the base station, the terminal can perform operations based on the unified TCI scheme using the corresponding TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0128] The first type is a joint TCI state, and the terminal can be instructed by the base station to use both the TCI state to apply to uplink transmission and downlink reception through a single TCI-State. If the terminal is instructed to use a TCI-State based on a joint TCI state, the terminal can use the RS corresponding to qcl-Type1 in the TCI-State based on the joint TCI state to instruct the parameters to use for downlink channel estimation, and the RS corresponding to qcl-Type2 to instruct the parameters to use as a downlink reception beam or reception filter. If the terminal is instructed to use a TCI-State based on a joint TCI state, the terminal can use the RS corresponding to qcl-Type2 in the TCI-State based on the joint DL / UL TCI state to instruct the parameters to use as an uplink transmission beam or transmission filter. In this case, if the terminal is instructed to use a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0129] The second form is a separate TCI state, in which the terminal can be individually instructed by the base station to select a UL TCI state to apply to uplink transmission and a DL TCI state to apply to downlink reception. If the terminal is instructed to select a UL TCI state, the terminal can be instructed to select parameters to use as an uplink transmission beam or transmission filter using the reference RS or source RS configured in the UL TCI state. If the terminal is instructed to select a DL TCI state, the terminal can be instructed to select parameters to use for downlink channel estimation using the RS corresponding to qcl-Type1 configured in the DL TCI state, and to select parameters to use as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2.

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

[0131] A terminal can receive a joint TCI state from a base station for each bandwidth part within a specific cell through upper layer signaling up to 128 times, and among the separate TCI states, a DL TCI state can be set for each bandwidth part within a specific cell up to 64 or 128 times through upper layer signaling based on a terminal capability report. Among the separate TCI states, the DL TCI state and the joint TCI state 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.

[0132] Among the separate TCI states, the UL TCI state can be set to a maximum of 32 or 64 upper layer signaling for each specific bandwidth part within a specific cell based on the terminal capability report, 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 TCI can also use the same upper layer signaling structure, and the UL TCI state among the separate TCI can use different upper layer signaling structures from the joint TCI state and the DL TCI state among the separate TCI states.

[0133] The use of different or identical upper layer signaling structures may be defined in the specification, or may be distinguished through another upper layer signaling established by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0134] The terminal can receive transmission and reception beam-related instructions in an integrated TCI manner using one of the joint TCI state and separate TCI state configured by the base station. The terminal can be configured by the base station via upper layer signaling whether to use either the joint TCI state or separate TCI state.

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

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

[0137] If a terminal receives an instruction related to a transmit / receive beam 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 indicating a separate TCI state from a base station, and the base station can schedule reception of a PDSCH including the corresponding MAC-CE to the terminal through a PDCCH. If the MAC-CE includes only one set of separate TCI states, the terminal can determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter using the separate TCI states included in the indicated separate TCI state set starting from 3 ms after transmitting a PUCCH including HARQ-ACK information indicating whether reception of the corresponding PDSCH was successful. At this time, the separate TCI state set may mean single or multiple separate TCI states that one code point of the TCI state field in DCI format 1_1 or 1_2 can have, and one 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 in the MAC-CE, the UE may confirm that the multiple separate TCI state sets indicated by the MAC-CE correspond to each code point of the TCI state field of DCI format 1_1 or 1_2 starting from 3 ms after transmitting the PUCCH including HARQ-ACK information indicating whether reception for the corresponding PDSCH was successful, and may activate the indicated separate TCI state set.At this time, each code point of the TCI state field of DCI format 1_1 or 1_2 can indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal can receive DCI format 1_1 or 1_2 and apply a separate set of TCI states indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beams. At this time, 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] FIG. 5 is a diagram of a beam application time that can be considered when using an integrated TCI method in a wireless communication system according to an embodiment of the present disclosure.

[0139] As described above, the terminal may receive DCI format 1_1 or 1_2 from the base station, including (with DL assignment) or not including (without DL assignment) downlink data channel scheduling information, and apply one joint TCI state or a separate set of TCI states indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beams.

[0140] - DCI format 1_1 or 1_2 with DL assignment (500): If the terminal receives DCI format 1_1 or 1_2 including downlink data channel scheduling information from the base station (501) and indicates one joint TCI state or a separate TCI state set based on the integrated TCI method, the terminal receives a PDSCH scheduled based on the received DCI (505), and can transmit a PUCCH including an HARQ-ACK indicating whether reception of the DCI and the PDSCH is successful (510). At this time, the HARQ-ACK can include the meaning of whether reception of both the DCI and the PDSCH is successful, and if at least one of the DCI and the PDSCH is not received, the terminal can transmit a NACK, and if reception of both is successful, the terminal can transmit an ACK.

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

[0142] ■ Includes scrambled CRC (cyclic redundancy check) using CS-RNTI (configured scheduling - radio network temporary identifier).

[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 if the FDRA method is dynamic switch, the value of all bits allocated to the FDRA field is 0.

[0147] The terminal can transmit a PUCCH including a HARQ-ACK indicating whether reception was successful for the DCI format 1_1 or 1_2 assuming the above-described matters (560).

[0148] - For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), if a new TCI state indicated through DCI (501, 555) is the same as a TCI state that has already been indicated and applied to an uplink transmission and downlink reception beam, the UE can maintain the previously applied TCI state, and if the new TCI state is different from the previously indicated TCI state, the UE can determine the application time of a joint TCI state or a separate TCI state set that can be indicated from the TCI state field included in the DCI as the time after the first slot (520, 570) after the time equal to BAT (beam application time, 515, 565) after the PUCCH transmission (530, 580), and can use the previously indicated TCI-state until (525, 575) before the corresponding slot (520, 570).

[0149] - For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), the BAT can be set by upper layer signaling based on terminal capability report information as a specific number of OFDM symbols, and the numerology for the BAT and the first slot after the 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 the DCI is applied.

[0150] A terminal can apply one joint TCI state indicated via MAC-CE or DCI to reception of control resource sets connected to all terminal-specific search spaces, reception of PDSCHs scheduled as PDCCHs transmitted from the control resource sets, transmission of PUSCHs, and transmission of all PUCCH resources.

[0151] A terminal may apply one separate TCI state set, if one separate TCI state set indicated via MAC-CE or DCI includes one DL TCI state, to reception for control resource sets connected to all terminal-specific search spaces, to reception for PDSCH scheduled as PDCCH transmitted from the control resource set, and to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

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

[0153] When a separate set of TCI states indicated via MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to reception for all control resource sets associated with the terminal-specific search space and to reception for PDSCH scheduled as PDCCH transmitted from the control resource set, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0154] [Unified TCI state MAC-CE]

[0155] Hereinafter, a single TCI state indication and activation method based on the integrated TCI scheme is described. The terminal receives a PDSCH including the following MAC-CE from the base station, and from 3 slots after transmitting a HARQ-ACK for the corresponding PDSCH to the base station, the terminal can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information in 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 illustrating another MAC-CE structure for activating and indicating a joint TCI state or separate DL or UL TCI state in a wireless communication system according to an embodiment of the present disclosure. The meaning of each field within the MAC-CE structure may be as follows.

[0157] - Serving Cell ID (600): This field can indicate which serving cell the MAC-CE is applied to. The length of this field can be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signaling simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE can 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 include the serving cell indicated by this field.

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

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

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

[0161] - D / U (620): This field can indicate whether the TCI state ID field in 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 in the same octet can be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field in the same octet can be a separate UL TCI state.

[0162] - TCI state ID (625): This field can indicate 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 express the TCI-StateId, which can be expressed in 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 express the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be activated can be 8 for a joint TCI state and 16 for separate DL or UL TCI states.

[0163] R: This indicates a reserved bit and can be set to 0.

[0164] For the MAC-CE structure of FIG. 6 described above, the terminal can include the third octet including the P1, P2, ..., P8 fields in FIG. 6 in the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal can perform TCI state activation using the fixed MAC-CE structure regardless of the upper layer signaling set by the base station. As another example, for the MAC-CE structure of FIG. 6 described above, the terminal can omit the third octet including the P1, P2, ..., P8 fields in FIG. 6 when unifiedTCI-StateType-r17 in MIMOparam-r17 in ServingCellConfig, which is an upper layer signaling, is set to joint. 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. In addition, all D / U fields located from the fourth octet to the first bit in Fig. 6 can be regarded as R fields, and all corresponding R fields can be set to 0 bits.

[0165] [CSI resource configuration]

[0166] NR has a Channel State Information (CSI) framework that directs base stations to measure and report channel state information (CSI) for terminals. The NR CSI framework can consist of at least two elements: resource settings and report settings. Report settings can reference at least one ID of resource settings to establish a connection relationship with each other.

[0167] According to one embodiment of the present disclosure, resource settings may include information related to a reference signal (RS) for measuring channel state information by a terminal. The base station may configure at least one resource setting for the terminal. For example, the base station and the terminal may exchange signaling information as shown in [Table 4] to convey information regarding resource settings.

[0168] [Table 4]

[0169]

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

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

[0172] [Table 5]

[0173]

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

[0175] CSI-RS may be the most representative reference signal included in a resource set. The base station and terminal can exchange signaling information, as shown in [Table 6], to convey information about CSI-RS resources.

[0176] [Table 6]

[0177]

[0178] In [Table 6], the signaling information NZP-CSI-RS-Resource contains information about each CSI-RS. The information contained in the 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 for 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 CSI-RS is a periodic CSI-RS.

[0186] The resourceMapping included in the above signaling information NZP-CSI-RS-Resource indicates resource mapping information of the CSI-RS resource, and may include frequency resource 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 set 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 (density), CDM type, CSI-RS component RE pattern (pattern) frequency axis and time axis start position that can be set according to the number of CSI-RS ports (X). ), the number of frequency-axis REs (k') and the number of time-axis REs (l') of the CSI-RS component RE pattern (pattern) are represented. The aforementioned CSI-RS component RE pattern may be a basic unit configuring 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 position may be specified without limitation of subcarriers in the PRB (Physical Resource Block), and the CSI-RS RE position may 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 positions can be specified for every two subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 6-bit bitmap. When the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE positions can be specified for every four subcarriers in the PRB, and the CSI-RS RE positions can be specified by a 3-bit bitmap. Similarly, time axis RE positions can be specified by a bitmap of a total of 14 bits.

[0190] [CSI report configuration]

[0191] According to one embodiment of the present disclosure, a report setting can have a connection relationship with at least one ID of a resource setting by referencing the ID of the resource setting, and the resource setting(s) having a connection relationship with the report setting provide configuration information including information on 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 can be used for reporting channel information according to a reporting method set in the report setting having the connection relationship.

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

[0193] [Table 8]

[0194]

[0195]

[0196] [Table 8] Signaling information CSI-ReportConfig contains information about each report setting. The information contained in the 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 that has a relationship with report settings

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

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

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

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

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

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

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

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

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

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

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

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

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

[0213] The base station can 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 can instruct a terminal to perform an aperiodic channel information report (CSI report) through higher layer signaling or DCI using DCI format 0_1. The base station sets a parameter for the aperiodic CSI report of the terminal, or a plurality of CSI report trigger states including parameters for the CSI report, through higher layer signaling. The parameters for the CSI report or the CSI report trigger states can include a set including a slot interval or a possible slot interval between a PDCCH including the DCI and a PUSCH including the CSI report, a reference signal ID for channel state measurement, a type of channel information to be included, etc. When the base station instructs the terminal to perform some of the multiple CSI report trigger states through the DCI, the terminal reports channel information according to the CSI report settings of the report settings set in the instructed CSI report trigger states. The channel information reporting can be performed through a PUSCH scheduled with DCI format 0_1. The time domain resource allocation of the PUSCH including the CSI report of the terminal can be performed through the slot interval with the PDCCH indicated through the DCI, the start symbol and symbol length indication within the slot for the time domain resource allocation of the PUSCH, etc. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted can be indicated through the slot interval with the PDCCH indicated through the DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the DCI described above.

[0215] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report on the PUSCH via DCI using DCI format 0_1. The base station can activate or deactivate the semi-persistent CSI report transmitted on the PUSCH via DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures a parameter for the terminal's semi-persistent CSI report or multiple CSI report trigger states including the parameters for the semi-persistent CSI report through upper layer signaling. Parameters for a CSI report, or a CSI report trigger state, may include a set including a slot interval or possible slot intervals between a PDCCH including DCI indicating a CSI report and a PUSCH including the CSI report, a slot interval between a slot in which upper layer signaling indicating a CSI report is activated and a PUSCH including the CSI report, a slot interval period of the CSI report, a type of channel information included, etc. When a base station activates some of a plurality of CSI report trigger states or some of a plurality of report settings for a terminal through upper layer signaling or DCI, the terminal may report channel information according to a report setting included in the indicated CSI report trigger state or a CSI report setting set in the activated report setting.The above channel information reporting can be performed through a PUSCH that is semi-persistently scheduled with DCI format 0_1 ​​scrambled with SP-CSI-RNTI. The time domain resource allocation of the PUSCH including the CSI report of the terminal can be performed through the slot interval period of the CSI report, the slot interval with respect to the slot in which upper layer signaling is activated, the slot interval with respect to the PDCCH indicated through DCI, the start symbol and symbol length indication within the slot for time domain resource allocation of the PUSCH, etc. For example, the position of the slot in which the PUSCH including the CSI report of the terminal is transmitted can be indicated through the slot interval with respect to the PDCCH indicated through DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the DCI format 0_1 ​​described above.

[0216] For example, a base station can instruct a terminal to transmit a semi-persistent CSI report to a PUCCH through upper layer signaling such as MAC-CE. Through the MAC-CE signaling, the base station can activate or deactivate the semi-persistent CSI report transmitted to the PUCCH. When the semi-persistent CSI report is activated, the terminal can periodically report channel information according to the configured slot interval. When the semi-persistent CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures parameters for the semi-persistent CSI report of the terminal through upper layer signaling. The parameters for the CSI report can include a PUCCH resource through which the CSI report is transmitted, a slot interval period of the CSI report, the type of channel information included, etc. The terminal can transmit the CSI report through the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted through the PUSCH. The location of the PUCCH transmission slot including the CSI report can be indicated through the slot interval period of the CSI report set through upper layer signaling, the slot interval between the slot in which the upper layer signaling is activated and the PUCCH including the CSI report, and the start symbol and symbol length within the slot can be indicated through the start symbol and symbol length to which the PUCCH resource is allocated set through upper layer signaling.

[0217] For example, a base station can instruct a terminal to perform a periodic CSI report through upper layer signaling. The base station can activate or deactivate the periodic CSI report through upper layer signaling including RRC signaling. When the periodic CSI report is activated, the terminal can periodically report channel information according to a configured slot interval. When the periodic CSI report is deactivated, the terminal can stop the activated periodic channel information reporting. The base station configures a report setting including parameters for the terminal's periodic CSI report through upper layer signaling. The parameters for the CSI report can include a PUCCH resource setting for the CSI report, a slot interval between a slot in which upper layer signaling indicating the CSI report is activated and a PUCCH including the CSI report, a slot interval period of the CSI report, a reference signal ID for channel state measurement, the type of channel information included, etc. The terminal can transmit the CSI report through the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted on the PUSCH. The position of the slot in which the PUCCH including the CSI report is transmitted can be indicated through the slot interval period of the CSI report set through upper layer signaling, the slot interval between the slot in which the upper layer signaling is activated and the PUCCH including the CSI report, and the start symbol and symbol length within the slot can be indicated through the start symbol and symbol length to which the PUCCH resource is allocated set through upper layer signaling.

[0218] For the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with one downlink (DL) bandwidth part identified by the upper layer parameter bandwidth part identifier (bwp-id) given by the CSI resource setting, CSI-ResourceConfig, associated with the corresponding report setting. For the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, which can be configured from the base station to the terminal by the reportConfigType parameter configured from the upper layer. The semi-persistent CSI reporting method supports 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. For periodic or semi-permanent CSI reporting methods, the UE can receive PUCCH or PUSCH resources for transmitting CSI from the base station through higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources for transmitting CSI can be given as numerology of the uplink (UL) bandwidth portion configured for CSI report transmission. For aperiodic CSI reporting methods, the UE can receive scheduling of PUSCH resources for transmitting CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

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

[0220] - CSI-IM resources for interference measurements

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

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

[0223] For CSI-RS resource sets associated with resource settings where the upper layer parameter resourceType is set to 'aperiodic', 'periodic', or 'semi-persistent', the trigger state for the CSI report setting where reportType is set to 'aperiodic' and the resource settings for channel or interference measurements for one or more component cells (CCs) can be set with the upper layer parameter CSI-AperiodicTriggerStateList.

[0224] Aperiodic CSI reporting of a terminal can utilize PUSCH, periodic CSI reporting can utilize PUCCH, and semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or PUCCH after activation by MAC control element (MAC CE). As mentioned above, CSI resource settings can also be configured as aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 9] below.

[0225] [Table 9]

[0226]

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

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

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

[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 can be indicated by the CSI request field.

[0231] [Table 10] below shows an example of the relationship between a CSI request indicator and the CSI trigger state that can be indicated by the indicator.

[0232] [Table 10]

[0233]

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

[0235] FIG. 7 is a diagram illustrating an example of an aperiodic CSI reporting method according to one embodiment of the present disclosure.

[0236] In an example (700) of FIG. 7, the terminal can monitor the PDCCH (701) to obtain 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 when to perform measurement on the transmitted CSI-RS (702) resource based on the time point of receiving DCI format 0_1 ​​and the parameter (aperiodicTriggeringOffset described above) for the offset in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the terminal can receive an offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station through upper layer signaling, and the set offset value X can mean an offset between a slot in which a DCI that triggers aperiodic CSI reporting is received and a slot in which a CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have a mapping relationship described in [Table 11] below.

[0237] [Table 11]

[0238]

[0239] An example (700) of Fig. 7 shows an example in which the aforementioned offset value is set to X=0. In this case, the terminal can receive the CSI-RS (702) in a slot (corresponding to slot 0 (706) of Fig. 7) in which the DCI format 0_1 ​​that triggers the aperiodic CSI report is received, and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (705). The terminal can obtain scheduling information (information corresponding to each field of the aforementioned DCI format 0_1) for the PUSCH (705) for CSI reporting from the DCI format 0_1. As an example, the terminal can obtain information on a slot in which the PUSCH (705) is to be transmitted from the aforementioned time domain resource allocation information for the PUSCH (705) in the DCI format 0_1. In an example (700) of FIG. 7, the terminal acquires a K2 value corresponding to a slot offset value for PDCCH-to-PUSCH as 3, and accordingly, the PUSCH (705) can be transmitted in slot 3 (709), which is 3 slots away from slot 0 (706), at the time when the PDCCH (701) is received.

[0240] In an example (710) of FIG. 7, the terminal can monitor the PDCCH (711) to obtain DCI format 0_1, and from this, can obtain scheduling information and CSI request information for the PUSCH (715). The terminal can obtain resource information for the CSI-RS (712) to be measured from the received CSI request indicator. An example (710) of FIG. 7 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (712) in a slot (corresponding to slot 0 (716) of FIG. 7) in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received, and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (715).

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

[0242] [Table 12]

[0243]

[0244]

[0245] In particular, in the case of PUSCH repetition transmission methods A and B, the UE can transmit the aperiodic CSI report by multiplexing it only in the first repetition transmission among the PUSCH repetition transmissions. This is because the aperiodic CSI report information to be multiplexed is encoded in a polar code manner, and in this case, in order to be multiplexed in multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, so the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition.

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

[0247] [CSI computation time]

[0248] When a base station instructs a terminal to perform an aperiodic CSI report or a semi-persistent CSI report through DCI, the terminal can determine whether or not a valid channel report can be performed through the instructed CSI report by considering the channel calculation time (CSI computation time) required for the CSI report. For an aperiodic CSI report or a semi-persistent CSI report instructed through DCI, the terminal can perform a valid CSI report starting from the uplink symbol following the Z symbol after the last symbol included in the PDCCH including the DCI instructing the CSI report. The Z symbol described above may vary depending on the numerology of the downlink bandwidth part to which the PDCCH including the DCI instructing the CSI report corresponds, the numerology of the uplink bandwidth part to which the PUSCH transmitting the CSI report corresponds, and the type or characteristics (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.) of the channel information reported in the CSI report. In other words, in order for a CSI report to be judged as a valid CSI report (if the CSI report is a valid CSI report), the uplink transmission of the CSI report must not be performed before the Zref symbol, including the timing advance. In this case, the Zref symbol is the time starting from the moment when the last symbol of the triggering PDCCH ends. This is the uplink symbol that starts the CP (cyclic prefix). Here, the detailed value of Z is as described below. , , , , and is numerology. At this time Is The largest of It can be promised that it will use what causes the value, is the subcarrier spacing used for PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, may 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 It is also possible to promise to use something that causes a value. and The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 1.

[0249] In addition, if the reference signal for channel measurement for an aperiodic CSI report indicated to a terminal through DCI is an aperiodic reference signal, a valid CSI report can be performed starting from the uplink symbol after the Z' symbol after the last symbol including the reference signal ends, and the above-mentioned Z' symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH including the DCI indicating the CSI report, the numerology of the bandwidth corresponding to the reference signal for channel measurement for the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type 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, in order for a CSI report to be determined to be a valid CSI report (if the CSI report is a valid CSI report), the uplink transmission of the CSI report must not be performed before the Zref' symbol, including the timing advance. At this time, the Zref' symbol starts from the moment when the last symbol of the aperiodic CSI-RS or aperiodic CSI-IM triggered by the triggering PDCCH ends. This is an uplink symbol that starts CP (cyclic prefix). Here, the detailed value of Z' is explained below. , , , , and is numerology. At this time Is The largest of It can be promised that it will use what causes the value, is the subcarrier spacing used for triggering PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, may 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 It can be promised that the value will be used. At this time, and The definition of is referred to above. For convenience of future explanation, satisfying the above conditions is referred to as satisfying CSI reporting validity condition 2.

[0250] If the base station instructs the terminal to perform an aperiodic CSI report for an aperiodic reference signal through DCI, the terminal can perform a valid CSI report starting from the first uplink symbol that satisfies both the point in time Z symbols after the last symbol included in the PDCCH including the DCI indicating the CSI report and the point in time Z' symbols after the last symbol including the reference signal. That is, in the case of aperiodic CSI reporting based on the aperiodic reference signal, both CSI reporting validity conditions 1 and 2 must be satisfied to be considered a valid CSI report.

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

[0252] The Z, Z' symbols for calculating the CSI computation time mentioned above 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 ports of the reference signal is 4 or less, there is one reference signal resource, and the codebook type is 'typeI-SinglePanel' or the type of channel information to be reported (report quantity) is 'cri-RI-CQI', the Z, Z' symbols follow [Table 14]. follows the value. This will be referred to as delay requirement 2 in the future. In addition, if the PUSCH containing the CSI report does not contain TB or HARQ-ACK and the CPU occupation of the terminal is 0, the Z and Z' symbols are as in [Table 13]. The value is followed and is named as delay requirement 1. The description of the CPU occupation mentioned above is described in detail below. In addition, when the report quantity is 'cri-RSRP' or 'ssb-Index-RSRP', the Z, Z' symbols are as shown in [Table 14]. Follow the values. X1, X2, X3, and X4 in [Table 14] represent the UE capability for beam reporting time, and KB1 and KB2 in [Table 14] represent the UE capability for beam change time. In case it does not correspond to the type or characteristic of channel information reported in the above-mentioned CSI report, the Z and Z' symbols are in [Table 14]. Follow the value.

[0253] [Table 13]

[0254]

[0255] [Table 14]

[0256]

[0257] [CSI reference resource]

[0258] When a base station instructs a terminal to perform an aperiodic / semi-persistent / periodic CSI report, it may configure a CSI reference resource to determine a reference time and frequency for a channel to be reported in the CSI report. The frequency of the CSI reference resource may be the carrier and subband information for measuring CSI, which are indicated in the CSI report configuration, and these may correspond to the carrier and reportFreqConfiguration in the upper layer signaling CSI-ReportConfig, respectively. The time of the CSI reference resource may be defined based on the time at which the CSI report is transmitted. For example, when instructing to transmit CSI report #X in the uplink slot n' of the carrier and BWP where the CSI report is to be transmitted, the time of the CSI reference resource of CSI report #X may be defined as the carrier on which the CSI report is to be transmitted and the downlink slot n of the BWP, n-nCSI-ref. Downlink slot n is named as μDL for the carrier measuring CSI and the numerology of BWP, and μUL for the carrier transmitting CSI report #X and the numerology of BWP. It is calculated as follows. The slot interval between the downlink slot n and the CSI reference signal, nCSI-ref, is the number of CSI-RS / SSB resources for channel measurement when the CSI report #X transmitted in the uplink slot n' is a semi-persistent or periodic CSI report. If a single CSI-RS / SSB resource is connected to the corresponding CSI report, , and if multiple CSI-RS / SSB resources are connected to the corresponding CSI report. If the CSI report #X transmitted in uplink slot n' is an aperiodic CSI report, the CSI computation time Z' for channel measurement is considered. is calculated as mentioned above is the number of symbols contained in one slot, and in NR Assume that.

[0259] When a base station instructs a terminal to transmit a CSI report in uplink slot n' through upper layer signaling or DCI, the terminal may report CSI by performing channel measurement or interference measurement on a CSI-RS resource, CSI-IM resource, or SSB resource that is transmitted no later than the CSI reference resource slot of the CSI report transmitted in uplink slot n' among the CSI-RS resources, CSI-IM, or SSB resources associated with the CSI report. The CSI-RS resource, CSI-IM resource, or SSB resource associated with the above-mentioned CSI report may mean a CSI-RS resource, CSI-IM resource, or SSB resource included in a resource set set in a resource setting referenced by a report setting for a CSI report of a terminal set through upper layer signaling, or a CSI-RS resource, CSI-IM resource, or SSB resource referenced by a CSI report trigger state including parameters for the CSI report, or a CSI-RS resource, CSI-IM resource, or SSB resource indicated 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 a transmission time of CSI-RS / CSI-IM / SSB resource(s) determined by a higher layer configuration or a combination of the higher layer configuration and DCI triggering. For example, a semi-persistent or periodic CSI-RS resource determines a slot to be transmitted according to a slot period and slot offset configured by higher layer signaling, and the transmission symbol(s) within the slot are determined according to resource mapping information (resourceMapping). As another example, an aperiodic CSI-RS resource determines a slot to be transmitted according to a slot offset from a PDCCH including a DCI indicating channel reporting configured by higher layer signaling, and the transmission symbol(s) within the slot are determined according to resourceMapping information.

[0261] The above-mentioned 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, and accordingly, the following two interpretations are possible for the CSI-RS occasion according to each resource set configuration.

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

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

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

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

[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 among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', the latest CSI-IM occasion among the CSI-RS occasions for CSI report #X transmitted in uplink slot n', and the latest SSB occasion among the SSB occasions for CSI report #0 transmitted in uplink slot n'.

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

[0269] In the embodiments of the present disclosure, it is possible to individually apply 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". In addition, when the two interpretations (Interpretation 1-1, Interpretation 1-2) for the CSI-RS occasion, CSI-IM occasion, and SSB occasion described above are considered, in the embodiments of the present disclosure, it is possible to individually apply 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" 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 can instruct the CSI report by considering the amount of channel information that the terminal can calculate simultaneously for the CSI report, i.e. the number of channel information calculation units (CSI processing units, CPUs) of the terminal. The number of channel information calculation units that the terminal can calculate simultaneously If you say so, the terminal Do not expect CSI report instructions from base stations that require more channel information calculations, or We may not consider updating channel information that requires more channel information calculations. The terminal can report to the base station through upper layer signaling or the base station can set it through upper layer signaling.

[0271] The CSI report that the base station instructs 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 used for calculating channel information. For each CSI report, for example, a CSI report The number of channel information calculation units required for Then, 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 for each reportQuantity set in the CSI report can be set as shown in [Table 15] below.

[0272] [Table 15]

[0273]

[0274] The number of channel information calculations required by a terminal for multiple CSI reports at a given point in time is the number of channel information calculation units that the terminal can calculate simultaneously. If there are more than this, the terminal may not consider updating channel information for some CSI reports. Among the multiple indicated CSI reports, the CSI reports that do not consider updating channel information are determined at least by considering the CPU time required for calculating channel information for the CSI report and the priority of the channel information being reported. For example, the channel information update may not be considered for the CSI report whose channel information calculation requires the latest CPU time, and it is also possible to preferentially not consider updating channel information for CSI reports with lower channel information priorities.

[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 through the priority value PriiCSI(y,k,c,s) in [Table 16]. Referring to [Table 16], the CSI priority value is determined through 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 on 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 values ​​PriiCSI(y,k,c,s) and determining that the CSI priority for a CSI report with a smaller priority value is higher.

[0279] If the time taken by the CPU to calculate the channel information required for the CSI report instructed by the base station to the terminal is called CPU occupation time, then the 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 slot or symbol occupied by the upper layer signaling or DCI indicating the CSI report, and part or all of the slot or symbol occupied by the reference signal for channel state measurement.

[0280] [PDCCH: DCI related]

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

[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 a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0283] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

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

[0285] DCI format 0_0 can be used as a fallback 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 can include, for example, the information in [Table 17] below.

[0286] [Table 17]

[0287]

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

[0289] [Table 18]

[0290]

[0291]

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

[0293] [Table 19]

[0294]

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

[0296] [Table 20]

[0297]

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

[0299] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0300] FIG. 8 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure.

[0301] FIG. 8 illustrates an example in which two control regions (Control Region #1 (801), Control Region #2 (802)) are set within a UE bandwidth part (810) on the frequency axis and within one slot (820) on the time axis. The control regions (801, 802) can be set to specific frequency resources (803) within the entire UE bandwidth part (810) on the frequency axis. The time axis can be set to one or more OFDM symbols, which can be defined as the control region length (Control Resource Set Duration, 804). Referring to the example illustrated in FIG. 8, Control Region #1 (801) is set to a control region length of two symbols, and Control Region #2 (802) is set to a control region length of one symbol.

[0302] The control region in the aforementioned 5G can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, frequency location of the control region, and symbol length of the control region. For example, this information 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 region.

[0306] Figure 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.

[0307] According to FIG. 9, the basic unit of time and frequency resources constituting the control channel can be referred to as 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, i.e., 12 subcarriers. The base station can concatenate REGs (903) to configure a downlink control channel allocation unit.

[0308] 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), 1 CCE (904) can be composed of multiple REGs (903). Taking the REG (903) illustrated in FIG. 9 as an example, the REG (903) can be composed of 12 REs, and if 1 CCE (904) is composed of 6 REGs (903), 1 CCE (904) can be composed of 72 REs. When a downlink control region is established, the region 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 region. CCEs (904) within the control area are distinguished by numbers, and the numbers of the CCEs (904) can be assigned according to a logical mapping method.

[0309] The basic unit of the downlink control channel illustrated in FIG. 9, that is, the REG (903), may include both the REs to which the DCI is mapped and the areas to which the DMRS (905), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 9, three DMRSs (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 a 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 (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

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

[0311] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot 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 corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the information in [Table 22] below can be included.

[0312] [Table 22]

[0313]

[0314] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

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

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

[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 a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

[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 RNTIs specified may follow the definitions and uses below.

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

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

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

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

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

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

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

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

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

[0335] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for 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 region p and search space set s can be expressed as in [Mathematical Formula 1] below.

[0340] [Mathematical Formula 1]

[0341]

[0342] - : Integration level

[0343] - : Carrier Index

[0344] - : Total number of CCEs existing within the control region p

[0345] - : slot index

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

[0347] - = 0, ..., : PDCCH candidate index of aggregation level L

[0348] - i = 0, ..., L -1

[0349] - , , , , ,

[0350] - : Terminal identifier

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

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

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

[0354] [PDSCH / PUSCH: Frequency Resource Allocation Related]

[0355] Next, we describe the frequency domain resource assignment (FDRA) for the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) in NR.

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

[0357] 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 set through an upper layer in an NR wireless communication system.

[0358] 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 RBG It contains a bitmap consisting of N bits. The conditions for this will be explained later. At this time, N RBG refers to the number of RBGs (resource block groups) determined according to the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size as shown in [Table 24] below, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0359] [Table 24]

[0360]

[0361] The size of the frequency resource in the bandwidth part can be defined as the number of RBs included in the bandwidth part. More specifically, if the terminal is instructed to allocate FDRA type-0 resources, the length of the FDRA field of the DCI received by the terminal is the number of RBGs (N) in the bandwidth part. RBG ) and Here, the first RBG within the bandwidth section is It contains RBs of the dog, and the last RBG within the bandwidth part is On the other hand, Contains the RBs of the dog, otherwise, It contains P RBs. The remaining RBGs within the bandwidth portion contain P RBs, where P is the number of nominal RBGs determined according to [Table 24] above.

[0362] If the terminal is configured to use only FDRA type 1 through upper layer signaling (1005), the DCI that allocates PDSCH or PUSCH to the terminal is It contains 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 of frequency axis resources (1025) allocated continuously therefrom.

[0363] If a 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 composed of bits of the larger value (1035) among the payload (1015) for configuring FDRA type-0 resource allocation and the payload (1020, 1025) for configuring FDRA type-1 resource allocation. The conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that FDRA type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that FDRA type-1 resource allocation is used.

[0364] If the terminal has been set to use the FDRA type-2 resource allocation method through upper layer signaling, the terminal can be instructed by the base station about the FDRA type-2 resource allocation method according to the following method.

[0365] The terminal can receive RB allocation information from the base station, which is a set of M interlace indices.

[0366] Interlace Index Silver is common It can be composed of fields, and M can be defined as in [Table 25].

[0367] [Table 25]

[0368]

[0369] RB in interlace m and bandwidth part i and common RB The relationship with can be defined as follows:

[0370]

[0371] When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlace set with m0 + l indices can be notified from the base station to the terminal. In addition, the resource allocation field can be configured with a resource indicator value (RIV). The resource indicator value , When the starting interlace m0 and the number of consecutive interlaces It can be composed of , and its values ​​are as follows:

[0372]

[0373] The resource indicator value is When this happens, the resource indicator value is composed of the start interlace index m0 and l values ​​and can be configured as in [Table 26].

[0374] [Table 26]

[0375]

[0376] 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 in 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.

[0377] Also, the least significant bit (LSB) of the FDRA field for 15 kHz and 30 kHz may mean a set of consecutive RBs of PUSCH scheduled with DCI format 0_1. The Y bit may be configured as a resource indication value (RIVRBset). , In , the RIVRBset value is the starting RB set ( ) and the number of consecutive RB sets ( ) can be determined. The RIVRBset value can be defined as follows.

[0378]

[0379] It refers to the number of RB sets included in the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set by upper signaling (or preset).

[0380] [PDSCH / PUSCH: Time Resource Allocation Related]

[0381] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0382] A base station can set up a table for time domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) to a terminal via higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for the PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for the PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of a start symbol for which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 27] or [Table 28] below may be transmitted from a base station to a terminal.

[0383] [Table 27]

[0384]

[0385] [Table 28]

[0386]

[0387] The base station can 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 in the DCI). The terminal can obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

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

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

[0390] [PUSCH: Transmission Method Related]

[0391] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

[0392] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 29] through higher-order signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 29] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-order signaling of [Table 29], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 30]. If the terminal has been 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 transmission operated by the configured grant.

[0393] [Table 29]

[0394]

[0395] 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 or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 30], is 'codebook' or 'nonCodebook'.

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

[0397] [Table 30]

[0398]

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

[0400] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0401] 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 layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0402] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value 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.

[0403] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

[0404] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0405] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE 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 UE is less than 42 symbols, the UE does not expect information about the precoder for SRS transmission to be updated.

[0406] 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. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0407] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS within the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS within the upper-level signaling SRS-ResourceSet to be configured together.

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

[0409] 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 measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0410] [PUSCH: Preparation time]

[0411] Next, the PUSCH preparation procedure time is described. When the base station schedules a UE to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method indicated through the DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). NR takes this into account and defines the PUSCH preparation procedure time. The PUSCH preparation procedure time of the UE can follow the following [Mathematical Formula 2].

[0412] [Equation 2]

[0413]

[0414] As described in [Mathematical Formula 2] In , each variable can have the following meanings:

[0415] - N2: The number of symbols determined by the UE processing capability (UE processing capability) 1 or 2 and the numerology μ according to the UE's capability. If UE processing capability 1 is reported according to the UE's capability report, it has the value of [Table 31]. If UE processing capability 2 is reported and the availability of UE processing capability 2 is set through upper layer signaling, it can have the value of [Table 32].

[0416] [Table 31]

[0417]

[0418] [Table 32]

[0419]

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

[0421] - : 64

[0422] - μ: or Medium, T proc,2 This follows the larger value. refers to the numerology of the downlink in which the PDCCH containing the DCI for scheduling the PUSCH is transmitted, It refers to the numerology of the uplink in which PUSCH is transmitted.

[0423] - T c : has

[0424] - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it has 0.

[0425] - d2: When the OFDM symbols of a PUCCH with a high priority index and a PUCCH with a low priority index overlap in time, the d2 value of the PUSCH with the high priority index is used. Otherwise, d2 is 0.

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

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

[0428] When the base station and the terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, the base station and the terminal determine T from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2 If the first symbol of the PUSCH begins before the first uplink symbol of the CP, the PUSCH preparation time is determined to be insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the PUSCH preparation time is insufficient.

[0429] [PUSCH: Repetitive Transmission Related]

[0430] 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 be configured with either PUSCH repetitive transmission type A or B via upper layer signaling.

[0431] 1. PUSCH Repetitive Transmission Type A

[0432] - As described above, the symbol length and the position of the start symbol of the uplink data channel are determined by the time domain resource allocation method within one 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).

[0433] - The terminal can repeatedly transmit an uplink data channel having the same length and start symbol as the configured uplink data channel based on the number of repeated transmissions received from the base station in consecutive slots. At this time, if at least one symbol among the slots configured by the base station as downlink to the terminal or the symbols of the uplink data channel configured to the terminal is configured as downlink, the terminal skips the uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel. In other words, although it is included in the number of repeated transmissions of the uplink data channel, the uplink data channel may not be transmitted. On the other hand, a terminal that supports Rel-17 repeated uplink data transmission determines a slot in which repeated uplink data transmission is possible as an available slot, and can count the number of transmissions when repeated uplink data channels are transmitted in slots determined as available slots. If repeated uplink data channel transmission is omitted in a slot determined as an available slot, the terminal does not count the omitted repeated transmission and can postpone it until the next available slot before transmitting.

[0434] - In order to determine the available slot, if at least one symbol set to TDRA (time domain resource allocation) for PUSCH in a slot for PUSCH transmission overlaps with a symbol for a purpose other than uplink transmission (e.g., downlink), the slot is determined as an unavailable slot (e.g., a slot that is not an available slot and is determined to be unavailable for PUSCH transmission). In addition, the available slot may be considered as an uplink resource for determining resources for PUSCH transmission and transport block size (TBS) in repeated PUSCH transmission and multi-slot PUSCH transmission consisting of one TB (TBoMS (transport block on multiple slots)).

[0435] 2. PUSCH Repetitive Transmission Type B

[0436] - As described above, the start symbol and length of the uplink data channel are determined by a time domain resource allocation method within one 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).

[0437] - First, the nominal repetition of the uplink data channel is determined based on the start symbol and length of the established uplink data channel as follows. The slot where the nth nominal repetition starts is The symbol given by and starting from that slot is is given by . The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is is given by . Here, n=0,..., numberofrepetitions-1, S represents the start symbol of the established uplink data channel, and L represents the symbol length of the established uplink data channel. indicates the slot in which the PUSCH transmission starts. Indicates the number of symbols per slot.

[0438] - The terminal may determine a specific OFDM symbol as an invalid symbol for the following cases for PUSCH repetitive transmission type B.

[0439] o Symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated may be determined as invalid symbols for PUSCH repetition transmission type B.

[0440] o In unpaired spectrum (TDD spectrum), symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, which is a higher layer signaling, for SSB reception may be determined as invalid symbols for PUSCH repetition transmission type B.

[0441] o In unpaired spectrum (TDD spectrum), symbols indicated through pdcch-ConfigSIB1 in the MIB to transmit a control resource set associated with a Type0-PDCCH CSS set may be determined as invalid symbols for PUSCH repetition transmission Type B.

[0442] o In Unpaired spectrum (TDD spectrum), if the upper layer signaling numberOfInvalidSymbolsForDL-UL-Switching is set, symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for numberOfInvalidSymbolsForDL-UL-Switching can be determined as invalid symbols.

[0443] - Additionally, an invalid symbol can be set in a higher layer parameter (e.g., InvalidSymbolPattern). The higher layer parameter (e.g., InvalidSymbolPattern) provides a symbol-level bitmap spanning one or two slots, where an invalid symbol can be set. A 1 in the bitmap indicates an invalid symbol. Additionally, the period and pattern of the bitmap can be set via a higher layer parameter (e.g., periodicityAndPattern). If the higher 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 layer 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.

[0444] After invalid symbols are determined, for each nominal repetition, the UE may consider symbols other than the invalid symbol as valid symbols. If each nominal repetition contains at least one valid symbol, the nominal repetition may contain one or more actual repetitions. Here, each actual repetition contains a contiguous set of valid symbols that can be used for PUSCH repetitive transmission type B within a single slot. If the OFDM symbol length of the nominal repetition is not 1, the UE may ignore the transmission for the corresponding actual repetition if the actual repetition length is 1.

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

[0446] When the base station configures 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 terminal can determine available slots for the configured uplink resources according to the following two methods.

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

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

[0449] As an example of a method for determining available slots based on a TDD configuration, in FIG. 12, when the TDD configuration is set to 'DDFUU' through upper layer signaling, the base station and terminal can determine slot #3 and slot #4 set to uplink 'U' based on the TDD configuration as available slots (1201). At this time, slot #2 (1202) set to 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 settings.

[0450] As an example of a method for determining available slots considering TDD configuration and 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 that satisfy SLIV of PUSCH for the set uplink slot 'U' as available slots. At this time, the base station and the terminal may determine slot #2 ('L=9') that does not satisfy SLIV, which is a TDRA condition for PUSCH transmission. 'L=12') can be judged as an unavailable slot (1203). This is for illustrative purposes only and does not limit the scope to PUSCH transmission. It can also be applied to PUCCH transmission, PUSCH / PUCCH repeated transmission, nominal repetition of PUSCH repetition type B, and TBoMS.

[0451] FIG. 13 is a diagram illustrating an example of PUSCH repetition transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0452] The terminal may set the start symbol S of the uplink data channel to 0, the length L of the uplink data channel to 14, and the number of repeated transmissions to 16. In this case, the nominal repetition is indicated in 16 consecutive slots (1301). After that, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (1301) is an invalid symbol. In addition, the terminal determines that the symbols set to 1 in the invalid symbol pattern (1302) are invalid symbols. If valid symbols that are not invalid symbols in each nominal repetition consist of one or more consecutive symbols in one slot, they are set to the actual repetition and transmitted (1303).

[0453] Additionally, for PUSCH repetitive transmissions, NR Release 16 can define the following additional methods for UL grant-based PUSCH transmissions across slot boundaries and configured grant-based PUSCH transmissions:

[0454] - Method 1 (mini-slot level repetition): Two or more PUSCH repetitive transmissions are scheduled within a slot or across the boundaries of consecutive slots through a single UL grant. In addition, for Method 1, the time-domain resource allocation information in the DCI indicates the resources of the first repetitive transmission. In addition, the time-domain resource information of the first repetitive transmission and the time-domain resource information of the remaining repetitive transmissions can be determined based on the uplink or downlink direction determined for each symbol in each slot. Each repetitive transmission occupies consecutive symbols.

[0455] - Method 2 (multi-segment transmission): Two or more repeated PUSCH transmissions are scheduled in consecutive slots through a single UL grant. At this time, one transmission is designated for each slot, and each transmission may have a different starting point or repetition length. In addition, in Method 2, the time-domain resource allocation information in the DCI indicates the starting point and repetition length of all repeated transmissions. In addition, when performing repeated transmissions in a single slot through Method 2, if there are multiple sets of consecutive uplink symbols in the slot, each repeated transmission is performed for each set of uplink symbols. If there is only one set of consecutive uplink symbols in the slot, one repeated PUSCH transmission is performed according to the method of NR Release 15.

[0456] - Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive slots via two or more UL grants. In this case, one transmission is designated for each slot, and the nth UL grant can be received before the PUSCH transmission scheduled for the n-1th UL grant ends.

[0457] - Method 4: One or more PUSCH repetitive transmissions within a single slot, or two or more PUSCH repetitive transmissions across the boundaries of consecutive slots, can be supported through one UL grant or one configured grant. The number of repetitions indicated by the base station to the terminal is only a nominal value, and the number of PUSCH repetitive transmissions actually performed by the terminal may be greater than the nominal number of repetitions. The time-domain resource allocation information in the DCI or the configured grant indicates the resources of the first repetitive transmission indicated by the base station. The time-domain resource information of the remaining repetitive transmissions can be determined with reference to at least the resource information of the first repetitive transmission and the uplink or downlink direction of the symbols. If the time-domain resource information of the repetitive transmission indicated by the base station crosses a slot boundary or includes an uplink / downlink switchover point, the repetitive transmission can be divided into multiple repetitive transmissions. In this case, one repetitive transmission can be included for each uplink period within one slot.

[0458] [PUSCH: Frequency Hopping Process]

[0459] Below, we specifically describe frequency hopping of the uplink data channel (PUSCH) in a 5G system.

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

[0461] The intra-slot frequency hopping method supported by PUSCH repetitive transmission type A is a method in which a terminal transmits by changing the allocated frequency domain resources by a set frequency offset in two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be expressed using [Mathematical Formula 3].

[0462] [Equation 3]

[0463]

[0464] In [Mathematical Formula 3], i=0 and i=1 represent the first hop and the second hop, respectively. Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. The upper layer parameter indicates the frequency offset between two hops. The number of symbols in the first hop is can be represented as , and the number of symbols in the second hop is can be expressed as is the length of PUSCH transmission within one slot, expressed as the number of OFDM symbols.

[0465] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal changes the allocated resources of the frequency domain by a set frequency offset for each slot and transmits them. In inter-slot frequency hopping, The starting RB during the slot can be expressed by [Mathematical Formula 4].

[0466] [Equation 4]

[0467]

[0468] In [Equation 4], is the current slot number in multi-slot PUSCH transmission, Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. Indicates the frequency offset between two hops through upper layer parameters.

[0469] Next, the inter-repetition frequency hopping method supported by PUSCH repetitive transmission type B is to transmit the allocated resources in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. RB is the index of the starting RB in the frequency domain for one or more actual repetitions within the nth nominal repetition. start (n) can follow the following [Mathematical Formula 5].

[0470] [Equation 5]

[0471]

[0472] In [Mathematical Equation 5], n is the index of nominal repetition, Indicates the RB offset between two hops via upper layer parameters.

[0473] [PUSCH: Transmission Power Related]

[0474] Below, a method for determining the transmission power of an uplink data channel in a 5G system is specifically described.

[0475] In a 5G system, the transmission power of an uplink data channel can be determined using the following [Mathematical Formula 6].

[0476] [Equation 6]

[0477]

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

[0479] [Table 33]

[0480]

[0481] [PUSCH: TPMI Related]

[0482] Next, we describe the TPMI (Transmit Precoding Matrix Indicator) indicated by the base station through DCI during codebook-based PUSCH transmission.

[0483] If the terminal is scheduled for 1-layer transmission using a single PUSCH antenna port by the base station via DCI or higher layer signaling, the TPMI can be defined as W=1. Otherwise, that is, if the terminal is scheduled for 1-layer or higher PUSCH transmission using multiple PUSCH antenna ports by the base station via DCI or higher layer signaling, the TPMI W can be defined as in [Table 34] to [Table 40] below.

[0484] [Table 34]

[0485]

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

[0487] [Table 35]

[0488]

[0489] The above [Table 35] shows the TPMI for a 1-layer case where the terminal has 4 PUSCH antenna ports, transform precoding is used (i.e., DFTS-OFDM waveform is used). In the above [Table 35], if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 3, if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 11, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 27.

[0490] [Table 36]

[0491]

[0492] The above [Table 36] shows the TPMI for a 1-layer case where the terminal has 4 PUSCH antenna ports, no transform precoding is used (i.e., CP-OFDM waveform is used). In the above [Table 36], if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 3, if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 11, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indexes 0 to 27.

[0493] [Table 37]

[0494]

[0495] The above [Table 37] shows a 2-layer TPMI when a terminal has two PUSCH antenna ports, no transform precoding is used (i.e., a CP-OFDM waveform is used). In the above [Table 37], if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal to select TPMI index 0, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal to select one of TPMI index 0 to 2.

[0496] [Table 38]

[0497]

[0498] The above [Table 38] shows a 2-layer TPMI when a terminal has 4 PUSCH antenna ports, no transform precoding is used (i.e., a CP-OFDM waveform is used). In the above [Table 38], if a terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 5, if a terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 13, and if a terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 21.

[0499] [Table 39]

[0500]

[0501] The above [Table 39] shows a 3-layer TPMI when a terminal has 4 PUSCH antenna ports, no transform precoding is used (i.e., a CP-OFDM waveform is used). In the above [Table 39], if a terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by TPMI index 0, if a terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indexes 0 to 2, and if a terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indexes 0 to 6.

[0502] [Table 40]

[0503]

[0504] The above [Table 40] shows a 4-layer TPMI when a terminal has 4 PUSCH antenna ports, no transform precoding is used (i.e., a CP-OFDM waveform is used). In the above [Table 40], if a terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by TPMI index 0, if a terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indexes 0 to 2, and if a terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indexes 0 to 4.

[0505] [Regarding terminal capability reporting]

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

[0507] A base station can transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station, or the base station can include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can compose a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, a UE capability request can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). Additionally, the terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but the base station may request it under any conditions when necessary.

[0508] In the above step, the terminal that receives the UE capability report request from the base station configures the terminal capability based on the RAT type and band information requested from the base station. Below is a summary of how the terminal configures the UE capability in the NR system.

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

[0510] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the UE completely removes NR SA BCs from the list of configured BC candidates. This operation can only occur when the LTE base station (eNB) requests the "eutra" capability.

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

[0512] 4. The terminal selects BCs to report 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 set order. That is, the terminal constructs BCs and UE capabilities to report according to the preset rat-Type order (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0513] 5. Also, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set is included only in UE-NR-Capabilities.

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

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

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

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

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

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

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

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

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

[0523] - MIB (Master Information Block)

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

[0525] - RRC (Radio Resource Control)

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

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

[0528] - PDCCH (Physical Downlink Control Channel)

[0529] - DCI (Downlink Control Information)

[0530] - UE-specific DCI

[0531] - Group common DCI

[0532] - Common DCI

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

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

[0535] - PUCCH (Physical Uplink Control Channel)

[0536] - UCI (Uplink Control Information)

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

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

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

[0540] As one embodiment of the present disclosure, a method for a terminal to be scheduled for a PUSCH that does not include a transport block (TB) and to multiplex and transmit a CSI report within the PUSCH is described. This embodiment can be operated in combination with other embodiments of the present disclosure. The terminal being scheduled for a PUSCH that does not include a TB may mean that the UL-SCH indicator field, which is a 1-bit field in the DCI received by the terminal, indicates 0, and in this case, the terminal can multiplex and transmit a CSI report without including data within the PUSCH.

[0541] Hereinafter, an operation of determining a table that a terminal can consider in order to interpret a Time Domain Resource Assignment (TDRA) field within a specific DCI format (e.g., DCI format 0_1, 0_2, or 0_3) received by the terminal is described. At this time, the table that the terminal can consider can be determined based on which DCI format the terminal interprets (for example, one of DCI formats 0_1, 0_2, or 0_3) and the upper layer signaling configuration conditions received by the terminal, as mentioned in [Table 41], [Table 42], or [Table 43] below. In addition, the terminal can further consider an RNTI associated with the specific DCI format in order to interpret the TDRA field. For specific operations, refer to the specific examples below.

[0542] The terminal may determine upper layer signaling related to time resource allocation that can be applied to the Time Domain Resource Assignment field in DCI format 0_1 ​​monitored in the terminal-specific search space, including a CRC scrambled with C-RNTI, modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), CS-RNTI, or semi persistent-channel state information-radio network temporary identifier (SP-CSI-RNTI) through [Table 41] below.

[0543] - For example, row 3 in [Table 41] below may mean that if the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (No), does not set pusch-TimeDomainAllocationList in pusch-Config (No), does not set pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (No), and does not set pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal has received DCI format 0_1 ​​that satisfies the above conditions and can use the Default A table for PUSCH when interpreting the time domain resource assignment field in the DCI. For example, if the terminal receives the DCI format 0_1 ​​and receives a value of m=10 through the time domain resource assignment field in the DCI, the terminal can use the m+1 = 11th row in the Default A table for PUSCH to consider it as time resource allocation information for the PUSCH and obtain it. The Default A table for PUSCH can be confirmed through [Table 44] and [Table 45] below.

[0544] - As another example, row 4 in [Table 41] below may mean that if the terminal has configured pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), has not configured pusch-TimeDomainAllocationList in pusch-Config (No), has not configured pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (No), and has not configured pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal has received DCI format 0_1 ​​that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList configured in pusch-Configcommon.

[0545] - As another example, row 5 in [Table 41] below may mean that if the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, or does set it (No / Yes), sets pusch-TimeDomainAllocationList in pusch-Config (Yes), does not set pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (No), and does not set pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal has received DCI format 0_1 ​​that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList set in pusch-Config.

[0546] - As another example, row 6 in [Table 41] below may mean that if the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, or sets it (No / Yes), does not set pusch-TimeDomainAllocationList in pusch-Config (No), and sets pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (Yes), the terminal has received DCI format 0_1 ​​that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationListDCI-0-1 set in pusch-Config.

[0547] - As another example, row 7 in [Table 41] below may mean that if the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, or sets it (No / Yes), does not set pusch-TimeDomainAllocationList in pusch-Config (No), and sets pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (Yes), the terminal has received DCI format 0_1 ​​that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationListForMultiPUSCH set in pusch-Config.

[0548] [Table 41]

[0549]

[0550] The terminal may determine upper layer signaling related to time resource allocation that includes a CRC scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI and that can be applied to the Time Domain Resource Assignment field in DCI format 0_2 monitored in the terminal-specific search space through [Table 42] below.

[0551] - For example, the 3rd row in [Table 42] below may mean that if the UE does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (No), does not set pusch-TimeDomainAllocationList in pusch-Config (No), and does not set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (No), the UE receives DCI format 0_2 that satisfies the above conditions and can use the Default A table for PUSCH to interpret the time domain resource assignment field in the corresponding DCI. For example, if the UE receives the DCI format 0_2 and receives a value of m=10 through the time domain resource assignment field in the corresponding DCI, the UE can regard and obtain the m+1 = 11th row in the Default A table for PUSCH as time resource allocation information for the corresponding PUSCH. At this time, the Default A table for PUSCH can be confirmed through [Table 44] and [Table 45] below.

[0552] - As another example, row 4 in the table [Table 42] below may mean that if the terminal has set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), has not set pusch-TimeDomainAllocationList in pusch-Config (No), and has not set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (No), the terminal has received DCI format 0_2 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList set in pusch-Configcommon.

[0553] - As another example, row 5 in the table [Table 42] below may mean that if the terminal has set or not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, (No / Yes), has set pusch-TimeDomainAllocationList in pusch-Config (Yes), and has not set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (No), the terminal has received DCI format 0_2 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList set in pusch-Config.

[0554] - As another example, row 6 in the table [Table 42] below may mean that if the terminal has set or not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, (No / Yes), has not set pusch-TimeDomainAllocationList in pusch-Config (No), and has set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (Yes), the terminal has received DCI format 0_2 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationListDCI-0-2 set in pusch-Config.

[0555] [Table 42]

[0556]

[0557] The terminal may determine upper layer signaling related to time resource allocation that includes a CRC scrambled with C-RNTI or MCS-C-RNTI and that can be applied to the Time Domain Resource Assignment field in DCI format 0_3 monitored in the terminal-specific search space through [Table 43] below.

[0558] - For example, the 3rd row in [Table 43] below may mean that if the UE does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (No), does not set pusch-TimeDomainAllocationList in pusch-Config (No), and does not set pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (No), the UE receives DCI format 0_3 that satisfies the above conditions and can use the Default A table for PUSCH to interpret the time domain resource assignment field in the DCI. For example, if the UE receives the DCI format 0_3 and receives a value of m=10 through the time domain resource assignment field in the DCI, the UE can regard and obtain the m+1 = 11th row in the Default A table for PUSCH as time resource allocation information for the PUSCH. At this time, the Default A table for PUSCH can be confirmed through [Table 44] and [Table 45] below.

[0559] - As another example, row 4 in [Table 43] below may mean that if the terminal has set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), has not set pusch-TimeDomainAllocationList in pusch-Config (No), and has not set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (No), the terminal has received DCI format 0_3 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList set in pusch-Configcommon.

[0560] - As another example, row 5 in [Table 43] below may mean that if the terminal receives or does not receive (No / Yes) pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, or receives (Yes) pusch-TimeDomainAllocationList in pusch-Config, or does not receive (No) pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config, the terminal has received DCI format 0_3 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationList set in pusch-Config.

[0561] - As another example, row 6 in [Table 43] below may mean that if the terminal has set or not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, or has not set pusch-TimeDomainAllocationList in pusch-Config (No), or has set pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config (Yes), the terminal has received DCI format 0_3 that satisfies the above conditions and can interpret the time domain resource assignment field in the DCI using pusch-TimeDomainAllocationListDCI-0-1 set in pusch-Config.

[0562] [Table 43]

[0563]

[0564] [Table 44] and [Table 45] below show the Default A table that can be used when allocating time resources of the PUSCH mentioned in [Table 41], [Table 42], or [Table 43] above. [Table 44] and [Table 45] can be used in the case of a general CP (cyclic prefix) and an extended CP, respectively. Table 44 applies when a general CP is used, and Table 45 applies when an extended CP is used. In [Table 44] and [Table 45] below, j can be determined according to the subcarrier spacing for PUSCH transmission. For example, the UE can determine the value of j to be 1, 1, 2, or 3, respectively, depending on whether the subcarrier spacing for PUSCH transmission is 15 kHz, 30 kHz, 60 kHz, or 120 kHz. In [Table 44] and [Table 45] below, K2 is information indicating a slot offset, and indicates a slot offset value from a slot in which DCI is received, S indicates a start symbol, and the start symbol indicates the position of the start symbol in the slot in which PUSCH is transmitted, and L indicates the length of a symbol allocated for PUSCH transmission.

[0565] [Table 44]

[0566]

[0567] [Table 45]

[0568]

[0569] For example, if the terminal has been provided with search space and control resource set configuration from the base station so that the terminal can monitor DCI formats 0_1 and 0_2, and the terminal has configured pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), has not configured pusch-TimeDomainAllocationList in pusch-Config (No), and has not configured pusch-TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-2, and pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal can interpret the time domain resource assignment field in DCI formats 0_1 and 0_2 using pusch-TimeDomainAllocationList configured in pusch-Configcommon. That is, in the case where the terminal has received upper layer signaling as described above, the time domain resource assignment field in DCI formats 0_1 and 0_2 can be interpreted using pusch-TimeDomainAllocationList in pusch-Configcommon, which is the same upper layer signaling.

[0570] As another example, if the terminal has been provided with a search space and control resource set configuration from the base station so that the terminal can monitor DCI formats 0_1 and 0_2, and the terminal has configured pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), has not configured pusch-TimeDomainAllocationList in pusch-Config (No), has not configured pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config (No), has configured pusch-TimeDomainAllocationListDCI-0-2 (Yes), and has not configured pusch-TimeDomainAllocationListForMultiPUSCH (No), the terminal may interpret the time domain resource assignment fields in DCI formats 0_1 and 0_2 based on different upper layer signaling. Under these conditions, when interpreting the time domain resource assignment field in DCI format 0_1, the terminal can interpret it using pusch-TimeDomainAllocationList set in pusch-Configcommon, and when interpreting the time domain resource assignment field in DCI format 0_2, the terminal can interpret it using pusch-TimeDomainAllocationListDCI-0-2 set in pusch-Config. Through the time resource allocation information corresponding to different upper layer signaling in this way, the terminal can receive different DCI formats from the base station and interpret different time resource allocation information, so the base station can schedule in a more flexible time resource allocation manner.

[0571] The terminal can interpret the time domain resource assignment field in the uplink scheduling DCI (one of DCI formats 0_1, 0_2, or 0_3) through the above time resource allocation information interpretation method.

[0572] If a UE is scheduled to transmit one or more CSI reports multiplexed via a PUSCH that does not include a TB through a CSI request field in the DCI, the UE may interpret and apply the time domain resource assignment field in the DCI to the time resource allocation information of the PUSCH (e.g., Start and Length Indicator Value (SLIV) representing a start symbol and the length of consecutive symbols therefrom, or a start symbol S that can be used for PUSCH repetition type B transmission and L representing the length of consecutive symbols therefrom, PUSCH mapping type, and slot offset from the DCI to the PUSCH transmission), and may interpret and apply only the slot offset information from the DCI to the PUSCH transmission by interpreting other upper layer signaling. That is, the UE may ignore the slot offset value from the DCI to the PUSCH that can be obtained when interpreting the time domain resource assignment field in the DCI, and may obtain the information (slot offset information from the DCI to the PUSCH transmission) through other parameters. To this end, the terminal may set at least one of reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2, reportSlotOffsetListDCI-0-1-r17, reportSlotOffsetListDCI-0-2-r17, and reportSlotOffsetList-r17 in CSI-ReportConfig, which is an upper layer signaling.

[0573] The above upper layer signaling reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2, reportSlotOffsetListDCI-0-1-r17, reportSlotOffsetListDCI-0-2-r17, reportSlotOffsetListDCI-0-2-r17 may include a list of slot offsets, and if the value indicated by the time domain resource assignment field in the DCI among one or more entries in this list is m, the terminal may use the slot offset corresponding to the (m+1)th entry to calculate the slot offset from the DCI and transmit the PUSCH. The slot offset determined in this way may be used as a parameter for determining the slot offset of the CSI report corresponding to the CSI-ReportConfig including the above upper layer signaling when the CSI report is multiplexed on the PUSCH and transmitted. If a terminal is scheduled to multiplex CSI reports corresponding to one or more CSI-ReportConfigs within a PUSCH without TB, the terminal may perform PUSCH transmission using a slot offset corresponding to the maximum value among the (m+1)th entries in the list of slot offsets set within each CSI-ReportConfig, if the value indicated through the time domain resource assignment field within the DCI is m.For example, if the terminal has set reportSlotOffsetList in the first CSI-ReportConfig and the second CSI-ReportConfig, respectively, and the value indicated through the time domain resource assignment field in the DCI format 0_1 ​​received by the terminal is m, and the (m+1)th entry in each reportSlotOffsetList in the first CSI-ReportConfig and the second CSI-ReportConfig corresponds to slot offsets 5 and 7, respectively, the terminal can determine the position of the slot in which the PUSCH is transmitted from the DCI by considering slot offset 7, which is the maximum value among these. The terminal may determine which of the upper layer signalings among reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2, reportSlotOffsetListDCI-0-1-r17, reportSlotOffsetListDCI-0-2-r17, and reportSlotOffsetList-r17 in the upper layer signaling CSI-ReportConfig, according to the conditions below, will be used as a parameter for determining the slot offset when CSI reporting is multiplexed in a PUSCH without TB.

[0574] - If the terminal is scheduled for PUSCH through DCI format 0_2 and one of reportSlotOffsetListDCI-0-2 or reportSlotOffsetListDCI-0-2-r17 is set, the terminal can determine the slot offset from the DCI to the PUSCH as one of the values ​​in reportSlotOffsetListDCI-0-2 or reportSlotOffsetListDCI-0-2-r17 when scheduling a PUSCH that multiplexes CSI reporting without including TB.

[0575] - If the UE is scheduled for a PUSCH through DCI format 0_1, or one or more PUSCHs through 0_3, and for a PUSCH that can be transmitted to the first scheduled cell, and one of reportSlotOffsetListDCI-0-1 or reportSlotOffsetListDCI-0-1-r17 is set, the UE may determine the slot offset from the DCI to the PUSCH as one value in reportSlotOffsetListDCI-0-1 or reportSlotOffsetListDCI-0-1-r17 when the UE is scheduled for a PUSCH that multiplexes CSI reporting without including TB.

[0576] - In cases other than the above two, when the terminal schedules a PUSCH that multiplexes CSI reporting without including TB, the slot offset from the DCI to the PUSCH can be determined as one value in reportSlotOffsetList or reportSlotOffsetList-r17.

[0577] A terminal may not expect that upper layer signaling related to a list containing one or more slot offsets determined according to the conditions described above contains more than 16 slot offset values.

[0578] Among the upper layer signaling related to the list including one or more slot offsets determined according to the conditions described above, the slot offset value available to the terminal may also include an upper layer signaling set in a CSI-ReportConfig connected to a disabled bandwidth portion among one or more CSI-ReportConfigs that can be triggered through the corresponding DCI.

[0579] As an example, if the terminal has been provided with search space and control resource set configuration from the base station so that it can monitor DCI formats 0_1 and 0_2, and if the terminal has been configured with upper layer signaling reportSlotOffsetList and reportSlotOffsetListDCI-0-2, and if the terminal has been scheduled through DCI format 0_1 ​​so that CSI reporting is multiplexed within a PUSCH without TB, the slot offset from the DCI to the PUSCH can be determined as the slot offset corresponding to the (m+1)th entry within the upper layer signaling reportSlotOffsetList if the value indicated through the time domain resource assignment field within the DCI is m. Additionally, if the terminal is scheduled via DCI format 0_2 to multiplex CSI reporting within a PUSCH without TB, the slot offset from the DCI to the PUSCH can be determined as the slot offset corresponding to the m+1th entry within the upper layer signaling reportSlotOffsetListDCI-0-2 if the value indicated via the time domain resource assignment field within the DCI is m.

[0580] As another example, if the UE has been provided with a search space and control resource set configuration from the base station to be able to monitor DCI formats 0_1 and 0_2, and if the UE has only been configured with a higher layer signaling reportSlotOffsetList, and if the UE is scheduled through DCI format 0_1 ​​or 0_2 so that CSI reporting is multiplexed within a TB-less PUSCH, the slot offset from the DCI to the PUSCH can be determined as the slot offset corresponding to the (m+1)th entry within the higher layer signaling reportSlotOffsetList, if the value indicated through the time domain resource assignment field within the DCI is m. That is, if CSI reporting is multiplexed within a TB-less PUSCH that can be scheduled through two different DCI formats 0_1 and 0_2, the UE can determine the slot offset from the DCI to the PUSCH through the same higher layer signaling.

[0581] As described above, if a terminal is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in a DCI via a PUSCH that does not include a TB, the terminal may interpret and apply the time domain resource assignment field in the corresponding DCI to the time resource allocation information of the PUSCH (e.g., Start and Length Indicator Value (SLIV) that represents a start symbol and the length of consecutive symbols therefrom, or a start symbol S that can be used for PUSCH repetition type B transmission and L that represents the length of consecutive symbols therefrom, PUSCH mapping type, and slot offset from the DCI to the PUSCH transmission), and at this time, as described above, a method of interpreting the time domain resource assignment field in the corresponding DCI may consider a combination of at least one of the following [Method 1-1] to [Method 1-4].

[0582] [Method 1-1]

[0583] When a UE is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in DCI over a PUSCH that does not include TB, the UE may not expect that Default A or pusch-TimeDomainResourceAllocationList in pusch-Configcommon will be used when interpreting the time domain resource assignment field in the DCI. That is, in the case described above, the UE may not expect that Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon will be determined to be used according to the upper layer signaling configuration conditions in [Table 41], [Table 42], or [Table 43] described above when interpreting the time domain resource assignment field in the DCI.That is, in the case described above, when interpreting the time domain resource assignment field in DCI, the terminal can be expected to interpret it using parameters determined according to the upper layer signaling setting conditions in [Table 41], [Table 42], or [Table 43], excluding Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon (for example, in the case of DCI format 0_1, one of pusch-TimeDomainResourceAllocationList in pusch-Config, pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config, or pusch-TimeDomainResourceAllocationListForMultiPUSCH in pusch-Config, in the case of DCI format 0_2, one of pusch-TimeDomainResourceAllocationList in pusch-Config or pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config, and in the case of DCI format 0_3 Either pusch-TimeDomainResourceAllocationList in pusch-Config or pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config).

[0584] For example, when a terminal is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information and which slot offset information to use when interpreting the DCI based on the following conditions.

[0585] - If the terminal has not set or has set (No / Yes) the pusch-TimeDomainAllocationList in the upper layer signaling pusch-Configcommon, has set (Yes), and has not set (No) the pusch-TimeDomainAllocationList in the pusch-Config, and has not set (No) TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-2, and pusch-TimeDomainAllocationListForMultiPUSCH, the terminal may commonly use the pusch-TimeDomainAllocationList in the upper layer signaling pusch-Config when interpreting the values ​​indicated through the time domain resource assignment fields in DCI formats 0_1 and 0_2, and may regard this as the 1-1 time resource allocation parameter.

[0586] - If the terminal has set reportSlotOffsetList, which is an upper layer signaling in CSI-ReportConfig, and has not set reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI formats 0_1 and 0_2 to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may commonly use the value in reportSlotOffsetList and regard it as the 1-1 slot offset parameter.

[0587] - If the terminal has received a value of m through the time domain resource assignment field in DCI format 0_1 ​​or 0_2, it can determine the slot offset between the PUSCH and DCI format 0_1 ​​or 0_2 as the slot offset corresponding to the m+1th entry in reportSlotOffsetList, which is upper layer signaling.

[0588] - The terminal can expect that the number of entries included in the 1-1 time resource allocation parameter (pusch-TimeDomainAllocationList in pusch-Config in the example described above) and the 1-1 slot offset parameter (reportSlotOffsetList in CSI-ReportConfig in the example described above) are set to be the same.

[0589] - The terminal can expect that the number of entries included in the 1-1 time resource allocation parameter (pusch-TimeDomainAllocationList in pusch-Config in the above-described example) is set to be greater than or equal to the number of entries included in the 1-1 slot offset parameter (reportSlotOffsetList in CSI-ReportConfig in the above-described example).

[0590] - At this time, when the terminal receives reportSlotOffsetList settings from the base station through upper layer signaling, the number of entries in the corresponding parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetList to the terminal to be greater than 16.

[0591] As another example, when a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information and which slot offset information to use when interpreting the DCI based on the following conditions:

[0592] - If the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, (No), does not set pusch-TimeDomainAllocationList in pusch-Config (No), sets TimeDomainAllocationListDCI-0-1 (Yes), and sets pusch-TimeDomainAllocationListDCI-0-2 (Yes), the terminal can use pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_1, and the terminal can use pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_2. That is, the terminal may receive different DCI formats 0_1 and 0_2 and interpret the time domain resource assignment field based on different upper layer signaling. In this case, the upper layer signaling applied to DCI format 0_1 ​​(pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config in the above-described situation) may be regarded as the 1-2-1 time resource allocation parameter, and the upper layer signaling applied to DCI format 0_2 (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config in the above-described situation) may be regarded as the 1-2-2 time resource allocation parameter.

[0593] - If the terminal has set reportSlotOffsetList, which is an upper layer signaling in CSI-ReportConfig, and has not set reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI formats 0_1 and 0_2 to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may commonly use the values ​​in reportSlotOffsetList and regard them as the 1st-2nd slot offset parameters.

[0594] - If the terminal has received a value of m through the time domain resource assignment field in DCI format 0_1 ​​or 0_2, it can determine the slot offset between the PUSCH and DCI format 0_1 ​​or 0_2 as the slot offset corresponding to the m+1th entry in reportSlotOffsetList, which is upper layer signaling.

[0595] - The terminal can expect that the number of entries included in the 1-2-1 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config applicable to DCI format 0_1 ​​in the above-described example), the 1-2-2 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config applicable to DCI format 0_2 in the above-described example), and the 1-2 slot offset parameter (reportSlotOffsetList in CSI-ReportConfig in the above-described example) are set to be the same. That is, the terminal can expect that the 1-2-1 time resource allocation parameter, the 1-2-2 time resource allocation parameter, and the 1-2 slot offset parameter all have the same number of entries.

[0596] - The terminal may expect that the number of entries included in the 1-2-1 time resource allocation parameter and the number of entries included in the 1-2-2 time resource allocation parameter are set to be the same as the larger value, and the number of entries included in the 1-2 slot offset parameter are set to be the same. For example, the terminal may expect that the 1-2 slot offset parameter includes 16 entries when the 1-2-1 time resource allocation parameter includes 16 entries and the 1-2-2 time resource allocation parameter includes 8 entries.

[0597] - The terminal may expect that the smaller value of the number of entries included in the 1-2-1 time resource allocation parameter and the number of entries included in the 1-2-2 time resource allocation parameter is set to be equal to the number of entries included in the 1-2 slot offset parameter. For example, the terminal may expect that when the 1-2-1 time resource allocation parameter includes 16 entries and the 1-2-2 time resource allocation parameter includes 8 entries, the 1-2 slot offset parameter includes 8 entries.

[0598] - The terminal can expect that the number of entries included in the 1-2-1 time resource allocation parameter is set to be less than or equal to a larger value between the number of entries included in the 1-2-2 time resource allocation parameter and the number of entries included in the 1-2-2 time resource allocation parameter.

[0599] - The terminal can expect that the number of entries included in the 1-2-1 time resource allocation parameter is set to be less than or equal to a smaller value among the number of entries included in the 1-2-2 time resource allocation parameter and the number of entries included in the 1-2-2 time resource allocation parameter.

[0600] At this time, when the terminal receives reportSlotOffsetList settings from the base station through upper layer signaling, the number of entries in the corresponding parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetList to the terminal to be greater than 16.

[0601] As another example, when a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information and which slot offset information to use when interpreting the DCI based on the following conditions:

[0602] - If the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, (No), does not set pusch-TimeDomainAllocationList in pusch-Config (No), sets TimeDomainAllocationListDCI-0-1 (Yes), and sets pusch-TimeDomainAllocationListDCI-0-2 (Yes), the terminal can use pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_1, and the terminal can use pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_2. That is, the terminal may receive different DCI formats 0_1 and 0_2 and interpret the time domain resource assignment field based on different upper layer signaling. In this case, the upper layer signaling applied to DCI format 0_1 ​​(pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config in the above-described situation) may be regarded as the 1-3-1 time resource allocation parameter, and the upper layer signaling applied to DCI format 0_2 (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config in the above-described situation) may be regarded as the 1-3-2 time resource allocation parameter.

[0603] - If the terminal has set reportSlotOffsetListDCI-0-1, which is an upper layer signaling in CSI-ReportConfig, and has set reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI format 0_1 ​​to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may use the value in reportSlotOffsetListDCI-0-1, and when the terminal determines the slot offset from the time of receiving DCI format 0_2 to PUSCH, the terminal may use the value in reportSlotOffsetListDCI-0-2. reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, which are determined by the upper layer signaling setting status, may be regarded as the 1-3-1 slot offset parameter and the 1-3-2 slot offset parameter, respectively.

[0604] - If the terminal receives a value m through the time domain resource assignment field in DCI format 0_1, the terminal can determine the slot offset between DCI format 0_1 ​​and PUSCH as the slot offset corresponding to the m+1th entry in reportSlotOffsetListDCI-0-1, which is a higher layer signaling. If the terminal receives a value m through the time domain resource assignment field in DCI format 0_2, the terminal can determine the slot offset between DCI format 0_2 and PUSCH as the slot offset corresponding to the m+1th entry in reportSlotOffsetListDCI-0-2, which is a higher layer signaling.

[0605] - The terminal can expect that the number of entries included in the 1-3-1 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-1 in pusch-Config applicable to DCI format 0_1 ​​in the above-described example), the 1-3-2 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config applicable to DCI format 0_2 in the above-described example), the 1-3-1 slot offset parameter (reportSlotOffsetListDCI-0-1 in CSI-ReportConfig in the above-described example) and the number of entries included in the 1-3-2 slot offset parameter (reportSlotOffsetListDCI-0-2 in CSI-ReportConfig in the above-described example) are set to be the same. That is, the terminal can expect that the 1-3-1 time resource allocation parameter, the 1-3-2 time resource allocation parameter, the 1-3-1 slot offset parameter, and the 1-3-2 slot offset parameter all have the same number of entries.

[0606] - The terminal can expect that the number of entries included in the 1-3-1 time resource allocation parameter and the number of entries included in the 1-3-1 slot offset parameter are set to be the same, and the number of entries included in the 1-3-2 time resource allocation parameter and the number of entries included in the 1-3-2 slot offset parameter are set to be the same. For example, when the 1-3-1 time resource allocation parameter includes 16 entries and the 1-3-2 time resource allocation parameter includes 8 entries, the terminal can expect that the 1-3-1 slot offset parameter includes 16 entries and the 1-3-2 slot offset parameter includes 8 entries.

[0607] - At this time, when the terminal receives reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2 from the base station through upper layer signaling, the number of entries in each parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2 to the terminal to not exceed 16.

[0608] Since this method assumes that the terminal is scheduled to transmit CSI reports multiplexed on a PUSCH without TB from the base station after entering the RRC connected mode, it will be after all upper layer signaling configuration information specific to the terminal has been acquired, and therefore, the use of Default A or pusch-TimeDomainResourceAllocation in pusch-Configcommon, which can be used as time resource allocation information before acquiring the terminal-specific upper layer signaling configuration information, may not be considered.However, if a specific operator or base station performs scheduling using only Default A or pusch-TimeDomainResourceAllocation in pusch-Configcommon even after the terminal enters RRC connected mode in order to control the amount of upper layer signaling configuration information, additional upper layer signaling may need to be configured for CSI multiplexing in PUSCH without TB (for example, in the case of DCI format 0_1, one of pusch-TimeDomainResourceAllocationList in pusch-Config, pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config, or pusch-TimeDomainResourceAllocationListForMultiPUSCH in pusch-Config, in the case of DCI format 0_2, one of pusch-TimeDomainResourceAllocationList in pusch-Config or pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config, or in the case of DCI format 0_3, pusch-Config The amount of upper layer signaling configuration information can be increased (one of pusch-TimeDomainResourceAllocationList in pusch-Config or pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config).

[0609] [Method 1-2]

[0610] When a terminal is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in DCI over a PUSCH that does not include TB, it can be expected that any table or upper layer signaling configuration information that can be determined according to the upper layer signaling configuration conditions in [Table 41], [Table 42], or [Table 43] described above will be used when interpreting the time domain resource assignment field in the DCI.That is, in the case described above, the terminal can be expected to interpret the time domain resource assignment field in the DCI using parameters determined according to the upper layer signaling setting conditions in [Table 41], [Table 42], or [Table 43] (For example, in the case of DCI format 0_1, the terminal can use one of Default A, pusch-TimeDomainResourceAllocationList in pusch-Configcommon, pusch-TimeDomainResourceAllocationList in pusch-Config, pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config, pusch-TimeDomainResourceAllocationListForMultiPUSCH in pusch-Config, and in the case of DCI format 0_2, Default A, pusch-TimeDomainResourceAllocationList in pusch-Configcommon, pusch-TimeDomainResourceAllocationList in pusch-Config, or pusch-TimeDomainResourceAllocationList in pusch-Config). One of pusch-TimeDomainResourceAllocationListDCI-0-2, Default A for DCI format 0_3, pusch-TimeDomainResourceAllocationList in pusch-Configcommon, pusch-TimeDomainResourceAllocationList in pusch-Config, or pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config can be used.).

[0611] For example, when a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information to use when interpreting the DCI based on the following conditions:

[0612] - If the terminal has configured pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), and has not configured pusch-TimeDomainAllocationList, TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-2, and pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal may commonly use pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling, when interpreting the values ​​indicated through the time domain resource assignment fields in DCI formats 0_1 and 0_2, and may regard this as the 2-1 time resource allocation parameter.

[0613] - If the terminal has set reportSlotOffsetList, which is an upper layer signaling in CSI-ReportConfig, and has not set reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI formats 0_1 and 0_2 to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may commonly use the value in reportSlotOffsetList and regard it as the 2-1 slot offset parameter.

[0614] - If the terminal has received a value of m through the time domain resource assignment field in DCI format 0_1 ​​or 0_2, it can determine the slot offset between the PUSCH and DCI format 0_1 ​​or 0_2 as the slot offset corresponding to the m+1th entry in reportSlotOffsetList, which is upper layer signaling.

[0615] - The terminal can expect that the number of entries included in the 2-1 time resource allocation parameter (pusch-TimeDomainAllocationList in pusch-Configcommon in the above-described example) and the 2-1 slot offset parameter (reportSlotOffsetList in CSI-ReportConfig in the above-described example) are set to be the same.

[0616] - The terminal may expect that the number of entries included in the 2-1 time resource allocation parameter is set to be greater than or equal to the number of entries included in the 2-1 slot offset parameter.

[0617] - At this time, when the terminal receives reportSlotOffsetList settings from the base station through upper layer signaling, the number of entries in the corresponding parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetList to the terminal to be greater than 16.

[0618] As another example, when a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information and which slot offset information to use when interpreting the DCI based on the following conditions:

[0619] - If the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), does not set pusch-TimeDomainAllocationList in pusch-Config (No), does not set TimeDomainAllocationListDCI-0-1 (No), does not set pusch-TimeDomainAllocationListDCI-0-2 (Yes), and does not set pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal can use pusch-TimeDomainAllocationListDCI in pusch-Configcommon, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_1, and the terminal can use pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_2. That is, the terminal may receive different DCI formats 0_1 and 0_2 and may base its interpretation of the time domain resource assignment field on different upper layer signaling.At this time, the upper layer signaling applied to DCI format 0_1 ​​(pusch-TimeDomainAllocationList in pusch-Configcommon in the above-described situation) can be considered as a 2-2-1 time resource allocation parameter, and the upper layer signaling applied to DCI format 0_2 (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config in the above-described situation) can be considered as a 2-2-2 time resource allocation parameter.

[0620] - If the terminal has set reportSlotOffsetList, which is an upper layer signaling in CSI-ReportConfig, and has not set reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI formats 0_1 and 0_2 to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may commonly use the value in reportSlotOffsetList and regard it as the 2-2 slot offset parameter.

[0621] - If the terminal has received a value of m through the time domain resource assignment field in DCI format 0_1 ​​or 0_2, it can determine the slot offset between the PUSCH and DCI format 0_1 ​​or 0_2 as the slot offset corresponding to the m+1th entry in reportSlotOffsetList, which is upper layer signaling.

[0622] - The terminal can expect that the number of entries included in the 2-2-1 time resource allocation parameter (pusch-TimeDomainAllocationList in pusch-Configcommon applicable to DCI format 0_1 ​​in the above-described example), the 2-2-2 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config applicable to DCI format 0_2 in the above-described example), and the 2-2 slot offset parameter (reportSlotOffsetList in CSI-ReportConfig in the above-described example) are set to be the same. That is, the terminal can expect that the 2-2-1 time resource allocation parameter, the 2-2-2 time resource allocation parameter, and the 2-2 slot offset parameter all have the same number of entries.

[0623] - The terminal may expect that the number of entries included in the 2-2-1 time resource allocation parameter and the number of entries included in the 2-2-2 time resource allocation parameter are set to be the same as the larger value, and the number of entries included in the 2-2 slot offset parameter are set to be the same. For example, the terminal may expect that the 2-2 slot offset parameter includes the number of entries of 16 when the 2-2-1 time resource allocation parameter includes the number of entries of 16 and the 2-2-2 time resource allocation parameter includes the number of entries of 8.

[0624] - The terminal may expect that the smaller value of the number of entries included in the 2-2-1 time resource allocation parameter and the number of entries included in the 2-2-2 time resource allocation parameter is set to be equal to the number of entries included in the 2-2 slot offset parameter. For example, the terminal may expect that when the 2-2-1 time resource allocation parameter includes 16 entries and the 2-2-2 time resource allocation parameter includes 8 entries, the 2-2 slot offset parameter includes 8 entries.

[0625] - The terminal can expect that the number of entries included in the 2-1 slot offset parameter is set to be less than or equal to a larger value between the number of entries included in the 2-2-1 time resource allocation parameter and the number of entries included in the 2-2-2 time resource allocation parameter.

[0626] - The terminal can expect that the number of entries included in the 2-1 slot offset parameter is set to be less than or equal to a smaller value between the number of entries included in the 2-2-1 time resource allocation parameter and the number of entries included in the 2-2-2 time resource allocation parameter.

[0627] - At this time, when the terminal receives reportSlotOffsetList settings from the base station through upper layer signaling, the number of entries in the corresponding parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetList to the terminal to be greater than 16.

[0628] As another example, when a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in a DCI over a PUSCH that does not include a TB, the terminal may determine which time resource allocation information and which slot offset information to use when interpreting the DCI based on the following conditions:

[0629] - If the terminal does not set pusch-TimeDomainAllocationList in pusch-Configcommon, which is an upper layer signaling (Yes), does not set pusch-TimeDomainAllocationList in pusch-Config (No), does not set TimeDomainAllocationListDCI-0-1 (No), does not set pusch-TimeDomainAllocationListDCI-0-2 (Yes), and does not set pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config (No), the terminal can use pusch-TimeDomainAllocationListDCI in pusch-Configcommon, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_1, and the terminal can use pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config, which is an upper layer signaling, when interpreting the value indicated through the time domain resource assignment field in DCI format 0_2. That is, the terminal may receive different DCI formats 0_1 and 0_2 and may base its interpretation of the time domain resource assignment field on different upper layer signaling.At this time, the upper layer signaling applied to DCI format 0_1 ​​(pusch-TimeDomainAllocationList in pusch-Configcommon in the above-described situation) can be considered as a 2-3-1 time resource allocation parameter, and the upper layer signaling applied to DCI format 0_2 (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config in the above-described situation) can be considered as a 2-3-2 time resource allocation parameter.

[0630] - If the terminal has set reportSlotOffsetListDCI-0-1, which is an upper layer signaling in CSI-ReportConfig, and has set reportSlotOffsetListDCI-0-2, when the terminal determines the slot offset from the time of receiving DCI format 0_1 ​​to PUSCH when receiving CSI report multiplexing scheduling through PUSCH that does not include TB, the terminal may use the value in reportSlotOffsetListDCI-0-1, and when the terminal determines the slot offset from the time of receiving DCI format 0_2 to PUSCH, the terminal may use the value in reportSlotOffsetListDCI-0-2. reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2, which are determined by the upper layer signaling setting status, may be regarded as the 2-3-1 slot offset parameter and the 2-3-2 slot offset parameter, respectively.

[0631] - If the terminal receives a value m through the time domain resource assignment field in DCI format 0_1, the terminal can determine the slot offset between DCI format 0_1 ​​and PUSCH as the slot offset corresponding to the m+1th entry in reportSlotOffsetListDCI-0-1, which is a higher layer signaling. If the terminal receives a value m through the time domain resource assignment field in DCI format 0_2, the terminal can determine the slot offset between DCI format 0_2 and PUSCH as the slot offset corresponding to the m+1th entry in reportSlotOffsetListDCI-0-2, which is a higher layer signaling.

[0632] - The terminal can expect that the number of entries included in the 2-3-1 time resource allocation parameter (pusch-TimeDomainAllocationList in pusch-Configcommon applicable to DCI format 0_1 ​​in the above-described example), the number of entries included in the 2-3-2 time resource allocation parameter (pusch-TimeDomainAllocationListDCI-0-2 in pusch-Config applicable to DCI format 0_2 in the above-described example), the number of entries included in the 2-3-1 slot offset parameter (reportSlotOffsetListDCI-0-1 in CSI-ReportConfig in the above-described example), and the number of entries included in the 2-3-2 slot offset parameter (reportSlotOffsetListDCI-0-2 in CSI-ReportConfig in the above-described example) are set to be the same. That is, the terminal can expect that the 2-3-1 time resource allocation parameter, the 2-3-2 time resource allocation parameter, the 2-3-1 slot offset parameter, and the 2-3-2 slot offset parameter all have the same number of entries.

[0633] - The terminal can expect that the number of entries included in the 2-3-1 time resource allocation parameter and the number of entries included in the 2-3-1 slot offset parameter are set to be the same, and the number of entries included in the 2-3-2 time resource allocation parameter and the number of entries included in the 2-3-2 slot offset parameter are set to be the same. For example, when the 2-3-1 time resource allocation parameter includes 16 entries and the 2-3-2 time resource allocation parameter includes 8 entries, the terminal can expect that the 2-3-1 slot offset parameter includes 16 entries and the 2-3-2 slot offset parameter includes 8 entries.

[0634] - At this time, when the terminal receives reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2 from the base station through upper layer signaling, the number of entries in each parameter may not be expected to exceed 16. At this time, the base station may not set the number of entries in reportSlotOffsetListDCI-0-1 and reportSlotOffsetListDCI-0-2 to the terminal to not exceed 16.

[0635] This method may be the most effective method in terms of signaling efficiency and flexibility, because all time resource allocation methods that the UE can use for uplink scheduling can be utilized when the UE is scheduled to multiplex CSI reports on the PUSCH without TB from the base station. However, as described above, this scheduling situation can be assumed after entering the RRC connected mode, and thus after all upper layer signaling configuration information specific to the UE has been acquired. Therefore, since the information that can be used as time resource allocation information before acquiring the UE-specific upper layer signaling configuration information may be unlikely to be used, signaling overhead can be saved by not configuring upper layer signaling such as pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-2, and pusch-TimeDomainAllocationListForMultiPUSCH that can be configured in the pusch-Config, but this may be considered unnecessary signaling flexibility.

[0636] [Method 1-3]

[0637] When a terminal is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in DCI over a PUSCH that does not include a TB, depending on the DCI format, one of all tables or upper layer signaling configuration information that can be determined according to the upper layer signaling configuration conditions in [Table 41], [Table 42], or [Table 43] described above is expected to be used when interpreting the time domain resource assignment field in the DCI, or one of the remaining tables or upper layer signaling configuration information excluding some of the tables or upper layer signaling configuration information is expected to be used.

[0638] For example, if a terminal is scheduled to transmit one or more CSI reports multiplexed via a CSI request field in DCI format 0_1 ​​over a PUSCH that does not include a TB, the terminal may expect that one of all tables or upper layer signaling configuration information that can be determined according to the upper layer signaling configuration conditions in [Table 41], [Table 42], or [Table 43] described above is used when interpreting the time domain resource assignment field in DCI format 0_1. That is, in the case described above, the terminal can be expected to interpret the time domain resource assignment field in DCI using a parameter determined according to the upper layer signaling setting conditions in [Table 41], [Table 42], or [Table 43] (for example, one of Default A, pusch-TimeDomainResourceAllocationList in pusch-Configcommon, pusch-TimeDomainResourceAllocationList in pusch-Config, pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config, and pusch-TimeDomainResourceAllocationListForMultiPUSCH in pusch-Config). At the same time, if a UE is scheduled to transmit one or more CSI reports multiplexed via the CSI request field in DCI format 0_2 over a PUSCH that does not include TB, the UE may not expect to use Default A or pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the time domain resource assignment field in the DCI format 0_2.That is, in the case described above, the terminal may not expect that Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon will be determined to be used according to the upper layer signaling setting conditions in [Table 41], [Table 42], or [Table 43] when interpreting the time domain resource assignment field in DCI. That is, in the case described above, the terminal may expect that, when interpreting the time domain resource assignment field in DCI, the terminal uses a parameter determined according to the upper layer signaling setting conditions in [Table 41], [Table 42], or [Table 43], excluding Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon (for example, one of pusch-TimeDomainResourceAllocationList in pusch-Config or pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config). That is, the terminal can apply the above [Method 1-1] to DCI format 0_1 ​​and apply the above [Method 1-2] to DCI format 0_2.

[0639] [Method 1-4]

[0640] When a terminal is scheduled to transmit one or more CSI reports multiplexed through a CSI request field in DCI via a PUSCH that does not include a TB, the terminal may expect to be notified by the base station via at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling for at least one combination of [Method 1-1] to [Method 1-3], or as fixedly defined in the standard.

[0641] For example, the terminal can expect that the above [Method 1-1] is fixedly defined in the specification (this is just one example of what can be defined in the specification, and does not preclude the use of other methods 1-1, 1-2, 1-3 from being defined in the specification). That is, when the terminal is scheduled to transmit one or more CSI reports multiplexed via the CSI request field in the DCI over the PUSCH that does not include TB, the terminal can expect that, when interpreting the time domain resource assignment field in the DCI, the terminal will interpret it using parameters determined by the upper layer signaling configuration conditions in [Table 41], [Table 42], or [Table 43], excluding Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon.

[0642] As another example, if a terminal reports a specific terminal capability, the base station may follow [Method 1-2] above when scheduling the terminal to transmit one or more CSI reports multiplexed through a PUSCH that does not include a TB via a CSI request field in the DCI. If the terminal does not report such a terminal capability report to the base station, the terminal may follow [Method 1-1] above when being scheduled by the base station to transmit one or more CSI reports multiplexed through a PUSCH that does not include a TB via a CSI request field in the DCI. In this case, the terminal capability report may be reported per UE (User Equipment), per band, per band combination, per FS (Feature Set), and / or per FSPC (Feature Set Per Component Carrier). In this case, the terminal capability report may mean supporting [Method 1-2] as described above. Alternatively, the terminal capability report may indicate a version of the 5G standard supported by the terminal (e.g., accessStratumRelease), and may be one of 5G standard versions 15, 16, 17, 18, 19, or 20. For example, if the terminal and the base station report accessStratumRelease as 5G standard version 16 for the terminal capability report described above, when the terminal is scheduled to transmit one or more CSI reports multiplexed through the CSI request field in the DCI via the PUSCH that does not include TB from the base station, the above [Method 1-2] may be followed. If the terminal reports the terminal capability for a version later than 16, the above [Method 1-2] may be followed, and if the terminal reports the terminal capability for a version earlier than 16, the above [Method 1-1] may be followed.

[0643] As another example, if a terminal reports a specific terminal capability, the base station can configure upper layer signaling corresponding to the terminal capability to the terminal accordingly, and when the base station schedules the terminal for which such upper layer signaling has been configured to transmit one or more CSI reports multiplexed through a CSI request field in DCI via a PUSCH that does not include a TB, the base station can follow [Method 1-2] above. If the terminal does not report such terminal capability report to the base station, the base station cannot configure upper layer signaling corresponding to the terminal capability to the terminal accordingly, and when the terminal is scheduled from the base station to transmit one or more CSI reports multiplexed through a CSI request field in DCI via a PUSCH that does not include a TB, the base station can follow [Method 1-1] above. In this case, the terminal capability report can be reported in units of per UE (User Equipment), per band, per band combination, per FS (Feature Set), or per FSPC (Feature Set Per Component Carrier). At this time, the terminal capability report may mean that the terminal supports the above [Method 1-2] as described above. Alternatively, the terminal capability report may mean a version of the 5G standard supported by the terminal (e.g., accessStratumRelease), and one of 5G standard versions 15, 16, 17, 18, 19, or 20 may be possible values. For example, if the terminal and the base station report 5G standard version 16 as the terminal capability report accessStratumRelease for the above-described matters, if the terminal is scheduled to transmit one or more CSI reports multiplexed through the CSI request field in the DCI via the PUSCH that does not include TB from the base station, the above [Method 1-2] may be followed.For a terminal that reports terminal capabilities for a version later than 16, the above [Method 1-2] may be followed, and for a terminal that reports terminal capabilities for a version earlier than 16, the above [Method 1-1] may be followed.

[0644] FIG. 14 is a diagram illustrating the operation of a terminal according to an embodiment of the present disclosure.

[0645] At step 1400, the terminal may transmit terminal capabilities to the base station. The terminal capability signaling that may be reported at this time may be a combination of at least one of [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4]. Step 1400 may also be omitted.

[0646] In step 1405, the terminal can receive upper layer signaling from the base station according to the reported terminal capability (if the terminal capability reporting operation is omitted in step 1400, the terminal capability may not be considered in the upper layer signaling). At this time, the terminal can receive upper layer signaling configurations from the base station that can determine time resource allocation and slot offset when multiplexing CSI reports on a PUSCH without TB by considering at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4].

[0647] At step 1410, the terminal may receive DCI for PUSCH scheduling without TB from the base station, and may trigger aperiodic CSI reporting or semi-persistent CSI reporting through the DCI.

[0648] In step 1415, the terminal may multiplex aperiodic or semi-persistent CSI on a PUSCH without a TB and transmit it to the base station. At this time, when multiplexing CSI reports on a PUSCH without a TB, time resource allocation and slot offset determination may be determined using one of the above [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4].

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

[0650] FIG. 15 is a diagram illustrating the operation of a base station according to an embodiment of the present disclosure.

[0651] At step 1500, the base station may receive terminal capabilities from the terminal. The terminal capability signaling that may be reported at this time may be a combination of at least one of [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4]. Step 1500 may also be omitted.

[0652] In step 1505, the base station may configure upper layer signaling to the terminal according to the terminal capability reported by the terminal (if the terminal capability reporting operation is omitted in step 1500, the terminal capability may not be considered in the upper layer signaling). At this time, the base station may provide the terminal with an upper layer signaling configuration that can determine time resource allocation and slot offset when multiplexing CSI reports on a PUSCH without TB by considering at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4].

[0653] At step 1510, the base station may transmit a DCI for PUSCH scheduling without TB to the terminal. Through the DCI, the terminal may trigger aperiodic CSI reporting or semi-persistent CSI reporting.

[0654] In step 1515, the base station can receive a CSI report from the terminal via a PUSCH without TB. At this time, when multiplexing CSI reports on the PUSCH without TB, time resource allocation and slot offset determination can be determined by one of the above [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4]. Although the above [Method 1-1], [Method 1-2], [Method 1-3], and [Method 1-4] have been described focusing on the operation of the terminal, the base station can also determine the time resource and slot offset for receiving the PUSCH without TB in the same way as the terminal.

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

[0656] FIG. 16 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0657] Referring to FIG. 16, the terminal may include a transceiver, which refers to a terminal receiving unit (16-00) and a terminal transmitting unit (16-10), a memory (not shown), and a terminal processing unit (16-05, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (16-00, 16-10), the memory, and the terminal processing unit (16-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 or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

[0659] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0660] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0661] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform terminal component control operations by executing programs stored in memory.

[0662] FIG. 17 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0663] Referring to FIG. 17, the base station may include a transceiver, which refers to a base station receiver (17-00) and a base station transmitter (17-10), a memory (not shown), and a base station processing unit (17-05, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver units (17-00, 17-10), the memory, and the base station processing unit (17-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 or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

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

[0665] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0666] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

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

[0668] The 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.

[0669] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The 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 the present disclosure.

[0670] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0671] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0672]

[0673] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0674] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

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

[0676] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0677] 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 harm the essence of the invention.

[0678] 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 appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. In a method performed by a terminal in a wireless communication system, A step of receiving, from the base station, upper layer signaling including first information for determining a table to be applied to interpretation of a TDRA (time domain resource assignment) field; A step of receiving DCI (downlink control information) from the base station for scheduling CSI (channel state information) reporting through PUSCH (physical uplink shared channel) without TB (transport block); A step of determining the table to be applied to the interpretation of the TDRA field of the DCI based on the first information; and A method comprising the step of multiplexing and transmitting the CSI report on the PUSCH without the TB based on the resources identified based on the table and the TDRA field of the DCI.

2. In paragraph 1, Further comprising a step of transmitting terminal performance information including second information for interpretation of the TDRA field to the base station, The above first information is determined based on the above second information, and A method in which the second information includes information indicating whether use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon is possible when interpreting the TDRA field or information indicating a version of a standard supported by the terminal.

3. In paragraph 1, The above first information is, Information indicating the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field, or A method including information that excludes the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field.

4. In paragraph 1, The above upper layer signal further includes a list of offset information for the CSI report, and The number of entries in the above offset information list is related to the above table applied to the interpretation of the above TDRA field.

5. In a method performed by a base station in a wireless communication system, A step of transmitting to a terminal an upper layer signaling including first information for determining a table to be applied to the interpretation of a TDRA (time domain resource assignment) field; A step of transmitting DCI (downlink control information) scheduling CSI (channel state information) reporting through PUSCH (physical uplink shared channel) without TB (transport block) to the terminal; and A method comprising the step of receiving, from the terminal, a CSI report multiplexed on the PUSCH without the TB based on the table applied to the interpretation of the TDRA field of the DCI determined based on the first information and the resource identified based on the TDRA field of the DCI.

6. In paragraph 5, Further comprising a step of transmitting terminal performance information including second information for interpretation of the TDRA field to the base station, The above first information is determined based on the above second information, and A method in which the second information includes information indicating whether use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon is possible when interpreting the TDRA field or information indicating a version of a standard supported by the terminal.

7. In paragraph 5, The above first information is, Information indicating the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field, or A method including information that excludes the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field.

8. In paragraph 5, The above upper layer signal further includes a list of offset information for the CSI report, and The number of entries in the above offset information list is related to the above table applied to the interpretation of the above TDRA field.

9. In the terminal of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said terminal, Receiving upper layer signaling from the base station, which includes first information for determining a table to be applied to the interpretation of the TDRA (time domain resource assignment) field, Receive DCI (downlink control information) from the base station for scheduling CSI (channel state information) reporting through PUSCH (physical uplink shared channel) without TB (transport block), Determine the table to be applied to the interpretation of the TDRA field of the DCI based on the first information, and A memory storing a command for multiplexing and transmitting the CSI report on the PUSCH without the TB based on the resources identified based on the table and the TDRA field of the DCI, A terminal including .

10. In paragraph 9, The above command causes the terminal to, Transmit terminal performance information including second information for interpretation of the TDRA field to the base station, The above first information is determined based on the above second information, and The second information is a terminal including information indicating whether use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon is possible when interpreting the TDRA field, or information indicating a version of a standard supported by the terminal.

11. In paragraph 9, The above first information is, Information indicating the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field, or A terminal that includes information that excludes the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the above TDRA field.

12. In paragraph 9, The above upper layer signal further includes a list of offset information for the CSI report, and The number of entries in the above offset information list is a terminal related to the table applied to the interpretation of the above TDRA field.

13. In a base station of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said base station, Transmitting to the terminal an upper layer signaling including first information for determining a table to be applied to the interpretation of the TDRA (time domain resource assignment) field, Transmits DCI (downlink control information) to the terminal to schedule CSI (channel state information) reporting through PUSCH (physical uplink shared channel) without TB (transport block), and A memory including a command for receiving a CSI report multiplexed on the PUSCH without the TB from the terminal based on the table applied to the interpretation of the TDRA field of the DCI determined based on the first information and the resource identified based on the TDRA field of the DCI, Base station including.

14. In paragraph 13, The above command causes the base station to: Transmit terminal performance information including second information for interpretation of the TDRA field to the base station, The above first information is determined based on the above second information, The first information includes information indicating the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the TDRA field, or information excluding the use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon when interpreting the TDRA field, and A base station including the second information, wherein the second information includes information indicating whether use of Default A and pusch-TimeDomainResourceAllocationList in pusch-Configcommon is possible when interpreting the TDRA field, or information indicating the version of the standard supported by the terminal.

15. In paragraph 13, The above upper layer signal further includes a list of offset information for the CSI report, The number of entries in the above offset information list is related to the above table applied to the interpretation of the above TDRA field.

Images