Terminal report method and device considering waveform in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure proposes a method and device for applying a plurality of waveforms to downlink transmission.

Description

Terminal reporting method and device considering waveform 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 configuring / reporting data information in a wireless communication system and an apparatus capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

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

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

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

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

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

[0008] As a result of the aforementioned developments and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to provide these services smoothly.

[0009] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a mobile communication system. In particular, when multiple waveforms may be used in a downlink, a method is required for a terminal to report and apply a preferred waveform.

[0010] According to one embodiment of the present disclosure, a method performed by a terminal of a communication system comprises: receiving configuration information for a preferred waveform report for receiving downlink data from a base station; identifying the preferred waveform by comparing the value of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise with a threshold value; and transmitting information indicating the preferred waveform to the base station based on the configuration information, wherein the preferred waveform is CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) when the value of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise is greater than or equal to the threshold value, and DFT-s-OFDM (discrete Fourier transform spread-OFDM) when the value is less than or equal to the threshold value.

[0011] In addition, a method performed by a base station of a communication system comprises the steps of: transmitting configuration information for reporting a preferred waveform for receiving downlink data to a terminal; and receiving information from the terminal indicating the preferred waveform associated with the configuration information, wherein the preferred waveform is determined by CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) or DFT-s-OFDM (discrete Fourier transform spread-OFDM) based on L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise values ​​and threshold values.

[0012] In addition, a terminal of a communication system comprises: a transceiver; and a control unit configured to receive configuration information regarding a preferred waveform report for receiving downlink data from a base station, identify the preferred waveform by comparing the value of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise with a threshold value, and transmit information indicating the preferred waveform to the base station based on the configuration information, wherein the preferred waveform is CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) when the value of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise is greater than or equal to the threshold value, and DFT-s-OFDM (discrete Fourier transform spread-OFDM) when the value is less than or equal to the threshold value.

[0013] In addition, a base station of a communication system comprises: a transceiver; and a control unit configured to transmit setting information for reporting a preferred waveform for receiving downlink data to a terminal, and to receive information from the terminal indicating the preferred waveform associated with the setting information, wherein the preferred waveform is determined by CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) or DFT-s-OFDM (discrete Fourier transform spread-OFDM) based on L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise values ​​and threshold values.

[0014] The disclosed embodiments provide an apparatus and method capable of effectively providing services in a mobile communication system. Specifically, efficient communication can be performed by using an appropriate waveform in the downlink between a terminal and a base station.

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

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

[0017] FIG. 3 is a drawing illustrating an example of PUSCH repeat transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 4 is a drawing illustrating an example of a non-periodic CSI reporting method according to one embodiment of the present disclosure.

[0019] Figure 5 is a diagram showing the method of setting up a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook) in an NR system.

[0020] Figure 6 is a diagram illustrating the method of setting up a dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) in an NR system.

[0021] FIG. 7 is a drawing illustrating an example of a signal transmission step according to one embodiment of the present disclosure.

[0022] FIG. 8a is a diagram illustrating an example of a method for reporting a waveform preferred by a terminal according to one embodiment of the present disclosure.

[0023] FIG. 8b is a diagram illustrating an example of a method in which a base station receives a waveform preferred by a terminal according to one embodiment of the present disclosure.

[0024] FIG. 9a is a drawing illustrating an example of a method in which a terminal reports terminal capability according to one embodiment of the present disclosure.

[0025] FIG. 9b is a diagram illustrating an example of a method in which a base station receives a terminal capability report according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0032] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (base station), radio access unit, base station controller, or a node on a network. A terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path for a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path for a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) or 6th generation mobile communication technology (6G) developed after LTE-A may be included therein, and the 5G or 6G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

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

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

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

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

[0037] As a representative example of the above-mentioned broadband wireless communication system, the LTE system employs OFDM (orthogonal frequency division multiplexing) or CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) for the downlink and SC-FDMA (single carrier frequency division multiple access) for the uplink. The uplink refers to a wireless link through which a terminal (UE (user equipment) or MS (mobile station)) transmits data or control signals to a base station (eNode B, or base station, BS), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0038] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra reliability low latency communication (URLC).

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

[0040] 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 IoT, mMTC requires support for the connection of a large number of terminals within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT provides communication functions by attaching to various sensors and devices, a large number of terminals within a cell (e.g., 1,000,000 terminals / km²) 2 It must be able to support mMTC. In addition, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones where cells cannot cover, such as building basements, so they may require wider coverage compared to other services provided by the 5G communication system. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace the device's battery, a very long battery life of 10 to 15 years may be required.

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

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

[0043] Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. The embodiments of the present disclosure may be applied to other communication systems with some modifications made in the judgment of a person skilled in the art, without significantly departing from the scope of the present disclosure. The contents of the present disclosure are applicable to FDD and TDD systems.

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

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

[0046] - MIB (master information block)

[0047] - SIB (system information block) or SIB

[0048] - RRC (radio resource control)

[0049] - MAC (medium access control) CE (control element)

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

[0051] - PDCCH (physical downlink control channel)

[0052] - DCI (downlink control information)

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

[0054] - Group Common DCI

[0055] - Common DCI

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

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

[0058] - PUCCH (physical uplink control channel)

[0059] - UCI (uplink control information)

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

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

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

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

[0064] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a resource block (resource block, RB, 104).

[0065] Figure 2 is a diagram illustrating the frame, subframe, and slot structure in a 5G system.

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

[0067] μ 014101114202214404314808414160165143203261464064

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

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

[0070] DCI can be transmitted via the PDCCH, a physical downlink control channel, after undergoing channel coding and modulation processes. A cyclic redundancy check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a radio network temporary identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

[0071] For example, a DCI scheduling a PDSCH for system information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for a random access response (RAR) message can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for a paging message can be scrambled to P-RNTI. A DCI notifying a slot format indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying a transmit power control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (cell RNTI).

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

[0073] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator - 0 or 1 bit

[0074] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the following information.

[0075] - Carrier indicator - 0 or 3 bits - UL / SUL indicator - 0 or 1 bit - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 or 2 bits - Frequency domain resource assignment - For resource allocation type 0, bits- For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook (when a dynamic HARQ-ACK codebook is used with a single HARQ-ACK codebook).- 2nd downlink assignment index - 0 or 2 bits ○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks (when a dynamic HARQ-ACK codebook is used with two HARQ-ACK sub-codebooks); ○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission(if PUSCH transmission is not codebook-based);○ bits for codebook-based PUSCH transmission. - Precoding information and number of layers - up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association - 0 or 2 bits - beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0 or 1 bit

[0076] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0077] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator - 3 bits- PDSCH-to-HARQ feedback timing indicator - [3] bits

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

[0079] - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger - 0, 1, or 2 bits - For transport block 1: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - For transport block 2: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports 4, 5, or 6 bits - Transmission configuration indication - 0 or 3 bits - SRS request - 2 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - CBG flushing out information - 0 or 1 bit - DMRS sequence initialization - 1 bit.

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

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

[0082] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

[0083] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS (sounding reference signal) transmission. Depending on whether the value of txConfig in pusch-Config within the upper signaling table 7 is 'codebook' or 'nonCodebook', PUSCH transmission can follow a codebook-based transmission method or a non-codebook-based transmission method, respectively.

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

[0085] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

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

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

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

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

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

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

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

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

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

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

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

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

[0098] The following describes PUSCH repeat transmission type A.

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

[0100] The terminal may repeatedly transmit an uplink data channel in consecutive slots that has the same length and starting symbol as the uplink data channel configured based on the number of repeated transmissions received from the base station. In this case, if at least one of the slots configured as downlink by the base station to the terminal, or at least one of the symbols of the uplink data channel configured to the terminal, is configured as downlink, the terminal skips the transmission of the uplink data channel, but counts the number of repeated transmissions of the uplink data channel.

[0101] The following describes PUSCH repeat transmission type B.

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

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

[0104] - The terminal determines invalid symbols for PUSCH repeat transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are determined as invalid symbols for PUSCH repeat transmission type B. Additionally, invalid symbols may be set in upper layer parameters (e.g., InvalidSymbolPattern). Invalid symbols may be set in upper layer parameters (e.g., InvalidSymbolPattern) by providing a symbol-level bitmap spanning one or two slots. In the bitmap, 1 represents an invalid symbol. Additionally, the periodicity and pattern of the bitmap may be set through upper layer parameters (e.g., periodicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies the invalid symbol pattern.

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

[0106] FIG. 3 is a diagram illustrating an example of PUSCH repeat transmission type B in a wireless communication system according to an embodiment of the present disclosure. A terminal can be set to 0 for the start symbol S of the uplink data channel and 14 for the length L of the uplink data channel, and can be set to 16 for the number of repeat transmissions. In this case, nominal repetition is indicated in 16 consecutive slots (301). Subsequently, the terminal can determine that the symbol set as a downlink symbol in each nominal repetition (301) is an invalid symbol. Additionally, the terminal determines that the symbols set to 1 in the invalid symbol pattern (302) are invalid symbols. In each nominal repetition, if valid symbols that are not invalid symbols are composed of one or more consecutive symbols in a single slot, they are set as actual repetitions and transmitted (303).

[0107] In addition, for PUSCH repeated transmissions, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmissions that cross slot boundaries and configured grant-based PUSCH transmissions.

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

[0109] - Method 2 (multi-segment transmission): Two or more PUSCH repeat transmissions are scheduled in consecutive slots through a single UL grant. In this case, one transmission is assigned per slot, and each transmission may have a different starting point or repeat length. Additionally, in Method 2, time-domain resource allocation information within the DCI indicates the starting point and repeat length of all repeat transmissions. Furthermore, when repeat transmissions are performed within a single slot via Method 2, if there are multiple consecutive uplink symbol bundles within that slot, each repeat transmission is performed for each uplink symbol bundle. If there is only a unique consecutive uplink symbol bundle within that slot, one PUSCH repeat transmission is performed according to the method of NR Release 15.

[0110] - Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive slots through two or more UL grants. In this case, one transmission is assigned per slot, and the n-th UL grant can be received before the PUSCH transmission scheduled by the n-1-th UL grant is finished.

[0111] - Method 4: Through one UL grant or one configured grant, one or more PUSCH repeat transmissions within a single slot, or two or more PUSCH repeat transmissions across the boundaries of consecutive slots, may be supported. The number of repeats instructed by the base station to the terminal is merely a nominal value, and the number of PUSCH repeat transmissions actually performed by the terminal may be greater than the nominal number of repeats. Time-domain resource allocation information within the DCI or within the configured grant refers to the resources of the first repeat transmission instructed by the base station. Time-domain resource information for the remaining repeat transmissions may be determined by referencing at least the resource information of the first repeat transmission and the uplink or downlink direction of the symbols. If the time-domain resource information of the repeat transmission instructed by the base station spans a slot boundary or includes an uplink / downlink switching point, the repeat transmission may be divided into multiple repeat transmissions. In this case, one repeat transmission may be included within a single slot for each uplink period.

[0112] The following describes in detail the method for measuring and reporting channel state in a 5G communication system. Channel state information (CSI) may include channel quality information (CQI), precoding matrix index (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSSBRI), layer indicator (LI), rank indicator (RI), and / or L1-RSRP (reference signal received power). The base station may control the time and frequency resources for the aforementioned CSI measurement and reporting by the terminal.

[0113] For the aforementioned CSI measurement and reporting, the terminal may receive setting information for N (≥1) CSI reports (CSI-ReportConfig), setting information for M (≥1) RS transmission resources (CSI-ResourceConfig), and one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) through upper layer signaling. More specifically, the setting information for the aforementioned CSI measurement and reporting may be as described in Tables 8 to 13 below.

[0114] CSI-ReportConfigThe IE CSI-ReportConfig is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI-ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214

[0019] , clause 5.2.1.CSI-ReportConfiginformation element-- ASN1START-- TAG-CSI-REPORTCONFIG-STARTCSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigType CHOICE {periodic SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH SEQUENCE {reportSlotConfig CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH SEQUENCE {reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alpha P0-PUSCH-AlphaSetId},aperiodic SEQUENCE {reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)}},reportQuantity CHOICE {none NULL,cri-RI-PMI-CQI NULL,cri-RI-i1 NULL,cri-RI-i1-CQI SEQUENCE {pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S},cri-RI-CQI NULL,cri-RSRP NULL,ssb-Index-RSRP NULL,cri-RI-LI-PMI-CQI NULL},reportFreqConfiguration SEQUENCE {cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI} OPTIONAL, -- Need Rpmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI} OPTIONAL, -- Need Rcsi-ReportingBand CHOICE {subbands3 BIT STRING(SIZE(3)),subbands4 BIT STRING(SIZE(4)),subbands5 BIT STRING(SIZE(5)),subbands6 BIT STRING(SIZE(6)),subbands7 BIT STRING(SIZE(7)),subbands8 BIT STRING(SIZE(8)),subbands9 BIT STRING(SIZE(9)),subbands10 BIT STRING(SIZE(10)),subbands11 BIT STRING(SIZE(13)),subbands12 BIT STRING(SIZE(12)),subbands13 BIT STRING(SIZE(4)),subbands14 BIT STRING(SIZE(13)),subbands15 BIT STRING(SIZE(12)),subbands16 BIT STRING(SIZE(13)),subbands17 BIT STRING(SIZE(17)),subbands18 BIT STRING(SIZE(18)),...,subbands19-v1530 BIT STRING(SIZE(19))} OPTIONAL -- Need S} OPTIONAL, -- Need RtimeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},codebookConfig CodebookConfig OPTIONAL, -- Need Rdummy ENUMERATED {n1, n2} OPTIONAL, -- Need RgroupBasedBeamReporting CHOICE {enabled NULL,disabled SEQUENCE {nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S}},cqi-Table ENUMERATED {table1, table2, table3, spare1} OPTIONAL, -- Need RsubbandSize ENUMERATED {value1, value2},non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R...,[[semiPersistentOnPUSCH-v1530 SEQUENCE {reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}} OPTIONAL -- Need R]],[[semiPersistentOnPUSCH-v1610 SEQUENCE {reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R} OPTIONAL, -- Need Raperiodic-v1610 SEQUENCE {reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need RreportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R} OPTIONAL, -- Need RreportQuantity-r16 CHOICE {cri-SINR-r16 NULL,ssb-Index-SINR-r16 NULL} OPTIONAL, -- Need RcodebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R]]}CSI-ReportPeriodicityAndOffset ::= CHOICE {slots4 INTEGER(0..3),slots5 INTEGER(0..4),slots8 INTEGER(0..7),slots10 INTEGER(0..9),slots16 INTEGER(0..15),slots20 INTEGER(0..19),slots40 INTEGER(0..39),slots80 INTEGER(0..79),slots160 INTEGER(0..159),slots320 INTEGER(0..319)}PUCCH-CSI-Resource ::= SEQUENCE {uplinkBandwidthPartId BWP-Id,pucch-Resource PUCCH-ResourceId}PortIndexFor8Ranks ::= CHOICE {portIndex8 SEQUENCE{rank1-8 PortIndex8 OPTIONAL, -- Need Rrank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, -- Need Rrank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, -- Need Rrank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, -- Need Rrank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, -- Need Rrank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, -- Need Rrank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, -- Need Rrank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL -- Need R},portIndex4 SEQUENCE{rank1-4 PortIndex4 OPTIONAL, -- Need Rrank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, -- Need Rrank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, -- Need Rrank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL -- Need R},portIndex2 SEQUENCE{rank1-2 PortIndex2 OPTIONAL, -- Need Rrank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL -- Need R},portIndex1 NULL}PortIndex8::= INTEGER (0..7)PortIndex4::= INTEGER (0..3)PortIndex2::= INTEGER (0..1)-- TAG-CSI-REPORTCONFIG-STOP-- ASN1STOP.

[0115] CSI-ReportConfigfield descriptions

[0116] carrier: Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration.

[0117] codebookConfig: Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network does not configure codebookConfig and codebookConfig-r16 simultaneously to a UE

[0118] cqi-FormatIndicato: Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI. (see TS 38.214

[0019] , clause 5.2.1.4).

[0119] cqi-Table: Which CQI table to use for CQI calculation (see TS 38.214

[0019] , clause 5.2.2.1).

[0120] csi-IM-ResourcesForInterference: CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

[0121] csi-ReportingBand: Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214

[0019] , clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise, the number of sub bands can be from 3 (24 PRBs, sub band size 8) to 18 (72 PRBs, sub band size 4).

[0122] dummy: This field is not used in the specification. If received it shall be ignored by the UE.

[0123] groupBasedBeamReporting: Turning on / off group beam based reporting (see TS 38.214

[0019] , clause 5.2.1.4).

[0124] non-PMI-PortIndication: Port indication for RI / CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214

[0019] , clause 5.2.1.4.2).

[0125] The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig, and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig.Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on.

[0126] nrofReportedRS: The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is either 2 or 4 depending on UE capability.

[0127] (see TS 38.214

[0019] , clause 5.2.1.4) When the field is absent the UE applies the value 1.

[0128] nzp-CSI-RS-ResourcesForInterference: NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

[0129] p0alpha:Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214

[0019] , clause 6.2.1.2).

[0130] pdsch-BundleSizeForCSI: PRB bundling size to assume for CQI calculation when reportQuantity is CRI / RI / i1 / CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214

[0019] , clause 5.2.1.4.2).

[0131] pmi-FormatIndicator: Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214

[0019] , clause 5.2.1.4).

[0132] pucch-CSI-ResourceList: Indicates which PUCCH resource to use for reporting on PUCCH.

[0133] reportConfigType: Time domain behavior of reporting configuration.

[0134] reportFreqConfiguration: Reporting configuration in the frequency domain. (see TS 38.214

[0019] , clause 5.2.1.4).

[0135] reportQuantity: The CSI related quantities to report. see TS 38.214

[0019] , clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix).

[0136] reportSlotConfig: Periodicity and slot offset (see TS 38.214

[0019] , clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).

[0137] reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2: Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity.

[0138] Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214

[0019] , clause 6.1.2.1). The field reportSlotOffsetList applies to DCI format 0_0, the field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214

[0019] , clause 6.1.2.1).

[0139] resourcesForChannelMeasurement: Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and / or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.

[0140] subbandSize: Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214

[0019] , table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field.

[0141] timeRestrictionForChannelMeasurements: Time domain measurement restriction for the channel (signal) measurements (see TS 38.214

[0019] , clause 5.2.1.1).

[0142] timeRestrictionForInterferenceMeasurements: Time domain measurement restriction for interference measurements (see TS 38.214

[0019] , clause 5.2.1.1).

[0143] CSI-ResourceConfigThe IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and / or CSI-SSB-ResourceSet.CSI-ResourceConfiginformation element-- ASN1START-- TAG-CSI-RESOURCECONFIG-STARTCSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigId CSI-ResourceConfigId,csi-RS-ResourceSetList CHOICE {nzp-CSI-RS-SSB SEQUENCE {nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetIdOPTIONAL, -- Need Rcsi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R},csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId},bwp-Id BWP-Id,resourceType ENUMERATED { aperiodic, semiPersistent, periodic},...}-- TAG-CSI-RESOURCECONFIG-STOP-- ASN1STOP

[0144] CSI-ResourceConfigfield descriptions

[0145] bwp-Id

[0146] The DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214

[0019] , clause 5.2.1.2.

[0147] csi-IM-ResourceSetList

[0148] List of references to CSI-IM resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214

[0019] , clause 5.2.1.2).

[0149] csi-ResourceConfigId

[0150] Used in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig.

[0151] csi-SSB-ResourceSetList

[0152] List of references to SSB resources used for beam measurement and reporting in a CSI-RS resource set (see TS 38.214

[0019] , clause 5.2.1.2).

[0153] nzp-CSI-RS-ResourceSetList

[0154] List of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214

[0019] , clause 5.2.1.2).

[0155] resourceType

[0156] Time domain behavior of resource configuration (see TS 38.214

[0019] , clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList.

[0157] NZP-CSI-RS-ResourceSetThe IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters.NZP-CSI-RS-ResourceSetinformation element-- ASN1START-- TAG-NZP-CSI-RS-RESOURCESET-STARTNZP-CSI-RS-ResourceSet ::= SEQUENCE {nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,repetition ENUMERATED { on, off} OPTIONAL, -- Need SaperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need Strs-Info ENUMERATED {true} OPTIONAL, -- Need R...,[[aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S]]}-- TAG-NZP-CSI-RS-RESOURCESET-STOP-- ASN1STOPThe IE CSI-SSB-ResourceSet is used to configure one SS / PBCH block resource set which refers to SS / PBCH as indicated in ServingCellConfigCommon.CSI-SSB-ResourceSetinformation element-- ASN1START-- TAG-CSI-SSB-RESOURCESET-STARTCSI-SSB-ResourceSet ::= SEQUENCE {csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index,...}-- TAG-CSI-SSB-RESOURCESET-STOP-- ASN1STOP.

[0158] NZP-CSI-RS-ResourceSetfield descriptions

[0159] aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16: Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset, the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16, the value indicates the number of slots. The network configures only one of the fields. When neither field is included, the UE applies the value 0.

[0160] nzp-CSI-RS-Resources: NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214

[0019] , clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set.

[0161] repetition: Indicates whether repetition is on / off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214

[0019] , clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP or "no report".

[0162] trs-Info: Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214

[0019] , clause 5.2.2.3.1).

[0163] CSI-IM-ResourceSetThe IE CSI-IM-ResourceSet is used to configure a set of one or more CSI Interference Management (IM) resources (their IDs) and set-specific parameters.CSI-IM-ResourceSetinformation element-- ASN1START-- TAG-CSI-IM-RESOURCESET-STARTCSI-IM-ResourceSet ::= SEQUENCE {csi-IM-ResourceSetId CSI-IM-ResourceSetId,csi-IM-Resources SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId,...}-- TAG-CSI-IM-RESOURCESET-STOP-- ASN1STOP

[0164] CSI-IM-ResourceSet field descriptions

[0165] csi-IM-Resources: CSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214

[0019] , clause 5.2)

[0166] CSI-AperiodicTriggerStateListThe CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state. Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state.CSI-AperiodicTriggerStateListinformation element-- ASN1START-- TAG-CSI-APERIODICTRIGGERSTATELIST-STARTCSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerStateCSI-AperiodicTriggerState ::= SEQUENCE {associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,...}CSI-AssociatedReportConfigInfo ::= SEQUENCE {reportConfigId CSI-ReportConfigId,resourcesForChannel CHOICE {nzp-CSI-RS SEQUENCE {resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic},csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)},csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterferencenzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference...}-- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP-- ASN1STOP.

[0167] CSI-AssociatedReportConfigInfo field descriptions

[0168] csi-IM-ResourcesForInterference

[0169] CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in nzp-CSI-RS-ResourcesforChannel.

[0170] csi-SSB-ResourceSet

[0171] CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on).

[0172] nzp-CSI-RS-ResourcesForInterference

[0173] NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on).

[0174] qcl-info

[0175] List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by nzp-CSI-RS-ResourcesforChannel. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info-forChannel corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info-forChannel corresponds to second entry in nzp-CSI-RS-Resources, and so on (see TS 38.214

[0019] , clause 5.2.1.5.1)

[0176] reportConfigId

[0177] The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig

[0178] resourceSet

[0179] NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to thesecond entry, and so on).

[0180] Conditional Presence and Explanation

[0181] Aperiodic: The field is mandatory present if the NZP-CSI-RS-Resources in the associated resourceSet have the resourceType aperiodic. The field is absent otherwise.

[0182] CSI-IM-ForInterference: This field is optional need M if the CSI-ReportConfig identified by reportConfigId is configured with csi-IM-ResourcesForInterference; otherwise it is absent.

[0183] NZP-CSI-RS-ForInterference: This field is optional need M if the CSI-ReportConfig identified by reportConfigId is configured with nzp-CSI-RS-ResourcesForInterference; otherwise it is absent.

[0184] CSI-SemiPersistentOnPUSCH-TriggerStateListThe CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214

[0019] , clause 5.2.CSI-SemiPersistentOnPUSCH-TriggerStateListinformation element-- ASN1START-- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STARTCSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerStateCSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE {associatedReportConfigInfo CSI-ReportConfigId,...}-- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP-- ASN1STOP

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

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

[0187] - CSI-IM resources for interference measurement

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

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

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

[0191] Non-periodic CSI reporting by the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-permanent CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after activation by the MAC control element (MAC CE). As previously mentioned, CSI resource settings can also be configured as non-periodic, periodic, or semi-permanent. Combinations between CSI reporting settings and CSI resource settings can be supported based on Table 14 below. Table 14 describes the Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations.

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

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

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

[0195] - If the number of CSI trigger states (M) within the configured CSI-AperiodicTriggerStateLite is 2N TS If it is greater than -1, according to the selected mapping relationship, the M CSI trigger states are 2N TS It can be mapped to -1, and 2N TS One of the trigger states of -1 can be indicated by the CSI request field.

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

[0197] Table 15 below shows an example of the relationship between CSI request indicators and CSI trigger states that can be indicated by those indicators.

[0198] CSI request fieldCSI trigger stateCSI-ReportConfigIdCSI-ResourceConfigId00no CSI requestN / AN / A01CSI trigger state#1CSI report#1CSI resource#1,CSI report#2CSI resource#210CSI trigger state#2CSI report#3CSI resource#311CSI trigger state#3CSI report#4CSI resource#4

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

[0200] FIG. 4 is a drawing illustrating an example of a non-periodic CSI reporting method according to one embodiment of the present disclosure.

[0201] In the example (400) of FIG. 4, the terminal can monitor the PDCCH (401) to obtain the DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (405). The terminal can obtain resource information for the CSI-RS (402) to be measured from the received CSI request indicator. The terminal can determine at what point in time it should perform a measurement on the CSI-RS (402) resource being transmitted based on the time when it receives the DCI format 0_1 ​​and the parameter for the offset within the CSI resource set setting (e.g., the aperiodicTriggeringOffset mentioned above) in the NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet). More specifically, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set setting as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the aperiodic CSI report is received and the slot in which the CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in Table 16 below.

[0202] aperiodicTriggeringOffsetOffset X00 slot11 slot22 slots33 slots44 slots516 slots624 slots

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

[0204] In the example (410) of FIG. 4, the terminal can monitor the PDCCH (411) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (415). The terminal can obtain resource information for the CSI-RS (412) to be measured from the received CSI request indicator. The example (410) of FIG. 4 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 (412) in the slot (corresponding to slot 0 (416) in FIG. 4) that received the DCI format 0_1 ​​triggering a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (415).

[0205] Aperiodic CSI reports may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI reports are transmitted via PUSCH, they may be multiplexed with a transport block. For multiplexing, a CRC may be inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The insertion of the CRC may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching during the multiplexing of CSI part 1 or CSI part 2 included in the aperiodic CSI reports can be calculated as shown in Table 17 below.

[0206] For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as Q' CSI-part1 , is determined as follows:[Mathematical Formula 1] For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as Q' CSI-part1 , is determined as follows:[Mathematical Formula 2] For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as Q' CSI-part1 , is determined as follows:if there is CSI part 2 to be transmitted on the PUSCH,[수학식 3] else end if…For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as Q' CSI-part2 , is determined as follows:[수학식 4] For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as Q' CSI-part2 , is determined as follows:[수학식 5] …For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as , is determined as follows:[수학식 6]

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

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

[0209] The following describes a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook). Figure 5 is a diagram illustrating an example of a method for setting up a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook) in an NR system.

[0210] In a situation where the number of HARQ-ACK PUCCHs a terminal can transmit within a slot is limited to one, when the terminal receives a semi-static HARQ-ACK codebook upper layer signaling setting, the terminal reports HARQ-ACK information regarding PDSCH reception or SPS PDSCH release in the HARQ-ACK codebook in the slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_x. In slots not indicated by the PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_x, the terminal reports the HARQ-ACK information bit value as NACK in the HARQ-ACK codebook. If the terminal reports only one SPS PDSCH release or one HARQ-ACK information for one PDSCH reception in the MA,C cases for candidate PDSCH reception, and the report is scheduled by DCI format 1_0 containing information in which the counter DACI field in the Pcell indicates 1, the terminal determines one HARQ-ACK codebook for the corresponding SPS PDSCH release or the corresponding PDSCH reception.

[0211] Except for that, the HARQ-ACK codebook determination method according to the method described above is followed.

[0212] If MA,c is the set of PDSCH reception candidate cases in serving cell c, MA,c can be obtained through the following [pseudo-code 1] steps.

[0213] [pseudo-code 1 start]

[0214] - Step 1: Initialize j to 0 and MA and c to empty sets. Initialize k, the HARQ-ACK transmission timing index, to 0.

[0215] - Step 2: Set R as the set of each row in the table containing slot information, start symbol information, and symbol count or length information where PDSCH is mapped. If the PDSCH-possible mapping symbol pointed to by each value in R is set to a UL symbol according to the DL and UL settings established above, delete the corresponding row from R.

[0216] - Step 3-1: If a terminal can receive one unicast PDSCH per slot and R is not an empty set, add 1 to set MA,c.

[0217] - Step 3-2: If the terminal can receive more than one unicast PDSCH in a slot, count the number of PDSCHs that can be assigned to different symbols in the calculated R and add that number to MA,c.

[0218] - Step 4: Increase k by 1 and start again from Step 2.

[0219] [End of pseudo-code 1]

[0220] With the example of FIG. 5, the above-described pseudo-code 1 is used to consider all slot candidates capable of PDSCH-to-HARQ-ACK timing that can indicate slot#k (508) in order to perform HARQ-ACK PUCCH transmission in slot#k (508). FIG. 5 assumes that HARQ-ACK transmission in slot#k (508) is possible by PDSCH-to-HARQ-ACK timing combinations that are only possible for PDSCHs scheduled in slot#n (502), slot#n+1 (504), and slot#n+2 (506). Then, the maximum number of PDSCHs that can be scheduled per slot is derived by considering the time domain resource configuration information of the PDSCHs that can be scheduled in slots 502, 504, and 506, respectively, and information indicating whether the symbol within the slot is a downlink or an uplink. For example, assuming that 2 PDSCHs are possible in slot 502, 3 PDSCHs in slot 504, and 2 PDSCHs in slot 506, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in slot 508 is 7. This is called the cardinality of the HARQ-ACK codebook.

[0221] The dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) is described below. Figure 6 is a diagram illustrating an example of a method for setting the dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) in an NR system.

[0222] The terminal transmits HARQ-ACK information transmitted within a PUCCH in slot n based on the PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release, and K0, which is transmission slot location information of the PDSCH scheduled in DCI format 1_x. Specifically, for the transmission of the HARQ-ACK information described above, the terminal determines the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by the PDSCH-to-HARQ_feedback timing and K0, based on the DAI included in the DCI indicating PDSCH or SPS PDSCH release.

[0223] The above DAI consists of Counter DAI and Total DAI. Counter DAI is information indicating the location within the HARQ-ACK codebook of HARQ-ACK information corresponding to the PDSCH scheduled in DCI format 1_x. Specifically, the value of the counter DAI in DCI format 1_x indicates the accumulated value of PDSCH reception or SPS PDSCH release scheduled by DCI format 1_x in a specific cell c. The aforementioned accumulated value is set based on the PDCCH monitoring occasion and serving cell where the scheduled DCI exists.

[0224] Total DAI is a value that indicates the size of the HARQ-ACK codebook. Specifically, the value of Total DAI represents the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time when the DCI was scheduled. Furthermore, Total DAI is a parameter used in Carrier Aggregation (CA) scenarios where the HARQ-ACK information in serving cell c includes HARQ-ACK information for PDSCHs scheduled in other cells, including serving cell c. In other words, the Total DAI parameter does not exist in systems operating as a single cell.

[0225] An example of the operation of the above DAI is shown in FIG. 6. FIG. 6 shows the change in the values ​​of Counter DAI (C-DAI) and Total DAI (T-DAI) indicated by the DCI found for each PDCCH monitoring occasion set for each carrier when the terminal transmits a selected HARQ-ACK codebook based on the DAI in the n-th slot of Carrier 0 (602) to PUCCH (620) in a situation where two carriers are set. First, the DCI found at m=0 (606) indicates that the C-DAI and T-DAI each have a value of 1 (612). The DCI found at m=1 (608) indicates that the C-DAI and T-DAI each have a value of 2 (614). The DCI found at Carrier 0 (c=0, 602) at m=2 (610) indicates that the C-DAI has a value of 3 (616). The DCI found in Carrier 1 (c=1, 604) of m=2 (610) indicates a C-DAI value of 4 (618). At this time, if Carrier 0 and 1 are scheduled on the same monitoring occasion, the T-DAI is indicated as 4 for both.

[0226] In FIGS. 5 and 6, the HARQ-ACK codebook determination operates under the condition that only one PUCCH containing HARQ-ACK information is transmitted within a single slot. This is referred to as Mode 1. As an example of a method in which a single PUCCH transmission resource is determined within a single slot, when PDSCHs scheduled in different DCIs are multiplexed into a single HARQ-ACK codebook and transmitted within the same slot, the PUCCH resource selected for HARQ-ACK transmission is determined as the PUCCH resource indicated by the PUCCH resource field indicated by the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated by the DCI scheduled prior to the above DCI is ignored.

[0227] The following description defines methods and devices for determining the HARQ-ACK codebook in situations where two or more PUCCHs containing HARQ-ACK information can be transmitted within a single slot. This is referred to as Mode 2. A terminal may be able to operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH within a slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs within a slot). Alternatively, for a terminal that supports both Mode 1 and Mode 2, the base station may be configured to operate in only one mode by upper-level signaling, or Mode 1 and Mode 2 may be implicitly determined by DCI format, RNTI, DCI specific field values, scrambling, etc. For example, PDSCHs scheduled in DCI format A and associated HARQ-ACK information are based on Mode 1, and PDSCHs scheduled in DCI format B and associated HARQ-ACK information are based on Mode 2.

[0228] The following describes the Type-3 HARQ-ACK codebook.

[0229] Unlike Type-1 and Type-2 HARQ-ACK codebooks, the Type-3 HARQ-ACK codebook is a method in which the terminal reports all HARQ-ACK information regarding all configured serving cells and the number of HARQ processes, the number of TBs per HARQ process, and the number of CBGs per TB. For example, if the terminal has 2 serving cells, 16 HARQ processes per serving cell, 1 TB per HARQ process, and 2 CBGs per TB, the terminal reports a total of 64 (= 2 x 16 x 1 x 2) HARQ-ACK information bits. Additionally, depending on a separate configuration, it may be possible to report the NDI value recently received by the terminal along with the HARQ-ACK information and the associated HARQ process. Through this NDI value, the base station can determine whether the PDSCH received for each of the terminal's HARQ processes is considered an initial transmission or a retransmission. If there is no separate report of the corresponding NDI value, if the terminal has already reported HARQ-ACK information for a specific HARQ process before receiving the DCI requesting the Type-3 HARQ-ACK codebook from the base station, the terminal maps the corresponding HARQ process to NACK; otherwise, it maps the HARQ-ACK information bit to the PDSCH received for each corresponding HARQ process. The number of serving cells, the number of HARQ processes, the number of TBs, and the number of CBGs can each be configured, and if there are no separate configurations for each, the terminal may consider the number of serving cells to be 1, the number of HARQ processes to be 8, the number of TBs to be 1, and the number of CBGs to be 1, respectively. Additionally, the number of HARQ processes may vary per serving cell. Additionally, the value of the number of TBs may vary per serving cell or per BWP within a serving cell. Additionally, the number of CBGs may vary per serving cell.

[0230] One of the reasons a Type-3 HARQ-ACK codebook is required is that a terminal may be unable to transmit a PUCCH or PUSCH containing HARQ-ACK information for a PDSCH due to reasons such as channel connection failure or overlap with other high-priority channels. Therefore, it is reasonable for the base station to request that only the relevant HARQ-ACK information be reported, without the need to reschedule a separate PDSCH. Accordingly, the base station may be able to schedule the aforementioned Type-3 HARQ-ACK codebook and the PUCCH resource containing it via upper-layer signals or L1 signals (e.g., specific fields within the DCI).

[0231] If the terminal searches for a DCI format in which the value of the field requesting a one-shot HARQ-ACK is 1, the terminal determines a PUCCH or PUSCH resource for multiplexing a Type-3 HARQ-ACK codebook in a specific slot indicated by the DCI format. Then, the terminal multiplexes only the Type-3 HARQ-ACK codebook within the PUCCH or PUSCH for transmission in the corresponding slot. That is, if two PUCCHs overlap, one is a Type-1 HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) and the other is a Type-3 HARQ-ACK codebook, the terminal multiplexes only the Type-3 HARQ-ACK codebook into the PUCCH or PUSCH. The reason is that the Type-3 HARQ-ACK codebook contains HARQ-ACK information bits for all serving cells, all HARQ process numbers, all TBs, and all CBGs that the terminal has been configured with, so the information of the Type-1 HARQ-ACK codebook and the Type-2 HARQ-ACK codebook can be seen as already included in the Type-3 HARQ-ACK codebook.

[0232] However, since the Type-3 HARQ-ACK codebook includes all HARQ-ACK information bits based on the information configured for all terminals, even HARQ-ACK information bits for unscheduled PDSCHs must be included in the codebook, even if they are mapped to NACK; consequently, there is a disadvantage in that the information bit size is large. Therefore, as the uplink control information bit size increases, there is a possibility that uplink transmission coverage or transmission reliability may decrease. Accordingly, a HARQ-ACK codebook with a size smaller than that of the Type-3 HARQ-ACK codebook is required. In this invention, this is regarded as different from the existing Type-3 HARQ codebook, and for convenience, it is described as an enhanced Type-3 HARQ-ACK codebook (or Type-4 HARQ-ACK codebook). However, it is entirely possible to replace it with other names. For example, the enhanced Type-3 HARQ-ACK codebook can be configured as follows.

[0233] - Type A: A subset of the total set of (configured) serving cells

[0234] - Type B: A subset of the total set of (configured) HARQ process numbers

[0235] - Type C: Subset of the total set of (configured) TB indexes

[0236] - Type D: A subset of the total set of (configured) CBG indices

[0237] - Type E: A combination of at least two of the above types A to D.

[0238] The enhanced Type-3 HARQ-ACK codebook may have at least one of the characteristics of Types A through E and may be composed of one or more sets. Instead of a subset of Types A through E, the entire set may be included. The meaning of multiple sets is, for example, that Type A and Type B may exist, or that even if it is Type A, there may be different subsets. Considering Types A through E, the enhanced Type-3 HARQ-ACK codebook may be indicated by an upper-level signal, an L1 signal, or a combination thereof. For example, as shown in [Table 26] below, the upper-level signal may indicate the set configuration for the HARQ-ACK information bits to be reported to each enhanced Type-3 HARQ-ACK codebook, and it may be possible for one of these values ​​to be indicated by the L1 signal. As shown in Table 18, it may be possible to individually set which type of enhanced Type-3 HARQ-ACK codebook is set for each index using an upper-level signal. Additionally, for specific indices such as index 3, it is possible to use a Type-3 HARQ-ACK codebook that reports all HARQ-ACK information bits. The Type-3 HARQ-ACK codebook may be indicated by a separate upper-level signal, or, if there is no upper-level signal, it may be determined to be used as a default value (e.g., ACK or NACK status for all HARQ process numbers).

[0239] IndexType 31 Serving cell i, HARQ process number (#1 ~ #8), TB 12 Serving cell i, HARQ process number (#9 ~ #12), TB 13 Type-3 HARQ-ACK codebook......

[0240] When the terminal receives a value requesting a one-shot HARQ-ACK feedback field and receives a value indicated by index 1 according to [Table 26], the terminal reports a total of 8 bits of HARQ-ACK information bits for serving cell i, HARQ process number (#1 to #8), and TB 1. When the terminal receives a value requesting a one-shot HARQ-ACK feedback field and receives a value indicated by index 2 according to Table 18, the terminal reports a total of 4 bits of HARQ-ACK information bits for serving cell i, HARQ process number (#1 to #8), and TB 1. When the terminal receives a value requesting a one-shot HARQ-ACK feedback field and receives a value indicated by index 3 according to Table 18, the terminal calculates the total number of HARQ-ACK bits by considering the serving cell set, the total number of HARQ processes per serving cell i, the number of TBs per HARQ process, and the number of CBGs per TB. Table 18 above is merely an example, and the total number of indices may be more or less than this, and the range of HARQ process values ​​indicated by each index and / or the information included in the enhanced Type-3 HARQ-ACK codebook may differ. Additionally, Table 18 above may be information indicated by upper-level signals, and specific indices may be notified via DCI.

[0241] In addition, HARQ-ACK information indicated by a specific index value or a one-shot HARQ-ACK feedback field (or other L1 signals) other than Table 18 above may be used for the purpose of resending specific HARQ-ACK information that was previously scheduled to be transmitted by the terminal but was dropped, rather than HARQ-ACK information for a specific (or all) HARQ process number. This is referred to as the retransmission of dropped HARQ-ACKs. The case of dropping may occur when the drop overlaps with another PUCCH or PUSCH that has a higher priority than the PUCCH or PUSCH containing the HARQ-ACK information. Alternatively, the case of dropping may occur when at least one symbol among the PUCCH or PUSCH containing the HARQ-ACK information has previously been designated as a downlink symbol by a higher layer signal. Alternatively, the above-mentioned drop may occur when the PUCCH or PUSCH containing the HARQ-ACK information overlaps at least partially with a resource indicated by the DCI containing Uplink Cancellation information intended to cancel uplink transmission. If the terminal supports both the dropped HARQ-ACK retransmission and (enhanced) type-3 HARQ codebook-based transmission, the terminal may be able to report HARQ information by selecting at least one of the dropped HARQ-ACK retransmission and (enhanced) type-3 HARQ codebook-based transmission through the DCI's CRC and scrambling RNTI information, the type of search space in which the DCI was searched, priority information among the DCI fields, or at least one of the information such as MCS, RV, NDI, HARQ process ID, or a combination thereof. Alternatively, a specific index value of Table 18 may be set and used as the dropped HARQ-ACK retransmission.The selection of a specific index in Table 18 above may be indicated by at least one or a combination thereof among the HARQ process number, MCS, NDI, RV, frequency resource allocation information, or time resource allocation information in the DCI fields. The size of the DCI bit field indicating the specific index in Table 18 above is. It can be determined as. Here represents the total number of indices in Table 18 set as upper-level signals.

[0242] The total number of HARQ-ACK bits N can be expressed as in the following mathematical formula 7.

[0243] [Mathematical Formula 7]

[0244]

[0245] In the above mathematical formula 7, n(c) is the total number of serving cells c, H c is the number of HARQ processes set in serving cell c, T b,c is the number of TBs per HARQ process set in serving cell c and BWP b, B c... is the number of CBGs configured in serving cell c. Additionally, when the terminal searches for a DCI format where the one-shot HARQ-ACK request field value is 1, the terminal determines a PUCCH or PUSCH resource to multiplex the corresponding Type-3 HARQ-ACK codebook (or enhanced Type-3 HARQ-ACK codebook). Then, the terminal multiplexes only the Type-3 HARQ-ACK codebook (or enhanced Type-3 HARQ-ACK codebook) on the determined PUCCH or PUSCH resource for transmission in the corresponding slot. If there exists a PUCCH or PUSCH containing SR information or CSI information that overlaps with the PUCCH or PUSCH, the terminal may drop the SR or CSI information without multiplexing it. That is, it may be possible to multiplex only the Type-3 HARQ-ACK information and drop the other UCIs, such as SR and CSI.

[0246] CP-OFDM is described below. CP-OFDM effectively reduces inter-symbol interference caused by multipath fading and facilitates the recovery and synchronization processes of received signals. This enhances the reliability of data transmission and enables support for high-speed data transmission in various wireless communication systems. A CP is generated by copying the end of an OFDM symbol and inserting it at the beginning of the symbol; the inserted CP absorbs inter-symbol interference (ISI) caused by multipath delay, thereby minimizing the impact on the received OFDM symbol. Additionally, the length of the CP must be set to be longer than the multipath delay spread. Therefore, OFDM symbols containing a CP minimize interference that may occur in a multipath environment and facilitate signal recovery and synchronization at the receiving end. The transmission process of CP-OFDM consists of the following procedures. These procedures can be performed by the transmitter (or RF).

[0247] 1. Data input: Data to be transmitted is input. This data is a digital signal, for example, in the form of a bit stream.

[0248] 2. Serial-to-parallel conversion: The input serial data stream is converted into a parallel data stream to map to each subcarrier of OFDM. The parallelized data becomes the signal symbols to be assigned to each subcarrier.

[0249] 3. Modulation: Parallelized data streams are modulated using digital modulation methods such as QAM (quadrature amplitude modulation) or PSK (phase shift keying). The modulated symbols represent data in the frequency domain, and each symbol corresponds to one subcarrier.

[0250] 4. IFFT (Inverse Fast Fourier Transform): Modulated subcarrier symbols are transformed from the frequency domain into a time domain signal through the IFFT. The output of the IFFT becomes an OFDM signal composed of multiple mutually orthogonal subcarriers.

[0251] 5. Cyclic Prefix Insertion: To prevent ISI caused by multipath fading, the transmitter copies a portion of the last part of the OFDM symbol and inserts it at the beginning of the symbol. The length of the inserted CP must be set longer than the multipath delay spread, which reduces interference that may occur when the transmitted signal is received.

[0252] 6. Parallel-to-serial conversion: The OFDM signal with the inserted CP is converted from parallel data back into a serial data stream. This is a preparation process for transmission to a wireless channel through a transmitter.

[0253] 7. D / A Conversion and RF Transmission: The serialized signal is converted into an analog signal through digital-to-analog conversion (D / A conversion). This analog signal is frequency-modulated and then transmitted to a wireless channel through a transmitting antenna.

[0254] The reception process of CP-OFDM consists of the following procedures. These procedures can be performed by a receiver (or RF).

[0255] 1. RF reception and A / D conversion: The transmitted analog signal is received by the receiving antenna. This signal is converted into a digital signal through analog-to-digital conversion (A / D conversion).

[0256] 2. Serial-to-parallel conversion: The received serial signal is converted into a parallel data stream. This parallelized signal is used for OFDM symbol recovery.

[0257] 3. Cyclic prefix removal: The CP is removed from the received signal. The removed signal is restored to the original OFDM symbol, and the CP has already performed the role of mitigating signal interference.

[0258] 4. FFT (Fast Fourier Transform): The signal with CP removed is transformed from the time domain to the frequency domain signal through the FFT. The FFT is the inverse process of the IFFT, in which the frequency components of each subcarrier are restored and modulated symbols are extracted.

[0259] 5. Equalization: Modulated symbols undergo a channel equalization process to correct distortion caused by the channel. In this process, the amplitude and phase of the signal are corrected based on channel state information, and the original modulated symbols are restored.

[0260] 6. Demodulation: The recovered symbols are demodulated back into the original bit data. Depending on the demodulation method based on QAM or PSK, each symbol is converted into the corresponding bit data.

[0261] 7. Parallel-to-serial conversion: The demodulated parallel data stream is converted into a serial data stream. This process recovers the original transmitted data bit stream.

[0262] 8. Data Output: The recovered data is output, and this matches the original data input from the transmitting side.

[0263] The following describes DFT-s-OFDM (discrete Fourier transform spread-OFDM). OFDM is a method that transmits data in parallel using multiple subcarriers and exhibits robust performance against frequency selective fading and ISI. However, the OFDM method has the disadvantage of a high peak-to-average power ratio (PAPR). A high PAPR can induce non-linear distortion in power amplifiers, thereby degrading transmission efficiency. To address this, the DFT-s-OFDM method, which introduces discrete Fourier transform spreading, has been proposed.

[0264] DFT-s-OFDM is a technology that improves transmission efficiency by effectively reducing PAPR while retaining the advantages of OFDM. DFT spreading is the process of converting an input data sequence into the frequency domain by applying the Digital Fourier Transform (DFT). The DFT evenly spreads each symbol of the input data across all subcarriers, ensuring that each subcarrier possesses the same signal energy. This lowers the PAPR, reducing non-linear distortion in the power amplifier and improving the quality of the transmitted signal. Next, the DFT-spreaded data is mapped into multiple subcarriers via an OFDM modulator, and these mapped subcarriers are transmitted in parallel while maintaining orthogonality. During this process, a CP (Positive Counter) is inserted to enhance resistance to multipath fading. Consequently, DFT-s-OFDM can effectively lower the PAPR while maintaining the robust performance of OFDM against frequency-selective fading and inter-symbol interference. A lower PAPR increases power amplifier efficiency and contributes to extended battery life and improved signal quality.

[0265] The transmission process of DFT-s-OFDM consists of the following procedures. These procedures can be performed by a transmitter (or RF).

[0266] 1. Data Input: Digital data to be transmitted is input. This data is generally in the form of a bit stream.

[0267] 2. Serial-to-parallel conversion: The input serial data stream is converted into a parallel data stream. The parallelized data can be individual data blocks.

[0268] 3. Modulation: Parallel data streams are modulated using digital modulation schemes such as QAM or PSK. The modulated symbols represent data in the frequency domain and can later be transmitted via DFT.

[0269] 4. DFT Spreading: Modulated symbols are converted from the frequency domain to the time domain signal through DFT operations. The DFT serves to distribute each modulated symbol across multiple subcarriers. In this process, each symbol is spread across multiple subcarriers, which has the effect of lowering the signal's PAPR.

[0270] 5. Serial-to-parallel conversion and subcarrier mapping: The output of the DFT is converted into a parallel data stream, which is mapped to each subcarrier of the OFDM. Each DFT spreading symbol is mapped to a given subcarrier to form an OFDM signal.

[0271] 6. IFFT (Inverse Fast Fourier Transform): Symbols mapped to each subcarrier are transformed into the time domain through the IFFT. The IFFT combines all subcarriers to generate a single OFDM symbol. In this case, the OFDM symbol consists of multiple mutually orthogonal subcarriers.

[0272] 7. Circular Prefix (CP) Insertion: The transmitter inserts a CP into the generated OFDM symbol. The CP is a copy of the last part of the OFDM symbol inserted at the beginning of the symbol, which prevents ISI caused by multipath fading.

[0273] 8. Parallel-to-serial conversion: The OFDM symbol with the inserted CP is converted from parallel data back into a serial data stream. This serial signal is ready to be transmitted from the transmitter to the radio channel.

[0274] 9. D / A Conversion and RF Transmission: Serialized signals are converted into analog signals through digital-to-analog conversion (D / A conversion). The analog signals are frequency-modulated and then transmitted to a wireless channel through a transmitting antenna.

[0275] The reception process of DFT-s-OFDM consists of the following procedures. These procedures can be performed by a receiver (or RF).

[0276] 1. RF reception and A / D conversion: The receiving antenna receives the transmitted analog signal. The received signal is converted into a digital signal through analog-to-digital conversion (A / D conversion).

[0277] 2. Serial-to-parallel conversion: The received serial signal is converted into a parallel data stream. This parallelized signal is used for OFDM symbol recovery.

[0278] 3. CP Removal: The received CP is removed. The signal with the CP removed is restored to the original OFDM symbol. The CP is intended to prevent interference caused by multipath and is removed during the reception process.

[0279] 4. FFT: The signal with CP removed is converted from the time domain to the frequency domain signal through the FFT. Through the FFT, frequency components separated by subcarrier are recovered, and modulated symbols are extracted.

[0280] 5. Subcarrier demapping and parallel-to-serial conversion: The symbols recovered from each subcarrier are restored back to the original parallel data stream. The recovered data can be converted back to the original modulated symbols through IDFT operations.

[0281] 6. IDFT despreading: The recovered data in the frequency domain is converted back to the original time domain through the IDFT (inverse discrete Fourier transform). The IDFT plays the role of recovering the original modulation symbols by inversely transforming the DFT-spreaded data from the transmitting side.

[0282] 7. Demodulation: The recovered symbols are demodulated and converted back into the original bit data. Each symbol is converted into a corresponding bit stream using a demodulation method based on QAM or PSK.

[0283] 8. Parallel-to-serial conversion: The demodulated parallel data stream is converted into a serial data stream. This serial data is restored to the original transmitted bit stream.

[0284] 9. Data Output: The recovered data is output, and this matches the original data input from the transmitting side.

[0285] As explained earlier, CP-OFDM is a method that adds CP to the OFDM method. OFDM is a method that transmits data simultaneously using multiple orthogonal subcarriers. In this process, each subcarrier must maintain orthogonality to prevent interference with one another. Accordingly, the following advantages and disadvantages of CP-OFDM are generally well known.

[0286] Advantage 1: Robust against multipath interference. CP plays a crucial role in mitigating multipath interference that may occur during signal transmission. Through this, CP-OFDM demonstrates robust performance against frequency-selective fading of the channel.

[0287] Advantage 2: Efficient use of frequency resources is possible. Frequency resources can be utilized efficiently by using orthogonal subcarriers.

[0288] Advantage 3: The receiver structure is simple. In CP-OFDM, the receiver structure is relatively simple because each subcarrier signal can be demodulated independently.

[0289] Disadvantage 1: High PAPR. One of the major disadvantages of CP-OFDM is its high PAPR. This can lead to inefficiency in amplifier design.

[0290] Disadvantage 2: Signal loss may occur due to multipath delay. If the length of CP is shorter than the multipath delay, signal loss may occur.

[0291] DFT-s-OFDM is a type of OFDM that first performs the DFT on the data to be transmitted and then maps the result to the OFDM subcarrier. This method was proposed to address the high PAPR problem of CP-OFDM. DFT-s-OFDM is also referred to as SC-FDMA. The following advantages and disadvantages of DFT-s-OFDM are generally known.

[0292] Advantage 1: Low PAPR. By spreading data through DFT, a lower PAPR compared to CP-OFDM can be provided. This increases power efficiency and creates favorable conditions for amplifier design.

[0293] Advantage 2: It has single-carrier characteristics. Unlike CP-OFDM, DFT-s-OFDM maintains single-carrier characteristics, so it can perform better with respect to frequency-selective fading.

[0294] Advantage 3: It can be demodulated in the same way as OFDM, while providing the flexibility to apply various modulation schemes. Therefore, modem designs with a structure similar to OFDM can be supported.

[0295] Disadvantage 1: Transceiver design complexity may increase. The design of the receiver may become complex due to the DFT process and additional processing. In addition, this may increase the computational load of the transceiver by adding DFT and Inverse DFT (IDFT) operations.

[0296] Disadvantage 2: In certain channel situations, DFT-s-OFDM may be inefficient compared to CP-OFDM in terms of frequency resource utilization.

[0297] CP-OFDM has a simple structure and is robust against multipath interference, but it suffers from the problem of high PAPR. DFT-s-OFDM has a low PAPR, resulting in good power efficiency and the ability to maintain single-carrier characteristics, but it involves increased computational complexity and may be disadvantageous in terms of efficiency under certain circumstances.

[0298] FIG. 7 is a diagram illustrating an example of a signal transmission step according to an embodiment of the present disclosure. According to FIG. 7, first, transform precoding (700) is applied exclusively to DFT-s-OFDM, and subsequently, sub-carrier mapping (710), IFFT (720), and CP insertion (730) can be applied commonly to both DFT-s-OFDM and CP OFDM. Therefore, since all processes except the transform precoding step are identical, it is easy to implement a modem. In addition, in the case of DFT-s-OFDM, the design complexity may increase compared to CP OFDM because the transform precoding step is added.

[0299] The following describes the orthogonal time-frequency space (OTFS). Frequency domain modulation schemes such as OFDM have been widely used in existing wireless communication systems. However, OFDM has the disadvantage of degrading performance in environments with severe time-frequency fluctuations, such as multipath fading. In particular, in high-speed mobile environments, interference in the frequency domain increases due to the Doppler effect, and communication quality can be significantly degraded.

[0300] OTFS is a modulation scheme proposed to address these issues, which modulates and transmits data in the delay-Doppler domain rather than the time-frequency domain. This enables the modulated data to exhibit robust performance against multipath fading and Doppler effects, allowing for more stable data transmission. Modulation in the delay-Doppler domain means that input data is converted into the delay-Doppler domain before modulation. To achieve this, a 2D transformation technique is applied to convert the signal from the time-frequency domain to the delay-Doppler domain. Subsequently, the converted data is modulated in the delay-Doppler domain. OTFS transmits each signal by mapping it to a combination of Doppler frequency and delay time, which enables transmission that is more robust against multipath and Doppler effects. Consequently, it offers strong resistance to multipath fading.

[0301] Because OTFS is designed to disperse transmitted signals in the time-Doppler domain, interference caused by multipath is dispersed, and the signal can be effectively recovered at the receiver. Furthermore, since OTFS naturally handles frequency shifts caused by the Doppler effect in the time-Doppler domain, it guarantees stable communication even in high-speed mobile environments. Additionally, at the receiver, the received signal is demodulated in the time-Doppler domain and then inversely transformed into the time-frequency domain. Through this process, the original data can be accurately recovered. Consequently, channel equalization is performed in the time-Doppler domain when using OTFS, effectively compensating for channel variability. As a result, OTFS systems can provide excellent performance even in environments with severe multipath and Doppler effects; in particular, communication performance is significantly improved in high-speed mobile environments or urban areas, and it can be usefully applied in applications such as vehicle-to-vehicle (V2X) and satellite communication.

[0302] The transmission process of OTFS consists of the following procedures. These procedures can be performed by a transmitter (or RF).

[0303] 1. Data Input: Digital data to be transmitted is input. This data is generally in the form of a bit stream.

[0304] 2. Serial-to-parallel conversion: The input serial data stream is converted into a parallel data stream. This parallel data is prepared for the latency-Doppler domain mapping of the OTFS.

[0305] 3. Modulation: Parallel data streams are modulated using digital modulation schemes such as QAM or PSK. The modulated symbols represent data in the frequency domain. In OTFS, these modulated symbols are mapped to the delay-Doppler domain.

[0306] 4. 2D Transform - Mapping to the Delay-Time-Doppler Domain: Modulated symbols are mapped to the delay-time-Doppler domain through a 2D transform. The 2D transform involves the process of converting a signal from the time-frequency domain to the delay-time-Doppler domain, and for this purpose, the separated fast Fourier transform (SFFT) or other 2D transform techniques may be used. In this mapping process, symbols are arranged in various combinations of delay times and Doppler frequencies, thereby increasing robustness against multipath and Doppler effects.

[0307] 5. Sampling after domain transformation: The signal mapped in the time-Doppler domain is transformed back into the time-frequency domain. At this point, the signal is transformed into the time domain through the Inverse Fast Fourier Transform (IFFT). The transformed signal consists of OTFS symbols and can then be transmitted in the time domain.

[0308] 6. CP Insertion: CP is inserted into OTFS symbols generated in the time domain. As with OFDM, CP is used to prevent multipath fading and inter-symbol interference (ISI).

[0309] 7. Parallel-to-serial conversion: An OTFS signal with a CP inserted is converted from parallel data to a serial data stream. The serialized signal can be transmitted over a wireless channel through a transmitter.

[0310] 8. D / A Conversion and RF Transmission: Serialized signals are converted into analog signals through digital-to-analog conversion (D / A conversion). The analog signals are frequency-modulated and then transmitted to a wireless channel through a transmitting antenna.

[0311] The reception process of OTFS consists of the following procedures. These procedures can be performed by a receiver (or RF).

[0312] 1. RF reception and A / D conversion: The receiving antenna receives the transmitted analog signal. This signal is converted into a digital signal through analog-to-digital conversion (A / D conversion).

[0313] 2. Serial-to-parallel conversion: The received serial signal is converted into a parallel data stream. This parallelized signal is used to recover OTFS symbols.

[0314] 3. CP Removal: Circular prefixes (CPs) are removed from the received signal. The signal with the CP removed is restored to its original OTFS symbols. The CP has already performed the role of reducing interference caused by multipath during the reception process.

[0315] 4. Time-Frequency Domain Transformation: The signal with CP removed is converted into a time-frequency domain signal. This transformation is performed using tools such as the Fast Fourier Transform (FFT). In this process, the received signal is converted into data sampled in the frequency domain.

[0316] 5. 2D Transformation - Transformation to the Time-Time-Doppler Domain: The signal transformed into the time-frequency domain is transformed again into the time-time-Doppler domain. Through this transformation, the received signal is mapped to the original Doppler frequency and time-time, thereby accurately compensating for variability due to multipath and Doppler effects.

[0317] 6. Demodulation: Data recovered in the latency-Doppler domain is converted back into the original bit data through a demodulation process. Each symbol is converted into a corresponding bit stream using a demodulation method based on QAM or PSK.

[0318] 7. Parallel-to-serial conversion: The demodulated parallel data stream is converted into a serial data stream. This serial data is restored to the original transmitted bit stream.

[0319] 8. Data Output: The recovered data is output, and this matches the original data input from the transmitting side.

[0320] The CP-OFDM, DFT-s-OFDM, and OTFS described above can be considered as waveforms capable of providing optimal performance in specific environments. For example, this may apply to supporting CP-OFDM and DFT-s-OFDM for uplink transmission in LTE and 5G NR. In next-generation communication systems, it may be possible to support one or more waveforms for downlink transmission as well as uplink transmission.

[0321] [1st Example]

[0322] The following describes a method for reporting a terminal preference for a waveform. Specifically, by directly reporting the waveform it prefers to the base station, the terminal can ensure that the waveform applied to the PDSCH subsequently scheduled for the terminal becomes the waveform preferred by the terminal. The base station may be able to receive downlink channel status information indirectly from the terminal through CSI feedback information. However, if it is possible for the terminal to derive a preferred waveform through direct downlink channel estimation, it may be more efficient for the terminal to directly determine the waveform rather than the base station directly determining the waveform applied to the downlink channel indirectly through separate CSI feedback. The aforementioned downlink channel may be at least one of PDSCH or PDCCH. Alternatively, it may refer to at least one of downlink reference signals such as DMRS (demodulation reference signal), PTRS (phase tracking reference signal), PRS (positioning reference signal), or CSI-RS.

[0323] When a terminal reports its waveform preference, it may apply at least one of the following methods. Here, "waveform" refers to a waveform to be applied to the downlink channel, and may be at least one of CP-OFDM, DFT-s-OFDM, or OTFS. Alternatively, it may be possible to apply at least one of the following reporting methods to waveforms to be applied to uplink channels (e.g., PUSCH, SRS, PUCCH), not limited to downlink channels. Combinations of the following methods may also be sufficiently considered.

[0324] The terminal's preferred waveform information may consist of 1 or 2 bits. If it consists of 1 bit, it may be used to indicate one of two waveforms among CP-OFDM, DFT-s-OFDM, and OTFS, depending on a value of 0 or 1. For example, based on terminal capability reports, the relative speed between the terminal and the base station, or the distance between the terminal and the base station, the two waveforms may be predetermined or set between the base station and the terminal. On the other hand, if it consists of 2 bits, the terminal may report a preference for one of three waveforms, CP-OFDM, DFT-s-OFDM, or OTFS, using a value of 00, 01, or 10. The values ​​described above are merely examples, and obvious variations are possible.

[0325] Method 1-1: When reporting scheduling request (SR) information from a terminal, 1 or 2 bits of information reporting waveform preference may be added in addition to the 1-bit SR. In this case, a bitmap may be configured in the form {SR, waveform preference}. This is merely an example, and obvious variations are possible, for instance, the order may be changed. For instance, when a terminal transmits an SR to request resources for uplink data, it may be possible to transmit information for transmitting a preferred waveform in addition to the SR, by adding 1 to 2 bits. Thus, it may be possible for the terminal to transmit 2 or 3 bits of information to the base station. Alternatively, depending on the configuration information related to the SR transmission resource, the terminal may transmit only an SR composed of 1 bit, or transmit an SR composed of 2 or 3 bits that includes information for transmitting the preferred waveform information. The above settings are provided differently, so the terminal can determine in advance whether to transmit only 1 bit (i.e., transmit only SR) or transmit 2 or 3 bits (i.e., report information reporting SR and waveform preference together) for SR resources that exist periodically in terms of time resources.

[0326] Alternatively, the terminal may report a preference for a specific waveform by transmitting an SR from one of multiple configured SR resources. In this case, each SR resource setting may correspond to a specific waveform. When the base station receives waveform preference information from the terminal, it may be possible to explicitly include the waveform preferred by the terminal in the scheduling information and transmit it to the terminal when scheduling downlink or uplink signals thereafter. Alternatively, the base station may include the waveform preferred by the terminal in the scheduling information and, based on the base station's judgment, schedule and transmit downlink or uplink signals using the waveform preferred by the terminal.

[0327] Method 1-2: When reporting CSI measurement results, the terminal may add 1 or 2 bits of information reporting waveform preference other than the CSI measurement result value. In this case, the bitmap may be configured in the form {CSI, waveform preference}. This is merely an example, and obvious variations are possible, for example, the order may be changed. For example, when the terminal reports result values ​​such as CQI, RI, or PMI information for downlink channel measurement information to the base station, it may add 1 or 2 bits of information reporting the preferred waveform.

[0328] There are three main types of resources for reporting channel measurement results: Aperiodic CSI, Semi-persistent CSI, and Periodic CSI. Aperiodic CSI refers to a single transmission containing CSI information via a PUSCH or PUCCH scheduled through DCI. Semi-persistent CSI refers to a transmission triggered by DCI or MAC CE, followed by periodic transmission containing CSI information via PUSCH or PUCCH. Periodic CSI refers to a transmission configured by RRC, followed by periodic transmission of CSI information via PUCCH. Among these three types of channel measurement result reporting resources, it may be possible to transmit including waveform information preferred by the terminal, limited to at least one specific resource type. Alternatively, separately, when the base station configures a specific CSI reporting resource in advance, it may be possible to configure whether transmission including waveform information is possible when reporting CSI from that resource.

[0329] For example, in a situation where a terminal is configured to report n bits of CSI information, it may be additionally configured to transmit including waveform preference information consisting of 1 or 2 bits. In this case, the terminal may be able to report the waveform information preferred by the terminal along with the CSI information in the form of n+1 or n+2 bits. When the base station receives waveform preference information from the terminal, it may be possible to explicitly include the waveform preferred by the terminal in the scheduling information and transmit it when scheduling downlink or uplink signals to the terminal.

[0330] Method 1-3: When reporting a HARQ-ACK, the terminal may add 1 or 2 bits of information reporting a waveform preference to the HARQ-ACK information for the received PDSCH demodulation / decoding. In this case, the bitmap may be configured in the form {HARQ-ACK, waveform preference}. This is merely an example, and obvious variations are possible, for instance, the order may be changed. For instance, after receiving a PDSCH from a base station, when the terminal generates the demodulation / decoding result value for the PDSCH as HARQ-ACK information and transmits it by including it in the PUCCH resource, it may be possible to transmit to the base station the waveform information preferred by the terminal along with that information. Specifically, the base station may provide the waveform information applied to the PDSCH within the DCI information for scheduling the PDSCH, and instruct the terminal to report the waveform information preferred by the terminal along with the HARQ-ACK for the PDSCH. That is, the terminal may be able to determine, through a specific DCI field, that when transmitting HARQ-ACK information within the DCI information received from the base station, the terminal should also report the waveform it prefers. Accordingly, when the terminal reports n bits of HARQ-ACK information and is instructed to also report the waveform it prefers, the terminal may transmit to the base station a PUCCH (or PUSCH) containing waveform preference information and HARQ-ACK information, which together consist of a total of n+1 or n+2 bits, including information on a waveform preferred by 1 or 2 bits.

[0331] In the case of a PDSCH received periodically without separate DCI scheduling, it may be possible for the terminal to be configured to transmit HARQ-ACK information for the PDSCH received periodically, including the waveform information preferred by the terminal, when the terminal reports such information through a higher-layer signal or DCI information that activates the PDSCH in advance.

[0332] When a base station receives waveform preference information from a terminal, it may be possible to explicitly include the waveform preferred by the terminal in the scheduling information and transmit it when scheduling downlink or uplink signals to the terminal.

[0333] Method 1-4: The above methods involve transmitting information indicating the waveform preferred by the terminal along with UCI information such as HARQ-ACK, SR, or CSI. This is because transmitting the preferred waveform information together with other control information can reduce the transmission power consumption of the terminal. However, if such a channel is not scheduled, there is a possibility of delay because the terminal cannot transmit the preferred waveform information separately. Therefore, to reduce delay, it may be possible for the terminal to transmit the waveform preferred by the terminal in a separate UCI format.

[0334] For example, the base station may periodically configure a reporting resource to report the waveform preferred by the terminal via an upper layer signal in advance, or temporarily instruct the resource to report via an L1 signal. The terminal may be able to report the waveform information preferred by the terminal, consisting of 1 or 2 bits, from the said resource. The advantage of this method is that the terminal may be able to transmit the waveform information preferred by the terminal to the base station independently, without separately transmitting HARQ-ACK, SR, or CSI information. When the base station receives waveform preference information from the terminal, it may be able to explicitly include the waveform preferred by the terminal in the scheduling information and transmit it to the terminal when scheduling downlink or uplink signals thereafter. The terminal preferred waveform may be encoded and transmitted in the form of a UCI using a repetition code or a Reed-Muller (RM) code. Alternatively, it may be reported in the form of a sequence. For example, a specific waveform that a terminal can report corresponds to a specific ZC (Zadoff-Chu) sequence or preamble, and the terminal can report a preferred waveform to the base station by reporting the specific ZC sequence or preamble.

[0335] Method 1-5: The terminal may be able to report its preferred waveform information in the form of a MAC CE. The terminal may be able to include and transmit the preferred waveform information in the MAC CE when it receives a downlink signal, even without a separate request from the base station. Specifically, when transmitting a PUSCH, the terminal transmits a MAC CE containing the preferred waveform information within that PUSCH. Additionally, it may be possible for the MAC CE header to indicate that the preferred waveform information is included. In this case, the base station may be able to determine that the waveform information is included in the MAC CE by examining the header field. Alternatively, the terminal may be able to transmit the terminal's preferred waveform information using the MAC CE header.

[0336] [2nd Example]

[0337] In the following embodiments, a method for reporting a waveform preferred by the terminal by considering certain criteria is described. Generally, since the coverage of a signal using DFT-s-OFDM is greater than that of a signal using CP-OFDM, the terminal may be able to report a waveform preferred by the terminal by considering the received signal strength or SINR (signal to interference plus noise ratio) in the downlink channel. Specifically, the terminal may be able to report waveform information preferred by the terminal when the corresponding conditions are satisfied by considering one of the following methods. Alternatively, not limited thereto, some combinations of the following methods may be considered.

[0338] Method 2-1: If the L1-RSRP, L1-SINR, TDCP (time domain channel property), or phase noise measured by the terminal is below a certain threshold value or a threshold value set by the base station or a predetermined threshold value, the terminal may be able to report a DFT-S-OFDM preference, report a CP-OFDM preference, or report an OTFS preference.

[0339] Method 2-2: If the L1-RSRP, L1-SINR, TDCP, or phase noise measured by the terminal is greater than a threshold value set by the base station or a predetermined threshold value, the terminal may be able to report a DFT-S-OFDM preference, report a CP-OFDM preference, or report an OTFS preference.

[0340] Method 2-3: The preceding methods described a method for reporting a waveform preferred by the terminal from a resource set by the base station by continuously determining reference conditions regardless of whether the waveform preference reported by the terminal is identical or not. However, if the waveform newly reported by the terminal is identical to the waveform reported immediately prior, it may be possible for the terminal not to report the preferred waveform, thereby reducing the power consumption of the terminal. For example, in the case of Method 1-4 described in the first embodiment, if the base station instructs the terminal to periodically report the waveform preferred by the terminal, the terminal may report the preferred waveform only when the preferred waveform to be reported is different from the preferred waveform reported immediately prior. For example, if the terminal reported that it preferred CP-OFDM immediately prior, and the terminal still has a preferred waveform of CP-OFDM, it does not use the waveform preference reporting resource thereafter (i.e., does not report the preferred waveform). However, if the terminal's preferred waveform is DFT-S-OFDM or OTFS, the terminal may be able to transmit the corresponding preferred waveform information to the base station. Therefore, if the base station does not receive any signal or information from the terminal through the relevant resource, it can determine that the preferred waveform previously reported by the terminal remains valid.

[0341] Method 2-4: Similar to Method 2-3, but the criteria for the terminal to report a preferred waveform may be limited to cases where the terminal has a preferred waveform that is different from the waveform applied to the PDSCH scheduled by the base station prior to the terminal reporting the preferred waveform (rather than determining whether it is the same as the preferred waveform the terminal reported immediately before). For example, if the waveform applied to the PDSCH scheduled prior to the terminal reporting the preferred waveform is DFT-S-OFDM, the terminal may not transmit any signal to the waveform preference reporting resource (i.e., does not report the preferred waveform) if the preferred waveform is still DFT-S-OFDM. However, if the terminal's preferred waveform is the same as CP-OFDM or OTFS, the terminal may be able to report the corresponding waveform preference to the base station.

[0342] [3rd Example]

[0343] In the following embodiments, a method for determining a waveform preferred by a terminal based on the type of CSI information reported by the terminal is described. Typically, DFT-S-OFDM is a waveform considered for the purpose of increasing coverage, and OTFS is a waveform suitable for terminals moving at high speeds. Therefore, when the terminal's CSI information and the terminal's preferred waveform information are transmitted together to a base station, it may be possible to determine the type of the terminal's preferred waveform based on the CSI information reporting type.

[0344] For example, when a terminal reports CSI information composed of L1-RSRP or L1-SINR to a base station, whether the terminal prefers CP-OFDM or DFT-S-OFDM can be reported based on whether the preferred waveform information (1 bit) is 1 or 0. The terminal can indirectly determine the distance between the base station and the terminal through L1-RSRP; in this case, if the distance between the base station and the terminal is long, data transmission using DFT-S-OFDM, which offers better coverage performance, may be advantageous. As another example, when a terminal reports CSI information composed of TDCP to a base station, whether it prefers CP-OFDM or OTFS can be reported based on whether the preferred waveform information (1 bit) is 1 or 0. The terminal can determine the change in relative speed between the base station and the terminal through TDCP; if the speed is faster, data transmission using OTFS may be advantageous. These methods are merely examples, and obvious variations are possible. The advantage of this method is that the terminal can report its preferred waveform using 1 bit instead of 2 bits, and the terminal can adaptively report a waveform preference other than CP-OFDM depending on the CSI information reporting type.

[0345] FIG. 8a is a diagram illustrating an example of a method for a terminal to report a preferred waveform according to an embodiment of the present disclosure. The terminal may be able to receive, in advance, information regarding the type of waveform capable of reporting preference and the reporting resource. Specifically, the terminal receives an upper layer signal or / and an L1 signal for reporting a preferred waveform, which includes at least one of the setting information regarding the type of waveform capable of reporting preference, the reporting resource, and the reporting method, by considering the methods described in the first to third embodiments (800). Then, the terminal determines the preferred waveform (810). The terminal may determine the preferred waveform based on at least one of various factors, such as, for example, the characteristics of a measured downlink channel (received signal strength, SINR, Doppler shift, delay, etc.), the speed of the terminal, or the coverage of the base station. Alternatively, the terminal may determine the preferred waveform based on a comparison of channel characteristics with a threshold value related to downlink channel characteristics that is predetermined or set by the base station. The terminal reports the preferred waveform information through a scheduled resource to report information indicating the preferred waveform (820). For example, the terminal may report preferred waveform information according to at least one combination of the methods described in the first to third embodiments. Through this, when the terminal subsequently receives a PDSCH schedule from the base station, it may be possible for the preferred waveform to be applied. For example, when the base station schedules the PDSCH via upper signaling or / and DCI, if the scheduling information does not include waveform information, the terminal may be able to determine that the preferred waveform reported by the terminal has been applied to the PDSCH.As another example, the base station may include information indicating which waveform among candidate waveforms, including the preferred waveform reported by the terminal, is applied to the PDSCH in the scheduling information, and the terminal can receive the scheduling information and determine which waveform is applied to the PDSCH.

[0346] FIG. 8b illustrates an example of a method for a base station to receive a waveform preferred by a terminal according to an embodiment of the present disclosure. The base station may be able to set the type of waveform capable of reporting preference and information on reporting resources in advance. Specifically, the base station transmits an upper layer signal or / and an L1 signal for reporting a preferred waveform, which includes at least one of the setting information for the type of waveform capable of reporting preference, reporting resources, and reporting method, by considering the methods described in Examples 1 to 3 (850). Subsequently, the base station receives the preferred waveform information from the terminal (860). For example, the base station may receive the preferred waveform information according to a combination of at least one of the methods described in Examples 1 to 3. The terminal determining the preferred waveform may determine the preferred waveform based on at least one of various factors, such as the characteristics of the downlink channel measured (received signal strength, SINR, Doppler shift, delay, etc.), the speed of the terminal, or the coverage of the base station. Alternatively, the terminal may determine the preferred waveform based on a comparison of channel characteristics with a threshold value related to downlink channel characteristics that is predetermined or set by the base station. Subsequently, if possible, the base station can transmit downlink data to the terminal by applying the waveform indicated by the terminal's preferred waveform information (870). This step is not mandatory and may be omitted. Additionally, the base station can inform the terminal of the waveform of the downlink data by including information indicating the waveform of the downlink data in the downlink control information that schedules the downlink data.For example, when a base station schedules a PDSCH via upper signaling or / and DCI, if the preferred waveform reported by the terminal is applied, the base station may not include waveform information in the scheduling information. As another example, the base station may include information in the scheduling information indicating which waveform among the candidate waveforms, including the preferred waveform reported by the terminal, was applied to the PDSCH.

[0347] The drawings described above illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of this specification. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0348] [Fourth Example]

[0349] In the following embodiments, methods for considering scheduling constraints to reduce the burden of terminal implementation when DFT-s-OFDM is applied in a situation where the terminal can support CP-OFDM and DFT-s-OFDM on both the downlink channel and the signal are described. For example, when the terminal reports terminal capability to the base station after initial connection or at another stage, it may be possible to report including at least one of the following information.

[0350] Scheduled BW Size Constraint:

[0351] For example, if a terminal is scheduled a PDSCH with DFT-S-OFDM applied, it may be possible to report that the terminal can receive it only if it does not exceed X MHz (or RB or unit of frequency resource). X can be any positive value or a positive integer value. If the terminal reports to the base station that it cannot be scheduled a PDSCH exceeding 10 MHz, the base station must allocate only resources within 10 MHz when scheduling a PDSCH with DFT-S-OFDM applied to the terminal. If a PDSCH exceeding this is scheduled, the terminal may consider it an error case. When the above BW size value is reported in RB units, it may be possible to report different values ​​depending on the subcarrier spacing.

[0352] PDSCH scheduling with DFT-s-OFDM applied may be possible, limited to repetitive transmissions. According to this method, the terminal may report as a terminal capability that DFT-s-OFDM is applicable to repetitive PDSCH transmissions, or it may be possible to apply DFT-S-OFDM limited to PDSCHs that are repetitively transmitted according to 3GPP standards. Repetitive transmission is also a technique that improves PDSCH coverage, and applying DFT-s-OFDM may enable support for wider coverage. Therefore, when the terminal PDSCH is not repetitively transmitted, only the CP-OFDM waveform is applied to the PDSCH; however, when the PDSCH is repetitively transmitted, the terminal may be able to determine whether CP-OFDM or DFT-S-OFDM is applied based on the DCI or / and upper-layer signal information that schedules the repetitively transmitted PDSCH.

[0353] When changing the waveform, check the required switching time value:

[0354] The terminal performs a blind search for the DCI through PDCCH monitoring before receiving the PDSCH. If the waveform applied to the PDCCH is CP-OFDM, the terminal may be able to apply or not apply a switching time depending on whether the waveform applied to the PDSCH identified through the DCI within the PDCCH is CP-OFDM or DFT-s-OFDM. For example, if the waveform applied to the PDSCH is CP-OFDM, there is no need to consider a separate switching time. However, if the waveform applied to the PDSCH is DFT-S-OFDM, the terminal may need to consider a switching time. For example, if the terminal reports the switching time as one symbol, the base station must schedule the PDSCH such that the gap between the last symbol of the PDCCH and the first symbol to which DFT-s-OFDM is applied is at least one symbol. The switching time value may vary depending on the capabilities of the terminal and may also have different values ​​depending on the subcarrier spacing. The terminal may report multiple switching times according to the subcarrier interval or / and waveform to the base station.

[0355] Multi-rank support:

[0356] In the case of DFT-s-OFDM, unlike CP-OFDM, it may be possible to limit the maximum rank value to 1 or 2. Accordingly, the terminal transmits such information to the base station in the form of terminal capability information, and the base station can schedule downlink data by considering the maximum rank value supported by the terminal when PDSCH scheduling with the DFT-s-OFDM waveform applied. This is merely an example, and the terminal reports terminal capability information to the base station by considering the characteristics of data transmission according to the waveform (e.g., the number of supported layers (rank), MCS (modulation and coding scheme), code rate, TB count, whether initial transmission and retransmission are possible, etc.), and the base station can schedule downlink data according to the terminal capability.

[0357] The above example describes a case where the base station supports downlink transmission based on DFT-s-OFDM, but even when the base station applies a different waveform (e.g., OTFS), the terminal can report to the base station with terminal capability regarding constraints that may be applied to scheduling.

[0358] FIG. 9a is a diagram illustrating an example of a method for a terminal to report terminal capability according to an embodiment of the present disclosure. The terminal receives configuration information related to a waveform from a base station (900). Subsequently, the terminal determines a waveform that the base station can support (910). For example, the terminal can determine a waveform that the base station can support based on the configuration information. Accordingly, for example, if the terminal determines that the base station supports DFT-s-OFDM, the terminal may be able to report terminal capability to the base station through PUSCH MAC CE or RRC signaling by considering the methods described in the fourth embodiment (920).

[0359] FIG. 9b illustrates an example of a method for a base station to receive a terminal capability report according to an embodiment of the present disclosure. The base station transmits configuration information related to a waveform to a terminal (950). Subsequently, the base station receives terminal capability information regarding a waveform that the base station can support from the terminal (960). For example, if the base station transmits configuration information for the case where DFT-s-OFDM is used to the terminal, the base station may receive terminal capability according to at least one of the methods described in the fourth embodiment. At this time, the terminal may be able to report terminal capability to the base station through MAC CE or RRC signaling of PUSCH.

[0360] The drawings described above illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of this specification. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

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

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

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

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

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

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

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

[0368] Referring to FIG. 11, a base station may include a transceiver unit (referring to a base station receiver unit (1100) and a base station transmitter unit (1110), a memory (not shown), and a base station processing unit (1105, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (1100, 1110), the memory, and the base station processing unit (1105) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

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

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

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

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

[0376] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or 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 through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

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

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

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

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

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

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

Claims

1. In a method performed by a terminal of a communication system, A step of receiving configuration information for a preferred waveform report for receiving downlink data from a base station; A step of identifying a preferred waveform by comparing the values ​​of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise with a threshold value; and The method includes the step of transmitting information indicating the preferred waveform based on the setting information to the base station. A method characterized in that the preferred waveform is CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) when the value of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise is greater than or equal to the threshold value, and DFT-s-OFDM (discrete Fourier transform spread-OFDM) when the value is less than or equal to the threshold value.

2. In Paragraph 1, A method characterized by further including the step of receiving downlink data to which the preferred waveform is applied from the base station.

3. In Paragraph 1, A method characterized by the information indicating the preferred waveform being reported to the base station on an SR resource along with a scheduling request (SR).

4. In Paragraph 1, A method characterized by the information indicating the preferred waveform being reported to the base station on a resource for CSI reporting together with channel state information (CSI).

5. In the method performed by a base station of a communication system, A step of transmitting configuration information for a preferred waveform report to a terminal for receiving downlink data; and The method includes the step of receiving information from the terminal indicating the preferred waveform associated with the setting information, and A method characterized in that the preferred waveform is determined by CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) or DFT-s-OFDM (discrete Fourier transform spread-OFDM) based on the values ​​and thresholds of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise.

6. In Paragraph 5, A method characterized by further including the step of transmitting downlink data to the terminal to which the preferred waveform is applied.

7. In Paragraph 5, A method characterized by the information indicating the preferred waveform being reported from the terminal on an SR resource together with a scheduling request (SR).

8. In Paragraph 5, A method characterized by the information indicating the preferred waveform being reported from the terminal on a resource for CSI reporting together with channel state information (CSI).

9. In a terminal of a communication system, Transmitter / receiver; and Receive configuration information for a preferred waveform report for receiving downlink data from a base station, and Identify the preferred waveform by comparing the values ​​and thresholds of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise, and It includes a control unit configured to transmit information indicating the preferred waveform based on the setting information to the base station, and A terminal characterized in that the preferred waveform is CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) when the value of the L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise is greater than or equal to the threshold value, and DFT-s-OFDM (discrete Fourier transform spread-OFDM) when the value is less than or equal to the threshold value.

10. In Paragraph 9, A terminal characterized in that the above control unit is further configured to receive downlink data to which the preferred waveform is applied from the base station.

11. In Paragraph 9, A terminal characterized by information indicating the preferred waveform being reported to the base station on an SR resource along with a scheduling request (SR).

12. In Paragraph 9, A terminal characterized by information indicating the preferred waveform being reported to the base station on a resource for CSI reporting together with channel state information (CSI).

13. In a base station of a communication system, Transmitter / receiver; and Transmit configuration information for preferred waveform reporting to the terminal for receiving downlink data, and It includes a control unit configured to receive information indicating the preferred waveform associated with the setting information from the terminal, and A base station characterized by the fact that the preferred waveform is determined by CP-OFDM (cyclic prefix orthogonal frequency division multiplexing) or DFT-s-OFDM (discrete Fourier transform spread-OFDM) based on the values ​​and thresholds of L1-RSRP (L1-received signal received power), L1-SINR (signal to interference plus noise ratio), TDCP (time domain channel property), or phase noise.

14. In Paragraph 13, A base station characterized by the above-described control unit being further configured to transmit downlink data to the terminal with the preferred waveform applied.

15. In Paragraph 13, Information indicating the preferred waveform is reported from the terminal on an SR resource along with a scheduling request (SR), or A base station characterized by the information indicating the preferred waveform being reported from the terminal on a resource for CSI reporting together with channel state information (CSI).

Images