Method and apparatus for generating HARQ-ack codebook including measurement information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The method performed by a user equipment (UE) may comprise the steps of: receiving, from a base station, downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), wherein the DCI indicates whether to report a measurement result for the PDSCH; receiving the PDSCH on the basis of the DCI; when the DCI indicates to report the measurement result, transmitting, to the base station, hybrid automatic repeat request (HARQ) information for the PDSCH and the measurement result; and when the DCI indicates not to report the measurement result, transmitting, to the base station, the HARQ information for the PDSCH.

Description

Method and apparatus for generating a HARQ-ACK codebook containing measurement information in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for transmitting HARQ-ACK information and measurement information.

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

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

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

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

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

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

[0008] The present disclosure aims to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0009] According to one embodiment of the present disclosure, a method performed by user equipment (UE) may include the steps of: receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) from a base station; the DCI indicating whether to report a measurement result for the PDSCH; receiving the PDSCH based on the DCI; transmitting hybrid automatic repeat request (HARQ) information for the PDSCH and the measurement result to the base station when the DCI indicates to report the measurement result; and transmitting the HARQ information for the PDSCH to the base station when the DCI indicates not to report the measurement result.

[0010] According to one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided.

[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

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

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

[0014] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting 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 area of ​​a downlink control channel in a wireless communication system according to one 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 illustrating a method for a base station and a terminal to transmit and / or receive data in consideration of a downlink data channel 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 one embodiment of the present disclosure.

[0020] FIG. 9 is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval 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 the 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 dynamic HARQ-ACK codebook generation according to one embodiment of the present disclosure.

[0023] FIG. 12 illustrates bits for receiving measurement reports for one PDSCH when transmitting a dynamic HARQ-ACK codebook according to one embodiment of the present disclosure.

[0024] FIG. 13 illustrates bits for receiving measurement reports for one PDSCH when transmitting a dynamic HARQ-ACK codebook according to one embodiment of the present disclosure.

[0025] FIG. 14 illustrates bits for receiving measurement reports for two PDSCHs when transmitting a dynamic HARQ-ACK codebook according to one embodiment of the present disclosure.

[0026] FIG. 15 is a drawing of a dynamic HARQ-ACK codebook generated according to one embodiment of the present disclosure.

[0027] FIG. 16 is a drawing of a dynamic HARQ-ACK codebook generated according to one embodiment of the present disclosure.

[0028] FIG. 17 illustrates a method for generating a plurality of subcodebooks according to one embodiment of the present disclosure.

[0029] FIG. 18 illustrates a method for generating a plurality of sub-codebooks according to one embodiment of the present disclosure.

[0030] FIG. 19 illustrates a method for generating a dynamic HARQ-ACK codebook of a terminal according to one embodiment of the present disclosure.

[0031] FIG. 20 illustrates a method for generating a dynamic HARQ-ACK codebook for a terminal for a plurality of PDSCHs according to one embodiment of the present disclosure.

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

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

[0034] Efforts are being made to develop improved 5G communication systems or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G (generation) communication systems. For this reason, 5G communication systems or pre-5G communication systems are referred to as systems beyond 4G networks or systems following LTE. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place 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-centered network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0036] Accordingly, various attempts are being made to apply 5G communication systems (5th generation communication systems or 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 technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier 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 accompanying drawings.

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

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

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

[0041] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B (next generation Node B), an eNode B (Evolved Universal Terrestrial Radio Access (E-UTRA) Node B), a Node B, a BS (Base Station), a radio 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, and / or a multimedia system capable of performing communication functions. In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, while LTE (Long-Term Evolution), LTE-A (LTE-Advanced), or 5G systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included, and the 5G below may 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 made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure. The contents of the present disclosure are applicable to FDD (frequency division duplex) and TDD systems.

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

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

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

[0045] In describing the present disclosure below, if it is determined that a detailed description of related known functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description will be omitted. Embodiments of the present disclosure may be described below with reference to the attached drawings.

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

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

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

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

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

[0051] Finally, URLLC is a mission-critical cellular-based wireless communication service. Examples include services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and may simultaneously require a packet error rate of 10^-5 or less. Consequently, for services supporting URLLC, 5G systems must provide a Transmission Time Interval (TTI) smaller than for other services, and design considerations may be required to allocate wide resources within the frequency band to ensure the reliability of the communication link.

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

[0053] As various services can be provided following the development of mobile communication systems as described above, measures to effectively provide these services are required, and in particular, a method for a terminal to efficiently select a reporting mode and transmit control information is required.

[0054] More specifically, the present disclosure relates to a method for a terminal to select one of a plurality of reporting modes to transmit uplink control information, and an apparatus capable of performing the same.

[0055] [NR Time-Frequency Resources]

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

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

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

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

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

[0061]

[0062] [Bandwidth Section (BWP)]

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

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

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

[0066]

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

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

[0069] According to one embodiment, the settings for the bandwidth portion supported by the 5G communication system can be used for various purposes.

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

[0071] According to one embodiment, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support both data transmission and / or reception using a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, the base station may set two bandwidth portions to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and / or reception is to be performed at a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

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

[0073] According to one embodiment, in a method for setting a bandwidth part, terminals prior to RRC connection (Connected) can receive setting information for an Initial Bandwidth Part through a Master Information Block (MIB) during the initial connection stage. For example, a terminal can receive a Control Resource Set (CORESET) for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIB) can be transmitted from the MIB of a Physical Broadcast Channel (PBCH). The bandwidth of the control resource set by the MIB can be considered as the Initial Bandwidth Part, and through the set Initial Bandwidth Part, the terminal can receive a Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and Random Access.

[0074] [Bandwidth Section (BWP) Change]

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

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

[0077]

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

[0079] According to one embodiment, in accordance with the requirements for the bandwidth change delay time described above, when a terminal receives a DCI containing a bandwidth change indicator in slot n, the terminal may complete the change to the new bandwidth portion indicated by the bandwidth change indicator at a time not later than slot n + TBWP. The terminal may perform transmission and / or reception for the data channel scheduled by the DCI containing the bandwidth change indicator in the changed new bandwidth portion. When a base station intends to schedule a data channel to the new bandwidth portion, it may determine the time domain resource allocation for the data channel by taking into account the terminal's bandwidth change delay time (TBWP). For example, when a base station schedules a data channel to the new bandwidth portion, in the method of determining the time domain resource allocation for the data channel, the base station may schedule the data channel after the bandwidth change delay time. Accordingly, the terminal may not expect the DCI indicating the bandwidth change to indicate a slot offset value (e.g., K0 or K2) smaller than the bandwidth change delay time (TBWP).

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

[0081] [SS / PBCH Block]

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

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

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

[0085] - SSS: Serves as the standard for downlink time / frequency synchronization and can provide the remaining cell ID (identity) information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0086] - PBCH (physical broadcast channel): Can provide essential system information required for the transmission and / or reception of the terminal's data channel and control channel. The essential system information may include search space-related control information indicating wireless resource mapping information of the control channel, scheduling control information for a separate data channel transmitting system information, etc.

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

[0088] According to one embodiment, the terminal can detect PSS and / or SSS during the initial connection phase and can decode PBCH. The terminal can obtain MIB from PBCH and, through the obtained MIB, receive a Control Resource Set (CORESET) #0 (e.g., may correspond to a control resource set with a control resource index of 0). The terminal can perform monitoring of Control Resource Set #0 by assuming that the selected SS / PBCH block and the Demodulation Reference Signal (DMRS) transmitted from Control Resource Set #0 are Quasi Co Locationd (QCL). The terminal can receive system information as downlink control information transmitted from Control Resource Set #0. The terminal can obtain Random Access Channel (RACH) related configuration information required for initial connection 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 which block the terminal selected among the respective SS / PBCH blocks and that it is monitoring control area #0 associated with the selected block.

[0089] [PDCCH: DCI related]

[0090] Next, Downlink Control Information (DCI) in 5G systems will be explained in detail.

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

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

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

[0094] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, at least one of the IEs (information elements) in Table 4. Of course, it is not limited to the following examples.

[0095]

[0096] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the information in Table 5. Of course, it is not limited to the following examples.

[0097]

[0098]

[0099]

[0100] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the information in Table 6. Of course, it is not limited to the following examples.

[0101]

[0102] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the information in Table 7. Of course, it is not limited to the following examples.

[0103]

[0104]

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

[0106] In the following, the downlink control channel in a 5G communication system is described in more detail with reference to the drawings.

[0107] FIG. 4 illustrates an example of setting a control resource set (CORESET) 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 resources (control resource #1 (401), control resource #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) on the frequency axis and one slot (420) on the time axis. The control resources (401, 402) may be set to a specific frequency resource (403) within the entire terminal bandwidth part (410) on the frequency axis. On the time axis, they may be set to one or multiple OFDM symbols and can be defined as the control resource set duration (Control Resource Set Duration, 404). Referring to the example illustrated in FIG. 4, control resource #1 (401) is set to a control resource length of 2 symbols, and control resource #2 (402) is set to a control resource length of 1 symbol.

[0108] The control domain in the 5G communication system described above can be configured by the base station to the terminal via upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring the control domain to the terminal may mean providing information such as the control domain identifier, the frequency location of the control domain, and / or the symbol length of the control domain. For example, it may include the information in Table 8 below. Of course, it may not be limited to the following examples.

[0109]

[0110]

[0111] 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 have a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control area. Of course, it may not be limited to the following examples.

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

[0113] Referring to FIG. 5, this is an example of a basic unit of time and frequency resources that can be used in a 5G communication system according to one embodiment. Referring to FIG. 5, the basic unit of time and frequency resources that constitute the control channel can be called a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, for example, 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0114] 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), then 1 CCE (504) can be composed of multiple REGs (503). For example, the REG (503) illustrated in FIG. 5 can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), then 1 CCE (504) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the Aggregation Level (AL) within the control area. The CCEs (504) in the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0115] The basic unit of the downlink control channel, namely the REG (503) illustrated in FIG. 5, may include both the REs to which the DCI is mapped and the DMRS (505), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 5, three DMRS (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 the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode at a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

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

[0117] According to one embodiment, in a 5G communication system, parameters for a search space for a PDCCH can be set from a base station to a terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may set to the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control domain index to be monitored in the search space. For example, parameters for a search space for a PDCCH may include the information in [Table 9]. Of course, they are not limited to the following examples.

[0118]

[0119]

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

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

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

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

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

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

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

[0127] - DCI format 2_3 with CRC scrambled by TPC-SRS(sounding reference signal)-RNTI

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143]

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

[0145]

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

[0147] 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 for the terminal by the base station) and the time index.

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

[0149] [PDCCH: BD / CCE limit]

[0150] When multiple sets of search spaces are configured for a terminal, the following conditions may be considered in determining the set of search spaces that the terminal must monitor. Of course, the following examples are not limited to this.

[0151] If the terminal receives the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, as r15monitoringcapability, the terminal can define the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (e.g., the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot. If the value of monitoringCapabilityConfig-r16 is received as r16monitoringcapability, the terminal can define the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (e.g., the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per span.

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

[0153] As described above, M is the maximum number of PDCCH candidate groups that the terminal can monitor, depending on the setting value of the upper layer signaling. μ In a cell set to a subcarrier interval of 15·2^μ kHz, if defined based on slots, it may follow [Table 11] below, and if defined based on spans, it may follow [Table 12] below.

[0154]

[0155]

[0156] [Condition 2: Limit on Maximum CCEs]

[0157] As described above, depending on the setting value of the upper layer signaling, C, which is the maximum number of CCEs constituting the entire search space (for example, the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets), μ In a cell set to a subcarrier interval of 15·2^μ kHz, if defined based on slots, it may follow [Table 13] below, and if defined based on spans, it may follow [Table 14] below.

[0158]

[0159]

[0160] For the convenience of explanation, a situation in which both Condition 1 and Condition 2 are satisfied at a specific point in time is defined as “Condition A”. Therefore, not satisfying Condition A may mean not satisfying at least one of the above Conditions 1 and 2.

[0161] [PDCCH: Overbooking]

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

[0163] You can follow the method below to select some of the navigation spaces from the entire set of configured navigation spaces.

[0164] According to one embodiment, if condition A for PDCCH is not satisfied at a specific time point (slot), the terminal (or base station) may preferentially select a search space set in which the search space type is set as a common search space among the search space sets existing at that time point, over a search space set in which the search space type is set as a terminal-specific search space.

[0165] According to one embodiment, when all sets of search spaces set as common search spaces are selected (e.g., when condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) may select sets of search spaces set as terminal-specific search spaces. In this case, if there are multiple sets of search spaces set as terminal-specific search spaces, the search space set with a lower search space set index may have a higher priority. The terminal (or base station) may select sets of terminal-specific search spaces within the range where condition A is satisfied, taking priority into consideration.

[0166] [Regarding Rate Matching / Puncturing]

[0167] The rate matching and puncturing operations are described in detail below.

[0168] When a time and frequency resource A intended to transmit an arbitrary symbol sequence A overlaps with an arbitrary time and frequency resource B, rate matching or puncturing operations may be considered as transmission and / or reception operations of channel A, taking into account the area resource C where resource A and resource B overlap. Specific operations may follow the details below.

[0169] Rate Matching Operation

[0170] - A base station may transmit a symbol sequence A to a terminal by mapping Channel A only to the remaining resource area, excluding Resource C which corresponds to the area overlapping with Resource B, from the entire Resource A. For example, if symbol sequence A consists 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 may sequentially map and send symbol sequence A to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3} which corresponds to Resource C within Resource A. Consequently, the base station can transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #3} by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0171] According to one embodiment, a terminal can determine resource A and resource B from scheduling information for a symbol sequence A from a base station, and thereby determine resource C, which is an area where resource A and resource B overlap. The terminal can receive symbol sequence A by assuming that symbol sequence A is mapped and transmitted in the remaining area of ​​all resource A, excluding resource C. For example, if symbol sequence A consists 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 receive symbol sequence A by assuming that it is sequentially mapped to the remaining resources {resource #1, resource #2, resource #4}, excluding {resource #3} which corresponds to resource C among resource A. Consequently, the terminal can perform a subsequent series of receiving operations by assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #3} is transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0172] Puncturing action

[0173] According to one embodiment, if there is a resource C corresponding to an area overlapping with resource B among all resources A to which a base station intends to transmit a symbol sequence A to a terminal, the base station maps the 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 in the remaining resource area of ​​resource A excluding resource C. For example, if symbol sequence A consists 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} respectively, and can 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, and may not transmit {Symbol #3} mapped to {Resource #3} corresponding to resource C. Consequently, the base station can map and transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #4} to {Resource #1, Resource #2, Resource #4} respectively.

[0174] According to one embodiment, a terminal can determine resources A and B from scheduling information for a symbol sequence A from a base station, and thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive a symbol sequence A by assuming that the symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource A excluding resource C. For example, if symbol sequence A consists 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 by assuming that 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—is mapped and transmitted. Consequently, the terminal can perform a subsequent series of receiving operations by assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #4} has been transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0175] In the following, a method for setting rate matching resources is described for the purpose of rate matching in a 5G communication system. Rate matching can be understood as adjusting the size of a signal by considering the amount of resources available to transmit the signal. For example, rate matching of a data channel can be understood as adjusting the size of the data by mapping the data channel to a specific time and frequency resource range so that it is not transmitted.

[0176] FIG. 6 is a diagram illustrating a method for a base station and a terminal to transmit and / or receive data in consideration of a downlink data channel and rate matching resources according to one embodiment of the present disclosure.

[0177] Referring to FIG. 6, a downlink data channel (PDSCH, 601) and a rate matching resource (602) are illustrated. A base station may set one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). The setting information for the rate matching resources (602) may include time-axis resource allocation information (603), frequency-axis resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-axis resource allocation information (604) is named the “first bitmap,” the bitmap corresponding to the time-axis resource allocation information (603) is named the “second bitmap,” and the bitmap corresponding to the period information (605) is named the “third bitmap.” If all or part of the time and frequency resources of a scheduled data channel (601) overlap with a set rate matching resource (602), the base station can transmit the data channel (601) by rate matching it 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.

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

[0179] In a 5G system, the granularity of “RB symbol level” and “RE level” is supported by setting the aforementioned rate matching resources to a terminal. More specifically, the following setting method may be followed.

[0180] RB symbol level

[0181] According to one embodiment, the terminal may receive up to four RateMatchPatterns as upper-layer signaling for each bandwidth portion, and one RateMatchPattern may include the following contents. Of course, it is not limited to the following examples.

[0182] - As a Reserved Resource within the bandwidth portion, a resource may be included in which the time and frequency resource domains of the said Reserved Resource are set as a combination of an RB level bitmap and a symbol level bitmap along the frequency axis. The Reserved Resource may span one or two slots. Additionally, 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 set.

[0183] - It may include time and frequency domain resource areas set as control resource sets within the bandwidth portion, and resource areas corresponding to time domain patterns set as search space settings where the resource areas are repeated.

[0184] RE level

[0185] The terminal can receive the following configurations through upper-layer signaling. Of course, it is not limited to the examples below.

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

[0187] - It may include configuration information for resource sets corresponding to one or more ZP (Zero Power) CSI-RS within the bandwidth portion.

[0188] [Regarding LTE CRS rate match]

[0189] Next, the rate match process for the LTE CRS described above will be explained in detail. For the coexistence of LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR provides a function to set the pattern of the LTE CRS (Cell Specific Reference Signal) to the NR terminal. More specifically, the CRS pattern may be provided by RRC signaling that includes at least one parameter within the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the above parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0190] In Rel-15 NR, a function is provided to set one CRS pattern per serving cell through the above lte-CRS-ToMatchAround parameter. In Rel-16 NR, the function to set one CRS pattern per serving cell has been extended to allow for the setting of multiple CRS patterns per serving cell. For example, for a Single-TRP (transmission and reception point) configured terminal, one CRS pattern can be set per LTE carrier, and for a Multi-TRP configured terminal, two CRS patterns can be set per LTE carrier. For example, for a Single-TRP configured terminal, up to three CRS patterns per serving cell can be set through the above lte-CRS-PatternList1-r16 parameter. As another example, for a multi-TRP configured terminal, a CRS can be 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 configured as described above, whether to apply both the CRS patterns of TRP1 and TRP2 or only the CRS pattern of a single TRP 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 a single TRP is applied, whereas otherwise, both CRS patterns of the two TRPs can be applied.

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

[0192]

[0193]

[0194]

[0195]

[0196]

[0197]

[0198] [PDSCH: Regarding Frequency Resource Allocation]

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

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

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

[0202]

[0203] According to one embodiment, if the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that assign 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 the frequency axis resources continuously allocated therefrom, as described above.

[0204] According to one embodiment, 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 consisting of bits of the larger value (735) of a payload (715) for setting resource type 0 and a payload (720, 725) for setting resource type 1. Conditions for this will be explained later. At this time, one bit may be added to the most significant bits (MSB) of the frequency axis resource allocation information within the DCI, and if the added bit has a value of '0', it indicates that resource type 0 is used, and if it has a value of '1', it indicates that resource type 1 is used.

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

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

[0207] According to one embodiment, a base station may set a table for time domain resource allocation information for a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) for a terminal using upper layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of a maximum of maxNrofDL-Allocations = 16 entries may be set, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 16 entries may be set. For example, time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information regarding the position and length of the starting symbol for which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH and / or PUSCH. 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 examples.

[0208]

[0209]

[0210] According to one embodiment, a base station may notify a terminal of one of the entries in a table for the time domain resource allocation information described above via L1 signaling (e.g., DCI). For example, it may be indicated by the 'time domain resource allocation' field within the DCI. Based on the DCI received from the base station, the terminal may obtain time domain resource allocation information for PDSCH or PUSCH.

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

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

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

[0214] 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 by aligning with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is 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 based on the subcarrier interval of the PDCCH and in accordance with a predetermined slot offset K0.

[0215] [PUSCH: Regarding transmission method]

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

[0217] According to one embodiment, the configured grant Type 1 PUSCH transmission of the terminal can be semi-statically configured by receiving a configuredGrantConfig containing the rrc-ConfiguredUplinkGrant of [Table 20] through upper-layer signaling, without receiving a UL grant within the DCI. The configured grant Type 2 PUSCH transmission of the terminal can be semi-continuously scheduled by a UL grant within the DCI after receiving a configuredGrantConfig that does not contain the rrc-ConfiguredUplinkGrant of [Table 20] through upper-layer signaling. When the PUSCH transmission is operated by the configured grant, the parameters applied to the PUSCH transmission can be applied through the upper-layer signaling configuredGrantConfig of [Table 20], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by the upper-layer signaling pusch-Config of [Table 21]. 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] to PUSCH transmissions operated by the configured grant.

[0218]

[0219]

[0220]

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

[0222] According to one embodiment, as described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1 and can be semi-statically configured by a configured grant. If a terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal may perform beam configuration for the PUSCH transmission using a pucch-spatialRelationInfoID corresponding to a terminal-specific PUCCH resource corresponding to a minimum ID (identity) within an active uplink BWP in a serving cell. In this case, the PUSCH transmission may be based on a single antenna port. Within a BWP where a PUCCH resource containing pucch-spatialRelationInfo is not configured, the terminal may not expect scheduling for the PUSCH transmission via DCI format 0_0. If the terminal has not configured txConfig within pusch-Config of [Table 21], the terminal may not expect to be scheduled via DCI format 0_1.

[0223]

[0224]

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

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

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

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

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

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

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

[0232] According to one embodiment, if the value of resourceType in the upper layer signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS may be indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS may be indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the DCI may not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS may be located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the transmission configuration indication (TCI) states set on the scheduled subcarrier may not be set to QCL-TypeD.

[0233] According to one embodiment, if a periodic or semi-continuous SRS resource set is configured, the associated NZP CSI-RS may be indicated via the associated CSI-RS within the upper layer signaling, SRS-ResourceSet. For non-codebook-based transmission, the terminal does not expect the upper layer signaling, spatialRelationInfo, for the SRS resource and the associated CSI-RS within the upper layer signaling, SRS-ResourceSet, to be configured together.

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

[0235] According to one embodiment, a base station may transmit one NZP-CSI-RS connected to an SRS resource set to a terminal. Based on the results measured upon receiving the NZP-CSI-RS, the terminal may calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set. The terminal may apply the calculated precoder when transmitting one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, and the base station may select one or more SRS resources from among the received one or more SRS resources. In this case, in non-codebook-based PUSCH transmission, the SRI may represent an index capable of expressing a combination of one or more SRS resources, and the SRI may be included within the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of PUSCH, and the terminal can transmit PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0236] [PUSCH: Preparation Process Time]

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

[0238]

[0239] The aforementioned T in mathematical formula 2 proc,2 In this, each variable can have the following meanings.

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

[0241]

[0242]

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

[0244] - κ: 64

[0245] - μ: μ DL or μ UL Middle, T proc,2 This can follow a larger value. μ DL represents the numerology of the downlink through which a PDCCH containing a DCI scheduling PUSCH is transmitted, and μ UL can refer to the numerology of the uplink through which PUSCH is transmitted.

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

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

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

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

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

[0251] When considering the time-axis resource mapping information of the PUSCH scheduled via DCI and the influence of uplink-downlink timing advance, the base station and the terminal, starting from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, T proc,2 Subsequently, if the first symbol of the PUSCH starts before the first uplink symbol initiated by the CP, it can be determined that the PUSCH preparation time is insufficient. Otherwise, the base station and the terminal can determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only if the preparation time is sufficient, and can ignore the DCI scheduling the PUSCH if the preparation time is insufficient.

[0252] [CA / DC Related]

[0253] FIG. 10 is a diagram illustrating the 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.

[0254] 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 / or NR MAC (Medium Access Control 1040, 1055) at the terminal and the NR base station, respectively. Of course, it is not limited to examples and may include more or fewer layers.

[0255] According to one embodiment, the main functions of the NR SDAP (1025, 1070) may include some of the following functions. Of course, it is not limited to the examples below.

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

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

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

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

[0260] According to one embodiment, regarding an SDAP layer device, the terminal may receive a setting via an RRC message on whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. If the SDAP header is set, the base station may instruct the terminal to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for at least one of data processing priority or scheduling information to support smooth service.

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

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

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

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

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

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

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

[0268] - Retransmission of PDCP SDUs

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

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

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

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

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

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

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

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

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

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

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

[0280] - Duplicate detection

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

[0282] - RLC SDU discard function

[0283] RLC re-establishment function

[0284] According to one embodiment, the in-sequence delivery function of the NR RLC device may be referred to as a function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering the divided multiple RLC SDUs when a single RLC (radio link control) SDU (service data unit) is originally received divided into multiple RLC SDUs, a function of rearranging the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, or a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs described above may be processed in the order in which they are received (e.g., regardless of the order of 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, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the concatenation function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0285] According to one embodiment, the out-of-sequence delivery function of the NR RLC device may be referred to as a function that delivers RLC SDUs received from a lower layer directly to an upper layer regardless of order. The out-of-sequence delivery function may include a function of reassembling and delivering the divided multiple RLC SDUs when a single RLC SDU is originally received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0286] The NR MAC (1040, 1055) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions. Of course, it is not limited to the examples below.

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

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

[0289] - Scheduling information reporting function

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

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

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

[0293] - MBMS service identification function

[0294] - Transport format selection function

[0295] - Padding

[0296] The NR PHY layer (1045, 1050) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them over a wireless channel, or demodulating OFDM symbols received through a wireless channel and channel decoding them to transmit them to an upper layer. Of course, it is not limited to the above examples.

[0297] According to one embodiment, the detailed structure of the wireless protocol structure may vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer, such as 1000. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers at a single Transmission Reception Point (TRP), the base station and the terminal may use a protocol structure having a single structure up to the RLC, such as 1010, but multiplexing the physical layer (PHY layer) through the MAC layer. For example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers at multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to the RLC, such as 1020, but multiplexing the PHY layer through the MAC layer.

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

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

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

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

[0302] - MIB (Master Information Block)

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

[0304] - RRC (Radio Resource Control)

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

[0306] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling. Of course, it is not limited to the following examples.

[0307] - PDCCH (Physical Downlink Control Channel)

[0308] - DCI (Downlink Control Information)

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

[0310] - Group common DCI

[0311] - Common DCI

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

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

[0314] - PUCCH (Physical Uplink Control Channel)

[0315] - UCI (Uplink Control Information)

[0316] Dynamic HARQ-ACK Codebook

[0317] A terminal can transmit HARQ-ACK (hybrid automatic repeat request-acknowledgement) information bits for multiple PDSCHs (physical downlink shared channels) by multiplexing them on a single PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel). As an example of a method for multiplexing HARQ-ACK information bits for multiple PDSCHs, a dynamic HARQ-ACK codebook generation method may be as follows.

[0318] According to one embodiment, the terminal may receive a dynamic HARQ-ACK codebook generation setting from a base station. Unless otherwise noted, the dynamic HARQ-ACK codebook may not include multiple sub-codebooks in the following description. An embodiment in which the dynamic HARQ-ACK codebook includes multiple sub-codebooks is described later.

[0319] According to one embodiment, a terminal may receive scheduling information of a PDSCH (e.g., time and frequency resources, Modulation and coding scheme (MCS), Redundancy version (RV), HARQ process number, New data indicator (NDI), etc.) from a DCI (downlink control information) format that schedules a PDSCH. The terminal may be instructed on the transmission slot of a HARQ-ACK of a PDSCH based on the DCI (or DCI format). The terminal may multiplex HARQ-ACK information (e.g., HARQ-ACK IEs (information elements)) of PDSCHs corresponding to the same HARQ-ACK transmission slot and transmit them through a PUCCH or PUSCH in the HARQ-ACK transmission slot.

[0320] According to one embodiment, the HARQ-ACK information bits corresponding to the PDSCH may be 1 bit or 2 bits. For example, if the PDSCH is configured to include up to 1 transport block, the terminal may generate 1 bit as the HARQ-ACK information bits corresponding to the PDSCH. For example, if the PDSCH is configured to include up to 2 transport blocks, the terminal may generate 2 bits as the HARQ-ACK information bits corresponding to the PDSCH. For example, the first bit may be a HARQ-ACK information bit corresponding to the first transport block, and the second bit may be a HARQ-ACK information bit corresponding to the second transport block. If the PDSCH includes only one transport block, the second bit may be a NACK (negative-ACK).

[0321] Unless otherwise specified in the present disclosure, the HARQ-ACK information bits corresponding to PDSCH are described as 2 bits.

[0322] According to one embodiment, the DCI format for scheduling PDSCH may include a counter DAI (Downlink Assignment Index) to a total DAI.

[0323] According to one embodiment, Counter DAI can be used to determine the order of HARQ-ACK information bits of a PDSCH scheduled by a DCI format within a dynamic HARQ-ACK codebook. For example, Counter DAI can be a value of 1, 2, 3, or 4. For example, if the counter DAI of the first DCI format is 1 and the counter DAI of the second DCI format is 2, the HARQ-ACK information bits of the PDSCH scheduled by the first DCI format in the dynamic HARQ-ACK codebook can be placed in a position preceding the HARQ-ACK information bits of the PDSCH scheduled by the second DCI format.

[0324] According to one embodiment, Total DAI can be used to determine the number of DCI formats corresponding to the dynamic HARQ-ACK codebook. For example, Total DAI can be a value of 1, 2, 3, or 4. For example, if the value of Total DAI is n, the dynamic HARQ-ACK codebook may contain HARQ-ACK information bits of 4*i+n (i=0,1,2,...) DCI formats.

[0325] For example, the definitions of Counter DAI and total DAI in the TS 38.213 document may be as shown in the following Table 24.

[0326]

[0327] FIG. 11 is a diagram illustrating the generation of a dynamic HARQ-ACK codebook according to one embodiment. The terminal can generate a dynamic HARQ-ACK codebook based on Counter DAI to Total DAI. Counter DAI will be described in the following description. The same embodiment may also be used with Total DAI.

[0328] Referring to FIG. 11, the terminal can determine (or identify) five PDSCHs corresponding to PUCCH or PUSCH. For example, the DCI format for scheduling PDSCH may include Counter DAI values. For example, the Counter DAI value corresponding to PDSCH#0 (1100) may be 1 (cDAI=1), the Counter DAI value corresponding to PDSCH#1 (1101) may be 2 (cDAI=2), the Counter DAI value corresponding to PDSCH#2 (1102) may be 3 (cDAI=3), the Counter DAI value corresponding to PDSCH#3 (1103) may be 4 (cDAI=4), and the Counter DAI value corresponding to PDSCH#4 (1104) may be 1 (cDAI=1).

[0329] According to one embodiment, the terminal can determine HARQ-ACK information bits corresponding to each PDSCH. For example, the HARQ-ACK information bits corresponding to PDSCH#0 (1100) are {b 0,0 , b 0,1} and the HARQ-ACK information bits corresponding to PDSCH#1(1101) are {b 1,0 , b 1,1} and the HARQ-ACK information bits corresponding to PDSCH#2(1102) are {b 2,0 , b 2,1} and the HARQ-ACK information bits corresponding to PDSCH#3(1103) are {b 3,0 , b 3,1} and the HARQ-ACK information bits corresponding to PDSCH#4(1104) are {b 4,0 , b 4,1} and the HARQ-ACK information bits corresponding to PDSCH#5(1105) are {b 5,0 , b 5,1 It can be.

[0330] According to one embodiment, the terminal can generate a dynamic HARQ-ACK codebook by multiplexing the HARQ-ACK information bits of the PDSCHs according to the order of the Counter DAI. For example, the generated dynamic HARQ-ACK codebook is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 It is and can contain 10 bits.

[0331] For reference, the terminal may fail to receive some DCI formats. For example, it may fail to receive the DCI format scheduling PDSCH#1 (1101). In this case, the terminal can obtain Counter DAI values ​​of 1 and 3 from the DCI formats scheduling PDSCH#0 and PDSCH#2. Therefore, it can determine that the reception of the DCI format corresponding to Counter DAI value 2 has failed. Accordingly, the terminal uses {b as the HARQ-ACK bits corresponding to the DCI format corresponding to Counter DAI value 2. 1,0 , b 1,1 It can be determined as}={NACK,NACK}.

[0332] Referring to FIG. 11(a), the number of HARQ-ACK information bits for DCI formats corresponding to the dynamic HARQ-ACK codebook may be the same. For example, the number of HARQ-ACK information bits may be the same at 2 bits. If the number of HARQ-ACK information bits differs for each DCI format (e.g., 1 bit corresponds to some DCI formats and 2 bits correspond to others), the following problem may occur.

[0333] For example, a terminal may fail to receive a DCI format scheduling PDSCH#1 (1101). In this case, the terminal can obtain Counter DAI values ​​of 1 and 3 from DCI formats scheduling PDSCH#0 and PDSCH#2. Therefore, the terminal can determine that the reception of the DCI format corresponding to Counter DAI value 2 has failed. However, in this case, the terminal cannot determine the number of HARQ-ACK information bits corresponding to the DCI format. For example, the terminal may generate a dynamic HARQ-ACK codebook assuming that the HARQ-ACK information is 1 bit, but the base station may transmit a DCI format corresponding to 2 bits as HARQ-ACK information. In this case, the size of the dynamic HARQ-ACK codebook transmitted by the terminal and the dynamic HARQ-ACK codebook assumed by the base station may differ. Therefore, the number of HARQ-ACK bits corresponding to the DCI format must always be the same.

[0334] Referring to FIG. 11(b), when a terminal transmits a dynamic HARQ-ACK codebook in PUCCH to PUSCH, the codebook may multiplex together the HARQ-ACK information of PDSCH and the reception measurement information of PDSCH. For example, the term "reception measurement information" in the present disclosure may be replaced with the term "measurement information."

[0335] The number of bits corresponding to the received measurement information of a single PDSCH may be X bits, and the number of bits may be a value set by the base station. For example, the terminal may receive the number of bits through a radio resource control (RRC) message. For example, for convenience, X may be described as 4 in this disclosure.

[0336] According to one embodiment, the terminal may report HARQ-ACK information and PDSCH reception measurement information for all PDSCHs according to the settings of the base station. For example, in a dynamic HARQ-ACK codebook, each PDSCH may always include 2 bits of HARQ-ACK information and reception measurement information (e.g., X=4 bits). In this case, a dynamic HARQ-ACK codebook may be generated by assuming that the number of HARQ-ACK bits corresponding to the DCI format is 2+X bits.

[0337] According to one embodiment, the terminal may report only HARQ-ACK information for some PDSCHs and report both HARQ-ACK information and reception measurement information for other PDSCHs, depending on the configuration of the base station. That is, different numbers of bits may correspond according to the DCI format. For example, the terminal may transmit only HARQ-ACK information without reception measurement information to the base station for at least one first PDSCH, and may transmit HARQ-ACK information along with reception measurement information for at least one second PDSCH.

[0338] According to one embodiment, the terminal can determine (or identify) whether to report received measurement information based on at least one of the following methods.

[0339] In the first method, the base station may instruct the terminal whether to report reception measurement information in the DCI format that schedules the PDSCH. For example, the DCI format that schedules the PDSCH may include information (e.g., 1 bit of information) indicating whether to report reception measurement information. For example, if the value of the 1 bit is '0', the report of reception measurement information may be omitted for the PDSCH scheduled by the DCI format. That is, the terminal may report HARQ-ACK information for the PDSCH but not report reception measurement information. Therefore, the DCI format may correspond to 2 bits. (e.g., the number of bits in the DCI may be 2 bits.) For example, if the value of the 1 bit is '1', the report of reception measurement information may be included for the PDSCH scheduled by the DCI format. That is, HARQ-ACK information and reception measurement information may be reported together for the PDSCH. Therefore, the DCI format may correspond to 2+X=2+4=6 bits.

[0340] In a second method, whether to report received measurement information can be determined based on the values ​​of fields included in the DCI format that schedules the PDSCH.

[0341] - For example, if the HARQ process number (HPN) field is a specific value, a report of incoming measurement information may be included.

[0342] - For example, if the Redundancy Version (RV) field is a specific value, incoming measurement information reporting may be included.

[0343] - For example, if the Modulation and coding scheme (MCS) field is a specific value, a received measurement information report may be included. For example, if the New data indicator (NDI) field is a specific value, a received measurement information report may be included. As an example, if the value corresponding to the New data indicator (NDI) field indicates an initial transmission, the terminal may include a received measurement information report. As another example, if the value corresponding to the New data indicator (NDI) field indicates a retransmission, the terminal may include a received measurement information report.

[0344] For example, if the Time domain resource assignment (TDRA) field indicates a specific value (specific row), a report of received measurement information may be performed. For example, if the PDSCH mapping type corresponding to the TDRA field is a specific value, a report of received measurement information may be performed. For example, if the start symbol of the PDSCH corresponding to the TDRA field is a specific value (or is smaller than a specific value, or is larger than a specific value), a report of received measurement information may be performed. For example, if the length (number of OFDM symbols) of the PDSCH corresponding to the TDRA field is a specific value (or is smaller than a specific value, or is larger than a specific value), a report of received measurement information may be performed. For example, if the last symbol of the PDSCH corresponding to the TDRA field is a specific value (or is smaller than a specific value, or is larger than a specific value), a report of received measurement information may be performed.

[0345] - For example, if the physical layer priority field is a specific value (e.g., high priority), received measurement information reporting may be included.

[0346] - For example, if the value of the Downlink assignment index (DAI) field is a specific value, incoming measurement information may be reported. For example, if the counter DAI value of the DAI field is a specific value, incoming measurement information may be reported. For example, if the total DAI value of the DAI field is a specific value, incoming measurement information may be reported.

[0347] - For example, if the TPC command for scheduled PUCCH field is a specific value, a report of received measurement information may be included. For example, if the TPC command for scheduled PUCCH field increases the PUCCH transmission power, a report of received measurement information may be included. As another example, if the TPC command for scheduled PUCCH field decreases the PUCCH transmission power, a report of received measurement information may be included. For example, if the TPC command for scheduled PUCCH field does not change the PUCCH transmission power, a report of received measurement information may be included.

[0348] - For example, if the PUCCH resource indicator field has a specific value, a report of incoming measurement information may be included.

[0349] - For example, if the PDSCH-to-HARQ_feedback timing indicator field is a specific value, a report of incoming measurement information may be included. For example, if the K1 value indicated by the PDSCH-to-HARQ_feedback timing indicator field is less than (less than or equal to) a specific value, a report of incoming specific information may be included.

[0350] - For example, if the PDSCH group index field is a specific value, a report of incoming measurement information may be included.

[0351] - For example, if the Transmission configuration indication field is a specific value, a report of incoming measurement information may be included. Therefore, a report of incoming measurement information may be included only for a specific beam or QCL (Quasi-Colocation).

[0352] - For example, if the SRS request or SRS offset indicator is at a specific value, a report of received measurement information may be included. For example, if the SRS request does not trigger the SRS and the SRS offset indicator is at a specific value, a report of received measurement information may be performed.

[0353] - For example, if the DMRS (demodulation reference signal) sequence initialization field is a specific value, a report of received measurement information may be included. That is, a report of received measurement information may be performed for a specific DMRS sequence.

[0354] The specific value described above may be one or more values. For example, the specific value described above may be set by a base station. For example, the specific value described above may be set to the terminal by a base station via at least one of an RRC message, MAC CE, or DCI.

[0355] In a third method, PDSCH can determine whether to include a received measurement information report based on scheduling information.

[0356] - For example, if PDSCH includes only one TB (transport block), it may include a report of received measurement information, and if it includes multiple TBs, it may not include a report of received measurement information.

[0357] - For example, if the PDSCH is a semi-persistent scheduled (SPS) PDSCH, incoming measurement information reporting may be included, and if it is a dynamic grant (DG) PDSCH, incoming measurement information reporting may not be included. Conversely, if the PDSCH is a semi-persistent scheduled (SPS) PDSCH, incoming measurement information reporting may not be included, and if it is a dynamic grant (DG) PDSCH, incoming measurement information reporting may be included.

[0358] - For example, if the size of the TB included in PDSCH exceeds a specific value, the received measurement information report may be included, and if it is equal to or less than the specific value, the received measurement information report may not be included. Conversely, if the size of the TB included in PDSCH is less than the specific value, the received measurement information report may be included, and if it exceeds the specific value, the received measurement information report may not be included.

[0359] - For example, if the number of resource elements (REs) or resource blocks (RBs) or symbols scheduled in PDSCH exceeds a specific value, a report of received measurement information may be included, and if it does not exceed the specific value, a report of received measurement information may not be included. Conversely, if the number of resource elements or RBs or symbols scheduled in PDSCH does not exceed a specific value, a report of received measurement information may be included, and if it exceeds the specific value, a report of received measurement information may not be included.

[0360] - For example, if a PDSCH is scheduled for a specific slot or a specific time interval, a reception measurement information report may be included. For example, the specific slot or specific time interval may be set by the base station. For example, the specific slot or specific time interval may be set periodically. For example, one specific slot may be set for every P slots. If P=10, one slot for every 10 slots is set as a specific slot, and a reception measurement information report may be included for the PDSCH scheduled in said one slot. For example, Q slots may be set as specific time intervals for every P slots. The Q slots may be consecutive slots. Or, the Q slots may be set by the base station among the P slots. For example, the base station may indicate the Q slots through a P-bits bitmap. Here, if the bitmap is '1', it may be included in a specific time interval. A reception measurement information report may be included for the PDSCH scheduled in said Q slots.

[0361] - For example, if the DCI format scheduling the PDSCH is a specific DCI format, a received measurement information report may be included. For example, the specific DCI format may be DCI format 1_1 to DCI format 1_2. Or the specific DCI format may be set by the base station.

[0362] According to the above first to third methods, the terminal can report HARQ-ACK information and reception measurement information for a PDSCH scheduled in a specific DCI format. If the terminal does not receive the DCI format, the terminal may find it difficult to determine the number of bits corresponding to the DCI format. Methods for resolving this are disclosed.

[0363] <1st Embodiment: Generating a dynamic HARQ-ACK codebook based on the sum of HARQ-ACK bits and bits of received measurement information>

[0364] In a first embodiment of the present disclosure, a terminal can generate a dynamic HARQ-ACK codebook based on the sum of HARQ-ACK bits and bits of received measurement information. For example, when the number of HARQ-ACK bits generated per PDSCH is denoted as Y bits and the number of received measurement information bits is denoted as X bits, the terminal can generate a dynamic HARQ-ACK codebook based on X+Y bits.

[0365] Referring to FIGS. 11(a) and 11(b), a dynamic HARQ-ACK codebook transmitted by the terminal to PUCCH or PUSCH may correspond to five PDSCHs. Thus, the dynamic HARQ-ACK codebook may contain 5*(X+Y) bits. For each PDSCH, the terminal may be instructed to include a received measurement information report in the HARQ-ACK information or not to include it. The terminal may generate X+Y bits for each PDSCH. For example, if the terminal is instructed to include a received measurement information report for a PDSCH (e.g., PDSCH#3 (1153)), X bits of the X+Y bits corresponding to the PDSCH may include a valid received measurement information report. If no received measurement information is reported to the PDSCH (e.g., PDSCH#0 (1150)), X bits among the X+Y bits may contain a specific value (e.g., all '0's) indicating that no received measurement information is reported.

[0366] <Second Embodiment: Setting the Maximum Number of Received Measurement Information Reports Per Dynamic HARQ-ACK Codebook>

[0367] According to one embodiment of the present disclosure, a terminal may receive from a base station a maximum number of received measurement reports per dynamic HARQ-ACK codebook. For example, the terminal may receive from the base station a maximum number of received measurement reports via at least one of an RRC message, MAC CE, or DCI. For example, the terminal may receive a setting for how many PDSCHs among the PDSCHs for which HARQ-ACK information bits are multiplexed should have received measurement reports included using the dynamic HARQ-ACK codebook. If the terminal receives a setting of N, the dynamic HARQ-ACK codebook may include received measurement information reports for up to N PDSCHs. If the terminal is requested to receive received measurement reports for more than N PDSCHs, the terminal may determine (or identify) this as an error case. Alternatively, if the terminal is requested to receive received measurement reports for more than N PDSCHs, it may include received measurement reports for the most recent (latest in time) N PDSCHs in the dynamic HARQ-ACK codebook.

[0368] According to one embodiment, when a terminal transmits a dynamic HARQ-ACK codebook, it may always include bits for reporting reception measurement information for N PDSCHs. (e.g., N may be a value set by the base station, such as 1, 2, ...) For example, if the bits for reporting reception measurement information are X bits, the size of the dynamic HARQ-ACK codebook may be n_HARQ-ACK + N*X bits. For example, n_HARQ-ACK may be the number of HARQ-ACK information bits included in the dynamic HARQ-ACK codebook and may be determined based on Counter DAI and total DAI. Accordingly, the size of n_HARQ-ACK in different PUCCH or PUSCH may vary depending on the base station's PDSCH scheduling. However, N*X bits may be fixed.

[0369] FIGS. 12 and 13 are diagrams illustrating bits for receiving measurement reports for one PDSCH when transmitting a dynamic HARQ-ACK codebook according to one embodiment.

[0370] Referring to FIG. 12, the terminal may receive five PDSCHs for scheduling, and the terminal may multiplex and transmit the HARQ-ACK bits of the five PDSCHs to PUCCH or PUSCH. For example, the DCI format for scheduling PDSCHs may include Counter DAI values. For example, the Counter DAI value corresponding to PDSCH#0 (1200) may be 1 (cDAI=1), the Counter DAI value corresponding to PDSCH#1 (1201) may be 2 (cDAI=2), the Counter DAI value corresponding to PDSCH#2 (1202) may be 3 (cDAI=3), the Counter DAI value corresponding to PDSCH#3 (1203) may be 4 (cDAI=4), and the Counter DAI value corresponding to PDSCH#4 (1204) may be 1 (cDAI=1).

[0371] According to one embodiment, the terminal can determine HARQ-ACK information bits corresponding to each PDSCH. The HARQ-ACK information bits corresponding to PDSCH#0 (1200) are {b 0,0 , b 0,1} and the HARQ-ACK information bits corresponding to PDSCH#1(1201) are {b 1,0 , b 1,1} and the HARQ-ACK information bits corresponding to PDSCH#2(1202) are {b 2,0 , b 2,1} and the HARQ-ACK information bits corresponding to PDSCH#3(1203) are {b 3,0 , b 3,1} and the HARQ-ACK information bits corresponding to PDSCH#4(1204) are {b 4,0 , b 4,1} and the HARQ-ACK information bits corresponding to PDSCH#5(1205) are {b 5,0 , b 5,1}am.

[0372] According to one embodiment, the terminal may generate a portion of HARQ-ACK bits (e.g., n_HARQ-ACK bits) of a dynamic HARQ-ACK codebook by multiplexing the HARQ-ACK information bits of the PDSCHs according to the order of Counter DAI. For example, the generated dynamic HARQ-ACK codebook is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1} and can include n_HARQ-ACK = 10 bits.

[0373] Referring to Fig. 12, the base station may instruct only the reporting of HARQ-ACK information for the five PDSCHs. In this case, there may be no received measurement information reports corresponding to the dynamic HARQ-ACK codebook. Therefore, there may be no information to report in the X bits corresponding to the receiving measurement information reports in the dynamic HARQ-ACK codebook. In this case, the value of (m0, m1, m2, m3) where X=4 bits can be determined as a specific value. For example, the specific value may indicate that the terminal has no information to report as receiving measurement information. For example, the specific value may be all '0'. That is, if the terminal instructs (m0, m1, m2, m3) = (0,0,0,0), it may indicate that the terminal has no information to report as receiving measurement information.

[0374] Therefore, the dynamic HARQ-ACK codebook generated by the terminal is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 , m0, m1, m2, m3} = {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 It can be , 0, 0, 0, 0}.

[0375] Referring to FIG. 13, a terminal according to one embodiment may be instructed to include a received measurement information report for one PDSCH (PDSCH#3 (1303)).

[0376] According to FIG. 13, identical to FIG. 12, the terminal can generate a portion of HARQ-ACK bits (n_HARQ-ACK bits) of a dynamic HARQ-ACK codebook. For example, the generated dynamic HARQ-ACK codebook is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1} and can include n_HARQ-ACK = 10 bits.

[0377] According to one embodiment, when the terminal receives PDSCH#3, the terminal may generate X bits as received measurement information and include the information in a dynamic HARQ-ACK codebook. For example, the values ​​of (m0, m1, m2, m3) in X bits may be non-specific values. For example, specific values ​​may be values ​​indicating that there is no information for the terminal to report as received measurement information. For example, when specific values ​​are (0, 0, 0, 0), they may be values ​​where (m0, m1, m2, m3) ≠ (0, 0, 0, 0). Therefore, the dynamic HARQ-ACK codebook generated by the terminal is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 , m0, m1, m2, m3} = {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1m0, m1, m2, m3} can be.

[0378] According to one embodiment, if the terminal does not receive PDSCH#3, the terminal has no information to include in the reception measurement information report in the dynamic HARQ-ACK codebook, so the value of (m0, m1, m2, m3), which is X bits, can be set to a specific value. For example, (m0, m1, m2, m3) can be set to (0,0,0,0). Therefore, the dynamic HARQ-ACK codebook generated by the terminal is {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 , m0, m1, m2, m3} = {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1 It can be 0, 0, 0, 0}.

[0379] According to one embodiment, when a terminal transmits a dynamic HARQ-ACK codebook, if the maximum number (N) of PDSCHs for reporting received measurement information is set to 1, the terminal may include received measurement information (e.g., X bits) of one PDSCH in X bits of the dynamic HARQ-ACK codebook. However, if N > 1, the terminal must include received measurement information (e.g., X bits) of one PDSCH in X bits of N*X bits of the dynamic HARQ-ACK codebook. Here, the terminal may determine X bits among N*X bits. Methods for solving this are disclosed.

[0380] According to one embodiment, if N > 1, the terminal may include a new field in the DCI format. For example, depending on the value of the new field, the position of X bits among N*X bits may be indicated. The length of the new field may be ceil(log2(N)). If N=2 (maximum 2 PDSCHs), the length of the new field may be 1 bit; if N=3 (maximum 3 PDSCHs), the length of the new field may be 2 bits; and if N=4 (maximum 4 PDSCHs), the length of the new field may be 2 bits. For example, if the new field is 1 bit and the bit value is '0', the received measurement information may be included in the first X bits among N*X bits. If the new field is 1 bit and the bit value is '1', the received measurement information may be included in the second X bits among N*X bits. For example, if the new field is 2 bits and the bit value is '00', the received measurement information may be included in the first X bits of the N*X bits. If the new field is 2 bits and the bit value is '01', the received measurement information may be included in the second X bits of the N*X bits. If the new field is 2 bits and the bit value is '10', the received measurement information may be included in the third X bits of the N*X bits. If the new field is 2 bits and the bit value is '11', the received measurement information may be included in the fourth X bits of the N*X bits.

[0381] According to one embodiment, the terminal may include a new field in the DCI format. Depending on the value of the new field, whether to perform a received measurement information report and the position of X bits among N*X bits may be indicated. The length of the new field may be ceil(log2(N+1)). If N=1 (maximum 1 PDSCH), the length of the new field may be 1 bit; if N=2 (maximum 2 PDSCHs), the length of the new field may be 2 bits; and if N=4 (maximum 4 PDSCHs), the length of the new field may be 3 bits. For example, if N=1, the new field (1 bit) may be '0', the received measurement information report may not be included. For example, if N=1, the new field (1 bit) may be '1', the received measurement information report (X bits) may be included in the X bits for the received measurement information report of the dynamic HARQ-ACK codebook. For example, if N=2 and the new field (2 bits) is '00', the received measurement information report may not be included. For example, if N=2 and the new field (2 bits) is '01', the received measurement information report (X bits) may be included in the first X bits of the 2*X bits for the received measurement information report of the dynamic HARQ-ACK codebook. For example, if N=2 and the new field (2 bits) is '10', the received measurement information report (X bits) may be included in the second X bits of the 2*X bits for the received measurement information report of the dynamic HARQ-ACK codebook.

[0382] Figure 14 is a diagram illustrating the bits for receiving measurement reports for two PDSCHs when transmitting a dynamic HARQ-ACK codebook.

[0383] Referring to Fig. 14, the dynamic HARQ-ACK codebook generated by the terminal always uses 2*X=2*4=8 bits {m} to report reception measurement information for two PDSCHs.0,0 , m 0,1 , m 0,2 , m 0,3 , m 1,0 , m 1,1 , m 1,2 , m 1,3} may be included. The terminal may receive five PDSCHs scheduled from the base station. The DCI format corresponding to each PDSCH may include an indicator indicating whether to include the received measurement information report and / or an indicator indicating the location of the received measurement information within 8 bits. For example, the DCI format scheduling PDSCH#0, PDSCH#1, and PDSCH#4 may indicate that the received measurement information report is not included in the HARQ-ACK codebook. The DCI format scheduling PDSCH#2 and PDSCH#3 may indicate that the received measurement information report is included in the HARQ-ACK codebook. And, the DCI format scheduling PDSCH#2 indicates the first X=4 bits {m of 2*X=8 bits 0,0 , m 0,1 , m 0,2 , m 0,3 It can indicate that received measurement information reports are included in}, and the DCI format scheduling PDSCH#3 is the second X=4 bits {m of 2*X=8 bits 1,0 , m 1,1 , m 1,2 , m 1,3 It can indicate that the received measurement information report is included in}.

[0384] According to the first embodiment, when a terminal generates a dynamic HARQ-ACK codebook, it may always include bits for reporting received measurement information. Accordingly, uplink resource consumption or power consumption may occur for the terminal to transmit the dynamic HARQ-ACK codebook. To improve this, the number of bits for reporting received measurement information in the dynamic HARQ-ACK codebook may be variable. The method of variation may be at least one of the following methods.

[0385] - A variable method based on MAC (medium access control)-CE (control element). A terminal may receive a MAC-CE signal from a base station. The terminal may be instructed to receive an N value based on the MAC-CE signal. When the terminal receives the MAC-CE signal in a specific slot, the terminal may apply the instructed N value to a PUCCH or PUSCH transmitted in a slot after a certain time from the specific slot. For example, the certain time may be 3ms or the number of slots included in 3ms. For example, the certain time may be set by the base station.

[0386] - Method for indicating a maximum number in a field of a DCI format. A terminal may receive a DCI format. For example, the DCI format may be a DCI format for scheduling PDSCH or a group common DCI format. For example, the terminal may be indicated a maximum number (value of N) from a field of the DCI format. For example, the field may indicate at least one of the following.

[0387] From the field, the terminal can obtain whether the dynamic HARQ-ACK codebook contains a report of received measurement information. For example, the field may be 1 bit, and if the bit is '0', the terminal can determine that there are no bits for the report of received measurement information in the dynamic HARQ-ACK codebook. That is, the size of the dynamic HARQ-ACK codebook may be n_HARQ-ACK. If the bit is '1', the terminal can determine that there are bits for the report of received measurement information in the dynamic HARQ-ACK codebook. That is, the size of the dynamic HARQ-ACK codebook may be n_HARQ-ACK + N*X bits. Here, the value of N may be a maximum number set by the base station.

[0388] * From the field, the terminal can obtain the maximum number of received measurement information reports in the dynamic HARQ-ACK codebook. The field may be B bits, where B is the maximum number of candidate values ​​(N1, N2, ..., N) set by the base station for the terminal. T It can be determined based on the number of ). For example, B = ceiling(log2(T)). For example, T is the maximum number of candidate values ​​(N1, N2, ..., N) set by the base station for the terminal. T It can be the number of ). For reference, N1 can be 0 without separate settings of the base station. For example, if T=2 is set (N1 and N2 are set), if 1 bit is '0', the terminal can determine that there are N1*X bits for reporting received measurement information in the dynamic HARQ-ACK codebook. That is, the size of the dynamic HARQ-ACK codebook can be n_HARQ-ACK + N1*X bits. For example, if the bit is '1', the terminal can determine that there are N2*X bits for reporting received measurement information in the dynamic HARQ-ACK codebook. That is, the size of the dynamic HARQ-ACK codebook can be n_HARQ-ACK + N2*X bits.

[0389] For reference, the terminal may assume that it will be instructed to the same maximum number (e.g., value of N) for the same dynamic HARQ-ACK codebook. That is, if a different value is instructed, the terminal may determine (or identify) this as an error case. For example, if a different value is instructed, the terminal may determine the most recently received maximum value as the valid value. That is, it may determine (or identify) whether to include and the length of the received measurement information report based on the most recently received maximum value.

[0390] - Method to exclude received measurement information reporting when specific conditions are met.

[0391] If a terminal receives only one PDSCH and includes the HARQ-ACK information of that one PDSCH in the dynamic HARQ-ACK codebook, and the DCI format scheduling the one PDSCH does not instruct the inclusion of the received measurement information report, the terminal may exclude the bits for the received measurement information report from the dynamic HARQ-ACK codebook.

[0392] If N>1 is set, and the terminal receives only one PDSCH and includes the HARQ-ACK information of that single PDSCH in the dynamic HARQ-ACK codebook, the terminal may include only X bits in the HARQ-ACK codebook for reporting received measurement information. That is, it may include only X bits out of N*X bits and exclude (N-1)*X bits.

[0393] If N>1 is set and the terminal receives only M PDSCHs and includes the HARQ-ACK information of the said M PDSCHs in the dynamic HARQ-ACK codebook, the terminal may include only min(M,N)*X bits for reporting reception measurement information. That is, among the N*X bits, only min(M,N)*X bits are included, and (min(M,N)-1)*X bits are excluded.

[0394] Although the above-described embodiment describes a dynamic HARQ-ACK codebook, it can be applied substantially the same way to a general HARQ-ACK codebook. For example, N*X bits may be attached to a semi-static HARQ-ACK codebook to report received measurement information.

[0395] <Third Embodiment: Creation of a first sub-codebook for reporting HARQ-ACK information and a second sub-codebook for reporting HARQ-ACK information and received measurement information>

[0396] In a third embodiment of the present disclosure, a dynamic HARQ-ACK codebook may be composed of a plurality of sub-codebooks. A PDSCH (or a corresponding DCI format) may correspond to one sub-codebook. For example, regarding a PDSCH (or a corresponding DCI format), if the terminal is not instructed to report received measurement information, the HARQ-ACK information of the PDSCH (or a corresponding DCI format) may be included in a first sub-codebook. For example, the bits corresponding to the PDSCH (or a corresponding DCI format) may be Y bits. If the terminal is instructed to report received measurement information regarding the PDSCH (or a corresponding DCI format), the HARQ-ACK information of the PDSCH (or a corresponding DCI format) and the received measurement information may be included in a second sub-codebook. For example, the bits corresponding to the PDSCH (or a corresponding DCI format) may be X+Y bits.

[0397] To describe the present embodiment, a first type PDSCH (or a corresponding first type DCI format) may represent a PDSCH that is not instructed to report received measurement information, and a second type PDSCH (or a corresponding second type DCI format) may represent a PDSCH that is instructed to report received measurement information. For example, the DCI fields and DCI lengths included in the first type DCI format and the second type DCI format may be the same. For example, the type may be distinguished based on whether or not there is an instruction to report received measurement information, and the type may not refer to a separate DCI format.

[0398] According to one embodiment, the DCI format may include a DAI field for generating a dynamic HARQ-ACK codebook. For example, a counter DAI value and a total DAI value may be indicated from the DAI field.

[0399] According to one embodiment, the terminal can obtain a counter DAI value and / or a total DAI value from the DAI field of the DCI format. If the DCI format is a first type DCI format, the terminal can determine (or identify) that the counter DAI value and / or the total DAI value correspond to a first sub-codebook. For convenience, the counter DAI value and the total DAI value may be referred to as the first counter DAI value and the first total DAI value. If the DCI format is a second type DCI format, the terminal can determine (or identify) that the counter DAI value and / or the total DAI value correspond to a second sub-codebook. For convenience, the counter DAI value and the total DAI value may be referred to as the second counter DAI value and the second total DAI value.

[0400] According to one embodiment, the terminal may use a first counter DAI value and a first total DAI value to generate a first sub-codebook. The terminal may use a second counter DAI value and a second total DAI value to generate a second sub-codebook.

[0401] FIG. 15 is a diagram showing the generation of a dynamic HARQ-ACK codebook according to one embodiment.

[0402] Referring to FIG. 15, the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH may correspond to five PDSCHs (or corresponding DCI formats). For example, four of the five PDSCHs (PDSCH#0 (1500), PDSCH#1 (1501), PDSCH#2 (1502), PDSCH#4 (1504)) may be first type PDSCHs, and one PDSCH (PDSCH#3 (1503)) may be second type PDSCH. For example, the terminal may obtain a first counter DAI value and a first total DAI value from DCI formats that schedule the four PDSCHs (PDSCH#0 (1500), PDSCH#1 (1501), PDSCH#2 (1502), PDSCH#4 (1504)).

[0403] According to one embodiment, the terminal may generate a first sub-codebook based on a first counter DAI value and a first total DAI value. For example, 2 bits of HARQ-ACK information bits may be included in the first sub-codebook according to the order of the first counter DAI value. Accordingly, the size of the first sub-codebook is 8 bits, and the included bits are {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b2,1 , b 4,0 , b 4,1 It can be}. For example, 2 bits {b i,0 , b i,1} can represent HARQ-ACK information corresponding to PDSCH#i.

[0404] According to one embodiment, the terminal may generate a second sub-codebook based on a second counter DAI value and a second total DAI value. For example, 2+4 bits of HARQ-ACK information bits may be included in the second sub-codebook according to the order of the second counter DAI value. Accordingly, the size of the second sub-codebook is 6 bits, and the included bits are {b 3,0 , b 3,1 , m 3,0 , m 3,1 , m 3,2 , m 3,3 It can be}. For example, 4 bits {m i,0 , m i,1 , m i,2 , m i,3} can represent received measurement information corresponding to PDSCH#i.

[0405] According to one embodiment, a terminal can combine a first sub-codebook and a second sub-codebook to generate a single dynamic HARQ-ACK codebook. The terminal can transmit the dynamic HARQ-ACK codebook to a base station via PUCCH or PUSCH.

[0406] FIG. 16 is a diagram showing the generation of a dynamic HARQ-ACK codebook according to one embodiment.

[0407] Referring to FIG. 16, the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH according to one embodiment may correspond to five PDSCHs (or corresponding DCI formats). Among the five PDSCHs, three PDSCHs (PDSCH#0 (1600), PDSCH#1 (1601), PDSCH#4 (1604)) may be first type PDSCHs, and two PDSCHs (PDSCH#2 (1602), PDSCH#3 (1603)) may be second type PDSCHs. The terminal may obtain a first counter DAI value and a first total DAI value from the DCI formats that schedule the three PDSCHs (PDSCH#0 (1600), PDSCH#1 (1601), PDSCH#4 (1604)).

[0408] According to one embodiment, the terminal may generate a first sub-codebook based on a first counter DAI value and a first total DAI value. For example, 2 bits of HARQ-ACK information bits may be included in the first sub-codebook according to the order of the first counter DAI value. Accordingly, the size of the first sub-codebook is 6 bits, and the included bits are {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 4,0 , b 4,1 It can be}. For example, 2 bits {b i,0 , b i,1} can represent HARQ-ACK information corresponding to PDSCH#i.

[0409] According to one embodiment, the terminal may generate a second sub-codebook based on a second counter DAI value and a second total DAI value. For example, 2+4 bits of HARQ-ACK information bits may be included in the second sub-codebook according to the order of the second counter DAI values. Accordingly, the size of the second sub-codebook is 12 bits, and the included bits are {b 2,0 , b 2,1 , m 2,0 , m 2,1 , m 2,2 , m 2,3 , b 3,0 , b 3,1 , m 3,0 , m 3,1 , m 3,2 , m 3,3 It can be}. For example, 4 bits {m i,0 , m i,1 , m i,2 , m i,3} can represent received measurement information corresponding to PDSCH#i.

[0410] According to one embodiment, the terminal can combine a first sub-codebook and a second sub-codebook to generate a dynamic HARQ-ACK codebook. The terminal can transmit the dynamic HARQ-ACK codebook to a base station via PUCCH or PUSCH.

[0411] <Fourth Embodiment: Creation of a first sub-codebook for reporting HARQ-ACK information and a second sub-codebook for reporting received measurement information>

[0412] In a fourth embodiment of the present disclosure, a dynamic HARQ-ACK codebook may be composed of a plurality of sub-codebooks. For example, all PDSCHs corresponding to the dynamic HARQ-ACK codebook may correspond to a first sub-codebook. For example, among the PDSCHs corresponding to the dynamic HARQ-ACK codebook, a PDSCH instructed to report received measurement information may correspond to a second sub-codebook.

[0413] Combinations between the embodiments of the present disclosure can be obviously understood by a person skilled in the art. For example, a person skilled in the art can easily combine the first, second, third, and fourth embodiments within a non-contradictory scope.

[0414] For example, HARQ-ACK information for all PDSCHs may be included in a first sub-codebook. In the first sub-codebook, the bits corresponding to a single PDSCH (or, corresponding DCI format) may be Y bits. When a terminal is instructed by a base station to report reception measurement information regarding a PDSCH (or, corresponding DCI format), the reception measurement information of the PDSCH (or, corresponding DCI format) may be included in a second sub-codebook. For example, in the second sub-codebook, the bits corresponding to a single PDSCH (or corresponding DCI format) may be Y bits.

[0415] According to one embodiment, the DCI format may include a DAI field for generating a dynamic HARQ-ACK codebook. For example, a counter DAI value and / or a total DAI value may be indicated from the DAI field. For example, the counter DAI value and / or the total DAI value may correspond to a first sub-codebook.

[0416] According to one embodiment, the DCI format may indicate an additional DAI value (e.g., additional DAI or add-DAI) for generating a second sub-codebook of the dynamic HARQ-ACK codebook. For example, the add-DAI may be applied only to the second sub-codebook. For example, the additional DAI value included in the DCI format may indicate the number of received measurement information reports requested up to the time of receiving the DCI format among the DCI formats corresponding to the dynamic HARQ-ACK codebook. Here, the DCI formats corresponding to the dynamic HARQ-ACK codebook may be listed in the following order.

[0417] - Based on the symbols in which the DCI format is received, the DCI format received in an earlier symbol may be listed as the DCI format that comes first in order compared to the DCI format received in a later symbol.

[0418] - If multiple DCI formats are received for the same symbol, the DCI formats may be listed in ascending order of the cell index corresponding to the DCI format. Here, the cell index corresponding to the DCI format may be the index of the PDSCH cell that the DCI format schedules.

[0419] - If there are multiple DCI formats with the same corresponding cell index among the DCI formats received in the same symbol, the terminal may list the DCI format for which the PDSCH corresponding to the relatively preceding symbols is scheduled as the DCI format that is positioned earlier in order than the DCI format for which the PDSCH corresponding to the subsequent symbols (e.g., following symbols, subsequent symbols).

[0420] For example, if the additional DAI value of the DCI format is '0', it may indicate that there are no DCI formats that have requested a report of received measurement information up to the DCI format. For example, if the additional DAI value of the DCI format is 'Z', it may indicate that there were Z DCI formats that have requested a report of received measurement information up to the DCI format. For example, Z can be a non-negative integer.

[0421] According to one embodiment, if the field indicating an additional DAI value is 1 bit, Z may be a value of 0 or 1. In this case, if the additional DAI value in the DCI format is '0', it may be indicated that there were 2*i DCI formats (i=0,1,2,...) for which a received measurement information report was requested up to the DCI format. If the additional DAI value in the DCI format is '1', it may be indicated that there were 2*i+1 DCI formats (i=0,1,2,...) for which a received measurement information report was requested up to the DCI format.

[0422] According to one embodiment, if the field indicating an additional DAI value is 2 bits (e.g., 00, 01, 10, 11), Z may be one of the values ​​0, 1, 2, or 3. For example, if the additional DAI value in the DCI format is '0', it may be indicated that there are 4*i DCI formats (i=0, 1, 2, ...) for which a received measurement information report was requested up to the DCI format. For example, if the additional DAI value in the DCI format is '1', it may be indicated that there are 4*i+1 DCI formats (i=0, 1, 2, ...) for which a received measurement information report was requested up to the DCI format. For example, if the additional DAI value in the DCI format is '2', it may be indicated that there are 4*i+2 DCI formats (i=0, 1, 2, ...) for which a received measurement information report was requested up to the DCI format. For example, if the additional DAI value in the DCI format is '3', it may be indicated that there are 4*i+3 DCI formats (i=0,1,2,. . .) that requested a report of received measurement information up to the DCI format.

[0423] According to one embodiment, the terminal may determine (or identify) that the number of DCI formats requesting a report of received measurement information up to the DCI format is Z based on an additional DAI value of the DCI format. If the DCI format requests a report of received measurement information, the terminal may determine (or identify) that the number of DCI formats containing a report of received measurement information among the DCI formats transmitted prior to the DCI format is Z-1. Accordingly, the position of the received measurement information X=4 bits corresponding to the DCI format in the second sub-codebook may be the (Z-1)*X+1th bits. For example, in the second sub-codebook, (Z-1)*X contains the received measurement information of the previously transmitted DCI format, and the received measurement information of the DCI format may be included in the X bits after the (Z-1)*X bits.

[0424] FIG. 17 is a drawing illustrating a fourth embodiment according to the present disclosure.

[0425] Referring to FIG. 17, five PDSCHs may correspond to the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH according to one embodiment.

[0426] Referring to FIG. 17, the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH may correspond to five PDSCHs (or corresponding DCI formats). For example, four of the five PDSCHs (PDSCH#0 (1700), PDSCH#1 (1701), PDSCH#2 (1702), PDSCH#4 (1704)) may be PDSCHs that do not include a received measurement information report, and one PDSCH (PDSCH#3 (1703)) may be a PDSCH that includes a received measurement information report. For example, the terminal can obtain counter DAI values ​​and total DAI values ​​from DCI formats that schedule five PDSCHs (PDSCH#0 (1700), PDSCH#1 (1701), PDSCH#2 (1702), PDSCH#3 (1703), PDSCH#4 (1704)).

[0427] According to one embodiment, the terminal may generate a first sub-codebook based on a counter DAI value and a total DAI value. For example, 2 bits of HARQ-ACK information bits may be included in the first sub-codebook according to the order of the counter DAI values. Accordingly, the size of the first sub-codebook is 10 bits, and the included bits are {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1} can be. Here, 2 bits {b i,0 , b i,1} can represent HARQ-ACK information corresponding to PDSCH#i.

[0428] According to one embodiment, the terminal can obtain an additional DAI value from DCI formats. The terminal can obtain 0 as an additional DAI value from the DCI format corresponding to PDSCH#0 (1700). The terminal can identify that no received measurement report is requested up to the DCI format. The terminal can obtain Z=0 as an additional DAI value from the DCI format corresponding to PDSCH#1 (1701). The terminal can identify that no received measurement report is requested up to the DCI format. The terminal can obtain Z=0 as an additional DAI value from the DCI format corresponding to PDSCH#2 (1702). The terminal can identify that no received measurement report is requested up to the DCI format. The terminal can obtain Z=1 as an additional DAI value from the DCI format corresponding to PDSCH#3 (1703). The terminal can identify that Z=1 received measurement information report is requested up to the DCI format. Receive measurement information in DCI format may be included in the second sub-codebook in (Z-1)*X+1 = X bits starting from the 1st bit. The terminal can obtain Z=1 as an additional DAI value from the DCI format corresponding to PDSCH#4 (1704). The terminal can identify that a report of Z=1 received measurement information has been requested up to the DCI format. Since the DCI format does not include a report of received measurement information, separate received measurement information may not be included in the second sub-codebook. Therefore, the second sub-codebook is 4 bits and {m 3,0 , m 3,1 , m 3,2 , m 3,3 It can be.

[0429] Referring to FIG. 17, the terminal may fail to receive a DCI format that schedules PDSCH#3. In this case, the terminal may obtain Z=0 as an additional DAI value from the DCI format corresponding to PDSCH#2 (1702) and Z=1 as an additional DAI value from the DCI format corresponding to PDSCH#4 (1704). The difference between the two values ​​is 1. Thus, the terminal may determine a failure to receive a DCI format requesting a reception measurement information report between the DCI format corresponding to PDSCH#2 (1702) and the DCI format corresponding to PDSCH#4 (1704). Thus, a 4-bit reception measurement information report may be included in the second sub-codebook. For example, the 4-bit reception measurement information report may be a specific value (all '0's) indicating an invalid reception measurement information report. Therefore, the second sub-codebook is 4 bits and can be {0, 0, 0, 0}.

[0430] According to one embodiment, a terminal can combine a first sub-codebook and a second sub-codebook to generate a dynamic HARQ-ACK codebook. For example, the terminal can transmit the dynamic HARQ-ACK codebook to a base station via PUCCH or PUSCH.

[0431] FIG. 18 is a drawing illustrating a fourth embodiment according to the present disclosure.

[0432] Referring to FIG. 18, five PDSCHs may correspond to the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH according to one embodiment.

[0433] Referring to FIG. 18, the dynamic HARQ-ACK codebook transmitted in PUCCH to PUSCH according to one embodiment may correspond to five PDSCHs (or corresponding DCI formats). Of the five PDSCHs, four PDSCHs (PDSCH#0 (1800), PDSCH#1 (1801), PDSCH#2 (1802), PDSCH#4 (1804)) are PDSCHs that do not include a received measurement information report, and two PDSCHs (PDSCH#2 (1802), PDSCH#3 (1803)) are PDSCHs that include a received measurement information report. The terminal can obtain counter DAI values ​​and total DAI values ​​from DCI formats that schedule 5 PDSCHs (PDSCH#0 (1800), PDSCH#1 (1801), PDSCH#2 (1802), PDSCH#3 (1803), PDSCH#4 (1804)).

[0434] According to one embodiment, the terminal may generate a first sub-codebook based on the counter DAI value and the total DAI value. For example, 2 bits of HARQ-ACK information bits may be included in the first sub-codebook according to the order of the counter DAI values. Accordingly, the size of the first sub-codebook is 10 bits, and the included bits are {b 0,0 , b 0,1 , b 1,0 , b 1,1 , b 2,0 , b 2,1 , b 3,0 , b 3,1 , b 4,0 , b 4,1} can be. Here, 2 bits {b i,0 , b i,1} can represent HARQ-ACK information corresponding to PDSCH#i.

[0435] According to one embodiment, the terminal can obtain an additional DAI value from DCI formats. The terminal can obtain 0 as an additional DAI value from the DCI format corresponding to PDSCH#0 (1800). The terminal can identify that no received measurement report is requested up to the DCI format. The terminal can obtain Z=0 as an additional DAI value from the DCI format corresponding to PDSCH#1 (1801). The terminal can identify that no received measurement report is requested up to the DCI format. The terminal can obtain Z=1 as an additional DAI value from the DCI format corresponding to PDSCH#2 (1802). The terminal can identify that Z=1 received measurement report is requested up to the DCI format. And the received measurement information of the DCI format may be included in X bits starting from the (Z-1)*X+1 = 1st bit in the second sub-codebook. The terminal can obtain Z=2 as an additional DAI value from the DCI format corresponding to PDSCH#3 (1803). The terminal can identify that Z=2 received measurement information reports have been requested up to the DCI format. Furthermore, the received measurement information in the DCI format may be included in X bits starting from the (Z-1)*X+1 = 1*X+1 = 1*4+1 = 5th bit in the second sub-codebook. The terminal can obtain Z=2 as an additional DAI value from the DCI format corresponding to PDSCH#4 (1804). The terminal can identify that Z=2 received measurement information reports have been requested up to the DCI format. Since the DCI format does not include received measurement information reports, separate received measurement information may not be included in the second sub-codebook. Therefore, the second sub-codebook may be 8 bits and {m 2,0 , m 2,1 , m 2,2 , m 2,3 , m 3,0 , m 3,1 , m 3,2 , m 3,3 It can be.

[0436] Referring to FIG. 18, the terminal may fail to receive a DCI format scheduling PDSCH#3 (1803). In this case, the terminal may obtain Z=1 as an additional DAI value from the DCI format corresponding to PDSCH#2 (1802) and Z=2 as an additional DAI value from the DCI format corresponding to PDSCH#4 (1804). The difference between the two values ​​is 1. Therefore, the terminal can identify a failure to receive a DCI format requesting a single reception measurement information report between the DCI format corresponding to PDSCH#2 (1802) and the DCI format corresponding to PDSCH#4 (1804). Thus, the terminal may include a 4-bit reception measurement information report in the second sub-codebook. For example, the 4-bit reception measurement information report may be a specific value (all '0's) indicating an invalid reception measurement information report. Thus, the second sub-codebook may be 8 bits, and {m 2,0 , m 2,1 , m 2,2 , m 2,3 It can be , 0, 0, 0, 0}.

[0437] Referring to FIG. 18, the terminal may fail to receive the DCI format scheduling PDSCH#2 (1802) and the DCI format scheduling PDSCH#3 (1803). In this case, the terminal may obtain Z=0 as an additional DAI value from the DCI format corresponding to PDSCH#1 (1801) and Z=2 as an additional DAI value from the DCI format corresponding to PDSCH#4 (1804). The difference between the two values ​​may be 2. Thus, the terminal may identify the failure to receive the DCI format requesting two reception measurement reports between the DCI format corresponding to PDSCH#1 (1801) and the DCI format corresponding to PDSCH#4 (1804). Thus, the terminal may include a 2*4 bit reception measurement report in the second sub-codebook. Here, the 2*4 bit reception measurement report may be a specific value (all '0's) indicating an invalid reception measurement report. Therefore, the second sub-codebook is 8 bits and can be {0, 0, 0, 0, 0, 0, 0, 0}.

[0438] According to one embodiment, a terminal can combine a first sub-codebook and a second sub-codebook to generate a dynamic HARQ-ACK codebook. The terminal can transmit the dynamic HARQ-ACK codebook to a base station via PUCCH or PUSCH.

[0439] In the example described above, the DCI format was explained as including an additional DAI value. Additionally, the DCI format may include an additional total DAI value. The additional total DAI may indicate the total number of PDSCHs (or corresponding DCI formats) that direct the reporting of received measurement information.

[0440] FIG. 19 illustrates a method for generating a dynamic HARQ-ACK codebook of a terminal according to one embodiment of the present disclosure.

[0441] Referring to FIG. 19, a method for generating a dynamic HARQ-ACK codebook of a terminal according to one embodiment may be as follows.

[0442] According to one embodiment, in the first step (1900), the terminal may receive necessary configuration information (e.g., an RRC message) from the base station. For example, the information may be transmitted via RRC signaling. For example, the information may include dynamic HARQ-ACK codebook configuration information. For example, the information may set the maximum number of HARQ-ACK bits (Y bits) to be generated per PDSCH to the terminal. For example, Y bits may be determined by the maximum number of transmission blocks (or the maximum number of MIMO layers) that the PDSCH contains. For example, the information may include information for enabling a received measurement information report. For example, the information may include information about the type of received measurement information report. For example, the information may set the number of bits (X bits) to be included in the received measurement report per PDSCH.

[0443] According to one embodiment, in the second step (1910), the terminal may receive one or more DCI formats. For example, the DCI format may schedule PDSCH. HARQ-ACK information of one or more DCI formats may be generated into a single dynamic HARQ-ACK codebook and transmitted over PUCCH to PUSCH. The terminal may obtain at least one of a counter DAI value, a total DAI value, an additional DAI value, or an additional total DAI value from the DCI format.

[0444] In the third step (1920), the terminal may generate a dynamic HARQ-ACK codebook based on DAI values. The terminal may generate a first sub-codebook based on Counter DAI values ​​or Total DAI values. For example, Y bits may correspond to one PDSCH (or, corresponding DCI format) in the first sub-codebook. For example, Y bits may be HARQ-ACK information bits of the corresponding PDSCH (or, corresponding DCI format). For example, the terminal may generate a second sub-codebook based on Additional DAI values ​​or Additional total DAI values. For example, X bits may correspond to one PDSCH (or, corresponding DCI format) in the second sub-codebook. For example, X bits may be reception measurement information bits of the corresponding PDSCH (or, corresponding DCI format).

[0445] FIG. 20 describes a method for generating a dynamic HARQ-ACK codebook containing reception measurement information when a terminal receives a DCI format that schedules multiple PDSCHs.

[0446] Referring to FIG. 20, a terminal according to one embodiment may receive from a base station a DCI format for scheduling one PDSCH and a DCI format for scheduling multiple PDSCHs. For example, PDSCH#0 (2000) may be a PDSCH scheduled based on a DCI format for scheduling one PDSCH. For example, PDSCH#1 (2001) may be a PDSCH scheduled based on a DCI format for scheduling one PDSCH. For example, PDSCH#2, PDSCH#3, and / or PDSCH#4 may be PDSCHs scheduled based on a DCI format for scheduling multiple PDSCHs.

[0447] According to one embodiment, each DCI format may include a counter DAI to a total DAI. When the DCI format schedules one PDSCH, the counter DAI to the total DAI of the DCI format may correspond to a first sub-codebook. The number of HARQ-ACK bits corresponding to the DCI format may be the maximum number of HARQ-ACK bits corresponding to one PDSCH. For example, the maximum number of HARQ-ACK bits corresponding to one PDSCH may be 1 bit or 2 bits. For example, 1 bit may be used when the PDSCH contains at most 1 TB (transport block), and 2 bits may be used when the PDSCH contains at most 2 TB (transport blocks).

[0448] According to one embodiment, when a DCI format schedules multiple PDSCHs, the counter DAI to total DAI of the DCI format may correspond to a second sub-codebook. The number of HARQ-ACK bits corresponding to the DCI format may be the maximum number among the HARQ-ACK bits corresponding to multiple PDSCHs. The maximum number of HARQ-ACK bits corresponding to multiple PDSCHs is N max Up to 2*N max It can be. For example, N max can be the maximum number of multiple PDSCHs that the DCI format can schedule. For example, N max The bit can be used when the PDSCH contains up to 1 TB (transport block), and 2*N max bits can be used when PDSCH contains up to 2 TBs (transport blocks).

[0449] Referring to FIG. 20, the counter-DAI corresponding to PDSCH#0 (2000) corresponds to the 1-1 sub-codebook and its value may be 1 (1 st cDAI=1). The counter-DAI corresponding to PDSCH#1(2001) corresponds to the 1-1 sub-codebook and its value is 2(1 st cDAI=2) can be. For example, the terminal sends 2 bits of HARQ-ACK bits (b to PDSCH#0). 0,0 , b 0,1 Can generate ) and 2 bits HARQ-ACK bits (b in PDSCH#1 1,0 , b 1,1 ) can be generated. Depending on the order of Counter-DAI, 2 bits of HARQ-ACK bits (b) are entered into PDSCH#0. 0,0 , b 0,1 ) is 2 bits HARQ-ACK bits (b in PDSCH#1 1,0, b 1,1 It can be placed in a position ahead of ).

[0450] Referring to FIG. 20, the counter-DAI corresponding to PDSCH#2 (2002), PDSCH#3 (2003), and / or PDSCH#4 (2004) corresponds to the first-second sub-codebook and the value is 1 (2 nd cDAI=1) The terminal may have 2 bits of HARQ-ACK bits (b) on each of PDSCH#2 (2002), PDSCH#3 (2003), and / or PDSCH#4 (2004). 2,0 , b 2,1 ), (b 3,0 , b 3,1 ), (b 4,0 , b 4,1 ) can be generated. For example, HARQ-ACK bits can be included in the 1st and 2nd sub-HARQ-ACK codebook.

[0451] Referring to FIG. 20, a DCI format for scheduling PDSCH#0 (2000), a DCI format for scheduling PDSCH#1 (2001), and a DCI format for scheduling multiple PDSCHs (e.g., PDSCH#2 (2002), PDSCH#3 (2003), PDSCH#4 (2004)) may include an additional DAI (additional DCI) that indicates whether to include received measurement information.

[0452] According to one embodiment, the DCI format scheduling PDSCH#0 (2000) may not request received measurement information, and since there is no DCI format that requested received measurement information up to the time of receiving the DCI format, the value of the additional DAI may be 0 (Add-DAI=0).

[0453] According to one embodiment, a DCI format scheduling PDSCH#1 (2001) may request received measurement information, and since there is only one DCI format that has requested received measurement information by the time the DCI format is received, the value of the additional DAI may be 1 (Add-DAI=1).

[0454] According to one embodiment, a DCI format scheduling multiple PDSCHs (e.g., PDSCH#2 (2002), PDSCH#3 (2003), PDSCH#4 (2004)) may request received measurement information, and since there is only one DCI format that has requested received measurement information by the time the DCI format is received (the DCI format scheduling PDSCH#1 (2001)), the value of the additional DAI may be 2 (Add-DAI=2).

[0455] According to one embodiment, if a DCI format scheduling a single PDSCH instructs the inclusion of received measurement information, the terminal can generate received measurement information for the scheduled PDSCH. If a DCI format scheduling multiple PDSCHs instructs the inclusion of received measurement information, the terminal can generate received measurement information by selecting one PDSCH (or at least one PDSCH) among the multiple scheduled PDSCHs. Here, the method of selecting one PDSCH among the multiple PDSCHs may be the PDSCH that is the latest in time among the multiple PDSCHs.

[0456] According to one embodiment, reception measurement information {m corresponding to a DCI format scheduling PDSCH#1 (2001). 1,0 , m 1,1 , m 1,2 , m 1,3} and receive measurement information corresponding to the DCI format scheduling multiple PDSCHs (PDSCH#2 (2002), PDSCH#3 (2003), PDSCH#4 (2004)) (the latest in time, PDSCH#4 (2004)) {m 4,0 , m 4,1 , m 4,2 , m 4,3} can be included in the second sub-codebook. That is, the second sub-codebook contains {m 1,0 , m 1,1 , m 1,2 , m 1,3} and {m 4,0 , m 4,1 , m 4,2 , m 4,3 This can be included according to the order of additional DAI.

[0457] According to one embodiment, the terminal can connect the 1-1 sub-codebook, the 1-2 sub-codebook, and the 2 sub-codebook to create a single codebook and transmit the codebook to a base station.

[0458] According to one embodiment of the present disclosure, a terminal may transmit received measurement information including at least one of the following. The received measurement information may be transmitted including a plurality (or at least one) of the following. The information to be included by the terminal as received measurement information may be set by a base station.

[0459] - As the first piece of information, MCS-related information may be included.

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

[0461] One or more PDSCHs may be selected as follows. Of course, they are not limited to the examples below. Additionally, the terminal is not limited to selecting a PDSCH using only one of the methods below.

[0462] In one embodiment, the terminal can select the most recently received PDSCH.

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

[0464] In one embodiment, the terminal can select a PDSCH containing the smallest number of RBs.

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

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

[0467] In one embodiment, the terminal can select a PDSCH corresponding to a specific slot.

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

[0469] In one embodiment, the terminal can select a PDSCH containing the largest number of OFDM (Orthogonal frequency-division multiplexing) symbols.

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

[0471] In one embodiment, the terminal can select a PDSCH containing the most REs.

[0472] In one embodiment, the terminal can select the PDSCH containing the least amount of RE.

[0473] In one embodiment, the terminal can select PDSCH, which is a specific HARQ process number.

[0474] In one embodiment, the terminal may select one PDSCH and include information related to the index of the selected PDSCH as received measurement information.

[0475] The MCS value that the terminal wishes to include as received measurement information may be expressed or indicated by at least one of the following methods. Of course, it is not limited to the examples below.

[0476] In the first method, the terminal may include an absolute MCS value as a received measurement information value. The absolute MCS value may be represented by 5 bits. More specifically, [Table 25] is an MCS table for interpreting MCS values. Referring to [Table 25], the terminal [requires] the desired MCS value (MCS index, I MCS ) can be determined, and the above index can be represented as 5 bits and included in the received measurement information value.

[0477]

[0478] In the second method, the terminal may include a relative MCS value (e.g., delta MCS) between the MCS of the received PDSCH and the desired MCS as a received measurement information value. For example, the delta MCS value may be represented by X bits. For example, X may be 2 bits. For example, the delta MCS may be determined based on the following [Table 26]. For example, is the MCS of the received PDSCH, and may be the MCS desired by the terminal. For example, δ1, δ2, and δ3 may be predetermined values ​​or values ​​set by the base station for the terminal. (0 ≤ δ1 < δ2 < δ3 may apply.)

[0479] For example, if δ1=1, δ2=3, and δ3=5, and the MCS index of the PDSCH received by the terminal is 12, referring to [Table 26], an MCS index of 12 can be identified as 16QAM and a 434 / 1024 code rate. If the PDSCH desired by the terminal is 8 (QPSK, 602 / 1024 code rate), - =12-8=4 can be obtained. Therefore, the terminal can determine 2 as the Delta MCS index.

[0480]

[0481] A terminal may receive one or more PDSCHs. A PDSCH may be scheduled as a first MCS. The terminal may transmit HARQ-ACK information of the PDSCHs on PUCCH or PUSCH. In this case, if the HARQ-ACK information is a specific value, the terminal may transmit MCS 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 an MCS information transmission mode. For example, the mode may be indicated by header information. For example, 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 said MCS information.

[0482] - As a second piece of information, information related to CQI (channel quality indicator) may be included. The CQI-related information may be a value determined based on the CSI-RS (channel state information-reference signal) and reference PDSCH scheduling information received by the terminal. For example, the CQI-related information may be a value determined based on the DMRS of the PDSCH received by the terminal.

[0483] - As third information, information related to the PMI (precoder matrix indicator) may be included. The PMI-related information may be a value determined based on the CSI-RS received by the terminal. For example, the PMI-related information may be a value determined based on the DMRS of the received PDSCHs.

[0484] - As a fourth piece of information, RI (rank indicator) related information may be included. For example, RI related information may be a value determined based on the CSI-RS received by the terminal. For example, RI related information may be a value determined based on the DMRS of the received PDSCHs.

[0485] - As the fifth piece of information, beam-related information may be included. For example, the beam-related information may be a value determined based on the CSI-RS to SSB received by the terminal. For example, the beam-related information may be a value determined based on the DMRS of the received PDSCHs.

[0486] - As the sixth piece of information, information regarding channel measurements (SINR (Signal-to-Interference-Plus-Noise Ratio), RSRP (reference signal received power), RSRQ (Reference Signal Received Quality), RSSI (received signal strength indicator), or interference amount) may be included. For example, information regarding channel measurements may be a value determined based on the CSI-RS received by the terminal. For example, in the case of interference amount, it may be a value determined based on ZP (zero power CSI-RS). For example, information regarding channel measurements may be a value determined based on the DMRS of the received PDSCHs.

[0487] - As the seventh piece of information, information regarding PDSCH decoding (LDPC (low density parity check) code decoding) may be included. Information regarding PDSCH decoding may be determined based on the PDSCH received by the terminal. For example, 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 contained in the PDSCH.

[0488] - As the eighth piece of information, information for PDCCH link adaptation may be included. The terminal may receive a PDCCH that schedules the PDCCH. The PDCCH may be mapped to a unique aggregation level. For example, the aggregation level may be one of the values ​​1, 2, 4, 8, or 16. For example, the terminal may report to the base station the aggregation level value required for the terminal to receive the PDCCH.

[0489] For example, the first through eighth information may be generated per sub-band. For example, the terminal may include, per sub-band, MCS, CQI, PMI, RI, Beam, channel measurements (e.g., SINR, RSRP, RSRP, RSSI, interference amount), information regarding PDSCH decoding and / or PDCCH link adaptation information in the received measurement information.

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

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

[0492] Referring to FIG. 21, a terminal according to one embodiment may include a transceiver (referring to a terminal receiver (2100) and a terminal transmitter (2110)), a memory (not shown), and / or a terminal processing unit (2105, or a terminal control unit or processor). According to the communication method of the terminal described above, the transceiver (2100, 2110), memory, and 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 components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip. The terminal of FIG. 21 may correspond to the terminals of FIG. 1 to FIG. 20.

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

[0494] According to one embodiment, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through the wireless channel.

[0495] According to one embodiment, the memory may store programs and data necessary for the operation of the terminal. Additionally, the memory may store control information or data included in signals transmitted and / or received by the terminal. The memory may be composed of a storage medium or a combination of storage media, such as ROM (read-only memory), RAM (random access memory), a hard disk, a CD-ROM, and a DVD. Additionally, there may be multiple memories.

[0496] According to one embodiment, the processor can control a series of processes to enable the terminal to operate according to the above-described embodiment. For example, the processor can control the components of the terminal to receive a DCI composed of two layers and receive a plurality of PDSCHs simultaneously. There may be multiple processors, and the processors can perform the control operation of the terminal components by executing a program stored in memory.

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

[0498] Referring to FIG. 22, a base station may include a transceiver unit, which refers to a base station receiver (2200) and a base station transmitter (2210), a memory (not shown), and / or 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 unit (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 components or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip. The base station of FIG. 22 of the present disclosure may correspond to the base station of FIG. 1 to FIG. 21.

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

[0500] According to one embodiment, the transceiver may also receive a signal through a wireless channel and output it to a processor, and transmit the signal output from the processor through a wireless channel.

[0501] According to one embodiment, the memory may store programs and data necessary for the operation of the base station. Additionally, the memory may store control information or data included in signals transmitted and / or received by the base station. The memory may be composed of a storage medium or a combination of storage media, such as ROM, RAM, a hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. In a method performed by UE (user equipment), A step of receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) from a base station, wherein the DCI indicates whether to report a measurement result for the PDSCH; A step of receiving the PDSCH based on the above DCI; When the above DCI indicates to report the measurement result, the step of transmitting to the base station HARQ (hybrid automatic repeat request) information for the PDSCH and the measurement result; and A method comprising the step of transmitting the HARQ information for the PDSCH to the base station when the DCI instructs not to report the measurement result.

2. In Claim 1, The above DCI includes a field indicating whether to report the measurement results, and When the above field is set to a first value, the measurement result is transmitted to the base station along with the HARQ information, and A method in which, when the above field is set to a second value, the HARQ information is transmitted to the base station without the measurement result.

3. In Claim 1, The above DCI includes a field for scheduling the above PDSCH, and Whether to report the measurement results is determined based on the above field, and A method in which the above field includes at least one of an HPN (HARQ process number) field, an RV (redundancy version) field, a TDRA (time domain resource assignment) field, or a priority field.

4. In Claim 1, The above DCI includes a first DAI (downlink assignment index) associated with the HARQ information for the PDSCH among a plurality of PDSCHs, and a second DAI associated with the measurement result, and A method in which bits indicating HARQ information for the plurality of PDSCHs and bits indicating measurement results for the plurality of PDSCHs are concatenated and transmitted to the base station.

5. In a method performed by a base station, A step of transmitting downlink control information (DCI) to a UE (user equipment) for scheduling a physical downlink shared channel (PDSCH), wherein the DCI instructs whether to report measurement results for the PDSCH; A step of transmitting the PDSCH based on the above DCI; When the above DCI indicates to report the measurement result, the step of receiving HARQ (hybrid automatic repeat request) information for the PDSCH and the measurement result from the UE; and A method comprising the step of receiving HARQ information for the PDSCH from the UE when the DCI instructs not to report the measurement results.

6. In Claim 5, The above DCI includes a field indicating whether to report the measurement results, and When the above field is set to a first value, the measurement result is received from the UE along with the HARQ information, and A method in which the HARQ information is received from the UE without the measurement result when the above field is set to a second value.

7. In Claim 5, The above DCI includes a field for scheduling the above PDSCH, and Whether the measurement result is reported is determined based on the above field, and A method in which the above field includes at least one of an HPN (HARQ process number) field, an RV (redundancy version) field, a TDRA (time domain resource assignment) field, or a priority field.

8. In Claim 5, The above DCI includes a first DAI (downlink assignment index) associated with the HARQ information for the PDSCH among a plurality of PDSCHs, and a second DAI associated with the measurement result, and A method in which bits indicating HARQ information for the plurality of PDSCHs and bits indicating measurement results for the plurality of PDSCHs are concatenated and received from the UE.

9. Regarding UE (user equipment), At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) from a base station, and the DCI instructs whether to report measurement results for the PDSCH. Receive the PDSCH based on the above DCI, and When the above DCI indicates to report the above measurement result, transmits HARQ (hybrid automatic repeat request) information for the PDSCH and the above measurement result to the base station, and A UE that, when the above DCI instructs not to report the above measurement result, instructs the base station to transmit the HARQ information for the above PDSCH.

10. In Claim 9, The above DCI includes a field indicating whether to report the measurement results, and When the above field is set to a first value, the measurement result is transmitted to the base station along with the HARQ information, and A UE in which, when the above field is set to a second value, the HARQ information is transmitted to the base station without the above measurement result.

11. In Claim 9, The above DCI includes a field for scheduling the above PDSCH, and Whether to report the measurement results is determined based on the above field, and The above field is a UE comprising at least one of an HPN (HARQ process number) field, an RV (redundancy version) field, a TDRA (time domain resource assignment) field, or a priority field.

12. In Claim 9, The above DCI includes a first DAI (downlink assignment index) associated with the HARQ information for the PDSCH among a plurality of PDSCHs, and a second DAI associated with the measurement result, and A UE in which bits indicating HARQ information for the plurality of PDSCHs and bits indicating measurement results for the plurality of PDSCHs are concatenated and transmitted to the base station.

13. Regarding base stations, At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the base station: Transmits downlink control information (DCI) to the UE (user equipment) for scheduling the physical downlink shared channel (PDSCH), and the DCI instructs whether to report the measurement results for the PDSCH. Transmit the PDSCH based on the above DCI, and When the above DCI indicates to report the above measurement results, the above UE receives HARQ (hybrid automatic repeat request) information for the PDSCH and the above measurement results, and A base station that receives the HARQ information for the PDSCH from the UE when the above DCI instructs not to report the above measurement results.

14. In Claim 13, The above DCI includes a field indicating whether to report the measurement results, and When the above field is set to a first value, the measurement result is received from the UE along with the HARQ information, and A base station in which the HARQ information is received from the UE without the measurement result when the above field is set to a second value.

15. In Claim 13, The above DCI includes a field for scheduling the above PDSCH, and Whether the measurement result is reported is determined based on the above field, and A base station, wherein the above field includes at least one of an HPN (HARQ process number) field, an RV (redundancy version) field, a TDRA (time domain resource assignment) field, or a priority field.

Images