Method and device for transmitting and receiving downlink feedback information 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 provides a method for configuring and receiving a downlink control channel in a wireless communication system. The method performed by a terminal in a communication system according to one embodiment of the present disclosure comprises the steps of: receiving, through higher layer signaling, a configuration for the maximum number of ranks related to physical uplink shared channel (PUSCH) transmission and a configuration for the maximum number of multi-input multi-output (MIMO) layers related to the PUSCH transmission; performing the PUSCH transmission, wherein at least one PUSCH included in the PUSCH transmission includes two transport blocks (TBs) on the basis that at least one of the maximum number of ranks or the maximum number of layers exceeds 4; and receiving downlink control information (DCI) via a physical downlink control channel (PDCCH).

Description

Method and device for transmitting and receiving downlink feedback information in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and device for receiving downlink feedback information when a terminal can transmit up to two transport blocks (TBs) over an uplink physical shared channel.

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

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

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

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

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

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

[0008] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

[0009] The disclosed embodiment seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0010] The technical problems to be achieved in the disclosed embodiments are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from the various embodiments of the present disclosure described below.

[0011] The present disclosure proposes a method for designing a DCI including HARQ-ACK information of a PUSCH for a terminal transmitting two transport blocks via a PUSCH.

[0012] A method performed by a terminal in a communication system according to one embodiment of the present disclosure includes the steps of: receiving, through higher layer signaling, a configuration for a maximum number of ranks related to a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers related to the PUSCH transmission; performing the PUSCH transmission; at least one PUSCH included in the PUSCH transmission including two transport blocks (TBs) based on at least one of the maximum number of ranks or the maximum number of layers exceeding 4; and receiving downlink control information (DCI) through a physical downlink control channel (PDCCH).

[0013] According to one embodiment of the present disclosure, if a configuration for spatial bundling related to hybrid automatic repeat request (HARQ-ACK) information for a second TB associated with the PUSCH transmission is not received via the higher layer signaling: the DCI includes a first HARQ-ACK bitmap for the first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for the second TB associated with the PUSCH transmission; and the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

[0014] According to one embodiment of the present disclosure, HARQ process indexes are mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the first HARQ-ACK bitmap, each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of a first TB related to a corresponding HARQ-ACK process, and HARQ process indexes are mapped in ascending order from the MSB to the least significant bit (LSB) of a bit corresponding to the second HARQ-ACK bitmap, and a bit corresponding to the second HARQ-ACK bitmap indicates an ACK or NACK of a second TB related to a corresponding HARQ-ACK process, and when a setting for the number of HARQ processes is received through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, and the setting for the number of HARQ processes is received through the upper layer signaling. If not received via signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits.

[0015] According to one embodiment of the present disclosure, when the setting for the spatial bundling is received via the upper layer signaling: the DCI includes a third HARQ-ACK bitmap, the third HARQ-ACK bitmap is based on the spatial bundling being applied between bits corresponding to the first HARQ-ACK bitmap and bits corresponding to the second HARQ-ACK bitmap for the same HARQ process, and the spatial bundling corresponds to a logical XOR operation or a logical OR operation.

[0016] According to one embodiment of the present disclosure, the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

[0017] A terminal of a communication system according to one embodiment of the present disclosure comprises a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: receive, through higher layer signaling, a configuration for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers associated with the PUSCH transmission; perform the PUSCH transmission, wherein at least one PUSCH included in the PUSCH transmission includes two transport blocks (TBs) based on at least one of the maximum number of ranks or the maximum number of layers exceeding 4; and receive downlink control information (DCI) through a physical downlink control channel (PDCCH).

[0018] According to one embodiment of the present disclosure, if a configuration for spatial bundling related to hybrid automatic repeat request (HARQ-ACK) information for a second TB associated with the PUSCH transmission is not received via the higher layer signaling: the DCI includes a first HARQ-ACK bitmap for the first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for the second TB associated with the PUSCH transmission; and the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

[0019] According to one embodiment of the present disclosure, HARQ process indexes are mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the first HARQ-ACK bitmap, each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of a first TB related to a corresponding HARQ-ACK process, and HARQ process indexes are mapped in ascending order from the MSB to the least significant bit (LSB) of a bit corresponding to the second HARQ-ACK bitmap, and a bit corresponding to the second HARQ-ACK bitmap indicates an ACK or NACK of a second TB related to a corresponding HARQ-ACK process, and when a setting for the number of HARQ processes is received through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, and the setting for the number of HARQ processes is received through the upper layer signaling. If not received via signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits.

[0020] According to one embodiment of the present disclosure, when the setting for the spatial bundling is received via the upper layer signaling: the DCI includes a third HARQ-ACK bitmap, the third HARQ-ACK bitmap is based on the spatial bundling being applied between bits corresponding to the first HARQ-ACK bitmap and bits corresponding to the second HARQ-ACK bitmap for the same HARQ process, and the spatial bundling corresponds to a logical XOR operation or a logical OR operation.

[0021] According to one embodiment of the present disclosure, the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

[0022] A method performed by a base station in a communication system according to one embodiment of the present disclosure includes the steps of transmitting, through higher layer signaling, a configuration for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers associated with the PUSCH transmission; receiving the PUSCH transmission, wherein at least one PUSCH included in the PUSCH transmission includes two transport blocks (TBs) based on at least one of the maximum number of ranks or the maximum number of layers exceeding 4; and transmitting downlink control information (DCI) through a physical downlink control channel (PDCCH).

[0023] According to one embodiment of the present disclosure, if a configuration for spatial bundling related to hybrid automatic repeat request (HARQ-ACK) information for a second TB associated with the PUSCH transmission is not transmitted via the higher layer signaling: the DCI includes a first HARQ-ACK bitmap for the first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for the second TB associated with the PUSCH transmission; and the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

[0024] According to one embodiment of the present disclosure, HARQ process indexes are mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the first HARQ-ACK bitmap, each bit of the first HARQ-ACK bitmap indicates ACK (acknowledgement) or NACK (negative ACK) of the first TB associated with the corresponding HARQ-ACK process, and HARQ process indexes are mapped in ascending order from the MSB to the least significant bit (LSB) of the bits corresponding to the second HARQ-ACK bitmap, and the bits corresponding to the second HARQ-ACK bitmap indicate ACK or NACK of the second TB associated with the corresponding HARQ-ACK process, and when a setting for the number of HARQ processes is transmitted through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, and the setting for the number of HARQ processes is transmitted through the upper layer signaling. If not transmitted via signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits.

[0025] According to one embodiment of the present disclosure, when the setting for the spatial bundling is transmitted via the upper layer signaling: the DCI includes a third HARQ-ACK bitmap, the third HARQ-ACK bitmap is based on the spatial bundling being applied between bits corresponding to the first HARQ-ACK bitmap and bits corresponding to the second HARQ-ACK bitmap for the same HARQ process, and the spatial bundling corresponds to a logical XOR operation or a logical OR operation.

[0026] According to one embodiment of the present disclosure, the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

[0027] A base station of a communication system according to one embodiment of the present disclosure includes a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: transmit, through higher layer signaling, a configuration for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers associated with the PUSCH transmission; upon receiving the PUSCH transmission, at least one PUSCH included in the PUSCH transmission includes two transport blocks (TBs) based on whether at least one of the maximum number of ranks or the maximum number of layers exceeds 4; and transmit downlink control information (DCI) through a physical downlink control channel (PDCCH).

[0028] According to one embodiment of the present disclosure, if a configuration for spatial bundling related to hybrid automatic repeat request (HARQ-ACK) information for a second TB associated with the PUSCH transmission is not transmitted via the higher layer signaling: the DCI includes a first HARQ-ACK bitmap for the first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for the second TB associated with the PUSCH transmission; and the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

[0029] According to one embodiment of the present disclosure, HARQ process indexes are mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the first HARQ-ACK bitmap, each bit of the first HARQ-ACK bitmap indicates ACK (acknowledgement) or NACK (negative ACK) of the first TB associated with the corresponding HARQ-ACK process, and HARQ process indexes are mapped in ascending order from the MSB to the least significant bit (LSB) of the bits corresponding to the second HARQ-ACK bitmap, and the bits corresponding to the second HARQ-ACK bitmap indicate ACK or NACK of the second TB associated with the corresponding HARQ-ACK process, and when a setting for the number of HARQ processes is transmitted through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, and the setting for the number of HARQ processes is transmitted through the upper layer signaling. If not transmitted via signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits.

[0030] According to one embodiment of the present disclosure, when the setting for the spatial bundling is transmitted via the upper layer signaling: the DCI includes a third HARQ-ACK bitmap, the third HARQ-ACK bitmap is based on the spatial bundling being applied between bits corresponding to the first HARQ-ACK bitmap and bits corresponding to the second HARQ-ACK bitmap for the same HARQ process, and the spatial bundling corresponds to a logical XOR operation or a logical OR operation.

[0031] According to one embodiment of the present disclosure, the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

[0032] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0033] The disclosed embodiment provides a device and method capable of effectively providing a service in a mobile communication system.

[0034] The effects that can be obtained from the disclosed embodiments are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.

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

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

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

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

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

[0040] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

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

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

[0043] FIG. 9 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

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

[0045] FIG. 11 is a diagram illustrating a CG-DFI including two bitmaps for two transport blocks according to one embodiment of the present disclosure.

[0046] FIG. 12 is a diagram illustrating a CG-DFI including one bitmap for two transport blocks according to one embodiment of the present disclosure.

[0047] FIG. 13 is a diagram illustrating a CG-DFI including two bitmaps for two transport blocks according to one embodiment of the present disclosure.

[0048] FIG. 14 is a flowchart illustrating the operation of a terminal according to one embodiment of the present disclosure.

[0049] FIG. 15 is a flowchart illustrating the operation of a terminal according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0067] [NR time-frequency resources]

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

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

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

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

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

[0073] [Table 1]

[0074]

[0075] [Bandwidth Part (BWP)]

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

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

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

[0079] [Table 2]

[0080]

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

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

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

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

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

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

[0087] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part through the MIB (Master Information Block) in the initial access stage. More specifically, the terminal can set a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) for scheduling a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to the purpose of receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0088] [Bandwidth Part (BWP) Change]

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

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

[0091] [Table 3]

[0092]

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

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

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

[0096] [SS / PBCH block]

[0097] Next, we will explain the SS (Synchronization Signal) / PBCH block in 5G.

[0098] An SS / PBCH block may refer to a physical layer channel block consisting of a PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

[0099] - PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides some information about the cell ID.

[0100] - SSS: It serves as a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0101] - PBCH: Provides essential system information required for the terminal's data channel and control channel transmission and reception. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

[0102] - SS / PBCH Block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be transmitted within a 5ms period, and each transmitted SS / PBCH block can be distinguished by an index.

[0103] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0104] [PDCCH: DCI related]

[0105] Next, we will specifically explain downlink control information (DCI) in the 5G system.

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

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

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

[0109] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 4.

[0110] [Table 4]

[0111]

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

[0113] [Table 5]

[0114]

[0115]

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

[0117] [Table 6]

[0118]

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

[0120] [Table 7]

[0121]

[0122]

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

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

[0125] FIG. 4 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and one slot (420) in the time axis. The control regions (401, 402) may be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 404). Referring to the example illustrated in FIG. 4, Control Region #1 (401) is set to a control region length of two symbols, and Control Region #2 (402) is set to a control region length of one symbol.

[0126] In the aforementioned 5G, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 8.

[0127] [Table 8]

[0128]

[0129]

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

[0131] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 503), and a REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to constitute a downlink control channel allocation unit.

[0132] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 504), 1 CCE (504) can be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control region. CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

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

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

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

[0136] [Table 9]

[0137]

[0138]

[0139]

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

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

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

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

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

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

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

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

[0148] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] The aforementioned specified DCI formats may follow definitions such as the examples in Table 10.

[0163] [Table 10]

[0164]

[0165] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in the following mathematical expression 1.

[0166] [Mathematical Formula 1]

[0167]

[0168] - L: Integration level

[0169] - : Carrier Index

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

[0171] - : slot index

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

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

[0174] -

[0175] - , , ,

[0176] - : Terminal identifier

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

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

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

[0180] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

[0181] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information may include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-domain resource allocation information (604) is named "the first bitmap", the bitmap corresponding to the time-domain resource allocation information (603) is named "the second bitmap", and the bitmap corresponding to the period information (605) is named "the third bitmap". If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

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

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

[0184] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, type-0 (7-00), type-1 (7-05), and dynamic switch (7-10), which can be set through an upper layer in an NR wireless communication system.

[0185] Referring to Fig. 7, if the terminal is configured to use only type-0 resource allocation through upper layer signaling (7-00), some downlink control information (DCI) that allocates PDSCH / PUSCH to the terminal is N RBG Contains a bitmap consisting of N bits. RBG refers to the number of RBGs (resource block groups) determined as shown in [Table 11] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0186] [Table 11]

[0187]

[0188] The size of the BWP is the number of RBs included in the BWP. More specifically, when type-0 resource allocation is instructed, the length of the frequency domain resource assignment (FDRA) field of the DCI received by the terminal is the number of RBGs (N RBG ) and Here, the first RBG is It contains RBs of the dog, and the last RBG is On the other hand, contains the RBs of , otherwise, It contains RBs of RBs. The remaining RBGs contain P RBs, where P is the number of nominal RBGs determined according to Table 11.

[0189] If the terminal is configured to use only type-1 resource allocation through upper layer signaling (7-05), the DCI that allocates PDSCH / PUSCH to the terminal is It contains frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the BWP. Through this, the base station can set the starting VRB (7-20) and the length of frequency axis resources (7-25) allocated continuously therefrom.

[0190] If a terminal is configured to use both type-0 resource allocation and type-1 resource allocation through upper layer signaling (7-10), some DCIs that allocate PDSCH / PUSCH to the terminal include frequency-axis resource allocation information consisting of bits of the larger value (7-35) among the payload (7-15) for configuring type-0 resource allocation and the payload (7-20, 7-25) for configuring type-1 resource allocation. The conditions for this will be explained later. At this time, one bit may be added to the most significant bit (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that type-1 resource allocation is used.

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

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

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

[0194] [Table 12]

[0195]

[0196] [Table 13]

[0197]

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

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

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

[0201] FIG. 9 is a diagram illustrating an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0202] Referring to Figure 9, when the subcarrier spacing of the data channel and the control channel are the same (9-00, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (9-05, μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0203] [PUSCH: Transmission method related]

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

[0205] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 14] through higher-level signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 14] through higher-level signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of [Table 14], which is higher-level signaling, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 15]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 14], the terminal applies tp-pi2BPSK in pusch-Config of [Table 15] to PUSCH transmission operated by the configured grant.

[0206] [Table 14]

[0207]

[0208]

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

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

[0211] [Table 15]

[0212]

[0213]

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

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

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

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

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

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

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

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

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

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

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

[0225] [CA / DC related]

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

[0227] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.

[0228] Key features of NR SDAP (S25, S70) may include some of the following:

[0229] - Transfer of user plane data

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

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

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

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

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

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

[0236] - User data transfer function

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

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

[0239] - PDCP PDU reordering for reception

[0240] - Duplicate detection of lower layer SDUs

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

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

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

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

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

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

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

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

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

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

[0251] - Re-segmentation of RLC data PDUs

[0252] - Reordering of RLC data PDUs

[0253] - Duplicate detection function

[0254] - Protocol error detection

[0255] - RLC SDU discard function

[0256] - RLC re-establishment function

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

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

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

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

[0261] - Multiplexing / demultiplexing of MAC SDUs

[0262] - Scheduling information reporting function

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

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

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

[0266] - MBMS service identification function

[0267] - Transport format selection function

[0268] - Padding function

[0269] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

[0270] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

[0271] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support PDCCH repetitive transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for repetitively transmitting PDCCHs through multiple transmission points (TRPs) to improve PDCCH reception reliability at a terminal. Specific methods are described in detail in the following examples.

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

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

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

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

[0276]

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

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

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

[0280] - MIB (Master Information Block)

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

[0282] - RRC (Radio Resource Control)

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

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

[0285] - PDCCH (Physical Downlink Control Channel)

[0286] - DCI (Downlink Control Information)

[0287] - UE-specific DCI

[0288] - Group common DCI

[0289] - Common DCI

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

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

[0292] - PUCCH (Physical Uplink Control Channel)

[0293] - UCI (Uplink Control Information)

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

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

[0296] [CG-DFI related]

[0297] The base station may provide the terminal with the reception result for the transport block (TB) transmitted by the terminal through the uplink physical shared channel (PUSCH) using at least one DCI format, for example, the base station may use DCI format 0_1 ​​of the 5G system to provide the terminal with the reception result or HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgement) information for the transport block included in the PUSCH. At this time, the DCI may include at least the reception result for the transport block transmitted by the terminal through the configured grant PUSCH transmission. At this time, the DCI may include the reception result for all the transport blocks transmitted by the terminal through the configured grant PUSCH transmission or the dynamic grant PUSCH transmission. At this time, in the present disclosure, for the convenience of explanation, the DCI format 0_1 ​​will be used for the description, but the DCI format 0_1 ​​is only an example, and it is also possible to use another DCI format.

[0298] Configured grant PUSCH transmission refers to periodically transmitting PUSCH according to the settings of the base station. The configured grant PUSCH can be activated in a higher layer or through a DCI format in which the CRC is scrambled with CS-RNTI. Dynamic grant PUSCH transmission refers to a PUSCH scheduled through a DCI format in which the CRC is scrambled with C-RNTI or MCS-C-RNTI.

[0299] Here, DCI format 0_1 ​​is a DCI format that can be used as a non-fallback DCI for scheduling one or more PUSCHs to the UE or can be used to indicate Configured Grant Downlink Feedback Information (CG-DFI). The CRC of DCI format 0_1 ​​can be scrambled with at least one RNTI among C(cell)-RNTI, CS(configured scheduling)-RNTI, MCS(modulation coding scheme)-C-RNTI, and SP(Semi-Persistent)-CSI-RNTI.

[0300] DCI format 0_1 ​​is used to indicate CG-DFI as follows:

[0301] In the case where DCI format 0_1 ​​is a DCI format for a cell operating in an unlicensed band (or shared spectrum), the CRC-CS-RNTI scrambled DCI format 0_1 ​​may include a DFI flag field. At this time, a terminal receiving the DCI may determine that the DCI is a DCI for activating a second uplink transmission / reception method or a second uplink transmission resource (or a DCI for scheduling a PUSCH) if the value of the DFI flag field is 0, and may determine that the DCI is a DCI indicating CG-DFI if the value of the field is 1.

[0302] If DCI format 0_1 ​​is used to indicate CG-DFI, DCI format 0_1 ​​can be configured as follows.

[0303] - Control Information Format Identifier (Identifier for DCI formats): An identifier that distinguishes the DCI format of a 1-bit field. For example, if the identifier value is 0 in a terminal that receives DCI through a 1-bit identifier, the DCI can be distinguished as a UL DCI format (e.g., DCI format 0_1), and if it is 1, the DCI can be distinguished as a DL DCI format (e.g., DCI format 1_0).

[0304] - Carrier indicator: A field of 0 or 3 bits that indicates the serving cell index of the PUSCH cell scheduled by DCI.

[0305] - DFI flag: A field of 0 or 1 bit size that distinguishes whether the received DCI is a DCI that activates the second uplink transmission resource or a DCI that indicates CG-DFI.

[0306] - HARQ-ACK bitmap: If the number of HARQ processes set in the CG PUSCH is 16 or more, it is 32 bits. Otherwise, it is a bitmap of 16 bits in size, and each bit is mapped to one HARQ process index. At this time, the HARQ process index is mapped in ascending order from the MSB (most significant bit) to the LSB (least significant bit) of the bitmap.

[0307] - Controls the increase or decrease of the terminal's PUSCH transmission power with the PUSCH transmission power control (TPC command for scheduled PUSCH) field.

[0308] - All remaining bits are set to 0 to match the size of DCI with other DCI formats.

[0309] Accordingly, if the value of the DFI flag field of the DCI format 0_1 ​​received by a terminal configured to monitor the CS-RNTI scrambled DCI format 0_1, which includes a CRC including a DFI flag field, is 1, the terminal determines that the DCI format is a DCI format including CG-DFI that provides HARQ-ACK information for a transport block transmitted via PUSCH, and receives the reception result of the transport block through the HARQ-ACK bitmap included in the DCI format.

[0310] The above HARQ-ACK bitmap may be HARQ-ACK information for a transport block received by the base station from the terminal via PUSCH for all HARQ processes for a serving cell in which the base station transmits DCI format 0_1 ​​or all uplink HARQ processes set for the serving cell. In this case, the HARQ-ACK bitmap may be HARQ-ACK information for a transport block received by the base station from the terminal via PUSCH for all HARQ processes for a serving cell indicated by the carrier indicator or all uplink HARQ processes set for the serving cell, if a carrier indicator is included in DCI format 0_1.

[0311] For a transport block transmitted via DG (dynamic grant) PUSCH, if the terminal receives the first symbol of the PDCCH transmitting the DCI format indicating CG-DFI after X symbols based on the last symbol of the PUSCH, the terminal determines that the HARQ-ACK information for the HARQ process number (or index) corresponding to the transport block transmitted via the PUSCH is valid. At this time, X is a value set by the base station via an upper signal or a value that can be defined in advance between the base station and the terminal.

[0312] For a transport block transmitted through DG PUSCH, in a case where a terminal receives CG-DFI providing HARQ-ACK information for a HARQ process number corresponding to the transport block, if the first symbol of a PDCCH transmitting DCI format 0_1 ​​providing the CG-DFI is at least X symbols later than the last symbol of either the PUSCH or the repeatedly transmitted PUSCH, the terminal determines that the HARQ-ACK information corresponding to the HARQ process number of the transport block provided through the CG-DFI is valid. At this time, X is a value set by the base station through an upper signal or a value that can be defined in advance between the base station and the terminal.

[0313] For a transport block initially transmitted via DG PUSCH, if the terminal receives CG-DFI providing HARQ-ACK information for the transport block, and the HARQ-ACK information value is ACK (acknowledgement), the terminal assumes that the base station has correctly received (or successfully decoded) the transport block. If the HARQ-ACK information value is NACK (negative ACK), the terminal assumes that the base station has not correctly received (or successfully decoded) the transport block.

[0314] In the following, we explain the case where a transport block transmitted through CG PUSCH is transmitted in multiple slots. In the case where the terminal receives CG-DFI providing HARQ-ACK information for the HARQ process number corresponding to the transport block,

[0315] - If the above HARQ-ACK information is ACK, and if it is at least X symbols after the last symbol of the PUSCH transmitted in the first slot among the PUSCHs transmitted in multiple slots, the terminal determines that the HARQ-ACK information corresponding to the HARQ process number of the transmission block provided through the CG-DFI is valid.

[0316] - If the above HARQ-ACK information is NACK, and if it is at least X symbols after the last symbol of the PUSCH transmitted in the last slot among the PUSCHs transmitted in multiple slots, the terminal determines that the HARQ-ACK information corresponding to the HARQ process number of the transmission block provided through the CG-DFI is valid.

[0317] At this time, the above X is a value set from the base station through an upper signal or a value that can be defined in advance between the base station and the terminal.

[0318] For a transport block transmitted via CG PUSCH, if the PUSCH is transmitted in multiple slots, if the terminal receives a valid ACK, the terminal may no longer repeatedly transmit the HARQ process number corresponding to the valid ACK via PUSCH. In other words, the PUSCH that repeatedly transmits the transport block of the HARQ process number corresponding to the valid ACK may be terminated.

[0319] In unlicensed bands, a terminal can perform listen before talk (LBT) (or channel access procedure) to acquire channel rights. To avoid collisions between multiple terminals during the LBT process, the terminal can determine a contention window size (CWS). The terminal determines the back-off time based on the CWS. If the terminal successfully transmits a transport block on the uplink, the CWS can be updated.

[0320] More specifically, the process of updating a CWS can be as follows. Let the CWS corresponding to priority class p be CWp.

[0321] Step 1) All priorities About Set up

[0322] Step 2) If HARQ-ACK feedback is available after the last update, proceed to step 3. Otherwise, if the terminal transmission after the procedure described in section 4.2.1.1 of 3GPP standard document TS37.213 does not include retransmissions or the last T w If transmitted within the period Perform step 5 during the reference period corresponding to the earliest UL channel occupancy since the last update. Otherwise, perform step 4.

[0323] Step 3) HARQ-ACK feedback(s) corresponding to the PUSCH(s) of the reference interval for the latest UL channel occupancy where HARQ-ACK feedback is possible are used as follows:

[0324] 3a) If at least one HARQ-ACK feedback is 'ACK' for a PUSCH(s) with transport block (TB)-based feedback or at least 10% of the HCBG (code block group)-based HARQ-ACK feedback are ACKs, then perform step 1, otherwise perform step 4.

[0325] Step 4) All priority classes for Increase to the next larger acceptable value

[0326] Step 5) All priority classes for Maintain and perform step 2

[0327] That is, the terminal can update (or adjust) the contention window size (CWS) in steps 3a) and 4) based on the valid HARQ-ACK information acquired through CG-DFI. More specifically, if at least one transport block among the valid HARQ-ACK information acquired by the terminal through CG-DFI in step 3a) is an ACK, step 1) is performed without CWS update, and if not, step 4) is performed to increase the CWS. This is to use a larger CWS value to reduce the collision between terminals, because the transmission of the transport block of the PUSCH may have failed due to a channel access collision between terminals.

[0328] [PUSCH related to 2 transport blocks]

[0329] The terminal can support up to 4 MIMO (multiple-input and multiple-output) layers for uplink physical shared channel (PUSCH) transmission and up to 4 ranks. In this case, the PUSCH transmitted by the terminal can include one transport block. When the terminal is scheduled for the PUSCH through the DCI, the terminal can receive an HARQ process number corresponding to the PUSCH from the DCI. One transport block corresponds to the HARQ process number.

[0330] If the terminal supports a value exceeding 4 for the maximum number of MIMO layers or the maximum number of ranks, the terminal may report the maximum number of MIMO layers or the maximum number of ranks supported by the terminal to the base station. This may be included in the terminal's capability report. The base station may set a value exceeding 4 for the maximum number of MIMO layers or the maximum number of ranks based on the terminal's capability report. In this case, the PUSCH transmitted by the terminal may include a maximum of 2 transport blocks.

[0331] More specifically, when PUSCH is scheduled through DCI (DG PUSCH), the HARQ process number corresponding to the PUSCH can be indicated through the DCI. If the terminal receives from the base station a value exceeding 4 as the maximum number of MIMO layers or the maximum number of ranks, the HARQ process number can correspond to a maximum of two transport blocks. Through the DCI, the terminal can determine whether one transport block or two transport blocks are scheduled. More specifically, the DCI can include an MCS (Modulation and coding scheme) field and an RV (redundancy value) field corresponding to each transport block, and the terminal can determine that the corresponding transport block is disabled when the MCS field and the RV field are specific values. In the case of a CG PUSCH in which the PUSCH is set to a higher layer or activated in a DCI format, the terminal can receive from the base station a HARQ process number corresponding to the CG PUSCH. When the terminal receives a value exceeding 4 as the maximum number of MIMO layers or the maximum number of ranks from the base station, a maximum of 1 transport block can be associated with the HARQ process number. That is, a maximum of 2 transport blocks can be associated with the HARQ process number corresponding to the DG PUSCH, but a maximum of 1 transport block can be associated with the HARQ process number corresponding to the CG PUSCH.

[0332] Hereinafter, the present disclosure relates to a case where a terminal receives a value exceeding 4 as the maximum number of MIMO layers or the maximum number of ranks from a base station. In the present disclosure, a DCI for scheduling a DG PUSCH can schedule up to two transport blocks. That is, a HARQ process number corresponding to the DCI for scheduling a DG PUSCH can correspond to a maximum of two transport blocks. In the present disclosure, a CG PUSCH can include one transport block. That is, a HARQ process number corresponding to a CG PUSCH can correspond to one transport block. In this situation, a CG-DFI design method and an analysis method of a terminal and a base station are disclosed.

[0333] Example 1: Increase the CG-DFI bit size (2 bits per HARQ process number)

[0334] In one embodiment of the present disclosure, the terminal may include HARQ-ACK information of 2 bits per HARQ process number in DCI format 0_1 ​​transmitting CG-DFI. More specifically, if the terminal is instructed to use up to 16 HARQ process numbers for uplink transmission, the terminal may receive HARQ-ACK information through 32 bits of DCI format 0_1. If the terminal is instructed to use up to 32 HARQ process numbers for uplink transmission, the terminal may receive HARQ-ACK information through 64 bits of DCI format 0_1.

[0335] For convenience, in the following description, it is assumed that the terminal is instructed to use up to 32 HARQ process numbers. This is merely an example and the present disclosure is not limited thereto.

[0336] A mapping relationship between the 64 bits of DCI format 0_1 ​​and up to two transport blocks of each HARQ process number must be determined. A method according to one embodiment of the present disclosure is described below. A combination of at least one or more of the following methods may also be used.

[0337] In the first method, the first 32 bits (MSB 32 bits) of the 64 bits may be HARQ-ACK information for the first transport block of each HARQ process number. The 32 bits (MSB 32 bits) may be mapped in ascending order of the HARQ process numbers. That is, the first bit of the 32 bits (MSB 32 bits) is HARQ-ACK information for the first transport block of HARQ process number 0, and the second bit is HARQ-ACK information for the first transport block of HARQ process number 1. In this way, the Nth bit may be mapped to HARQ-ACK information for the first transport block of HARQ process number N-1.

[0338] Among the 64 bits, the last 32 bits (LSB 32 bits) can be HARQ-ACK information for the second transport block of each HARQ process number. That is, the first bit of the 32 bits (LSB 32 bits) is HARQ-ACK information for the second transport block of HARQ process number 0, and the second bit is HARQ-ACK information for the second transport block of HARQ process number 1. In this way, the Nth bit can be mapped to HARQ-ACK information for the second transport block of HARQ process number N-1.

[0339] In a second method, the most leading 2 bits (MSB 2 bits) of the 64 bits may be HARQ-ACK information for two transport blocks of HARQ process number 0. The first bit of the 2 bits may be HARQ-ACK information for the first transport block of HARQ process number 0. The next 2 bits (the 3rd and 4th bits of the 64 bits) of the 64 bits may be HARQ-ACK information for two transport blocks of HARQ process number 1. The first bit of the 2 bits (the 3rd bit of the 64 bits) may be HARQ-ACK information for the first transport block of HARQ process number 1. The second bit of the 2 bits (the 4th bit of the 64 bits) may be HARQ-ACK information for the second transport block of HARQ process number 1. In this way, the 2*N-1th and 2*Nth bits (N=1,…,32) of the 64 bits can be mapped to HARQ-ACK information for two transport blocks of HARQ process number N-1. Here, the 2*N-1th bit can be HARQ-ACK information for the first transport block of HARQ process number N-1, and the 2*Nth bits can be HARQ-ACK information for the second transport block of HARQ process number N-1.

[0340] FIG. 11 is a diagram illustrating DCI format 0_1 ​​including CG-DFI according to the first method.

[0341] Figure 11(a) illustrates DCI format 0_1 ​​for transmitting CG-DFI when 16 HARQ process numbers (HPNs) are set for uplink transmission by a terminal. Figure 11(b) illustrates DCI format 0_1 ​​for transmitting CG-DFI when 32 HARQ process numbers are set for uplink transmission by a terminal.

[0342] Referring to FIG. 11(a) and FIG. 11(b), the first 1 bit of DCI format 0_1 ​​may be an Identifier for DCI formats field. The bit may always be fixed to 0. For example, the value of the bit may be 0.

[0343] Next, a 1-bit DFI flag field may be included. If the 1-bit DFI flag bit is 0 in the DCI format 0_1 ​​in which the CRC is scrambled with CS-RNTI, the DCI format 0_1 ​​may be interpreted as DCI for activating or releasing CG PUSCH. If the 1-bit DFI flag bit is 1 in the DCI format 0_1 ​​in which the CRC is scrambled with CS-RNTI, the DCI format 0_1 ​​may be interpreted as DCI for transmitting CG-DFI. It is assumed that the 1-bit DFI flag bit is 1 in the DCI format 0_1 ​​in which the CRC is scrambled with CS-RNTI.

[0344] According to the first method, DCI format 0_1 ​​transmitting CG-DFI includes HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd TB field may be included, where HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 ndThe length of each TB field can be equal to the HARQ process number set for uplink transmission. For example, if the HARQ process number set for uplink transmission is 16, the HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd Each TB field can be 16 bits. If the HARQ process number set for uplink transmission is 32, the HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd Each TB field can be 32 bits.

[0345] For reference, HARQ-ACK bitmap for 2 in DCI format 0_1 ​​including CG-DFI nd The inclusion of the TB field can be determined as follows: The terminal transmits the HARQ-ACK bitmap for 2 in DCI format 0_1 ​​that transmits the CG-DFI. nd The inclusion of the TB field can be determined as follows. The terminal can receive the number of MIMO layers or the maximum number of ranks to be used for PUSCH transmission from the base station. If at least one of the number of MIMO layers (maxMIMO-Layers parameter of the upper layer signal) and the number of maximum ranks (maxRank parameter of the upper layer signal) is greater than 4, the HARQ-ACK bitmap for 2 nd The inclusion of the TB field can be included in DCI format 0_1 ​​transmitting CG-DFI. Alternatively, the terminal may include the HARQ-ACK bitmap for 2 nd Whether or not the TB field is included can be set by the base station. That is, the terminal can receive a higher layer signal from the base station, and the higher layer signal is HARQ-ACK bitmap for 2 ndYou can set whether to include the TB field. HARQ-ACK bitmap for 2 nd The inclusion of the TB field can be set explicitly or implicitly.

[0346] Additionally, DCI format 0_1 ​​including CG-DFI may additionally include a 2-bit TPC command for PUSCH.

[0347] The length (size) of DCI format 0_1 ​​including CG-DFI must be identical to the length of DCI format 0_1 ​​scheduling PUSCH. This is because when the terminal performs blind decoding, if the DCIs have different lengths, blind decoding must be performed under different length assumptions. If the DCIs have the same length, blind decoding can be performed under the same length assumption. To match the length, '0's may be added to the LSB of DCI format 0_1 ​​including CG-DFI. The process of adding the '0's may be referred to as zero padding.

[0348] For example, referring to Fig. 11(a), let us assume that the length of DCI format 0_1 ​​scheduling PUSCH is 40 bits. DCI format 0_1 ​​including CG-DFI is 1 bit (Identifier for DCI formats) + 1 bit (DFI flag) + 16 bits (HARQ-ACK bitmap for 1 st TB) + 16 bits (HARQ-ACK bitmap for 2 nd TB) + 2 bits (TPC command for scheduled PUSCH) = 36 bits. Therefore, 4 bits '0000' can be added to match 40 bits (length of DCI format 0_1 ​​for scheduling PUSCH).

[0349] Example 2: Maintain CG-DFI bit size (1 bit per HARQ process number)

[0350] Referring to FIG. 11(b), the length of DCI format 0_1 ​​scheduling PUSCH may be smaller than the length of DCI format 0_1 ​​including CG-DFI. For example, the length of DCI format 0_1 ​​scheduling PUSCH is 40 bits, but the length of DCI format 0_1 ​​including CG-DFI is 1 bit (Identifier for DCI formats) + 1 bit (DFI flag) + 32 bits (HARQ-ACK bitmap for 1 st TB) + 32 bits (HARQ-ACK bitmap for 2 nd TB) + 2 bits (TPC command for scheduled PUSCH) = 68 bits. In this case, the length of DCI format 0_1 ​​including CG-DFI cannot be matched to the length of DCI format 0_1 ​​scheduling PUSCH with the zero padding used in Fig. 11(a). A method for resolving this is disclosed.

[0351] In the 0th method, the length of the DCI format 0_1 ​​for scheduling the PUSCH can be adjusted to the length of the DCI format 0_1 ​​including the CG-DFI. That is, if the length of the DCI format 0_1 ​​for scheduling the PUSCH is smaller than the length of the DCI format 0_1 ​​including the CG-DFI, the length of the DCI format 0_1 ​​for scheduling the PUSCH can be adjusted to be the same as the length of the DCI format 0_1 ​​including the CG-DFI by adding '0' to the LSB of the DCI format 0_1 ​​for scheduling the PUSCH. For example, referring to FIG. 11(b), since the length of the DCI format 0_1 ​​including the CG-DFI is 68 bits, 28 bits of '0' can be added to the LSB of the DCI format 0_1 ​​for scheduling the PUSCH, which is 40 bits. The terminal can perform blind decoding assuming that the length of DCI format 0_1 ​​is 68 bits.

[0352] According to method 0, CG-DFI uses HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd It may include a TB field. However, since the length of DCI format 0_1 ​​for scheduling PUSCH is increased, the reception performance of DCI format 0_1 ​​may deteriorate or more downlink control channel resources may be consumed.

[0353] Hereinafter, the present disclosure discloses a method for reducing the length of a DCI format 0_1 ​​including a CG-DFI. The length of the DCI format 0_1 ​​including the reduced CG-DFI may be equal to or less than the length of the DCI format 0_1 ​​for scheduling a PUSCH.

[0354] FIG. 12 and FIG. 13 are drawings showing a reduced length of CG-DFI according to one embodiment of the present disclosure.

[0355] Specifically, FIG. 12 is a diagram illustrating a CG-DFI including one bitmap for two transport blocks according to one embodiment of the present disclosure.

[0356] FIG. 13 is a diagram illustrating a CG-DFI including two bitmaps for two transport blocks according to one embodiment of the present disclosure. Here, the length of one bitmap may be less than the length of the other bitmap.

[0357] In the first method, DCI format 0_1 ​​including CG-DFI includes HARQ-ACK bitmap for 1 st TB field includes HARQ-ACK bitmap for 2 nd The TB field may not be included. In this case, the terminal is set to have a number of MIMO layers or a maximum rank greater than 4 for PUSCH transmission. That is, the terminal can transmit two transport blocks via PUSCH, but the terminal can only receive HARQ-ACK information of the first transport block via CG-DFI. For reference, although the terminal can transmit two transport blocks via PUSCH, only one transport block can be transmitted via CG-PUSCH, so whether the CG-PUSCH transmission was successful or not can be determined via the CG-DFI.

[0358] The first method can be applied when the length of DCI format 0_1 ​​for scheduling PUSCH is less than the length of DCI format 0_1 ​​including CG-DFI. The terminal sends HARQ-ACK bitmap for 2 nd The length of DCI format 0_1 ​​including CG-DFI excluding TB field can be expected to be always less than or equal to the length of DCI format 0_1 ​​scheduling PUSCH. That is, the base station can send HARQ-ACK bitmap for 2 ndThe length of DCI format 0_1 ​​scheduling PUSCH (or the length of fields included in DCI format 0_1 ​​scheduling PUSCH) must be set so that it is not less than the length of DCI format 0_1 ​​including CG-DFI excluding the TB field.

[0359] According to the first method, the terminal can obtain HARQ-ACK information of the first transmission block corresponding to every HARQ process number from the CG-DFI. Here, the first transmission block means the first transmission block when two transmission blocks are scheduled for the corresponding HARQ process number, and means the scheduled transmission block when one transmission block is scheduled for the corresponding HARQ process number.

[0360] Referring to Fig. 12, when 32 HARQ process numbers are set in the uplink, one 32-bit HARQ-ACK bitmap field may be included in the CG-DFI. The 32-bit HARQ-ACK bitmap field in Fig. 12 is HARQ-ACK bitmap for 1 st It can be a TB field. That is, the 32-bit HARQ-ACK bitmap field can contain HARQ-ACK information of the first transport block of 32 HARQ process numbers.

[0361] According to the first method, when a terminal transmits a PUSCH containing two transport blocks to a base station, the terminal cannot receive HARQ-ACK information for the second transport block through CG-DFI. For contention window size (CWS) update, the terminal may assume at least one of the following:

[0362] - In method 1-1, the terminal can assume the HARQ-ACK information of the second transport block as NACK for the purpose of CWS update. This does not actually mean that the second transport block failed to be decoded. That is, the terminal can use the value obtained from the CG-DFI for the HARQ-ACK information of the first transport block in the CWS update procedure and assume the HARQ-ACK information of the second transport block as NACK.

[0363] - In method 1-2, the terminal can assume the HARQ-ACK information of the second transport block as ACK for the purpose of CWS update. That is, the terminal can use the value obtained from the CG-DFI for the HARQ-ACK information of the first transport block in the CWS update procedure, and assume the HARQ-ACK information of the second transport block as NACK. This does not actually mean that the second transport block was successfully decoded. Therefore, according to the ACK assumption, the HARQ soft buffer corresponding to the second transport block may not be cleared, and previous data may continue to be stored.

[0364] - In method 1-3, the terminal can only use the HARQ-ACK information of the first transport block as the basis for CWS update. That is, since the terminal cannot obtain the HARQ-ACK information of the second transport block from the CG-DFI for CWS update, it can only use the HARQ-ACK information of the first transport block that can be obtained as the basis. For reference, when new transport blocks corresponding to a specific HARQ process number are scheduled through DCI that schedules PUSCH, the terminal can assume that the previous transport blocks corresponding to the specific HARQ process number are ACKs. This can be called an implicit HARQ-ACK indication. When an implicit HARQ-ACK indication is received, the terminal can use the HARQ-ACK information corresponding to the transport blocks for CWS update.

[0365] As a second method, DCI format 0_1 ​​including CG-DFI includes HARQ-ACK bitmap for 1 st TB field is included but HARQ-ACK bitmap for 2 nd Some of the TB fields may not be included. In this case, the terminal is set to have a number of MIMO layers or a maximum rank greater than 4 for PUSCH transmission. That is, the terminal can transmit two transport blocks via PUSCH, but the terminal can only receive HARQ-ACK information of the first transport block of all HARQ process numbers and HARQ-ACK information of the second transport block of some HARQ process numbers via CG-DFI. For reference, although the terminal can transmit two transport blocks via PUSCH, only one transport block can be transmitted via CG-PUSCH, so the terminal can determine whether the transmission of the CG-PUSCH is successful or not via the CG-DFI.

[0366] The second method can be applied when the length of DCI format 0_1 ​​for scheduling PUSCH is less than the length of DCI format 0_1 ​​including CG-DFI. The terminal sends HARQ-ACK bitmap for 2 nd By truncating some bits of the TB field, the length of the DCI format 0_1 ​​including the CG-DFI can always be made the same as the length of the DCI format 0_1 ​​scheduling the PUSCH. For example, referring to Fig. 11(b), the length of the DCI format 0_1 ​​scheduling the PUSCH is 40 bits, but the length of the DCI format 0_1 ​​including the CG-DFI is 1 bit (Identifier for DCI formats) + 1 bit (DFI flag) + 32 bits (HARQ-ACK bitmap for 1 stTB) + 32 bits (HARQ-ACK bitmap for 2 nd TB) + 2bits (TPC command for scheduled PUSCH) = 68bits, so HARQ-ACK bitmap for 2 nd The excess 28 bits in the TB field can be excluded, i.e., the HARQ-ACK bitmap for 2 included in the CG-DFI. nd The TB field can be 4 bits long.

[0367] The terminal has HARQ-ACK bitmap for 2 nd The LSBs of the TB field can be excluded. For example, referring to Fig. 11(b), the terminal may exclude the HARQ-ACK bitmap for 2 nd TB field is 4 bits so that HARQ-ACK bitmap for 2 nd The LSBs of the TB field can be excluded. The above 4 bits can correspond to the HARQ-ACK information of the second transmission block of HARQ process numbers 0, 1, 2, and 3.

[0368] The second method can be applied when the length of DCI format 0_1 ​​for scheduling PUSCH is less than the length of DCI format 0_1 ​​including CG-DFI. The base station sends HARQ-ACK bitmap for 2 nd By bundling some bits of the TB field, the length of DCI format 0_1 ​​containing CG-DFI can always be made identical to the length of DCI format 0_1 ​​scheduling PUSCH. The UE can set the HARQ-ACK bitmap for 2 based on the length of DCI format 0_1 ​​scheduling PUSCH. ndThe length and bundling information of the TB field can be determined. For example, referring to Fig. 11(b), the length of DCI format 0_1 ​​scheduling PUSCH is 40 bits, but the length (before bundling) of DCI format 0_1 ​​including CG-DFI is 1 bit (Identifier for DCI formats) + 1 bit (DFI flag) + 32 bits (HARQ-ACK bitmap for 1 st TB) + 32 bits (HARQ-ACK bitmap for 2 nd TB (before bundling)) + 2bits (TPC command for scheduled PUSCH) = 68bits, so HARQ-ACK bitmap for 2 nd The TB field can be 4 bits. That is, the base station can use the HARQ-ACK bitmap for 2 nd Bundling the 32 bits that should be included in TB into 4 bits and using the 4 bits as HARQ-ACK bitmap for 2 nd It can be included in the TB field. The terminal schedules the HARQ-ACK bitmap for 2 based on the length of 40 bits of DCI format 0_1 ​​that schedules the PUSCH. nd The length of the TB field can be determined as 4 bits. Additionally, the terminal can interpret the 4 bits as HARQ-ACK bits of the second TB of 32 HARQ process numbers depending on the bundling method.

[0369] HARQ-ACK bitmap for 2 nd Bundling of HARQ-ACK bits to be included in the TB field can be done as follows. For example, HARQ-ACK bitmap for 2 nd Let X be the number of HARQ-ACK bits to be included in the TB field, and HARQ-ACK bitmap for 2nd Let Y be the number of HARQ-ACK bits included in the TB field. X can be 16 or 32.

[0370] For example, the terminal and base station calculate S=ceil(X / Y) and HARQ-ACK bitmap of X bits for 2 nd HARQ-ACK bits to be included in the TB field can be sequentially grouped into S bits each. The last group (Yth group) can include XS*(Y-1) bits. The terminal and base station can assume NACK as the bit representing the group if all S bits included in the group are ACK or if at least one of the S bits is NACK. Alternatively, the terminal and base station can assume ACK as the bit representing the group if all S bits included in the group are NACK or if at least one of the S bits is ACK.

[0371] For example, the terminal and base station obtain S1=ceil(X / Y) and S2=floor(X / Y), and the HARQ-ACK bitmap for 2 X bits nd HARQ-ACK bits to be included in the TB field can be grouped into M1=mod(X,Y) bundles of S1 bits and M2=Y-mod(X,Y) bundles of S2 bits. The terminal and the base station can assume ACK as the bit representing the bundle if all bits included in the bundle are ACK, or NACK as the bit representing the bundle if at least one of the bits included in the bundle is NACK. Alternatively, the terminal and the base station can assume NACK as the bit representing the bundle if all bits included in the bundle are NACK, or ACK as the bit representing the bundle if at least one of the bits included in the bundle is ACK.

[0372] For example, the base station selects Y-1 bits out of X bits and sets the HARQ-ACK bitmap for 2 nd Include Y-1 bits of the TB field and generate one bit representing the remaining X-(Y-1) bits to create a HARQ-ACK bitmap for 2. nd It can be included in 1 bit of TB field. The terminal has Y bits HARQ-ACK bitmap for 2 nd From the Y-1 bits of the TB field, the HARQ-ACK bits of the second TB of Y-1 HARQ process numbers can be obtained, and from the remaining 1 bit, the HARQ-ACK bits of the second TB of X-(Y-1) HARQ process numbers can be obtained.

[0373] Here, the terminal and the base station can assume an ACK as a bit representing the X-(Y-1) bits if all X-(Y-1) bits are ACK, or an NACK as a bit representing the X-(Y-1) bits if at least one of the X-(Y-1) bits is NACK. Alternatively, the terminal can assume an ACK as a bit representing the X-(Y-1) bits if all X-(Y-1) bits are NACK, or an ACK as a bit representing the X-(Y-1) bits if at least one of the X-(Y-1) bits is ACK.

[0374] Referring to Fig. 13, for example, if 32 HARQ process numbers are set in the uplink, a 32-bit HARQ-ACK bitmap for 1 is set in CG-DFI. st TB field and 4-bit HARQ-ACK bitmap for 2 nd TB may be included. 32-bit HARQ-ACK bitmap for 1 in Fig. 13 stThe TB field can contain HARQ-ACK information of the first transport block of 32 HARQ process numbers. The 4-bit HARQ-ACK bitmap for 2 nd TB may contain HARQ-ACK information of the second transport block of some 4 HARQ process numbers, or may contain 4 bits bundling HARQ-ACK information of the second transport block of 32 HARQ process numbers.

[0375] As a third method, DCI format 0_1 ​​including CG-DFI includes HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd The TB field may contain spatially bundled bits. More specifically, the HARQ-ACK bitmap for 1 st The b-th bit of the TB field and the HARQ-ACK bitmap for 2 nd The b-th bit of the TB field can be spatially bundled and represented as 1 bit. Therefore, CG-DFI can include a 16-bit or 32-bit HARQ-ACK bitmap, and the b-th bit of the HARQ-ACK bitmap is a spatially bundled value of the HARQ-ACK bits of two transport blocks of HARQ process number n-1. In this case, the terminal is set to have a number of MIMO layers for PUSCH transmission or a maximum number of ranks greater than 4.

[0376] AND-based Spatial bundling means that if both HARQ-ACK bits are ACK, it indicates ACK, and if either HARQ-ACK bit is NACK, it indicates NACK. Note that if a terminal transmits only one transport block, the HARQ-ACK bit of the untransmitted transport block can be assumed to be ACK.

[0377] OR-based Spatial bundling means that if both HARQ-ACK bits are NACKs, it indicates a NACK, and if either one of the two HARQ-ACK bits is ACK, it indicates an ACK. Note that if a terminal transmits only one transport block, the HARQ-ACK bit of the untransmitted transport block can be assumed to be a NACK.

[0378] The third method is to schedule the PUSCH in DCI format 0_1 ​​with the length of HARQ-ACK bitmap for 1. st TB field and HARQ-ACK bitmap for 2 nd It can be applied when the length of DCI format 0_1 ​​including CG-DFI including TB field is less than that of HARQ-ACK bitmap for 1. In this case, the length st TB field and HARQ-ACK bitmap for 2 ndInstead of the TB field, a HARQ-ACK bitmap field with a length applied with spatial bundling may be included in the CG-DFI. The UE may expect that the length of the DCI format 0_1 ​​including the CG-DFI including the HARQ-ACK bitmap field of 16 bits to 32 bits is always less than or equal to the length of the DCI format 0_1 ​​scheduling the PUSCH. That is, the base station shall set the length of the DCI format 0_1 ​​scheduling the PUSCH (or the lengths of the fields included in the DCI format 0_1 ​​scheduling the PUSCH) to not be less than the length of the DCI format 0_1 ​​including the CG-DFI including the HARQ-ACK bitmap field.

[0379] In the third method, using AND-based spatial bundling, the terminal can obtain AND-based spatially bundled HARQ-ACK information corresponding to all HARQ process numbers from the CG-DFI. That is, when two transport blocks correspond to one HARQ process number, the terminal can know that both transport blocks of the HARQ process number are ACKs if the bit corresponding to the HARQ process number is ACK, and can know that at least one of the two transport blocks of the HARQ process is NACK if the bit corresponding to the HARQ process number is NACK. When one transport block corresponds to one HARQ process number, the terminal can know that one transport block of the HARQ process number is ACK if the bit corresponding to the HARQ process number is ACK, and can know that the transport block of the HARQ process is NACK if the bit corresponding to the HARQ process number is NACK. The terminal can determine whether the transmission of the CG PUSCH is successful. Since CG PUSCH transmits only one transport block per HARQ process number, HARQ-ACK information for the one transport block can be received. However, the terminal may have problems updating the CWS. CWS update may be determined based on whether or not at least one transport block has been successfully received. If the base station correctly receives one of the two transport blocks but fails to correctly receive the other, a NACK is generated in the case of AND-based spatial bundling. Therefore, the terminal may successfully transmit one transport block but may not use it for CWS update.

[0380] In the third method, by using OR-based spatial bundling, the terminal can obtain OR-based spatially bundled HARQ-ACK information corresponding to all HARQ process numbers from the CG-DFI. That is, when two TBs correspond to one HARQ process number, if the bit corresponding to the HARQ process number is NACK, it can be known that both transport blocks of the HARQ process number are NACK, and if the bit corresponding to one HARQ process number is ACK, it can be known that at least one of the two transport blocks of the HARQ process is ACK. When one transport block corresponds to one HARQ process number, if the bit corresponding to the HARQ process number is ACK, it can be known that one transport block of the HARQ process number is ACK, and if the bit corresponding to one HARQ process number is NACK, it can be known that one transport block of the HARQ process is NACK. The terminal can determine whether the transmission of the CG PUSCH is successful. Since CG PUSCH transmits only one transport block per HARQ process number, HARQ-ACK information for the one transport block can be received. In addition, the terminal can correctly update the CWS. Since the terminal is indicated through the OR-based spatial bundling bit that at least one of the two TBs has been successfully received, the CWS update operation can be performed based on whether at least one transport block has been successfully transmitted during the CWS update.

[0381] Referring to Fig. 12, when 32 HARQ process numbers are set in the uplink, the terminal can expect to include one 32-bit HARQ-ACK bitmap field in the CG-DFI. The 32-bit HARQ-ACK bitmap field of Fig. 12 can include 32 bits after spatial bundling is performed. It is an example that the spatial bundling is OR-based or AND-based, and other logical operations, for example, XOR operation, may also be applied.

[0382] As a fourth method, DCI format 0_1 ​​including CG-DFI includes HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd Some bits of the TB field may be included, where HARQ-ACK bitmap for 2 nd Some bits of the TB field may be HARQ process numbers other than the HARQ process number allocated to the CG-PUSCH configuration. The HARQ process number used for the CG PUSCH can be determined from the configuration of the CG PUSCH. More specifically, the UE can receive the number of HARQ processes (nrofHARQ-Processes) and Offset (harq-ProcID-Offset) used by the CG PUSCH from the CG PUSCH configuration (ConfiguredGrantConfig of the upper layer signal). The UE can determine the number of HARQ processes used by the CG PUSCH based on the number of HARQ processes and Offset. More specifically, the UE can determine that the HARQ process numbers whose indices are harq-ProcID-Offset, harq-ProcID-Offset+1,… harq-ProcID-Offset+nrofHARQ-Processes-1 are allocated to the CG PUSCH.

[0383] According to the fourth method, the terminal sends HARQ-ACK information of one transport block of the HARQ process number corresponding to the CG PUSCH from the CG-DFI to the HARQ-ACK bitmap for 1. st It can be obtained from the TB field. Since CG PUSCH transmits one transport block per HARQ process number, HARQ-ACK bitmap for 1 st The success or failure of CG PUSCH transmission can be determined based on the HARQ-ACK information obtained from the TB field. The terminal receives HARQ-ACK information of a HARQ process number other than the HARQ process number corresponding to the CG PUSCH from the CG-DFI in the HARQ-ACK bitmap for 1. st TB field and HARQ-ACK bitmap for 2 nd It can be obtained from the TB field. Therefore, the terminal can correctly perform CWS update from the HARQ-ACK information of the CG-DFI.

[0384] FIG. 14 illustrates a flowchart of the operation of a terminal according to one embodiment of the present disclosure. FIG. 14 may be for the operation of a terminal according to the first embodiment of the present disclosure. The flowchart of FIG. 14 illustrates an exemplary method that may be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0385] In step 1 (1400), the terminal may transmit to the base station the maximum number of MIMO layers or the maximum number of ranks in the terminal's uplink as a terminal capability report. Furthermore, the terminal may transmit to the base station the number of HARQ process numbers that the terminal can use in the uplink as a terminal capability report.

[0386] In the second step (1410), the terminal can receive an upper layer signal (e.g., an RRC signal) from the base station that sets the maximum number of MIMO layers or the maximum number of ranks in the uplink. The set maximum number of MIMO layers or the maximum number of ranks may be a value no greater than a value reported by the terminal. In addition, the terminal can receive from the base station the number of HARQ processes that the terminal can use in the uplink. Here, the number of HARQ processes can be set commonly for the cell, and can be set individually in each configured grant PUSCH setting. The number of HARQ processes can be one of 16 or 32.

[0387] In the third step (1420), if the number of maximum MIMO layers or the number of maximum ranks set by the terminal exceeds 4, the terminal includes HARQ-ACK bitmap for 1 in DCI format 0_1 ​​including CG-DFI. st TB field and HARQ-ACK bitmap for 2 nd We can assume that the TB field is included, where HARQ-ACK bitmap for 1 st The TB field can contain HARQ-ACK information of the first transmission block in ascending order of the HARQ process number, and HARQ-ACK bitmap for 2. nd The TB field may contain HARQ-ACK information of the second transmission block in ascending order of the HARQ process number.

[0388] In the fourth step (1430), the terminal sends the HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd Valid HARQ-ACK information can be obtained from the TB field. The terminal can use the valid HARQ-ACK information to determine whether to retransmit CG PUSCH or to update the contention window size.

[0389] FIG. 15 illustrates a flowchart of the operation of a terminal according to one embodiment of the present disclosure. FIG. 15 may be for the operation of a terminal according to a second embodiment of the present disclosure. The flowchart of FIG. 15 illustrates an exemplary method that may be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0390] In step 1 (1500), the terminal may transmit to the base station the maximum number of MIMO layers or the maximum number of ranks in the terminal's uplink as a terminal capability report. Furthermore, the terminal may transmit to the base station the number of HARQ process numbers that the terminal can use in the uplink as a terminal capability report.

[0391] In the second step (1510), the terminal can receive an upper layer signal (e.g., an RRC signal) from the base station that sets the maximum number of MIMO layers or the maximum number of ranks in the uplink. The set maximum number of MIMO layers or the maximum number of ranks may be a value no greater than a value reported by the terminal. In addition, the terminal can receive from the base station the number of HARQ processes that the terminal can use in the uplink. Here, the number of HARQ processes can be set commonly for the cell, and can be set individually in each configured grant PUSCH setting. The number of HARQ processes can be one of 16 or 32.

[0392] In the third step (1520), if the number of maximum MIMO layers or the number of maximum ranks set by the terminal exceeds 4, the terminal includes HARQ-ACK bitmap for 1 in DCI format 0_1 ​​including CG-DFI. st TB field and HARQ-ACK bitmap for 2 nd We can assume that the TB field is included, where HARQ-ACK bitmap for 1 st The TB field can contain HARQ-ACK information of the first transmission block in ascending order of the HARQ process number, and HARQ-ACK bitmap for 2. nd The TB field may contain HARQ-ACK information of the second transmission block in ascending order of the HARQ process number.

[0393] In the fourth step (1530), the terminal can receive DCI format 0_1 ​​from the base station. In this case, the terminal can blindly decode and receive DCI format 0_1 ​​based on the length of DCI format 0_1 ​​that schedules the PUSCH. The terminal can compare the length of DCI format 0_1, including the CG-DFI calculated / obtained by the terminal, with the length of DCI format 0_1 ​​that schedules the PUSCH. If the length of DCI format 0_1 ​​including CG-DFI calculated / obtained by the UE is less than the length of DCI format 0_1 ​​for scheduling PUSCH, zero padding may be performed on DCI format 0_1 ​​including CG-DFI calculated / obtained by the UE so that the length of DCI format 0_1 ​​including CG-DFI may be assumed to be the same as the length of DCI format 0_1 ​​for scheduling PUSCH. If the length of DCI format 0_1 ​​including CG-DFI calculated / obtained by the UE is greater than the length of DCI format 0_1 ​​for scheduling PUSCH, the UE may perform a method for reducing the length of CG-DFI. The method for reducing the length of CG-DFI may include at least one of the methods described above. Here, the length of the CG-DFI calculated / obtained by the terminal may be equal to the sum of the length (size) of the control information format delimiter field, the length (size) of the carrier indicator field, the length (size) of the DFI flag field, the length (size) of the HARQ-ACK bitmap field, and the length (size) of the PUSCH transmission power control field. For reference, when the PUSCH includes a maximum of two transport blocks, the HARQ-ACK bitmap field is the HARQ-ACK bitmap field for the first transport block (e.g., HARQ-ACK bitmap for 1). st TB field) and the HARQ-ACK bitmap field for the second transport block (e.g., HARQ-ACK bitmap for 2 ndTB field). The length of the CG-DFI calculated by the terminal is the length excluding zero-padding to match the length.

[0394] In the fifth step (1540), the terminal can receive a CG-DFI determined according to a zero-padding method or a length reduction method from the received DCI format 0_1, and obtain valid HARQ-ACK information corresponding to the HARQ process number. Using the valid HARQ-ACK information, the terminal can determine whether to retransmit CG PUSCH or determine whether to update the contention window size.

[0395] Example 3: Setting the HARQ process number included in CG-DFI

[0396] In one embodiment of the present disclosure, a HARQ process number to be included in a CG-DFI may be set. A terminal may expect that HARQ-ACK information corresponding to the set HARQ process number will be included in the CG-DFI.

[0397] More specifically, the terminal can receive information about the HARQ process number to be included in the CG-DFI from the base station as a bitmap through a higher layer signal. The length of the bitmap can be the same as the number of HARQ process numbers to which PUSCH transmission is assigned. If the number of HARQ process numbers to which PUSCH transmission is assigned is 16, the bitmap can be 16 bits, and if the number of HARQ process numbers to which PUSCH transmission is assigned is 32, the bitmap can be 32 bits. Each bit of the bitmap has a corresponding HARQ process number, and if a bit of the bitmap has a specific value (e.g., '1' or '0'), HARQ-ACK information of the corresponding HARQ process number can be excluded from the CG-DFI.

[0398] When the terminal receives DCI format 0_1 ​​including CG-DFI, the terminal can obtain HARQ-ACK information corresponding to HARQ process numbers other than the HARQ process numbers excluded according to the bitmap. For example, if the number of HARQ process numbers to which PUSCH transmission is allocated is 16, and HARQ-ACK information for HARQ process numbers 0, 1, 2, 3, 4, 5, 6, and 7 are excluded from the CG-DFI according to the bitmap, the CG-DFI received by the terminal includes HARQ-ACK information for HARQ process numbers 8, 9, 10, 11, 12, 13, 14, and 15. More specifically, the HARQ-ACK bitmap for 1 st The TB field contains HARQ-ACK information of the first transmission block of HARQ process number 8, 9, 10, 11, 12, 13, 14, and 15, and HARQ-ACK bitmap for 2. ndThe TB field can contain HARQ-ACK information of the second transport block of HARQ process number 8, 9, 10, 11, 12, 13, 14, and 15. Here, HARQ-ACK bitmap for 1 st TB field and HARQ-ACK bitmap for 2 nd The length of the TB field can be equal to the number of HARQ process numbers included in the CG-DFI (8 if the CG-DFI includes HARQ process numbers 8, 9, 10, 11, 12, 13, 14, and 15).

[0399] In one embodiment of the present disclosure, HARQ process numbers and transport blocks to be included in CG-DFI can be set. The terminal can expect that HARQ-ACK information corresponding to the set HARQ process number and transport block will be included in the CG-DFI.

[0400] More specifically, the terminal can receive information about the HARQ process number and transport blocks to be included in the CG-DFI from the base station as a bitmap via a higher layer signal. The length of the bitmap can be equal to the product of the number of HARQ process numbers assigned to PUSCH transmission and the number of transport blocks that the PUSCH can include. If the number of HARQ process numbers to which PUSCH transmission is assigned is 16 and the PUSCH can transmit only one transport block, the bitmap is 16 bits. If the number of HARQ process numbers to which PUSCH transmission is assigned is 16 and the PUSCH can transmit at most two transport blocks, the bitmap is 32 bits. If the number of HARQ process numbers to which PUSCH transmission is assigned is 32 and the PUSCH can transmit at most one transport block, the bitmap is 32 bits. If the number of HARQ process numbers to which PUSCH transmission is assigned is 32 and the PUSCH can transmit at most two transport blocks, the bitmap can be 64 bits. Each bit of the bitmap has a corresponding HARQ process number and transport block, and if a bit of the bitmap has a specific value (for example, '1'), HARQ-ACK information of the transport block of the corresponding HARQ process number can be excluded from the CG-DFI.

[0401] When the terminal receives DCI format 0_1 ​​including CG-DFI, it can obtain HARQ-ACK information corresponding to (HARQ process number, transport block) other than (HARQ process number, transport block) excluded according to the bitmap. For example, if the number of HARQ process numbers allocated to PUSCH transmission is 16 and PUSCH can transmit up to 2 transport blocks, if HARQ-ACK information for the second transport blocks of HARQ process numbers 0, 1, 2, 3, 4, 5, 6, and 7 is excluded from CG-DFI by the bitmap, and HARQ-ACK information for the first transport block of HARQ process numbers 0, 1, 2, and 3 is excluded from CG-DFI, the CG-DFI received by the terminal includes HARQ-ACK information for the first transport blocks of HARQ process numbers 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, and 15, and HARQ-ACK information for the second transport blocks of HARQ process numbers 8, 9, 10, 11, 12, 13, 14, and 15.

[0402] More specifically, HARQ-ACK bitmap for 1 st The TB field contains HARQ-ACK information of the first transmission block of HARQ process number 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, and 15, and HARQ-ACK bitmap for 2. nd The TB field can contain HARQ-ACK information of the second transport block of HARQ process number 8, 9, 10, 11, 12, 13, 14, and 15. Here, HARQ-ACK bitmap for 1 stThe length of the TB field is the number of HARQ process numbers of the first transport block included in the CG-DFI (12 since HARQ process numbers are 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, and 15), and the HARQ-ACK bitmap for 2 nd The length of the TB field can be the number of HARQ process numbers of the second transport block included in the CG-DFI (8 since HARQ process numbers are 8, 9, 10, 11, 12, 13, 14, and 15).

[0403] Example 4: Setting the number of transmission blocks by HARQ process number

[0404] In one embodiment of the present disclosure, a terminal may receive from a base station a configuration for the maximum number of transport blocks that can be included for each HARQ process number. The terminal may interpret CG-DFI based on the configuration.

[0405] For example, if the HARQ process number is 1,2,3,...,32, up to 2 transport blocks can be corresponding to HARQ process numbers 1,2,...,16, and 1 transport block can be corresponding to HARQ process numbers 17,18,19,...,32. The base station can set the above information to the terminal. The base station can set the maximum number of transport blocks that can be included for each HARQ process number to the terminal.

[0406] The terminal uses CG-DFI's HARQ bitmap for 1 st The TB field (the field containing the HARQ-ACK information of the first transmission block) is expected to be the same length as the number of all HARQ process numbers, i.e., HARQ bitmap for 1 st The TB field can be 32 bits long. HARQ bitmap for 2nd The TB field (the field containing the HARQ-ACK information of the second transport block) may have a length equal to the number of HARQ process numbers to which two transport blocks can correspond. That is, the HARQ bitmap for 2 nd The TB field can be 16 bits.

[0407] The method by which a base station sets the maximum number of transmission blocks that can be included in each HARQ process number for a terminal may be one or a combination of at least one of the following.

[0408] In a first method, the base station can indicate to the terminal the index of the HARQ process number that can include up to two transport blocks. For example, if the base station sets {1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16} to the terminal, the terminal can determine that HARQ process numbers 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 can include up to two transport blocks. And the terminal can determine that the remaining HARQ process numbers can include one transport block.

[0409] As a second method, the base station can indicate to the terminal the index of the HARQ process number that can contain one transport block. For example, if the base station sets {17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32} to the terminal, the terminal can determine that HARQ process numbers 17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32 can contain one transport block. In addition, the terminal can determine that the remaining HARQ process numbers can contain at most two transport blocks.

[0410] As a third method, the base station can indicate to the terminal the number of HARQ process numbers that can include at most two transport blocks. The terminal can assume that the indicated number of HARQ process numbers include at most two transport blocks, and the remaining HARQ process numbers include at most one transport block. Here, if the number of HARQ process numbers that can include at most two transport blocks is H, the terminal can determine that H HARQ process numbers with lower indices include at most two transport blocks. For example, if H=16, the terminal can determine that HARQ process numbers 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 can include at most two transport blocks. And the terminal can determine that the remaining HARQ process numbers can include at most one transport block. In another way, if the number of HARQ process numbers that can include at most 2 transport blocks is H, the terminal can determine that H HARQ process numbers with high indices can include at most 2 transport blocks. And the terminal can determine that the remaining HARQ process numbers can include 1 transport block. For example, if H=16, the terminal can determine that HARQ process numbers 17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32 can include at most 2 transport blocks. And the terminal can determine that the remaining HARQ process numbers can include 1 transport block.

[0411] In a fourth method, the base station can indicate to the terminal the number of HARQ process numbers that can include one transport block. The terminal can assume that the indicated number of HARQ process numbers includes one transport block, and that the remaining HARQ process numbers include at most two transport blocks. Here, if the number of HARQ process numbers that can include one transport block is H, the terminal can determine that H HARQ process numbers with lower indices include one transport block. And the terminal can determine that the remaining HARQ process numbers can include at most two transport blocks. For example, if H=16, the terminal can determine that HARQ process numbers 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16 can include one transport block. And the terminal can determine that the remaining HARQ process numbers can include at most two transport blocks. In another way, if the number of HARQ process numbers that can contain one transport block is H, the terminal can determine that H HARQ process numbers with high indices contain at most two transport blocks. For example, if H=16, the terminal can determine that HARQ process numbers 17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32 can contain at most one transport block. And the terminal can determine that the remaining HARQ process numbers can contain at most two transport blocks.

[0412] For reference, a terminal can report to a base station the number of HARQ process numbers that can include up to two transport blocks among HARQ process numbers as a terminal capability. For example, if a terminal capable of 32 HARQ process numbers has only 16 HARQ process numbers out of 32 that can include up to two transport blocks, the terminal can report 16 to the base station as a terminal capability. Based on the terminal capability, the base station can set a HARQ process number that can include up to two transport blocks.

[0413] For reference, if a terminal receives a DCI scheduling a PUSCH and the DCI corresponds to a HARQ process number that can include one transport block, it can be assumed that the second transport block is not scheduled. That is, if the base station schedules two transport blocks for a HARQ process number that can include one transport block, the terminal may determine this as an error case and discard the DCI. Discarding means that the terminal does not perform the operation indicated by the DCI.

[0414] Example 5: CG-DFI design including some HARQ bitmap fields

[0415] In one embodiment of the present disclosure, the CG-DFI may not include all information, but may include only some information. That is, the information included in the CG-DFI according to the above-described embodiment of the present disclosure may include all of the information mentioned in the description of the embodiment of the present disclosure, or may include some information. Here, the information to be included in the CG-DFI may be indicated in the DCI format 0_1 ​​including the CG-DFI.

[0416] More specifically, the base station and the terminal may assume as the first part of information a HARQ bitmap for 1st TB field (a field including HARQ-ACK bits of the first TB) and as the second part of information a HARQ bitmap for 2nd TB field (a field including HARQ-ACK bits of the second TB). Alternatively, the base station and the terminal may assume as the first part of information HARQ ACK information for HARQ process numbers 1,2,…,S (HARQ-ACK information for two TBs per one HARQ process number), and as the second part of information HARQ ACK information for HARQ process numbers S,S+1,…,Max_HPN (HARQ-ACK information for two TBs per one HARQ process number). Here, Max_HPN is the maximum number of HARQ process numbers set to the terminal, which may be 16 or 32. S can be half of Max_HPN.

[0417] DCI format 0_1 ​​including CG-DFI may include a field indicating an index of some information. For example, if a base station and a terminal assume first partial information and second partial information, DCI format 0_1 ​​including CG-DFI may include a 1-bit indicator. If the indicator is '0', CG-DFI may include first partial information, and if it is '1', CG-DFI may include second partial information. Based on the indicator, the terminal may determine which of the first partial information and second partial information is included. CG-DFI may include first partial information and / or second partial information.

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

[0419] Referring to FIG. 16, the terminal may include a transceiver, which refers to a terminal receiving unit (1600) and a terminal transmitting unit (1610), a memory (not shown), and a terminal processing unit (1605), or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1600, 1610), the memory, and the terminal processing unit (1605) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

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

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

[0425] Referring to FIG. 17, the base station may include a transceiver, which refers to a base station receiver (1730) and a base station transmitter (1710), a memory (not shown), and a base station processor (1705), or a base station control unit or processor). According to the communication method of the base station described above, the transceiver (1700, 1710), the memory, and the base station processor (1705) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

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

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

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

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

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

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

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

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

[0437] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

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

[0439] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. In a method performed by a terminal in a communication system, A step of receiving, through upper layer signaling, a setting for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a setting for a maximum number of MIMO (multi-input multi-output) layers associated with the PUSCH transmission; The step of performing the PUSCH transmission, wherein at least one of the number of the maximum ranks or the number of the maximum layers exceeds 4, and at least one PUSCH included in the PUSCH transmission includes two TBs (transport blocks); and A step of receiving DCI (downlink control information) through a PDCCH (physical downlink control channel), If the configuration for spatial bundling related to the HARQ-ACK (hybrid automatic repeat request) information for the second TB associated with the PUSCH transmission is not received via the higher layer signaling: The DCI includes a first HARQ-ACK bitmap for a first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for a second TB associated with the PUSCH transmission; A method wherein the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of the bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

2. In paragraph 1, The HARQ process index is mapped in ascending order from the MSB (most significant bit) to the LSB of the first HARQ-ACK bitmap, and each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of the first TB related to the corresponding HARQ-ACK process. The HARQ process index is mapped in ascending order from the MSB to the LSB of the bit corresponding to the second HARQ-ACK bitmap, and the bit corresponding to the second HARQ-ACK bitmap indicates ACK or NACK of the second TB related to the corresponding HARQ-ACK process. When the setting for the number of HARQ processes is received through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, A method wherein the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits, if the setting for the number of the above HARQ processes is not received via the above upper layer signaling.

3. In paragraph 1, If the settings for the above space bundling are received via the above upper layer signaling: The above DCI includes a third HARQ-ACK bitmap, The above third HARQ-ACK bitmap is based on the application of the spatial bundling between the bits corresponding to the first HARQ-ACK bitmap and the bits corresponding to the second HARQ-ACK bitmap for the same HARQ process. The above spatial bundling is a method corresponding to a logical XOR operation or a logical OR operation.

4. In paragraph 3, A method wherein the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

5. At the terminal of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Receive, via higher layer signaling, a configuration for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers associated with the PUSCH transmission; wherein at least one PUSCH included in the PUSCH transmission comprises two TBs (transport blocks) based on at least one of the number of the maximum ranks or the number of the maximum layers exceeding 4; and It is set to receive DCI (downlink control information) through PDCCH (physical downlink control channel). If the configuration for spatial bundling related to the HARQ-ACK (hybrid automatic repeat request) information for the second TB associated with the PUSCH transmission is not received via the higher layer signaling: The DCI includes a first HARQ-ACK bitmap for a first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for a second TB associated with the PUSCH transmission; A terminal, wherein the number of bits included in the DCI is identified to be the same as the number of bits included in the PUSCH scheduling DCI, based on (i) one or more least significant bits (LSBs) of the bits corresponding to the second HARQ-ACK bitmap being truncated or (ii) one or more zero padding bits being added after the LSB of the PUSCH scheduling DCI.

6. In paragraph 5, The HARQ process index is mapped in ascending order from the MSB (most significant bit) to the LSB of the first HARQ-ACK bitmap, and each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of the first TB related to the corresponding HARQ-ACK process. The HARQ process index is mapped in ascending order from the MSB to the LSB of the bit corresponding to the second HARQ-ACK bitmap, and the bit corresponding to the second HARQ-ACK bitmap indicates ACK or NACK of the second TB related to the corresponding HARQ-ACK process. When the setting for the number of HARQ processes is received through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, A terminal, wherein the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits, if the setting for the number of the above HARQ processes is not received via the above upper layer signaling.

7. In paragraph 5, If the settings for the above space bundling are received via the above upper layer signaling: The above DCI includes a third HARQ-ACK bitmap, The above third HARQ-ACK bitmap is based on the application of the spatial bundling between the bits corresponding to the first HARQ-ACK bitmap and the bits corresponding to the second HARQ-ACK bitmap for the same HARQ process. The above space bundling is a terminal corresponding to a logical XOR operation or a logical OR operation.

8. In paragraph 7, A terminal wherein the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

9. In a method performed by a base station in a communication system, A step of transmitting, through upper layer signaling, a setting for a maximum number of ranks related to PUSCH (physical uplink shared channel) transmission and a setting for a maximum number of MIMO (multi-input multi-output) layers related to the PUSCH transmission; A step of receiving the PUSCH transmission, wherein at least one of the number of the maximum ranks or the number of the maximum layers exceeds 4, and at least one PUSCH included in the PUSCH transmission includes two TBs (transport blocks); and A step of transmitting DCI (downlink control information) through a PDCCH (physical downlink control channel), If the configuration for spatial bundling related to the HARQ-ACK (hybrid automatic repeat request) information for the second TB associated with the above PUSCH transmission is not transmitted via the higher layer signaling: The DCI includes a first HARQ-ACK bitmap for a first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for a second TB associated with the PUSCH transmission; A method wherein the number of bits included in the DCI is identified to be equal to the number of bits included in the PUSCH scheduling DCI based on (i) truncation of one or more least significant bits (LSBs) of the bits corresponding to the second HARQ-ACK bitmap or (ii) addition of one or more zero padding bits after the LSB of the PUSCH scheduling DCI.

10. In paragraph 9, The HARQ process index is mapped in ascending order from the MSB (most significant bit) to the LSB of the first HARQ-ACK bitmap, and each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of the first TB related to the corresponding HARQ-ACK process. The HARQ process index is mapped in ascending order from the MSB to the LSB of the bit corresponding to the second HARQ-ACK bitmap, and the bit corresponding to the second HARQ-ACK bitmap indicates ACK or NACK of the second TB related to the corresponding HARQ-ACK process. When the setting for the number of HARQ processes is transmitted through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, A method wherein the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits, when the setting for the number of the above HARQ processes is not transmitted via the above upper layer signaling.

11. In paragraph 9, If the settings for the above space bundling are transmitted via the above upper layer signaling: The above DCI includes a third HARQ-ACK bitmap, The above third HARQ-ACK bitmap is based on the application of the spatial bundling between the bits corresponding to the first HARQ-ACK bitmap and the bits corresponding to the second HARQ-ACK bitmap for the same HARQ process. The above spatial bundling is a method corresponding to a logical XOR operation or a logical OR operation.

12. In paragraph 11, A method wherein the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

13. In the base station of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Transmitting, through higher layer signaling, a configuration for a maximum number of ranks associated with a physical uplink shared channel (PUSCH) transmission and a configuration for a maximum number of multi-input multi-output (MIMO) layers associated with the PUSCH transmission; At least one PUSCH included in the PUSCH transmission comprises two TBs (transport blocks) based on receiving the PUSCH transmission, wherein at least one of the number of the maximum ranks or the number of the maximum layers exceeds 4; and It is set to transmit DCI (downlink control information) through PDCCH (physical downlink control channel). If the configuration for spatial bundling related to the HARQ-ACK (hybrid automatic repeat request) information for the second TB associated with the above PUSCH transmission is not transmitted via the higher layer signaling: The DCI includes a first HARQ-ACK bitmap for a first TB associated with the PUSCH transmission and a second HARQ-ACK bitmap for a second TB associated with the PUSCH transmission; A base station, wherein the number of bits included in the DCI is identified to be the same as the number of bits included in the PUSCH scheduling DCI, based on (i) one or more least significant bits (LSBs) of the bits corresponding to the second HARQ-ACK bitmap being truncated or (ii) one or more zero padding bits being added after the LSB of the PUSCH scheduling DCI.

14. In paragraph 13, The HARQ process index is mapped in ascending order from the MSB (most significant bit) to the LSB of the first HARQ-ACK bitmap, and each bit of the first HARQ-ACK bitmap indicates an ACK (acknowledgement) or NACK (negative ACK) of the first TB related to the corresponding HARQ-ACK process. The HARQ process index is mapped in ascending order from the MSB to the LSB of the bit corresponding to the second HARQ-ACK bitmap, and the bit corresponding to the second HARQ-ACK bitmap indicates ACK or NACK of the second TB related to the corresponding HARQ-ACK process. When the setting for the number of HARQ processes is transmitted through the upper layer signaling, the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 32 bits, A base station, wherein the number of bits corresponding to the first HARQ-ACK bitmap and the number of bits corresponding to the second HARQ-ACK bitmap are each 16 bits, if the setting for the number of the above HARQ processes is not transmitted via the above upper layer signaling.

15. In paragraph 13, If the settings for the above space bundling are transmitted via the above upper layer signaling: The above DCI includes a third HARQ-ACK bitmap, The above third HARQ-ACK bitmap is based on the application of the spatial bundling between the bits corresponding to the first HARQ-ACK bitmap and the bits corresponding to the second HARQ-ACK bitmap for the same HARQ process. The above spatial bundling corresponds to a logical XOR operation or a logical OR operation, A base station, wherein the exclusion of one or more LSBs, the addition of one or more zero padding bits, or the application of the spatial bundling is applied when the number of bits corresponding to the DCI is greater than the number of bits corresponding to the PUSCH scheduling DCI.

Images