Method and device for changing dynamic reporting mode in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. More specifically, the present disclosure relates to a method in which a terminal selects one mode from among a plurality of reporting modes to transmit uplink control information, and a device capable of performing same.

Description

Method and device for dynamic reporting mode change in wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for transmitting uplink control information by a terminal by selecting one of multiple reporting modes, such as hybrid automatic repeat request acknowledgment (HARQ-ACK) reporting and channel information reporting, and a device capable of performing the same.

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

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

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

[0005] In addition, standardization of radio interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IoT) 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 (CHO) 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 a result of the development of mobile communication systems and the aforementioned developments, various services have become available, and thus, methods for effectively providing these services are required. In particular, a method for allowing terminals to efficiently select a reporting mode and transmit control information is required.

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

[0010] The present invention, in order to solve the above problems, provides a method for processing a control signal in a wireless communication system, the method including: receiving a first control signal transmitted from a base station; processing the received first control signal; generating a second signal based on the processing; and transmitting the generated second control signal to the base station.

[0011] The disclosed embodiments can provide devices and methods for effectively providing services in a mobile communication system. The effects achieved by the present disclosure are not limited to those mentioned above, and other effects not mentioned will be readily apparent to those skilled in the art to which the present disclosure pertains, based on the description below.

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

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

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

[0015] 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 an embodiment of the present disclosure.

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

[0017] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and / or receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

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

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

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

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

[0022] FIG. 11 is a diagram illustrating a physical downlink control channel (PUCCH) / physical uplink shared channel (PUSCH) transmission including PDSCH reception and HARQ-ACK (hybrid automatic repeat request acknowledgement) information of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 12 is a diagram illustrating transmission of scheduling assistant information instead of HARQ-ACK information when HARQ-ACK information is All ACK in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 13 is a diagram illustrating transmission of scheduling assistant information instead of HARQ-ACK information when HARQ-ACK information is All ACK or All NACK in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 14 is a diagram illustrating transmission of HARQ-ACK information or 1-bit bundled HARQ-ACK bit and scheduling assistant information in a wireless communication system according to one embodiment of the present disclosure.

[0026] FIG. 15 is a diagram illustrating transmission of HARQ-ACK information or N-bit bundled HARQ-ACK bits and scheduling assistant information in a wireless communication system according to one embodiment of the present disclosure.

[0027] FIG. 16 is a diagram illustrating a terminal including MCS (modulation and coding scheme) information as scheduling assistant information in a wireless communication system according to one embodiment of the present disclosure.

[0028] FIG. 17 is a diagram illustrating transmission of CSI (channel state information) report triggering request information by a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 18 is a diagram illustrating a wireless communication system according to an embodiment of the present disclosure in which UCIs of different lengths are transmitted on a PUCCH according to a reporting mode.

[0030] FIG. 19 is a diagram illustrating transmission on PUCCH according to a reporting mode in a wireless communication system according to an embodiment of the present disclosure.

[0031] FIG. 20 is a diagram illustrating a method for transmitting a PUCCH according to HARQ-ACK information in a wireless communication system according to an embodiment of the present disclosure.

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

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

[0034] To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are also called beyond 4G networks or post-LTE systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0035] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technologies, wireless and wired communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0036] Accordingly, various attempts are being made to apply 5G communication systems (also known as New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN), a big data processing technology described above, can also be considered an example of the convergence of 3eG and IoT technologies.

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

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

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

[0040] 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 these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0041] Hereinafter, the base station is an entity that performs resource allocation of a 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 LTE (Long-Term Evolution), LTE-A (LTE-Advanced) or a 5G system may be described below as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, this may include the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications within 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.

[0042] 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).

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

[0044] 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'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. Also, in an embodiment, the '~part' may include one or more processors.

[0045] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

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

[0047] As a representative example of a 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-described multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources to be used to transmit data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0048] As a future communication system beyond LTE, for example, 5G communication systems must be able to freely reflect the diverse needs of users and service providers, and thus 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).

[0049] 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 provide not only the peak data rate but also the increased user-perceived data rate for terminals. To meet these requirements, various transmission and / or 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.

[0050] 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, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, due to the nature of the service. This may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, very long battery lifespans, such as 10 to 15 years, may be required.

[0051] 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 less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0052] 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 / or reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0053] [NR time-frequency resources]

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

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

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

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

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

[0059]

[0060] [Bandwidth Part (BWP)]

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

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

[0063] Referring to FIG. 3, an example is shown in which a terminal bandwidth (UE bandwidth) (300) is set to two bandwidth portions, for example, 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 terminal, and can set information such as Table 2 below for each bandwidth portion.

[0064]

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

[0066] According to one embodiment, 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, during the initial access phase, 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. 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.

[0067] According to one embodiment of the present disclosure, the setting of the bandwidth portion supported by the 5G communication system can be used for various purposes.

[0068] In one embodiment, 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 / or receive data at a specific frequency location within the system bandwidth.

[0069] Additionally, according to one embodiment, a base station may configure multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and / or reception using both a 15 kHz subcarrier spacing and a 30 kHz subcarrier spacing for a given terminal, the base station may configure two bandwidth portions with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth portions may be frequency division multiplexed, and when data is to be transmitted and / or received using a specific subcarrier spacing, the bandwidth portion configured for the corresponding subcarrier spacing may be activated.

[0070] Furthermore, according to one embodiment, for the purpose of reducing power consumption of the terminal, the base station can set bandwidth portions with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and constantly transmits and / or 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 can be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station can set 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 / or receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0071] According to one embodiment of the present disclosure, in a method for setting a bandwidth part, terminals prior to RRC connection can receive setting information for an initial bandwidth part through a Master Information Block (MIB) during an initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted from the MIB of a physical broadcast channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive a physical downlink shared channel (PDSCH) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0072] [Bandwidth Part (BWP) Change]

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

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

[0075]

[0076] The bandwidth-partial change delay time requirement can support either 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.

[0077] According to the requirement on the bandwidth part change delay time described above, when the terminal receives the DCI including the bandwidth part change indicator in slot n, the terminal can complete the change to the new bandwidth part indicated by the bandwidth part change indicator at a time no later than slot n + T_BWP, and can perform transmission and / or reception for the data channel scheduled by the DCI including the bandwidth part change indicator in the changed new bandwidth part. When the base station wants to schedule a data channel in the new bandwidth part, the base station can determine the time domain resource allocation for the data channel by considering the bandwidth part change delay time (T_BWP) of the terminal. For example, when the base station schedules a data channel in the new bandwidth part, the data channel can be scheduled after the bandwidth part change delay time in the method of determining the time domain resource allocation for the data channel. Therefore, the terminal may not expect the DCI indicating the bandwidth part change to indicate a slot offset (e.g., K0 or K2) value that is smaller than the bandwidth part change delay time (T_BWP).

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

[0079] [SS / PBCH block]

[0080] Next, we can explain the SS (Synchronization Signal) / PBCH block in the 5G communication system.

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

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

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

[0084] - PBCH: This channel can provide essential system information required for transmission and / or reception of data and control channels of a terminal. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, scheduling control information for a separate data channel that transmits system information, and more.

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

[0086] 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 (for example, it may correspond to a control region with a control region index of 0) through the obtained MIB. 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 about 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 the selected block.

[0087] [PDCCH: DCI related]

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

[0089] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) can be 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 pre-determined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0090] DCI can be transmitted over 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. For example, the RNTI can be transmitted as part of the CRC calculation process rather than being transmitted explicitly. Upon receiving a DCI message transmitted on the PDCCH, the UE verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message has been transmitted to the UE.

[0091] 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).

[0092] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with the C-RNTI. DCI format 0_0 with the CRC scrambled with the C-RNTI can include, for example, the information in Table 4. Of course, the present invention is not limited to the following examples.

[0093]

[0094] 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. Of course, the present invention is not limited to the following examples.

[0095]

[0096]

[0097] 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. Of course, the present invention is not limited to the following examples.

[0098]

[0099] 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. Of course, the present invention is not limited to the following examples.

[0100]

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

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

[0103] FIG. 4 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) setting of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. FIG. 4 may illustrate 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 within 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 illustrated example of 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.

[0104] In the aforementioned 5G communication system, the control region can be set by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Setting the control region for the terminal may mean 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, the information may include the information in Table 8 below. Of course, the present invention may not be limited to the examples below.

[0105]

[0106] 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. Of course, it may not be limited to the following examples.

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

[0108] Referring to FIG. 5, an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in a 5G communication system is provided. According to FIG. 5, the basic unit of time and frequency resources constituting 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, 1 PRB (Physical Resource Block, 502) on the frequency axis, for example, 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0109] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in a 5G system is called a CCE (Control Channel Element, 504), 1 CCE (504) may be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) may be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) may be composed of 72 REs. When a downlink control region is established, the region may be composed of multiple CCEs (504), and a specific downlink control channel may 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.

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

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

[0112] In a 5G communication system, parameters for a search space for a PDCCH can be set from a base station to a terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can set 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 parameters for a search space for a PDCCH can include the information in Table 9. Of course, the present invention is not limited to the following examples.

[0113]

[0114]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0137] The DCI formats described above may follow the definitions in Table 10 below. Of course, they are not limited to the examples below.

[0138]

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

[0140] [Mathematical Formula 1]

[0141]

[0142] - Integration level

[0143] - Carrier Index

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

[0145] - Slot Index

[0146] - Number of PDCCH candidates for aggregation level L

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

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

[0149] -

[0150] - : Terminal identifier

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

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

[0153] In a 5G communication system, since multiple search space sets can be set 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 set with an X-slot period and search space set #2 is set with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.

[0154] [PDCCH: BD / CCE limit]

[0155] When multiple search space sets are set for a terminal, the following conditions may be considered when determining the search space set that the terminal should monitor. The following examples are not limiting.

[0156] If the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, is set to r15monitoringcapability, the terminal can define the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (for example, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot. If the value of monitoringCapabilityConfig-r16 is set to r16monitoringcapability, the terminal can define the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (for example, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per Span.

[0157] [Condition 1: Limit the maximum number of PDCCH candidates]

[0158] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidates that the terminal can monitor is M. μ If defined on a slot basis in a cell with a subcarrier spacing of 15·2^μ kHz, it can follow Table 11 below, and if defined on a span basis, it can follow Table 12 below.

[0159]

[0160]

[0161] [Condition 2: Maximum CCE limit]

[0162] As above, according to the setting value of the upper layer signaling, the maximum number of CCEs that constitute the entire search space (for example, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is C μIf defined on a slot basis in a cell with a subcarrier spacing of 15·2^μ kHz, it can follow Table 13 below, and if defined on a span basis, it can follow Table 14 below.

[0163]

[0164]

[0165] For convenience of explanation, let us define a situation where both conditions 1 and 2 are satisfied at a certain point in time as “condition A.” Therefore, not satisfying condition A may mean not satisfying at least one of conditions 1 and 2.

[0166] [PDCCH: Overbooking]

[0167] Depending on the configuration of the search space sets of the base station, there may be cases where condition A is not satisfied at a certain point in time. If condition A is not satisfied at a certain point in time, the terminal can select and monitor only some of the search space sets configured to satisfy condition A at that point in time, and the base station can transmit a PDCCH to the selected search space set.

[0168] The following method can be followed to select a partial search space from the entire set of search spaces.

[0169] If condition A for PDCCH is not satisfied at a specific point in time (slot), the terminal (or base station) may preferentially select a search space set whose search space type is set to a common search space from among the search space sets existing at that point in time over a search space set whose search space type is set to a terminal-specific search space.

[0170] If all search space sets set as common search spaces are selected (e.g., if condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) can select search space sets set as terminal-specific search spaces. At this time, if there are multiple search space sets set as terminal-specific search spaces, a search space set with a lower search space set index may have a higher priority. The terminal (or base station) can select terminal-specific search space sets within the range where condition A is satisfied, taking the priority into consideration.

[0171] [Rate matching / Puncturing related]

[0172] Below, the rate matching operation and puncturing operation are described in detail.

[0173] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and / or reception operations of channel A considering resource C in the area where resources A and B overlap. The specific operations may follow the contents below.

[0174] Rate Matching Operation

[0175] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that want to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0176] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A except {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0177] Puncture action

[0178] If a base station wants to transmit symbol sequence A to a terminal, and there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0179] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A was transmitted only in the remaining area of ​​resource area A excluding resource C, even if symbol sequence A is mapped to the entire resource A. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0180] Below, we describe a method for configuring rate-matching resources for the purpose of rate-matching in 5G communication systems. Rate-matching refers to adjusting the size of a signal based on the amount of resources available for transmission. For example, rate-matching a data channel may mean adjusting the size of data accordingly, without mapping the data channel to a specific time and frequency resource region.

[0181] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and / or receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

[0182] Referring to FIG. 6, a downlink data channel (PDSCH, 601) and a rate matching resource (602) are illustrated. 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 “first bitmap,” the bitmap corresponding to the time-domain resource allocation information (603) is named “second bitmap,” and the bitmap corresponding to the period information (605) is named “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.

[0183] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the “rate-matching indicator” in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, the base station can indicate “1” when rate matching is required, and “0” when rate matching is not required.

[0184] In 5G systems, granularity at the "RB symbol level" and "RE level" is supported by setting the aforementioned rate matching resources on terminals. More specifically, the following configuration method can be followed.

[0185] RB symbol level

[0186] A terminal can receive up to four RateMatchPatterns for each bandwidth segment via upper-layer signaling, and a single RateMatchPattern can include the following content. Of course, the examples below are not limited to these.

[0187] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may be additionally set.

[0188] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0189] RE level

[0190] The terminal can receive the following information via upper-layer signaling. Of course, the terminal is not limited to the examples below.

[0191] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0192] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0193] [Regarding LTE CRS rate match]

[0194] Next, the rate match process for the LTE CRS described above will be described in detail. In order to coexist between LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR provides a function to set a pattern of LTE's CRS (Cell Specific Reference Signal) to NR terminals. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter in the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the parameters can include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0195] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides a function that allows one CRS pattern to be set per serving cell. In Rel-16 NR, the function that allows one CRS pattern to be set per serving cell has been expanded to allow multiple CRS patterns to be set per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can have one CRS pattern set per LTE carrier, and a multi-TRP configured terminal can have two CRS patterns set per LTE carrier. For example, a single-TRP configured terminal can have up to three CRS patterns set per serving cell through the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can have CRS set per TRP. For example, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are set as above, whether both the CRS patterns of TRP1 and TRP2 or only the CRS pattern for one TRP is applied to a specific PDSCH (Physical Downlink Shared Channel) is determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, and in other cases, the CRS patterns of both TRPs can be applied.

[0196] Table 15 shows a ServingCellConfig IE that includes the above CRS pattern, and Table 16 shows a RateMatchPatternLTE-CRS IE that includes at least one parameter for the CRS pattern.

[0197]

[0198]

[0199]

[0200]

[0201] [PDSCH: Frequency Resource Allocation Related]

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

[0203] Referring to FIG. 7, it is a diagram illustrating three frequency axis resource allocation methods, type 0 (700), type 1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.

[0204] Referring to Fig. 7, if a terminal is set to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH to the terminal may include a bitmap consisting of NRBG bits. The conditions for this will be explained later. At this time, NRBG means the number of RBGs (resource block groups) determined as shown in [Table 17] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data may be transmitted to an RBG indicated as 1 by the bitmap.

[0205]

[0206] If the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that allocate PDSCH to the terminal It may include frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. The base station may set the starting VRB (720) and the length (725) of frequency axis resources sequentially allocated therefrom as described above.

[0207] If a terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal may include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring resource type 0 and the payload (720, 725) for configuring resource type 1. Conditions for this will be described later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the added bit has a value of '0', it may indicate that resource type 0 is used, and if it has a value of '1', it may indicate that resource type 1 is used.

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

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

[0210] 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 of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of 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 18] or [Table 19] below may be transmitted from the base station to the terminal. Of course, it may not be limited to the above example.

[0211]

[0212]

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

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

[0215] 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 (800) and length (805) within a slot dynamically indicated through DCI.

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

[0217] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel is the same (900,μ 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 (905,μ 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.

[0218] [PUSCH: Transmission Method Related]

[0219] 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 can be provided in DCI format 0_0 or 0_1.

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

[0221]

[0222]

[0223] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission may be the same as the antenna port for SRS transmission. PUSCH transmission may follow a codebook-based or non-codebook-based transmission method, depending on whether the value of txConfig in the pusch-Config in [Table 21], which is a higher layer signaling, is 'codebook' or 'nonCodebook'.

[0224] 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 can perform 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. In this case, PUSCH transmission can be based on a single antenna port. The UE may 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 has not configured txConfig in pusch-Config of [Table 21], the UE may not expect to be scheduled with DCI format 0_1.

[0225]

[0226]

[0227] Next, we can explain 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 can determine 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).

[0228] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher layer signaling. The UE can be configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two SRS resources. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI provided through the DCI. 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 layer signaling. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI can be used to indicate the precoder to be applied in the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI can be used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0229] 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 higher layer signaling SRS-Config. In codebook-based PUSCH transmission, the UE can determine the codebook subset based on the TPMI and codebookSubset in the higher layer signaling pusch-Config. The codebookSubset in the higher 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 higher layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE may not expect the value of codebookSubset, which is a higher layer signaling, to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in SRS-ResourceSet, which is a higher layer signaling, points to two SRS antenna ports, the UE may not expect the value of codebookSubset, which is a higher layer signaling, to be set to 'partialAndNonCoherent'.

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

[0231] 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 layer signaling, and the base station can select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using transmission beam information of the selected 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 can be included in the DCI. Additionally, the base station can include in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal can perform PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the SRS resource indicated by the SRI, using the SRS resource indicated by the SRI.

[0232] Next, we can explain 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 layer signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0233] For an SRS resource set in which the usage value in the upper layer 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 may not expect that information for the precoder for SRS transmission is updated.

[0234] If the value of resourceType in the upper layer 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 may 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 may be 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 may not be set to QCL-TypeD.

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

[0236] 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 configured through the srs-ResourceIndicator, which is a higher layer 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 can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI provided through the DCI. 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 can be determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE transmits simultaneously can occupy the same RB. A terminal can configure one SRS port for each SRS resource. Only one SRS resource set with the usage value set to "nonCodebook" in the upper-layer signaling SRS-ResourceSet can be configured, and up to four SRS resources for non-codebook-based PUSCH transmission can be configured.

[0237] A base station can transmit one NZP-CSI-RS associated with an SRS resource set to a terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on a result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set in which usage is set to 'nonCodebook' to the base station, the terminal can apply the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. In this case, in non-codebook based PUSCH transmission, an SRI can indicate an index that can express a combination of one or more SRS resources, and the SRI can be included in a 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 can transmit the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0238] [PUSCH: Preparation time]

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

[0240] [Equation 2]

[0241]

[0242] The aforementioned T in mathematical formula 2 proc,2 In , each variable can have the following meanings:

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

[0244]

[0245]

[0246] - κ: 64

[0247] - μ: μ DL or μ UL Medium, T proc,2 This larger value can be followed by μ DLrefers to the numerology of the downlink in which the PDCCH containing the DCI scheduling the PUSCH is transmitted, and μ UL It can mean the numerology of the uplink in which PUSCH is transmitted.

[0248] - T c : 1 / (Δf max *N f ), Δf max = 480*10 3 Hz, N f =has 4096.

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

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

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

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

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

[0254] [CA / DC related]

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

[0256] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system may include NR SDAP (Service Data Adaptation Protocol 1025, 1070), NR PDCP (Packet Data Convergence Protocol 1030, 1065), NR RLC (Radio Link Control 1035, 1060), and NR MAC (Medium Access Control 1040, 1055) in the terminal and NR base station, respectively. Of course, it is not limited to the example, and more or fewer layers may be included.

[0257] The main functions of NR SDAP (1025, 1070) may include some of the following functions, but are not limited to the examples below.

[0258] - Transfer of user plane data

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

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

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

[0262] For the above SDAP layer device, the terminal can be configured by an RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the base station can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink using 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. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used for at least one of data processing priority or scheduling information to support a smooth service.

[0263] The main functions of NR PDCP (1030, 1065) may include some of the following functions, but are not limited to the examples below.

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

[0265] - User data transfer function

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

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

[0268] - PDCP PDU reordering for reception

[0269] - Duplicate detection of lower layer SDUs

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

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

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

[0273] 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 transmitting a status report on lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0274] The main functions of NR RLC (1035, 1060) may include some of the following functions, but are not limited to the examples below.

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

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

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

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

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

[0280] - Re-segmentation of RLC data PDUs

[0281] - Reordering of RLC data PDUs

[0282] - Duplicate detection function

[0283] - Protocol error detection

[0284] - RLC SDU discard function

[0285] - RLC re-establishment function

[0286] In the above, the in-sequence delivery function of the NR RLC device may refer to a 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 multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on an RLC SN (sequence number) or a PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting a 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 (e.g., regardless of the order of the sequence number, or in the order of arrival) 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 concatenation function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

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

[0288] NR MAC (1040, 1055) 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. Of course, it is not limited to the examples below.

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

[0290] - Multiplexing / demultiplexing of MAC SDUs

[0291] - Scheduling information reporting function

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

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

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

[0295] - MBMS service identification function

[0296] - Transport format selection function

[0297] - Padding function

[0298] The NR PHY layer (1045, 1050) 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. Of course, the present invention is not limited to the above examples.

[0299] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, if a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer, such as 1000. On the other hand, if the base station transmits data to a terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal may use a protocol structure having a single structure up to RLC but multiplexing the physical layer (PHY layer) through the MAC layer, such as 1010. As another example, if a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, such as 1020.

[0300] 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 layer signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

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

[0302] In the following disclosure, the above examples are described through multiple embodiments, but they are not independent, and it may be possible for one or more embodiments to be applied simultaneously or in combination.

[0303] In the following description of the present disclosure, the term "upper layer signaling" may refer to signaling corresponding to at least one or a combination of one or more of the following signaling. Of course, the present disclosure is not limited to the examples below.

[0304] - MIB (Master Information Block)

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

[0306] - RRC (Radio Resource Control)

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

[0308] Additionally, L1 signaling may be signaling corresponding to at least one or a combination of one or more of the following physical layer channels or signaling methods. Of course, it is not limited to the examples below.

[0309] - PDCCH (Physical Downlink Control Channel)

[0310] - DCI (Downlink Control Information)

[0311] - UE-specific DCI

[0312] - Group common DCI

[0313] - Common DCI

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

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

[0316] - PUCCH (Physical Uplink Control Channel)

[0317] - UCI (Uplink Control Information)

[0318] In the present disclosure, determining the priority between A and B can 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.

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

[0320] FIG. 11 is a diagram illustrating PDSCH reception and PUCCH / PUSCH transmission including HARQ-ACK information by a terminal in a wireless communication system according to one embodiment of the present disclosure. Here, the K1 value set for the terminal may be {6,7,8,9}.

[0321] Referring to FIG. 11, the terminal can receive PDSCH in each of slots 0, 1, 2, and 3, and HARQ-ACK information, which is a result of receiving the PDSCH, can be transmitted to PUCCH or PUSCH in slot 9. Here, the K1 value corresponding to the PDSCH scheduled in slot 0 may be 9, the K1 value corresponding to the PDSCH scheduled in slot 1 may be 8, the K1 value corresponding to the PDSCH scheduled in slot 2 may be 7, and the K1 value corresponding to the PDSCH scheduled in slot 3 may be 6. The terminal can multiplex HARQ-ACK bits of four PDSCHs on the PUCCH or PUSCH in slot 9 and transmit them to the base station.

[0322] Here, multiplexing of HARQ-ACK bits can refer to the process of converting multiple HARQ-ACK bits into a single bit stream. In the present disclosure, the multiplexed HARQ-ACK bits can be referred to as a HARQ-ACK codebook. Unless otherwise specified, the present disclosure can be described based on a Type-2 (dynamic) HARQ-ACK codebook of an NR system. Embodiments of the present disclosure can also be applied to a Type-1 (semi-static) HARQ-ACK codebook or a Type-3 (one-shot) HARQ-ACK codebook of an NR system.

[0323] In this disclosure, for convenience, it can be assumed that the HARQ-ACK bits corresponding to one PDSCH are 1 bit. If the PDSCH includes multiple transport blocks (TBs), the HARQ-ACK bits corresponding to one PDSCH can be 2 bits. If the PDSCH includes code block groups (CBGs), one PDSCH can be N CBG can correspond to bits. Here, N CBG may be the maximum number of CBGs that one PDSCH can contain.

[0324] The terminal can transmit 4-bit HARQ-ACK information in slot 9. For example, if the PDSCHs received in slots 0, 1, and 3 are successfully received, and the PDSCH received in slot 2 fails to be received, the terminal can determine [ACK, ACK, NACK, ACK] = [AANA] with the 4-bit HARQ-ACK information. In the following description and drawings, ACK may be represented as A, and NACK may be represented as N. In the following embodiments of the present disclosure, the determination of the terminal or base station may mean various terms such as judgment, determine, and identify.

[0325] Based on the HARQ-ACK information, the base station can determine whether the PDSCH has been successfully received. If the base station receives [AANA], it can determine that the third PDSCH (the PDSCH received by the terminal in slot 2) has not been successfully received. Therefore, the base station can retransmit the third PDSCH.

[0326] Based on the HARQ-ACK information, the base station can determine the scheduling method for the PDSCH to be transmitted in the future. For example, when the base station receives [AANA], the base station can schedule the PDSCH so that NACK does not occur in the future based on the scheduling information of the PDSCH where the NACK occurred or the scheduling information of the PDSCH where the ACK occurred. This can be called link adaptation. For example, when a specific MCS (modulation and coding scheme) is used for the PDSCH where the NACK occurred, the PDSCH can be transmitted using an MCS lower than the MCS. A lower MCS may be an MCS with low spectral efficiency. How low an MCS the base station selects can be implemented by the base station.

[0327] The terminal can receive PDSCH in each of slots 5, 6, 7, and 8. HARQ-ACK information of the four PDSCHs can be transmitted in the PUCCH or PUSCH of slot 14. If all four PDSCHs are correctly received, the HARQ-ACK information transmitted in slot 14 may be [AAAA]. When the base station receives the HARQ-ACK, the base station can determine that the terminal has correctly received all four PDSCHs. Therefore, there may be no need to retransmit the four PDSCHs. The base station may need to decide which MCS to use when transmitting the PDSCH in the future. Since all PDSCHs are correctly received, the base station can use a higher MCS. A higher MCS may be an MCS with high spectral efficiency. How high an MCS the base station selects may be determined by the implementation of the base station.

[0328] The terminal can receive PDSCH in each of slots 20, 21, 22, and 23. HARQ-ACK information of the four PDSCHs can be transmitted in the PUCCH or PUSCH of slot 29. If all four PDSCHs are not received correctly, the HARQ-ACK information transmitted in slot 29 can be [NNNN]. When the base station receives the HARQ-ACK, the base station can determine that the terminal did not correctly receive all four PDSCHs. Therefore, the base station needs to retransmit the four PDSCHs. In this case, the base station can use a lower MCS. How high an MCS the base station selects can be implemented by the base station.

[0329] In the example described above, the MCS selected by the base station for future PDSCH transmissions may be based on the HARQ-ACK information received by the base station. However, the MCS required by the terminal to properly receive the PDSCH may differ from the MCS selected by the base station. Therefore, it may be preferable for the terminal to report its desired MCS to the base station, rather than having the base station select an MCS.

[0330] In the example described above, the terminal transmits [NNNN] (HARQ-ACK information with all NACKs) as HARQ-ACK information in slot 29, but it may be more helpful for the terminal to report its desired MCS to the base station rather than the HARQ-ACK information. For example, the terminal can determine whether it is more helpful to report HARQ-ACK information or to report its desired MCS information based on the HARQ-ACK information.

[0331] In the above example, the terminal transmitted [AAAA] (HARQ-ACK information that is all ACKs) as HARQ-ACK information in slot 14, but it may be more helpful for the terminal to report the MCS information that the terminal wants rather than the 4-bit HARQ-ACK information (e.g., All ACK information). Therefore, the terminal can determine whether it is more helpful to report the HARQ-ACK information or the MCS information that the terminal wants.

[0332] In the present disclosure, a terminal can determine whether to report HARQ-ACK information to a base station based on the result of the HARQ-ACK information or to report MCS information instead of HARQ-ACK information. A specific method is described in the first embodiment.

[0333] Although only MCS information is described in the above example, MCS information can be a parameter used when scheduling PDSCH. In the following description, it can be expanded to include other parameters in addition to MCS information. In the following description, information that a UE can report instead of HARQ-ACK information can be called scheduling assistant information (SAI). The SAI can include various parameters. This is described in the second embodiment.

[0334] <First embodiment: Selecting HARQ-ACK transmission mode and scheduling assistant information transmission mode based on HARQ-ACK results>

[0335] Example 1-1: When all HARQ-ACKs are All NACKs, scheduling assistant information is transmitted.

[0336] FIG. 12 is a diagram illustrating transmission of scheduling assistant information instead of HARQ-ACK information when HARQ-ACK information is All ACK in a wireless communication system according to one embodiment of the present disclosure.

[0337] Referring to FIG. 12, two reporting modes may be set for a terminal. The first reporting mode may be a general HARQ-ACK information transmission mode. In the general HARQ-ACK information transmission mode, the terminal may transmit multiplexed HARQ-ACK bits (or HARQ-ACK codebook) to the base station. The second reporting mode may be a mode for transmitting scheduling assistant information to the base station. For example, in the first reporting mode, uplink control information (UCI) may be HARQ-ACK information, and in the second reporting mode, UCI may be scheduling assistant information.

[0338] In one embodiment, the terminal can determine the slot in which each HARQ-ACK information transmission is instructed. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 0, 1, 2, and 3, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 9 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 5, 6, 7, and 8, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 14 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 20, 21, 22, and 23, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the above four PDSCHs can be transmitted to PUCCH or PUSCH in slot 29.

[0339] In other words, the terminal can determine the slot and PUCCH (or PUSCH) on which HARQ-ACK information should be transmitted based on the scheduled PDSCH or the K1 value corresponding to the PDSCH. In addition, the HARQ-ACK bits corresponding to the PUCCH or PUSCH of one slot can be multiple bits, and the PUCCH resources and PUSCH resources on which the HARQ-ACK is to be transmitted can be determined based on the number of bits.

[0340] According to the above-described operation, the terminal can determine the PUCCH resource or PUSCH resource to be transmitted by the terminal, and can determine the number of HARQ-ACK bits (N bits) included in the PUCCH resource or PUSCH resource. When the terminal transmits uplink control information using the PUCCH resource or PUSCH resource regardless of the reporting mode, the length of the uplink control information corresponding to the PUCCH resource or PUSCH resource may be a value determined based on the number of HARQ-ACK bits (N bits).

[0341] In one embodiment, the terminal may include information indicating a reporting mode determined by the terminal in the PUCCH or PUSCH. The information indicating the reporting mode determined by the terminal may be referred to as header information. If the header information has a first value ('0'), it may indicate a first reporting mode, and if it has a second value ('1'), it may indicate a second reporting mode. The header information may be attached to the UCI transmitted by the terminal on the PUCCH or PUSCH or transmitted in another manner. A specific method may be described in Embodiment 3. Of course, the value of the header information is not limited to the above example.

[0342] In one embodiment, if there is at least one ACK in HARQ-ACK information to be transmitted by the terminal to the PUCCH or PUSCH, the terminal may transmit the PUCCH or PUSCH in the first reporting mode. More specifically, if at least one of the PDSCHs corresponding to the PUCCH or PUSCH is correctly received, the terminal may transmit HARQ-ACK information to the PUCCH or PUSCH. At this time, the header information transmitted by the terminal may be a first value ('0'). The base station may determine that the first reporting mode includes HARQ-ACK information in the received PUCCH or PUSCH through the first value ('0') which is the header information. In addition, the base station may not perform retransmission of the PDSCH corresponding to at least one ACK through the received HARQ-ACK information. Of course, the value of the header information is not limited to the above example.

[0343] In one embodiment, if all HARQ-ACK information to be transmitted by the terminal through the PUCCH or PUSCH is NACK, the terminal may transmit the PUCCH or PUSCH in the second reporting mode. More specifically, if all PDSCHs corresponding to the PUCCH or PUSCH are not correctly received, the terminal may transmit scheduling assistant information through the PUCCH or PUSCH instead of HARQ-ACK information. At this time, the header information transmitted by the terminal may be a second value ('1'). The base station may determine that the received PUCCH or PUSCH includes scheduling assistant information and is in the second reporting mode through the second value ('1') which is the header information. In addition, the base station may determine that all PDSCHs associated with the PUCCH or PUSCH are NACK. Therefore, the base station may retransmit the PDSCHs and, at this time, may utilize scheduling assistant information. Of course, the value of the header information is not limited to the above example.

[0344] In one embodiment, a case where a terminal indicates a first value ('0') as header information and all corresponding HARQ-ACK information is NACK may be defined as an error case. For example, the terminal may not be able to transmit [0, NNNN].

[0345] In one embodiment, a terminal may indicate a first value ('0') in the header information and report all NACKs with the corresponding HARQ-ACK information. For example, the terminal may transmit [0, NNNN]. This can be used when the terminal does not have valid scheduling assistant information to transmit in the second reporting mode.

[0346] In the above-described embodiment, the length of UCI reported to PUCCH or PUSCH can be determined by the payload length (B_HARQ) of HARQ-ACK information. And the length of the UCI can be fixed regardless of the reporting mode. If the number of bits (B_SAI) included in the scheduling assistant information transmitted in the second reporting mode is smaller than B_HARQ, the terminal can adjust the length to be the same as B_HARQ. For example, B_SAI B_HARQ-B_SAI bits with '0' can be added to the LSB (least significant bits) of bits.

[0347] Example 1-2: When all HARQ-ACKs are All NACKs or All ACKs, scheduling assistant information is transmitted.

[0348] FIG. 13 is a diagram illustrating transmission of scheduling assistant information instead of HARQ-ACK information when HARQ-ACK information is All ACK or All NACK in a wireless communication system according to one embodiment of the present disclosure.

[0349] Referring to FIG. 13, three reporting modes can be set for a terminal. The first reporting mode can be a general HARQ-ACK information transmission mode. In the general HARQ-ACK information transmission mode, the terminal can transmit multiplexed HARQ-ACK bits (or HARQ-ACK codebook) to the base station. The second reporting mode can be a mode in which scheduling assistant information is transmitted to the base station in the case of All ACK. The third reporting mode can be a mode in which scheduling assistant information is transmitted to the base station in the case of All NACK. For example, in the first reporting mode, uplink control information (UCI) can be HARQ-ACK information, and in the second and third reporting modes, UCI can be scheduling assistant information.

[0350] In one embodiment, the terminal can determine the slot in which each HARQ-ACK information transmission is instructed. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 0, 1, 2, and 3, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 9 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 5, 6, 7, and 8, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 14 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 20, 21, 22, and 23, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the above four PDSCHs can be transmitted to PUCCH or PUSCH in slot 29.

[0351] In other words, the terminal can determine the slot and PUCCH or PUSCH on which HARQ-ACK information should be transmitted based on the scheduled PDSCH or the K1 value corresponding to the PDSCH. In addition, the HARQ-ACK bits corresponding to the PUCCH or PUSCH of one slot can be multiple bits, and the PUCCH resources and PUSCH resources on which the HARQ-ACK is to be transmitted can be determined based on the number of bits.

[0352] According to the above-described operation, the terminal can determine the PUCCH resource or PUSCH resource to be transmitted by the terminal, and can determine the number (N bits) of HARQ-ACK bits included in the PUCCH resource or PUSCH resource. When the terminal transmits uplink control information using the PUCCH resource or PUSCH resource regardless of the reporting mode, the length of the uplink control information corresponding to the PUCCH resource or PUSCH resource may be a value determined based on the number (N bits) of HARQ-ACK bits.

[0353] In one embodiment, the terminal may include information for indicating a reporting mode determined by the terminal in the PUCCH or PUSCH. The information for indicating the reporting mode determined by the terminal may be referred to as header information. If the header information has a first value ('00'), it may indicate a first reporting mode, if it has a second value ('01'), it may indicate a second reporting mode, and if it has a third value ('10'), it may indicate a third reporting mode. The header information may be attached to UCI transmitted by the terminal on the PUCCH or PUSCH or may be transmitted in another manner. A specific method is described in Embodiment 3. Of course, the value of the header information is not limited to the above example.

[0354] In one embodiment, when there is at least one ACK or one NACK in HARQ-ACK information to be transmitted by a terminal to a PUCCH or a PUSCH, the terminal may transmit the PUCCH or the PUSCH in the first reporting mode. More specifically, when at least one of the PDSCHs corresponding to the PUCCH or the PUSCH is correctly received or when at least one is not correctly received, the terminal may transmit HARQ-ACK information to the PUCCH or the PUSCH. At this time, the header information transmitted by the terminal may be a first value ('00'). The base station may determine that the first reporting mode in which the received PUCCH or PUSCH includes HARQ-ACK information is present through the first value ('00') which is the header information. In addition, the base station may not perform retransmission of the PDSCH corresponding to at least one ACK through the received HARQ-ACK information. In addition, the base station may perform retransmission of the PDSCH corresponding to at least one NACK through the received HARQ-ACK information. Of course, the values ​​of the above header information are not limited to the above examples.

[0355] In one embodiment, if all HARQ-ACK information to be transmitted by the terminal to the PUCCH or PUSCH is ACK, the terminal may transmit the PUCCH or PUSCH in the second reporting mode. More specifically, if all PDSCHs corresponding to the PUCCH or PUSCH are correctly received, the terminal may transmit scheduling assistant information to the PUCCH or PUSCH instead of HARQ-ACK information. At this time, the header information transmitted by the terminal may be the second value ('01'). The base station may determine that the received PUCCH or PUSCH includes scheduling assistant information and is in the second reporting mode through the second value ('01') which is the header information. In addition, the base station may determine that all PDSCHs associated with the PUCCH or PUSCH are ACK. Therefore, the base station may not retransmit the PDSCHs and may utilize the scheduling assistant information when scheduling the PDSCH in the future. Of course, the value of the header information is not limited to the above example.

[0356] In one embodiment, if all HARQ-ACK information to be transmitted by the terminal through the PUCCH or PUSCH is NACK, the terminal may transmit the PUCCH or PUSCH in the third reporting mode. More specifically, if all PDSCHs corresponding to the PUCCH or PUSCH are not correctly received, the terminal may transmit scheduling assistant information through the PUCCH or PUSCH instead of HARQ-ACK information. At this time, the header information transmitted by the terminal may be a third value ('10'). The base station may determine that the third reporting mode includes scheduling assistant information in the received PUCCH or PUSCH through the header information, which is the third value ('10'). In addition, the base station may determine that all PDSCHs associated with the PUCCH or PUSCH are NACK. Therefore, the base station may retransmit the PDSCHs, and at this time, may utilize scheduling assistant information. Of course, the value of the header information is not limited to the above example.

[0357] In one embodiment, a case in which a terminal indicates a first value ('00') as header information and all corresponding HARQ-ACK information are NACKs may be defined as an error case. For example, the terminal may not be able to transmit [00, NNNN]. In addition, according to the present disclosure, a case in which a terminal indicates a first value ('00') as header information and all corresponding HARQ-ACK information are ACKs may be defined as an error case. For example, the terminal may not be able to transmit [00, AAAA]. Of course, the value of the header information is not limited to the above example.

[0358] According to the present disclosure, a terminal can indicate a first value ('00') as header information and report all ACKs with the corresponding HARQ-ACK information. For example, the terminal can transmit [00, AAAA]. In this case, the terminal can use it when there is no valid scheduling assistant information to transmit in the second reporting mode. According to the present disclosure, a terminal can indicate a first value ('00') as header information and report all NACKs with the corresponding HARQ-ACK information. For example, the terminal can transmit [00, NNNN]. In this case, the terminal can use it when there is no valid scheduling assistant information to transmit in the third reporting mode. Of course, the value of the header information is not limited to the above example.

[0359] Example 1-3: Transmission of 1-bit bundled HARQ-ACK and scheduling assistant information

[0360] FIG. 14 is a diagram illustrating transmission of HARQ-ACK information or 1-bit bundled HARQ-ACK bit and scheduling assistant information according to an embodiment of a wireless communication system according to an embodiment of the present disclosure.

[0361] Referring to FIG. 14, two reporting modes may be set for a terminal. The first reporting mode may be a general HARQ-ACK information transmission mode. In the general HARQ-ACK information transmission mode, the terminal may transmit multiplexed HARQ-ACK bits (or HARQ-ACK codebook) to the base station. The second reporting mode may be a mode in which the result of bundling HARQ-ACK bits into 1 bit and scheduling assistant information are transmitted to the base station. For example, in the first reporting mode, uplink control information (UCI) may be HARQ-ACK information, and in the second reporting mode, UCI may be a 1-bit bundled HARQ-ACK bit and scheduling assistant information.

[0362] In one embodiment, the terminal can determine the slot in which each HARQ-ACK information transmission is instructed. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 0, 1, 2, and 3, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 9 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 5, 6, 7, and 8, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 14 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 20, 21, 22, and 23, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the above four PDSCHs can be transmitted to PUCCH or PUSCH in slot 29.

[0363] In other words, the terminal can determine the slot and PUCCH or PUSCH on which HARQ-ACK information should be transmitted based on the scheduled PDSCH or the K1 value corresponding to the PDSCH. In addition, the HARQ-ACK bits corresponding to the PUCCH or PUSCH of one slot can be multiple bits, and the PUCCH resources and PUSCH resources on which the HARQ-ACK is to be transmitted can be determined based on the number of bits.

[0364] According to the above-described operation, the terminal can determine the PUCCH resource or PUSCH resource to be transmitted by the terminal, and determine the number of HARQ-ACK bits included in the PUCCH resource or PUSCH resource.

[0365] In one embodiment, the terminal may include information indicating a reporting mode determined by the terminal in the PUCCH or PUSCH. The information indicating the reporting mode determined by the terminal may be referred to as header information. If the header information has a first value ('0'), it may indicate a first reporting mode, and if it has a second value ('1'), it may indicate a second reporting mode. The header information may be attached to UCI transmitted by the terminal on the PUCCH or PUSCH or transmitted in another manner. A specific method may be described in Embodiment 3. Of course, the value of the header information is not limited to the above example.

[0366] In one embodiment, the terminal may transmit a PUCCH or PUSCH in the first reporting mode. More specifically, the terminal may transmit HARQ-ACK information through the PUCCH or PUSCH. At this time, the header information transmitted by the terminal may be a first value ('0'). The base station may determine that the received PUCCH or PUSCH includes HARQ-ACK information in the first reporting mode through the first value ('0') of the header information. In addition, the base station may perform retransmission of the PDSCH based on the received HARQ-ACK information. Of course, the value of the header information is not limited to the above example.

[0367] In one embodiment, the terminal may transmit a PUCCH or PUSCH in a second reporting mode. More specifically, the terminal may bundle HARQ-ACK information into 1 bit and transmit the 1-bit information and scheduling assistant information through the PUCCH or PUSCH. At this time, the header information transmitted by the terminal may be a second value ('1'). The base station may determine, through the second value ('1') which is the header information, that the received PUCCH or PUSCH includes a 1-bit bundled HARQ-ACK bit and scheduling assistant information, and is in the second reporting mode. The base station may determine, through the 1-bit bundled HARQ-ACK bit, whether all PDSCHs associated with the PUCCH or PUSCH are ACKs or NACKs. Of course, the value of the header information is not limited to the above example.

[0368] According to the present disclosure, the condition for a terminal to use the second reporting mode may be limited to cases where all HARQ-ACK information is ACK or all NACK. If all are ACK or none are NACK (e.g., at least one ACK and at least one NACK are included), a 1-bit bundled HARQ-ACK may be determined as a NACK as the HARQ-ACK of a correctly received PDSCH. Accordingly, the base station may perform unnecessary retransmission.

[0369] Example 1-4: N-bit bundled HARQ-ACK and scheduling assistant information transmission

[0370] FIG. 15 is a diagram illustrating transmission of HARQ-ACK information or N-bit bundled HARQ-ACK bits and scheduling assistant information in a wireless communication system according to one embodiment of the present disclosure.

[0371] Referring to FIG. 15, two reporting modes may be set for a terminal. The first reporting mode may be a general HARQ-ACK information transmission mode. In the general HARQ-ACK information transmission mode, the terminal may transmit multiplexed HARQ-ACK bits (or HARQ-ACK codebook) to the base station. The second reporting mode may be a mode in which the result of bundling HARQ-ACK bits into N bits and scheduling assistant information are transmitted to the base station. For example, in the first reporting mode, uplink control information (UCI) may be HARQ-ACK information, and in the second reporting mode, UCI may be N-bit bundled HARQ-ACK bits and scheduling assistant information.

[0372] In one embodiment, the terminal can determine the slot in which each HARQ-ACK information transmission is instructed. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 0, 1, 2, and 3, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 9 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 5, 6, 7, and 8, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the four PDSCHs may be transmitted in slot 14 as a PUCCH or PUSCH. For example, the K1 values ​​corresponding to the PDSCHs scheduled in slots 20, 21, 22, and 23, respectively, may be 9, 8, 7, and 6. Accordingly, the HARQ-ACK information of the above four PDSCHs can be transmitted to PUCCH or PUSCH in slot 29.

[0373] In other words, the terminal can determine the slot and PUCCH or PUSCH on which HARQ-ACK information should be transmitted based on the scheduled PDSCH or the K1 value corresponding to the PDSCH. In addition, the HARQ-ACK bits corresponding to the PUCCH or PUSCH of one slot can be multiple bits, and the PUCCH resources and PUSCH resources on which the HARQ-ACK is to be transmitted can be determined based on the number of bits.

[0374] According to the above-described operation, the terminal can determine the PUCCH resource or PUSCH resource to be transmitted by the terminal, and can determine the number (N bits) of HARQ-ACK bits included in the PUCCH resource or PUSCH resource. When the terminal transmits uplink control information using the PUCCH resource or PUSCH resource regardless of the reporting mode, the length of the uplink control information corresponding to the PUCCH resource or PUSCH resource may be a value determined based on the number (N bits) of HARQ-ACK bits.

[0375] In one embodiment, the terminal may include information indicating a reporting mode determined by the terminal in the PUCCH or PUSCH. The information indicating the reporting mode determined by the terminal may be referred to as header information. If the header information has a first value ('0'), it may indicate a first reporting mode, and if it has a second value ('1'), it may indicate a second reporting mode. The header information may be attached to UCI transmitted by the terminal on the PUCCH or PUSCH or transmitted in another manner. A specific method may be described in Embodiment 3. Of course, the value of the header information is not limited to the above example.

[0376] In one embodiment, the terminal may transmit a PUCCH or PUSCH in the first reporting mode. More specifically, the terminal may transmit HARQ-ACK information through the PUCCH or PUSCH. At this time, the header information transmitted by the terminal may be a first value ('0'). The base station may determine that the received PUCCH or PUSCH includes HARQ-ACK information in the first reporting mode through the first value ('0') of the header information. In addition, the base station may perform retransmission of the PDSCH based on the received HARQ-ACK information. Of course, the value of the header information is not limited to the above example.

[0377] In one embodiment, the terminal may transmit a PUCCH or PUSCH in a second reporting mode. More specifically, the terminal may bundle HARQ-ACK information into N bits and transmit the N bits of information and scheduling assistant information through the PUCCH or PUSCH. At this time, the header information transmitted by the terminal may be a second value ('1'). The base station may determine that the received PUCCH or PUSCH includes an N-bit bundled HARQ-ACK bit and scheduling assistant information through the second value ('1') of the header information, that is, the second reporting mode. The base station may determine whether the PDSCHs associated with the PUCCH or PUSCH are ACKs or NACKs through the N-bit bundled HARQ-ACK bit. Of course, the value of the header information is not limited to the above example.

[0378] In one embodiment, the condition for the terminal to use the second reporting mode may be limited to the case where all HARQ-ACK information of the PDSCH corresponding to one bundled HARQ-ACK bit is ACK or all NACK. If the PDSCHs corresponding to one bundled HARQ-ACK bit are neither ACK nor NACK (including at least one ACK and at least one NACK), one bundled HARQ-ACK bit is determined to be NACK, and accordingly, the HARQ-ACK of the correctly received PDSCH may be determined to be NACK. Accordingly, the base station may perform unnecessary retransmission.

[0379] The method for determining N in this disclosure is as follows. Of course, it is not limited to the following examples.

[0380] The base station can set the N value for the terminal. When the terminal receives the second reporting mode from the base station, the terminal can receive the N value from the base station. The N value can have values ​​such as 2, 3, 4, 5, 6, 7, or 8.

[0381] The terminal can determine the value of N based on the payload length of the HARQ-ACK information. For example, if the payload length of the HARQ-ACK information is B bits and the number of bits required to transmit the scheduling assistant information is S bits, then N can be determined as BS. For example, the terminal can use the remaining bits, excluding the bits required to transmit the scheduling assistant information among the B bits, for bundled HARQ-ACK transmission.

[0382] In addition to the bundling technique in the above-described embodiment, various methods for reducing the payload length of HARQ-ACK information can be used.

[0383] For example, if a terminal is configured to transmit two TB (transport blocks) on one PDSCH, the terminal can generate 2-bit HARQ-ACK information for one PDSCH. The terminal can generate 1-bit HARQ-ACK information by spatially bundling the 2-bit HARQ-ACK information with the HARQ-ACK information corresponding to a specific header value. Here, the spatial bundling can be as follows. Of course, it is not limited to the following example.

[0384] If a terminal correctly receives a PDSCH including one TB, one bit of spatially bundled HARQ-ACK may be an ACK, and if the terminal does not correctly receive the TB, one bit of spatially bundled HARQ-ACK may be a NACK. In an embodiment of the present disclosure, correctly receiving a TB by a terminal may include receiving information included in the TB without loss.

[0385] If the terminal correctly receives the two TBs for a PDSCH including two TBs, the spatially bundled HARQ-ACK 1 bit may be an ACK, and if at least one TB among the two TBs is not correctly received, the spatially bundled HARQ-ACK 1 bit may be a NACK. However, the present invention is not limited to the above example, and the spatially bundled HARQ-ACK 1 bit may be an ACK even if the terminal correctly receives at least one TB.

[0386] As another example, when a terminal is configured for CBG (code block group)-based transmission, the terminal can generate N_CBG HARQ-ACK bits for one PDSCH. The terminal can generate a 1-bit TB-based HARQ-ACK bit with HARQ-ACK information corresponding to a specific header value. Here, the 1-bit TB-based HARQ-ACK bit can be an ACK if the TB CRC included in the PDSCH is checked correctly, and can be a NACK if the TB CRC is not checked correctly.

[0387] <Example 2: Scheduling assistant information types>

[0388] According to the present disclosure, a terminal may transmit scheduling assistant information including at least one of the following: Scheduling assistant information may be transmitted including a plurality of the following: Information to be included in the terminal's scheduling assistant information may be configured by the base station.

[0389] As the first information, MCS related information may be included.

[0390] The above MCS-related information may correspond to an MCS value (expressed as an MCS value desired by the terminal) required for the terminal to correctly decode the PDSCH. Here, the PDSCH may be a PDSCH scheduled by the terminal. For example, referring to FIG. 12, PDSCHs corresponding to the PUCCH or PUSCH transmitted in slot 29 (four PDSCHs received in slots 20, 21, 22, and 23, respectively) may be determined. The terminal may determine an MCS value based on one or more of the four PDSCHs.

[0391] One or more PDSCHs may be selected as follows. The examples below are not limiting. Furthermore, a terminal may not select a PDSCH using only one of the following methods.

[0392] In one embodiment, the terminal may select the most recently received PDSCH.

[0393] In one embodiment, the terminal may select a PDSCH containing the largest number of RBs.

[0394] In one embodiment, the terminal may select a PDSCH containing the fewest number of RBs.

[0395] In one embodiment, the terminal may select the PDSCH scheduled with the highest MCS value.

[0396] In one embodiment, the terminal may select the PDSCH scheduled with the lowest MCS value.

[0397] In one embodiment, the terminal may select a PDSCH corresponding to a particular slot.

[0398] In one embodiment, the terminal may select a PDSCH according to a DCI format corresponding to the PDSCH.

[0399] In one embodiment, the terminal may select a PDSCH containing the largest number of OFDM symbols.

[0400] In one embodiment, the terminal may select a PDSCH containing the fewest number of OFDM symbols.

[0401] In one embodiment, the terminal may select a PDSCH that includes the most REs.

[0402] In one embodiment, the terminal may select the PDSCH containing the fewest REs.

[0403] In one embodiment, the terminal may select a PDSCH that is a specific HARQ process number.

[0404] In one embodiment, the terminal may select one PDSCH and include information related to an index of the selected PDSCH as scheduling assistant information.

[0405] The desired MCS value to be included in the scheduling assistant information of the terminal may be expressed in at least one of the following ways, although the present invention is not limited to the examples below.

[0406] As a first method, the terminal can include the absolute MCS value as the scheduling assistant information value. The absolute MCS value can be expressed in 5 bits. More specifically, Table 24 is an MCS table for interpreting MCS values. The terminal, referring to Table 24, can input the desired MCS value (MCS index, I MCS ) can be determined, and the index can be represented as 5 bits and included as a scheduling assistant information value.

[0407]

[0408] As a second method, the terminal can include the relative MCS value (delta MCS) between the MCS of the received PDSCH and the desired MCS as the scheduling assistant information value. The delta MCS value can be expressed as X bits, where X can be 2 bits. The delta MCS can be determined based on the following Table 25. Here, is the MCS of the received PDSCH, may be the MCS desired by the terminal. Here, It can be a pre-determined value or a value set by the base station to the terminal. It could be.

[0409] for example, And, if the MCS index of the PDSCH received by the terminal is 12, referring to Table 25, if the MCS index is 12, it can be determined as 16QAM and 434 / 1024 code rate. If the PDSCH desired by the terminal is 8 (QPSK, 602 / 1024 code rate), can be obtained. Therefore, the terminal can determine 2 as the Delta MCS index.

[0410]

[0411] FIG. 16 is a diagram illustrating a terminal including MCS information as scheduling assistant information in a wireless communication system according to one embodiment of the present disclosure.

[0412] Referring to FIG. 16, a terminal may receive one or more PDSCHs. The PDSCHs may be scheduled with a first MCS. The terminal may transmit HARQ-ACK information of the PDSCHs through a PUCCH or a PUSCH. In this case, if the HARQ-ACK information has a specific value, the terminal may transmit MCS information instead of HARQ-ACK information. For example, the first reporting mode may be a HARQ-ACK information mode, and the second reporting mode may be an MCS information transmission mode. The mode may be indicated by header information. When transmitting MCS information in the second reporting mode, the base station may schedule the PDSCH using a new MCS (second MCS) based on the MCS information.

[0413] Secondary information may include channel quality indicator (CQI)-related information. The CQI-related information may be a value determined based on the CSI-RS and reference PDSCH scheduling information received by the terminal. Alternatively, the CQI-related information may be a value determined based on the DMRS of the PDSCH received by the terminal.

[0414] Third information may include PMI (precoder matrix indicator)-related information. The PMI-related information may be a value determined based on the CSI-RS received by the terminal. Alternatively, the PMI-related information may be a value determined based on the DMRS of the received PDSCHs.

[0415] The fourth information may include RI (rank indicator)-related information. The RI-related information may be a value determined based on the CSI-RS received by the terminal. Alternatively, the RI-related information may be a value determined based on the DMRS of the received PDSCHs.

[0416] The fifth information may include beam-related information. The beam-related information may be a value determined based on the CSI-RS or SSB received by the terminal. Alternatively, the beam-related information may be a value determined based on the DMRS of the received PDSCHs.

[0417] The sixth information may include information regarding channel measurements (SINR, RSRP, RSRQ, RSSI, or interference). The channel measurement information may be determined based on the CSI-RS received by the terminal. In the case of interference, the value may be determined based on ZP (zero power CSI-RS). Alternatively, the channel measurement information may be determined based on the DMRS of the received PDSCHs.

[0418] The seventh information may include information regarding PDSCH decoding (LDPC code decoding). Information regarding PDSCH decoding may be determined based on the PDSCH received by the terminal. Here, the information regarding PDSCH decoding may be a value corresponding to a Log Likelihood Ratio (LLR) value or a Mutual Information value that can be obtained when decoding an LDPC code block included in the PDSCH.

[0419] The eighth information may include information for PDCCH link adaptation. The terminal may receive a PDCCH scheduling PDSCH. The PDCCH may be mapped to a unique aggregation level. The aggregation level may be one of 1, 2, 4, 8, or 16. The terminal may report to the base station the aggregation level value required for PDCCH reception.

[0420] The first to eighth information may be generated for each subband. For example, the terminal may include MCS, CQI, PMI, RI, Beam, channel measurements (e.g., SINR, RSRP, RSSI, interference), information regarding PDSCH decoding, and PDCCH link adaptation information in scheduling assistant information for each subband.

[0421] The first to eighth pieces of information described above may exceed the payload size of the HARQ-ACK information. The terminal may determine that more accurate CSI reporting is required to the base station. In this case, the terminal may include CSI report triggering request information as the ninth piece of information.

[0422] FIG. 17 is a diagram illustrating transmission of CSI report triggering request information by a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0423] Referring to FIG. 17, a terminal may receive one or more PDSCHs. The terminal may transmit HARQ-ACK information of the PDSCHs via a PUCCH or a PUSCH. In this case, if the HARQ-ACK information is a specific value, the terminal may transmit CSI report triggering request information instead of transmitting HARQ-ACK information. For example, the first report mode may be a HARQ-ACK information mode, and the second report mode may be a CSI report triggering request mode. The mode may be indicated by header information.

[0424] When a terminal transmits a PUCCH or PUSCH in a CSI report triggering request mode, the terminal can monitor a DCI format indicating CSI report triggering from the base station. This monitoring can only be performed during a specific time period. When the terminal receives a DCI format indicating CSI report triggering, it can perform a CSI report according to the DCI format. The CSI report can be performed as an aperiodic CSI report.

[0425] Here, the specific time interval may be configured as a certain time period starting from the PUCCH or PUSCH transmission. Alternatively, the specific time interval may be configured as a certain time period starting from the first PDCCH monitoring occasion after the PUCCH or PUSCH transmission. Here, the certain time period may be a value set by the base station. The first PDCCH monitoring occasion may be the earliest PDCCH monitoring occasion among the PDCCH monitoring occasions capable of monitoring the DCI format indicating CSI report triggering.

[0426] The terminal may not be able to transmit a CSI report triggering request mode through another PUCCH or PUSCH within the specific period. For example, the terminal may monitor a DCI format indicating CSI report triggering from the base station during the specific period, and if the DCI format is not received during the specific period, the terminal may transmit a PUCCH or PUSCH in the CSI report triggering request mode after the specific period.

[0427] The above-described CSI report triggering can be further subdivided into detailed triggering. For example, CSI report triggering can be further subdivided into MCS report triggering, CQI report triggering, PMI report triggering, RI report triggering, beam report triggering, channel measurement value report triggering, and value reporting triggering for PDCCH link adaptation. For example, when a terminal transmits a PUCCH or PUSCH in an MCS report triggering mode, the terminal can monitor and receive a DCI format that triggers an MCS report from a base station. The above-described detailed triggering can be triggered in combination, for example.

[0428] When a terminal receives multiple pieces of information as scheduling assistant information, the terminal can determine the priority of each piece of information. This priority may be set by the base station or may be a predefined priority.

[0429] A terminal can include multiple pieces of information in UCI in ascending order of priority. Information within the payload length determined based on HARQ-ACK information can be included in scheduling assistant information. However, information exceeding the payload length determined based on HARQ-ACK information can be excluded from scheduling assistant information. For example, some or all of the information can be included and transmitted in UCI depending on the payload length determined based on HARQ-ACK information.

[0430] <Example 3: Method for Transmitting Header Information>

[0431] Header information transmitted by a terminal to a base station can indicate the reporting mode of the terminal. Referring to FIGS. 12, 14, and 15, the terminal may have two reporting modes, and the header information may be determined by 1 bit. Referring to FIG. 13, the terminal may have three reporting modes, and the header information may be determined by 2 bits. A method for transmitting header information to a base station by a terminal is disclosed.

[0432] In a first method, when a terminal transmits UCI via PUCCH or PUSCH (information included in the UCI is determined according to the reporting mode), header information may be attached to the UCI payload. More specifically, when the terminal determines B bits as the length of the HARQ-ACK payload to be transmitted via PUCCH or PUSCH, B+H bits may be transmitted via the PUCCH or PUSCH. Here, H bits may be header information. And the information included in B bits may be determined according to the reporting mode.

[0433] In a second method, when a terminal transmits UCI on PUCCH or PUSCH, the CRC attached to the UCI can be masked with different values ​​according to the header information. More specifically, the CRC can be attached to the UCI and encoded with a channel code (e.g., a polar code) and transmitted on PUCCH or PUSCH. Here, the CRC can be 6 bits or 11 bits. The CRC and the Mask that the terminal will use In that case, the terminal can be attached to the UCI. Here can be the XOR operator or A+B mod 2.

[0434] If the header information is a first value, a first mask corresponding to the first value can be determined, and if the header information is a second value, a second mask corresponding to the second value can be determined.

[0435] The base station can decode UCI using PUCCH or PUSCH. The base station can determine whether the CRC attached to the UCI is masked with the first mask or the second mask. If it is masked with the first mask, the base station can determine it in the first reporting mode. If it is masked with the second mask, the base station can determine it in the second reporting mode. The base station can interpret the UCI according to the determined reporting mode.

[0436] In a third method, when a terminal transmits UCI through PUCCH or PUSCH, the DMRS sequence of the PUCCH or PUSCH can be determined according to header information.

[0437] More specifically, the DMRS of PUCCH format 3 can be expressed by mathematical expression 3.

[0438] [Equation 3]

[0439]

[0440] Here may be the number of subcarriers included in the PUCCH. is a specific sequence, is determined here And, is the cyclic shift value, is the value corresponding to the sequence group, is the value corresponding to the sequence number.

[0441] According to the present method, when the terminal transmits PUCCH in the first reporting mode, When transmitting PUCCH with values ​​and second reporting mode, At least one of the values ​​can be different. For example, different values ​​can be different. This can be used in the first reporting mode and the second reporting mode.

[0442] More specifically, the DMRS of PUSCH can be expressed by mathematical expression 4.

[0443] [Equation 4]

[0444]

[0445] Here, c(i) is a pseudo-random sequence, and the initial value can be expressed as mathematical expression 5.

[0446] [Equation 5]

[0447]

[0448] Here, is the number of OFDM symbols contained in a slot, is the slot index within the frame, l may be the OFDM symbol index within the slot. And, is a DMRS initialization value that can be 0 or 1, or may be a value set from the base station.

[0449] According to this embodiment, when the terminal transmits PUSCH in the first reporting mode, When transmitting PUCCH with values ​​and second reporting mode, At least one of the values ​​can be different. For example, different values ​​can be different. The values ​​can be used in both the first reporting mode and the second reporting mode.

[0450] In a fourth method, when a terminal transmits UCI via PUCCH or PUSCH, it can be transmitted on different time-frequency resources depending on the header information. For example, the terminal can receive a first PUCCH resource set and a second PUCCH resource set from the base station. If the header information is the first value, the terminal can transmit UCI on a PUCCH selected from the first PUCCH resource set, and if the header information is the second value, the terminal can transmit UCI on a PUCCH selected from the second PUCCH resource set.

[0451] <Example 4: Method for determining UCI length variation and PUCCH resources according to header information>

[0452] According to the first embodiment described above, the length of the UCI can be determined by the payload length of the HARQ-ACK information. Furthermore, the length of the UCI can be fixed regardless of the reporting mode. However, to allow the terminal to transmit a greater amount of scheduling assistant information to the base station, different UCI lengths can be defined for each reporting mode.

[0453] More specifically, for the first reporting mode (HARQ-ACK information reporting), the length of UCI may be the same as the length of HARQ-ACK information (e.g., B_HARQ). For the second reporting mode (Scheduling assistant information reporting), the length of UCI may be different from the length of HARQ-ACK information (e.g., B_SAI). Note that B_HARQ may be determined according to the number of PDSCHs associated with PUCCH or PUSCH, and B_SAI may be determined according to the configuration of the base station.

[0454] FIG. 18 is a diagram illustrating a wireless communication system according to an embodiment of the present disclosure in which UCIs of different lengths are transmitted on a PUCCH according to a reporting mode.

[0455] Referring to FIG. 18, a terminal can determine a starting PRB (PRB) of a PUCCH. The starting RB can be set by a base station and indicated by a DCI that schedules a PDSCH.

[0456] The terminal can determine a first set of PRBs from the starting PRB. The first set of PRBs includes at least one PRB from the starting PRB and may include consecutive PRBs. The number of PRBs included in the first set of PRBs can be determined based on the amount of header information.

[0457] The terminal can determine a second set of PRBs among PRBs other than the first set of PRBs determined. Here, the starting PRB in the second set of PRBs may be a PRB adjacent to the first set of PRBs, and may be composed of consecutive RBs from the PRB. The number of PRBs included in the second set of PRBs may be determined according to the payload size of the UCI. For example, the UCI payload size may be one of B_HARQ (first reporting mode) or B_SAI (second reporting mode). Accordingly, the number of PRBs included in the second set of PRBs may be a value determined according to B_HARQ or a value determined according to B_SAI.

[0458] The terminal can encode header information and UCI separately. Header information can be encoded as a channel code and mapped to the first PRB set, and UCI can be encoded as a channel code and mapped to the second PRB set.

[0459] The base station can decode header information from PRBs belonging to the first PRB set. If the header information indicates the first reporting mode (HARQ-ACK information reporting), the base station can determine that the length of the UCI transmitted by the terminal is B_HARQ. Based on B_HARQ, the base station can determine the number of PRBs included in the second PRB set. Then, the base station can decode HARQ-ACK information from the determined PRBs. If the header information indicates the second reporting mode (Scheduling assistant information reporting), the base station can determine that the length of the UCI transmitted by the terminal is B_SAI. Based on B_SAI, the base station can determine the number of PRBs included in the second PRB set. Then, the base station can decode scheduling assistant information from the determined PRBs.

[0460] FIG. 19 is a diagram illustrating a method of transmitting on a PUCCH according to a reporting mode in a wireless communication system according to an embodiment of the present disclosure.

[0461] Referring to Figure 19, the terminal may not have a UCI corresponding to the second PRB set. In this case, the terminal may not use the PRBs corresponding to the second PRB set for PUCCH transmission. For example, the power corresponding to the PRBs may be 0.

[0462] For example, if the header information transmitted in the first PRB set indicates the second reporting mode, the terminal may need to transmit scheduling assistant information in the second PRB set. However, the terminal may not be able to obtain valid scheduling assistant information. In this case, the terminal may not use the PRBs included in the second PRB set. This allows the terminal to allocate higher power to the first PRB set. Therefore, the header information transmitted in the first PRB set can be transmitted with higher reliability.

[0463] <Embodiment 5: PUCCH transmission method according to HARQ-ACK information or reporting mode>

[0464] According to one embodiment of the present disclosure, a terminal can determine the transmission power of a PUCCH according to HARQ-ACK information or a reporting mode.

[0465] More specifically, the terminal can transmit HARQ-ACK information via the PUCCH. In this case, the transmission power of the PUCCH can be determined based on the ACK or NACK included in the HARQ-ACK information.

[0466] In one embodiment, if all HARQ-ACK information is NACK, the terminal can change the transmission power of the PUCCH. For example, even if the base station does not successfully receive a PUCCH in which all HARQ-ACK information is NACK, the base station can recognize that all HARQ-ACK information is NACK. Therefore, in order to reduce the power consumption of the terminal, the transmission power of the PUCCH in which all HARQ-ACK information is NACK can be reduced and transmitted.

[0467] In one embodiment, if all HARQ-ACK information is ACK, the terminal can change the transmission power of the PUCCH. For example, if all HARQ-ACK information is ACK, the link between the base station and the terminal can be determined to be excellent, and the transmission power of the PUCCH can be reduced accordingly. Therefore, to reduce the power consumption of the terminal, the transmission power of the PUCCH in which all HARQ-ACK information is ACK can be reduced and transmitted.

[0468] In one embodiment, if the NACK rate or ACK rate in HARQ-ACK information exceeds a certain threshold, the terminal may change the transmission power of the PUCCH. This allows the terminal to use different transmission powers depending on the NACK rate or ACK rate, thereby controlling the PUCCH reception probability and the power consumption of PUCCH transmission.

[0469] In one embodiment, if at least one NACK is included in the HARQ-ACK information, the terminal can change the transmission power of the PUCCH. This allows the terminal to adjust the PUCCH reception probability and the power consumption of PUCCH transmission by using different transmission powers depending on the presence or absence of NACK.

[0470] In one embodiment, if at least one ACK is included in the HARQ-ACK information, the terminal can change the transmission power of the PUCCH. This allows the terminal to use different transmission powers depending on the presence or absence of an ACK, thereby controlling the reception probability of the PUCCH and the power consumption of PUCCH transmission.

[0471] In one embodiment, if HARQ-ACK information includes a specific ACK or NACK pattern, the terminal can change the transmission power of the PUCCH. This allows the terminal to adjust the reception probability of the PUCCH and the power consumption of PUCCH transmission by using different transmission powers depending on the ACK or NACK pattern.

[0472] In one embodiment, when the reporting mode is the first mode, the terminal may use the first transmission power when transmitting the PUCCH, and when the reporting mode is the second mode, the terminal may use the second transmission power when transmitting the PUCCH. Here, the first transmission power and the second transmission power may be different from each other. For example, when the terminal is in the second reporting mode (reporting scheduling assistant information), the base station may maintain the conventional operation even if the transmission fails. Therefore, in the second reporting mode, the second transmission power of the PUCCH may be lower than the first transmission power.

[0473] According to the present disclosure, when a PUCCH transmits an HARQ-ACK, a first transmission power may be used, and when a PUCCH transmits CSI, a second transmission power may be used. Here, when a PUCCH simultaneously transmits HARQ-ACK and CSI, either the first transmission power or the second transmission power may be used. Here, one transmission power may be the higher transmission power of the two. For example, a transmission power may be set for each UCI type, and a PUCCH may be transmitted based on the highest transmission power among the multiplexed UCI types.

[0474] The terminal can receive new power parameter values ​​from the base station to change the transmission power of the PUCCH. For example, the power for PUCCH transmission can be determined using Equation 6.

[0475] [Equation 6]

[0476]

[0477] For an explanation of Equation 6, please refer to Section 7.2.1 of the 3GPP standard document TS38.213. In Equation 6, is associated with the number of RBs included in the PUCCH, is associated with the Pathloss reference signal, is associated with the PUCCH format. Also, is a value determined by the PUCCH format and the UCI length, OFDM symbol number, and RB number included in the PUCCH. And may be a value determined according to the Transmit power control (TPC) command of the DCI that schedules the PUCCH. Therefore, the above parameter may be commonly used in HARQ-ACK information or reporting mode.

[0478] is q with P0 value u (q u =0,1, ..., Q u -1) Different values ​​can be set for each value. Q u The base station can set the number of P0 values. Therefore, the terminal can use the HARQ-ACK information or reporting mode from the base station. or set q u The index can be set. For example, in the first reporting mode, the first q u The value is set, and in the second reporting mode, the second q u The value can be set.

[0479] Alternatively, an additional power backoff value may be added to Equation 6. For example, the terminal may receive from the base station a power backoff value to be applied when reducing power usage according to HARQ-ACK information or reporting mode. When reducing power usage according to HARQ-ACK information or reporting mode, the terminal may reduce the transmission power of the PUCCH using the power backoff value.

[0480] FIG. 20 is a diagram illustrating a method for transmitting a PUCCH according to HARQ-ACK information in a wireless communication system according to an embodiment of the present disclosure.

[0481] Referring to FIG. 20a, the PUCCH may be PUCCH format 3 or PUCCH format 4. When a terminal transmits HARQ-ACK on the PUCCH, the PUCCH may be divided into a DMRS symbol for channel estimation and a UCI portion in which HARQ-ACK information is encoded. Here, the DMRS symbol may be determined using mathematical expression 3 regardless of the HARQ-ACK information.

[0482] Referring to FIG. 20b, if the HARQ-ACK information corresponding to the PUCCH transmitted by the terminal is a specific value, the terminal may transmit the specific value as a DMRS symbol and not transmit the UCI portion. More specifically, if all HARQ-ACK information is ACK, or if all HARQ-ACK information is NACK, the terminal may transmit the information via DMRS and not transmit the UCI portion. Not transmitting may be equivalent to not allocating power to the symbol corresponding to the UCI portion. Accordingly, the terminal may save transmission power.

[0483] Referring to mathematical expression 3, when all terminals transmit a PUCCH with ACK, The values ​​can be specific values. This specific value is for transmitting a PUCCH that is not an ACK (containing at least one NACK). At least one of the values ​​may be different.

[0484] Referring to mathematical expression 3, when all terminals transmit a PUCCH with NACK, The values ​​can be specific values. This specific value is for transmitting a PUCCH that is not all NACKs (containing at least one ACK). At least one of the values ​​may be different.

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

[0486] Referring to FIG. 21, the terminal may include a transceiver, which refers to a terminal receiving unit (2100) and a terminal transmitting unit (2110), a memory (not shown), and a terminal processing unit (2105, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2100, 2110), the memory, and the terminal processing unit (2105) 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, the memory, and the processor may be implemented in the form of a single chip.

[0487] A transceiver unit can transmit and / or receive signals to and from a base station or other terminals. 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.

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

[0489] The memory can store programs and data necessary for the terminal's operation. Furthermore, the memory can store control information or data included in signals transmitted and / or received by the terminal. The memory may 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 may be multiple memories.

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

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

[0492] Referring to FIG. 22, the base station may include a transceiver, which refers to a base station receiver (2200) and a base station transmitter (2210), a memory (not shown), and a base station processing unit (2205, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver units (2200, 2210), the memory, and the base station processing unit (2205) 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.

[0493] A transceiver unit can transmit and / or receive signals to and from a terminal or another 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.

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

[0495] 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 / or 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.

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

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

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

[0499] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or 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.

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

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

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

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

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

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

[0506] 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 of a wireless communication system, A step of receiving downlink data from a base station on a PDSCH (physical downlink shared channel); A step of identifying a reporting mode for feedback of the downlink data based on HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for reception of the downlink data; and A step of transmitting UCI (uplink control information) including header information indicating the reporting mode to the base station on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH), The above reporting mode includes the first reporting mode and the second reporting mode, If the header information indicates the first reporting mode, the UCI further includes the HARQ-ACK information, and A method wherein, when the header information indicates the second reporting mode, the UCI further includes scheduling assistant information (SAI).

2. In paragraph 1, If the header information indicates the second reporting mode, the UCI further includes bundled information of the HARQ-ACK information, and A method wherein the SAI includes at least one of a modulation and coding scheme (MCS), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), beam-related information, channel measurement information, information regarding PDSCH decoding, physical downlink control channel (PDCCH) link adaptation information, or information for triggering channel state information (CSI) reporting.

3. In paragraph 1, The above header information is included in the payload of the UCI, or The CRC (cyclic redundancy check) for the above UCI is associated with the above header information, or A method wherein the DMRS (demodulation reference signal) sequence of the PUCCH or the PUSCH is based on the header information.

4. In paragraph 3, A method wherein the PRBs (physical resource blocks) of the PUCCH include a first PRB set associated with the header information and a second PRB set associated with the payload.

5. In a method performed by a base station of a wireless communication system, A step of transmitting downlink data on a PDSCH (physical downlink shared channel) to a terminal; and A step of receiving, from the terminal, uplink control information (UCI) including header information indicating a reporting mode for feedback of the downlink data on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH), The above reporting mode is based on HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for reception of the downlink data, The above reporting mode includes a first reporting mode and a second reporting mode, If the header information indicates the first reporting mode, the UCI further includes the HARQ-ACK information, and A method wherein, when the header information indicates the second reporting mode, the UCI further includes scheduling assistant information (SAI).

6. In paragraph 5, If the header information indicates the second reporting mode, the UCI further includes bundled information of the HARQ-ACK information, and A method wherein the SAI includes at least one of a modulation and coding scheme (MCS), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), beam-related information, channel measurement information, information regarding PDSCH decoding, physical downlink control channel (PDCCH) link adaptation information, or information for triggering channel state information (CSI) reporting.

7. In paragraph 5, The above header information is included in the payload of the UCI, or The CRC (cyclic redundancy check) for the above UCI is associated with the above header information, or A method wherein the DMRS (demodulation reference signal) sequence of the PUCCH or the PUSCH is based on the header information.

8. In paragraph 7, A method wherein the PRBs (physical resource blocks) of the PUCCH include a first PRB set associated with the header information and a second PRB set associated with the payload.

9. At the terminal: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor, so that the terminal: From the base station, downlink data is received on the PDSCH (physical downlink shared channel), Identifying a reporting mode for feedback of the downlink data based on HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for reception of the downlink data, and To the above base station, UCI (uplink control information) including header information indicating the reporting mode is transmitted on a PUCCH (physical uplink control channel) or a PUSCH (physical uplink shared channel), The above reporting mode includes the first reporting mode and the second reporting mode, If the header information indicates the first reporting mode, the UCI further includes the HARQ-ACK information, and A terminal, wherein when the header information indicates the second reporting mode, the UCI further includes scheduling assistant information (SAI).

10. In paragraph 9, If the header information indicates the second reporting mode, the UCI further includes bundled information of the HARQ-ACK information, and A terminal, wherein the SAI includes at least one of a modulation and coding scheme (MCS), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), beam-related information, channel measurement information, information regarding PDSCH decoding, physical downlink control channel (PDCCH) link adaptation information, or information for triggering CSI (channel state information) reporting.

11. In paragraph 9, The above header information is included in the payload of the UCI, or The CRC (cyclic redundancy check) for the above UCI is associated with the above header information, or A terminal wherein the DMRS (demodulation reference signal) sequence of the PUCCH or the PUSCH is based on the header information.

12. In paragraph 11, A terminal, wherein the PRBs (physical resource blocks) of the PUCCH include a first PRB set associated with the header information and a second PRB set associated with the payload.

13. At the base station: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor so that the base station: The terminal transmits downlink data on the PDSCH (physical downlink shared channel), and From the terminal, UCI (uplink control information) including header information indicating a reporting mode for feedback of the downlink data is received on a PUCCH (physical uplink control channel) or a PUSCH (physical uplink shared channel). The above reporting mode is based on HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for reception of the downlink data, The above reporting mode includes a first reporting mode and a second reporting mode, If the header information indicates the first reporting mode, the UCI further includes the HARQ-ACK information, and A base station, wherein when the header information indicates the second reporting mode, the UCI further includes scheduling assistant information (SAI).

14. In paragraph 13, If the header information indicates the second reporting mode, the UCI further includes bundled information of the HARQ-ACK information, and A base station, wherein the SAI includes at least one of a modulation and coding scheme (MCS), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), beam-related information, channel measurement information, information regarding PDSCH decoding, physical downlink control channel (PDCCH) link adaptation information, or information for triggering channel state information (CSI) reporting.

15. In paragraph 13, The above header information is included in the payload of the UCI, or The CRC (cyclic redundancy check) for the above UCI is associated with the above header information, or A base station, wherein the DMRS (demodulation reference signal) sequence of the PUCCH or the PUSCH is based on the header information.

Images