Method and apparatus for puncturing-based uplink control information transmission in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure provides a method and apparatus for puncturing-based uplink control information transmission in a wireless communication system. The method carried out by a terminal, according to an embodiment of the present disclosure, may comprise the steps of: receiving information about a parameter γ>1; acquiring a transport block corresponding to a uplink shared channel (UL-SCH); acquiring a plurality of code blocks on the basis of splitting the transport block, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is determined on the basis of the parameter γ; mapping the plurality of code blocks to resource elements (REs) corresponding to a physical uplink shared channel (PUSCH), wherein at least some of REs to which the one or more first code blocks are mapped, among the REs corresponding to the PUSCH, are punctured, and bits for uplink control information (UCI) are mapped thereto; and transmitting the PUSCH.

Description

Method and device for transmitting uplink control information based on puncturing in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for transmitting an uplink control signal of a terminal and an apparatus capable of performing the same.

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

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

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

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) 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 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) to incorporate 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, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; 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 Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

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

[0009] The above information is provided for background information only to aid in understanding the present disclosure. No determination or claim has been made as to whether any of the above contents can be applied as prior art to the present disclosure.

[0010] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0011] The technical problems to be solved in the various embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art from the various embodiments of the present disclosure described below.

[0012] The present disclosure describes a method in which a terminal transmits uplink control information (UCI) to a base station.

[0013] A method performed by a terminal in a communication system according to one embodiment of the present disclosure may include: receiving information regarding a parameter γ > 1; obtaining a transport block corresponding to an uplink shared channel (UL-SCH); obtaining a plurality of code blocks based on dividing the transport block, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is determined based on the parameter γ; mapping the plurality of code blocks to resource elements (REs) corresponding to a physical uplink shared channel (PUSCH), wherein at least some of the REs corresponding to the PUSCH to which the one or more first code blocks are mapped are punctured and bits for uplink control information (UCI) are mapped; and transmitting the PUSCH.

[0014] According to one embodiment of the present disclosure, the number of bits for the one or more first code blocks is determined based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and when the number of UCI bits is greater than or equal to the specific threshold, (i) the number of bits for the one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, if the number of UCI bits is less than the specific threshold, the number of bits for one or more first code blocks and the number of bits for one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, and G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of one or more second blocks, and C may be the number of scheduled code blocks of the transmission block.

[0015] According to one embodiment of the present disclosure, information regarding the parameter γ is received through upper layer signaling or a first DCI (downlink control information), and the one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the one or more second code blocks may be one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

[0016] According to one embodiment of the present disclosure, the method comprises: receiving a second DCI; determining retransmission for at least some of the code blocks among one or more first code blocks corresponding to the punctured RE based on the second DCI; and transmitting a PUSCH including the at least some code blocks, wherein the retransmission for the at least some code blocks may be determined based on a 1-bit indicator included in the second DCI indicating whether to retransmit the at least some code blocks, or based on the fact that the NDI (new data indicator) included in the second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or based on the fact that the NDI included in the second DCI is not toggled and the UL-SCH indicator is a specific value.

[0017] According to one embodiment of the present disclosure, at least some of the REs corresponding to the PUSCH are mapped to at least some of the bits for the UCI and at least some of the bits for the UL-SCH, and at least some of the bits for the UCI and at least some of the bits for the UL-SCH are based on the same modulation order, and the same modulation order can be determined based on the modulation order indicated for the UL-SCH.

[0018] A terminal of a communication system according to one embodiment of the present disclosure includes: a transceiver; and a processor connected to the transceiver, wherein the processor: receives information regarding a parameter γ > 1; obtains a transport block corresponding to an uplink shared channel (UL-SCH); obtains a plurality of code blocks based on dividing the transport block, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is determined based on the parameter γ; maps the plurality of code blocks to resource elements (REs) corresponding to a physical uplink shared channel (PUSCH), wherein at least some of the REs corresponding to the PUSCH to which the one or more first code blocks are mapped are punctured and bits for uplink control information (UCI) are mapped; and may be configured to transmit the PUSCH.

[0019] According to one embodiment of the present disclosure, the number of bits for the one or more first code blocks is determined based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and when the number of UCI bits is greater than or equal to the specific threshold, (i) the number of bits for the one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, if the number of UCI bits is less than the specific threshold, the number of bits for one or more first code blocks and the number of bits for one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, and G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of one or more second blocks, and C may be the number of scheduled code blocks of the transmission block.

[0020] According to one embodiment of the present disclosure, information regarding the parameter γ is received through upper layer signaling or a first DCI (downlink control information), and the one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the one or more second code blocks may be one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

[0021] According to one embodiment of the present disclosure, the processor: receives a second DCI; determines a retransmission for at least some of the code blocks of the one or more first code blocks corresponding to the punctured RE based on the second DCI; and is configured to transmit a PUSCH including the at least some code blocks, wherein the retransmission for the at least some code blocks may be determined based on a 1-bit indicator included in the second DCI indicating whether to retransmit the at least some code blocks, or based on the fact that the NDI (new data indicator) included in the second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or based on the fact that the NDI included in the second DCI is not toggled and the UL-SCH indicator is a specific value.

[0022] According to one embodiment of the present disclosure, at least some of the REs corresponding to the PUSCH are mapped to at least some of the bits for the UCI and at least some of the bits for the UL-SCH, and at least some of the bits for the UCI and at least some of the bits for the UL-SCH are based on the same modulation order, and the same modulation order can be determined based on the modulation order indicated for the UL-SCH.

[0023] A base station of a communication system according to one embodiment of the present disclosure includes a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: transmit information regarding a parameter γ > 1; receive a PUSCH (physical uplink shared channel); obtain bits for a plurality of code blocks and a UCI (uplink control information) mapped on REs (resource elements) corresponding to the PUSCH; and obtain a transport block corresponding to an UL-SCH (uplink shared channel) based on the plurality of code blocks, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is based on the parameter γ, and at least some of the REs corresponding to the PUSCH to which the one or more first code blocks are mapped are punctured, and bits for the UCI may be mapped to the punctured REs.

[0024] According to one embodiment of the present disclosure, the number of bits for the one or more first code blocks is based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and when the number of UCI bits is greater than or equal to the specific threshold, (i) the number of bits for the one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, if the number of UCI bits is less than the specific threshold, the number of bits for one or more first code blocks and the number of bits for one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, and G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of one or more second blocks, and C may be the number of scheduled code blocks of the transmission block.

[0025] According to one embodiment of the present disclosure, information regarding the parameter γ is transmitted through upper layer signaling or a first DCI (downlink control information), and the one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the one or more second code blocks may be one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

[0026] According to one embodiment of the present disclosure, the processor is configured to: determine to request retransmission for at least some of the code blocks among the one or more first code blocks corresponding to the punctured RE; transmit a second DCI for requesting retransmission; and transmit a PUSCH including the at least some code blocks, wherein the request for retransmission may be indicated based on a 1-bit indicator included in the second DCI indicating whether to retransmit the at least some code blocks, or based on the fact that the NDI (new data indicator) included in the second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or based on the fact that the NDI included in the second DCI is not toggled and the UL-SCH indicator is a specific value.

[0027] According to one embodiment of the present disclosure, at least some of the REs corresponding to the PUSCH are mapped to at least some of the bits for the UCI and at least some of the bits for the UL-SCH, and at least some of the bits for the UCI and at least some of the bits for the UL-SCH are based on the same modulation order, and the same modulation order may be based on the modulation order indicated for the UL-SCH.

[0028] The various embodiments of the present disclosure described above are merely some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by those skilled in the art based on the detailed description to be described below.

[0029] The disclosed embodiments can provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0030] The effects obtainable from the various embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art based on the following detailed description.

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

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

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

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

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

[0036] FIG. 6 is a diagram illustrating a method for transmitting and receiving data in a wireless communication system according to one embodiment of the present disclosure, in consideration of a downlink data channel and a rate matching resource, between a base station and a terminal.

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

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

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

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

[0041] FIG. 11 is a flowchart illustrating a method of transmitting UL-SCH (or TB) and UCI through PUSCH.

[0042] Figure 12 is a diagram illustrating the UCI-to-RE mapping when multiplexing UCI on PUSCH.

[0043] FIG. 13 is a drawing illustrating the problem to be solved in the present disclosure.

[0044] FIG. 14 is a drawing of an example in which more redundancy is allocated to some CB(s) according to one embodiment of the present disclosure.

[0045] FIG. 15 is a flowchart for an example of a method for allocating more redundancy to some CB(s) according to one embodiment of the present disclosure.

[0046] FIG. 16 is a diagram of an example in which UL-SCH and UCI are transmitted simultaneously to a single RE according to one embodiment of the present disclosure.

[0047] FIG. 17 is a flowchart of an example of a soft-puncturing method according to one embodiment of the present disclosure.

[0048] FIG. 18 is a drawing illustrating an example of a CB retransmission method according to one embodiment of the present disclosure.

[0049] FIG. 19 is a flowchart illustrating an example of a method for retransmitting punctured CBs according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0056] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE (Long-Term Evolution) or LTE-A (LTE-advanced) systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) 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 without significantly departing from the scope of the present disclosure, at the discretion of a person with skilled technical knowledge.

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

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

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

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

[0061] As a representative example of the above-mentioned 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 refers to 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 refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

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

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

[0064] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). 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.

[0065] 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 simultaneously require a packet error rate of 10⁻⁵ or less. Consequently, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services, and design considerations may be required to allocate wide resources within the frequency band to ensure the reliability of the communication link.

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

[0067] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. 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.

[0068] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. 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.

[0069] 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) communication, 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 5G and IoT technologies.

[0070] [NR Time-Frequency Resources]

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

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

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

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

[0075] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In 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.

[0076] [Table 1]

[0077]

[0078] [Bandwidth Section (BWP)]

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

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

[0081] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely 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 that shown in Table 2 below for each bandwidth portion.

[0082] [Table 2]

[0083]

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

[0085] According to some embodiments, 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 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 numerology, for Control Resource Set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for Control Resource Set #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

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

[0087] According to some embodiments, 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 receive data at a specific frequency position within the system bandwidth.

[0088] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0089] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and 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 can be very inefficient in terms of power consumption. To reduce 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 receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0090] In the method for configuring the above bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part through the Master Information Block (MIB) during the initial connection phase. More specifically, the 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 the 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 configured Initial Bandwidth Part, the terminal can receive the 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.

[0091] [Bandwidth Section (BWP) Change]

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

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

[0094] [Table 3]

[0095]

[0096]

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

[0098] In accordance with the aforementioned requirements for the bandwidth change delay time, when a terminal receives a DCI containing a bandwidth change indicator in slot n, the terminal can complete the change to the new bandwidth portion indicated by the bandwidth change indicator at a time not later than slot n + TBWP, and can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth portion. When the 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 considering the terminal's bandwidth change delay time (TBWP). That is, when the 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, it 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 (K0 or K2) value smaller than the bandwidth change delay time (TBWP).

[0099] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, 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 said DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the said DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the said DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0100] [SS / PBCH Block]

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

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

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

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

[0105] - PBCH: Provides essential system information required for the transmission and reception of the terminal's data and control channels. The essential system information may include search space-related control information representing wireless resource mapping information of the control channel, scheduling control information for a separate data channel transmitting system information, etc.

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

[0107] The terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. It can obtain MIB from PBCH and receive a Control Resource Set (CORESET) #0 from it (which 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-Locations (QCL). The terminal can receive system information using downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to the Random Access Channel (RACH) required for initial connection from the received system information. The terminal can transmit a Physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information regarding the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among the respective SS / PBCH blocks and is monitoring the associated control area #0.

[0108] [PDCCH: DCI related]

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

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

[0111] DCI can be transmitted through the 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 terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

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

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

[0114] [Table 4]

[0115]

[0116]

[0117] 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 can include, for example, the information in Table 5.

[0118] [Table 5]

[0119]

[0120]

[0121] 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 can include, for example, the information in Table 6.

[0122] [Table 6]

[0123]

[0124]

[0125] 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 can include, for example, the information in Table 7.

[0126] [Table 7]

[0127]

[0128]

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

[0130] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0131] FIG. 4 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control 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) can be set in a specific frequency resource (403) within the entire terminal bandwidth part (410) on the frequency axis. On the time axis, they can be set with one or more 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 with a control resource length of 2 symbols, and control resource #2 (402) is set with a control resource length of 1 symbol.

[0132] The control domain in the aforementioned 5G can be configured by a base station to a terminal through upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring a control domain to a terminal means providing information such as a control domain identifier, the frequency location of the control domain, and the symbol length of the control domain. For example, it may include the information in Table 8.

[0133] [Table 8]

[0134]

[0135]

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

[0137] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be 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, that is, 12 subcarriers. A base station can construct a downlink control channel allocation unit by concatenating REGs (503).

[0138] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 504), then 1 CCE (504) can be composed of multiple REGs (503). For example, if the REG (503) illustrated in FIG. 5 is described, the REG (503) 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.

[0139] The basic unit of the downlink control channel, namely the REG (503) shown 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.

[0140] Search spaces can be classified into common search spaces and UE-specific search spaces. 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 SIBs containing cell operator information can 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 can be defined as a pre-arranged set of CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0141] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure 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, the information in Table 9 may be included.

[0142] [Table 9]

[0143]

[0144]

[0145] According to the configuration information, the base station may set one or multiple sets of search spaces for the terminal. According to some embodiments, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] [Table 10]

[0169]

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

[0171] [Mathematical Formula 1]

[0172]

[0173] - L: Lamination Level

[0174] - : Carrier Index

[0175] - : Total number of CCEs existing within control domain p

[0176] - : Slot Index

[0177] - : Number of PDCCH candidates at assembly level L

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

[0179] -

[0180] - , , , , ,

[0181] - : Terminal identifier

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

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

[0184] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., the parameters in 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 configured with an X-slot period and search space set #2 is configured with a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0185] [PDCCH: BD / CCE limit]

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

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

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

[0189] 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. μ The subcarrier interval is 15·2 μ In a cell set to kHz, if defined based on slots, follow Table 11 below, and if defined based on spans, follow Table 12 below.

[0190] [Table 11]

[0191]

[0192] [Table 12]

[0193]

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

[0195] As described above, depending on the setting value of the upper layer signaling, the maximum number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is the subcarrier interval In a cell set to kHz, if defined based on slots, follow Table 13 below, and if defined based on spans, follow Table 14 below.

[0196] [Table 13]

[0197]

[0198] [Table 14]

[0199]

[0200] For the convenience of explanation, a situation in which both of the above conditions 1 and 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.

[0201] [PDCCH: Overbooking]

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

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

[0204] 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 with a search space type set as a common search space among the search space sets existing at that time point, over a search space set with a search space type set as a terminal-specific search space.

[0205] When all sets of search spaces configured as common search spaces have been selected (i.e., when Condition A is satisfied even after selecting all search spaces configured as common search spaces), the terminal (or base station) may select sets of search spaces configured as terminal-specific search spaces. In this case, if there are multiple sets of search spaces configured as terminal-specific search spaces, the search space set with a lower search space set index may have a higher priority. Considering the priority, sets of terminal-specific search spaces may be selected within the range where Condition A is satisfied.

[0206] [Regarding Rate Matching / Puncturing]

[0207] In the following, the rate matching operation and puncturing operation will be described in detail.

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

[0209] Rate Matching Operation

[0210] - 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 may transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #3} by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0211] The terminal can determine Resource A and Resource B from scheduling information regarding Symbol Sequence A from the base station, and thereby determine Resource C, which is the area where Resource A and Resource B overlap. The terminal can receive Symbol Sequence A by assuming that Symbol Sequence A was transmitted by mapping it to 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 receive Symbol Sequence A by assuming that it was sequentially mapped to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3}, which corresponds to Resource C. Consequently, the terminal can perform a series of subsequent reception operations by assuming that Symbol Sequence {Symbol #1, Symbol #2, Symbol #3} was transmitted by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0212] Puncturing action

[0213] If there is a resource C corresponding to an area overlapping with resource B among all resources A to which the base station intends to transmit symbol sequence A to a terminal, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only 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.

[0214] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and thereby determine resource C, which is the area where resources A and B overlap. The terminal can receive symbol sequence A by assuming that 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.

[0215] In the following, a method for configuring rate matching resources for the purpose of rate matching in a 5G communication system is described. Rate matching refers to the adjustment of the signal size by considering the amount of resources available to transmit the signal. For example, rate matching of a data channel may mean that the data channel is mapped to a specific time and frequency resource range so that the data size is adjusted accordingly without transmission.

[0216] FIG. 6 is a diagram illustrating a method for a base station and a terminal to transmit and receive data by considering downlink data channels and rate matching resources.

[0217] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station may set one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). The rate matching resource (602) setting information 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.

[0218] The base station can dynamically notify the terminal via DCI whether to rate match a data channel in the above-mentioned rate matching resource portion through additional settings (corresponding to the “rate matching indicator” within the aforementioned DCI format). Specifically, the base station can select some of the above-mentioned rate matching resources and group them into rate matching resource groups, and can 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 can set RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4} as rate matching groups, and can indicate to the terminal via a bitmap whether to rate match in RMG#1 and RMG#2, respectively, using 2 bits within the DCI field. For example, you can indicate “1” when rate matching is required and “0” when rate matching is not required.

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

[0220] RB symbol level

[0221] The terminal can receive up to four RateMatchPatterns as upper layer signaling for each bandwidth portion, and one RateMatchPattern may include the following contents.

[0222] - 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 said Reserved Resource may span across one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may be additionally set.

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

[0224] RE level

[0225] The terminal can receive the following settings through upper-layer signaling.

[0226] - 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 an NR slot corresponding to an LTE subframe.

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

[0228] [Regarding LTE CRS rate match]

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

[0230] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides the ability to set one CRS pattern per serving cell. In Rel-16 NR, this ability has been extended to allow multiple CRS patterns to be set per serving cell. More specifically, 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 lte-CRS-PatternList1-r16 parameter. As another example, for a multi-TRP configured terminal, CRS can be set per TRP. In other words, the CRS pattern for TRP1 is 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 TRP1 and TRP2's CRS patterns to a specific PDSCH (Physical Downlink Shared Channel) or only one TRP's CRS pattern is determined by the crs-RateMatch-PerCORESETPoolIndex-r16 parameter; if the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only one TRP's CRS pattern is applied, whereas otherwise, both TRP's CRS patterns are applied.

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

[0232] [Table 15]

[0233]

[0234]

[0235] [Table 16]

[0236]

[0237] [PDSCH: Regarding Frequency Resource Allocation]

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

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

[0240] Referring to FIG. 7, if the terminal is configured to use only resource type 0 through upper layer signaling (7-00), some downlink control information (DCI) that assigns PDSCH to the terminal includes 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 is transmitted to the RBG indicated as 1 by the bitmap.

[0241] [Table 17]

[0242]

[0243] If the terminal is configured to use only resource type 1 through upper layer signaling (7-05), some DCIs that assign PDSCH to the terminal are It includes frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (7-20) and the length (7-25) of the frequency axis resources continuously allocated therefrom.

[0244] If the terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (7-10), some DCIs that allocate PDSCH to the terminal include frequency axis resource allocation information consisting of bits of the larger value (7-35) of the payload (7-15) for setting resource type 0 and the payload (7-20, 7-25) for setting resource type 1. The conditions for this will be explained later. At this time, one bit may be added to the beginning part (MSB) of the frequency axis resource allocation information within the DCI, and if the 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.

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

[0246] The following describes a time-domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems).

[0247] The base station may set a table for time-domain resource allocation information for the Physical Downlink Shared Channel (PDSCH) and the Physical Uplink Shared Channel (PUSCH) for the 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. In one embodiment, the 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 on the position and length of the start symbol for which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH or PUSCH. For example, information such as [Table 18] or [Table 19] below may be transmitted from the base station to the terminal.

[0248] [Table 18]

[0249]

[0250] [Table 19]

[0251]

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

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

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

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

[0256] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel is the same (9-00, μPDSCH = μPDCCH), the slot number for data and control is the same, so the base station and the terminal can generate a scheduling offset by aligning it with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different (9-05, μPDSCH ≠ μPDCCH), the slot number for data and control is different, so the base station and the terminal can generate a scheduling offset by aligning it with a predetermined slot offset K0 based on the subcarrier spacing of PDCCH.

[0257] [PUSCH: Regarding transmission method]

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

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

[0260] [Table 20]

[0261]

[0262]

[0263] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based 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'.

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

[0265] [Table 21]

[0266]

[0267]

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

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

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

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

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

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

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

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

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

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

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

[0279] [PUSCH: Preparation Process Time]

[0280] 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 specified through the DCI (transmission precoding method of the SRS resource, number of transmission layers, spatial domain transmission filter). In NR, the PUSCH preparation procedure time has been defined taking this into account. The terminal's PUSCH preparation procedure time may follow [Equation 2] below.

[0281] [Mathematical Formula 2]

[0282]

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

[0284] - 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 processing capability is reported as 1 according to the terminal's capability report, 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].

[0285] [Table 22]

[0286]

[0287] [Table 23]

[0288]

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

[0290] - κ: 64

[0291] - μ: μDL or μUL, T proc,2 It follows the value that becomes larger. μDL refers to the downlink numerology through which the PDCCH is transmitted, including the DCI that schedules the PUSCH, and μUL refers to the uplink numerology through which the PUSCH is transmitted.

[0292] - T c : 1 / (Δf max *N f ), Δf max = 480*103Hz, N f It has =4096.

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

[0294] - 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 the higher priority index is used. Otherwise, d2 is 0.

[0295] - 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 time. Otherwise, Text is assumed to be 0.

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

[0297] When the base station and the terminal consider the time-axis resource mapping information of the PUSCH scheduled via the DCI and the influence of the uplink-downlink timing advance, they determine that the PUSCH preparation time is insufficient if the first symbol of the PUSCH starts before the first uplink symbol where the CP begins after Tproc,2, starting from the last symbol of the PDCCH that includes the DCI scheduling the PUSCH. Otherwise, the base station and the terminal determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only when the preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the preparation time is insufficient.

[0298] [CA / DC Related]

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

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

[0301] The main functions of NR SDAP (S25, S70) may include some of the following functions.

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

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

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

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

[0306] Regarding the above SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers to the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The above SDAP header may include QoS flow ID information indicating QoS. The above QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

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

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

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

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

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

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

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

[0314] - Retransmission of PDCP SDUs

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

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

[0317] In the above, the reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and 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 reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

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

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

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

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

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

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

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

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

[0326] - Duplicate detection

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

[0328] - RLC SDU discard function

[0329] RLC re-establishment function

[0330] In the above, the in-sequence delivery function of the NR RLC device refers to the 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 RLC SDUs when the original RLC SDU is 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 they are received (regardless of the order of sequence numbers, 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 this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0331] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering them when a single RLC SDU is 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.

[0332] The NR MAC (S40, S55) 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.

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

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

[0335] - Scheduling information reporting function

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

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

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

[0339] - MBMS service identification function

[0340] - Transport format selection function

[0341] - Padding

[0342] The NR PHY layer (S45, S50) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0343] The detailed structure of the above 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 use a protocol structure having a single structure for each layer, as shown in S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S20, but multiplexes the PHY layer through the MAC layer.

[0344] Referring to the descriptions regarding PDCCH and beam configuration above, PDCCH repeated transmission is not supported in current Rel-15 and Rel-16 NR, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for PDCCH repeated transmission through multiple transmission points (TRPs) to improve the PDCCH reception reliability of a terminal. The specific method is described in detail in the following examples.

[0345] Embodiments of the present disclosure will 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 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).

[0346] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above will be referred to as the NC-JT case.

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

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

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

[0350] - MIB (Master Information Block)

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

[0352] - RRC (Radio Resource Control)

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

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

[0355] - PDCCH (Physical Downlink Control Channel)

[0356] - DCI (Downlink Control Information)

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

[0358] - Group common DCI

[0359] - Common DCI

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

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

[0362] - PUCCH (Physical Uplink Control Channel)

[0363] - UCI (Uplink Control Information)

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

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

[0366] [UCI Multiplexing]

[0367] The terminal can transmit uplink control information to a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Herein, the uplink control information may include at least one of the following.

[0368] - HARQ-ACK information (information on whether PDSCH or PDCCH was successfully received)

[0369] - CSI information (information regarding CSI-RS or SSB measurements, including CQI (channel quality indicator), RI (rank indicator), PMI (precoder matrix indicator) or RSSI (received signal strength indicator), RSRP (reference signal received power), etc.)

[0370] - CG-UCI (configured grant UCI) information (information associated with CG PUSCH, for example, including the HARQ process number of the transmitted CG PUSCH)

[0371] - UTO-UCI (unused transmission occasion(s) indicated by UCI) information (including information regarding CG PUSCHs that will not be transmitted among subsequent CG PUSCHs, etc.)

[0372] The types of uplink control information described above are examples, and other types of UCI may be included. Additionally, the uplink control information described above may be subdivided and considered as different types. Furthermore, the same type of UCI having different priorities may be considered as different types of UCI. For example, HARQ-ACK information with a lower priority and HARQ-ACK information with a higher priority may be considered as different types of UCI. For convenience in this disclosure, UCI types may be expressed as UCI type 1, UCI type 2, …

[0373] When a terminal transmits a UCI over a PUSCH, the PUSCH may include an UL-SCH. Here, the UL-SCH is generally data information transmitted from the terminal to a base station. More specifically, the UL-SCH is information transmitted from the upper layer of the terminal to the physical layer of the terminal and may consist of multiple bits. The terminal can transmit the UL-SCH to the base station via the PUSCH. The physical layer of the base station can obtain the UL-SCH by receiving the PUSCH and can transmit the said UL-SCH to the upper layer of the base station. The multiple bits constituting the UL-SCH at the physical layer can be referred to as a transport block (TB).

[0374] In the present disclosure, unless specifically mentioned, PUSCH may include UL-SCH (or TB) and UCI.

[0375] FIG. 11 is a flowchart illustrating a method of transmitting UL-SCH (or TB) and UCI through PUSCH.

[0376] TB generation and TB CRC attachment block: The terminal receives an UL-SCH from an upper layer and can generate a TB based on the bits included in the UL-SCH. Here, the length of the TB (the number of bits included) can be determined based on the scheduling information of the PUSCH. The terminal may include a cyclic redundancy code (CRC) in the TB. The terminal may refer to the CRC as TB-CRC. When the base station receives the PUSCH, it can determine whether the TB has been correctly decoded based on the TB-CRC. The length of the TB-CRC may be 24 bits.

[0377] The scheduling information of PUSCH used to determine the length of TB may include at least one or more of the following: Modulation and coding scheme (MCS), Time domain resource assignment (TDRA), Frequency domain resource assignment (FDRA) and DMRS configuration information, antenna port (AP) related information and overhead related information (Xoh).

[0378] Code block segmentation and code block CRC attachment block: A TB and a TB-CRC can be divided into one or more code blocks (CBs). Here, the number of bits contained in each CB may be the same. A CB-CRC may be attached to each CB. Here, when a base station decodes a PUSCH, the CB-CRC can be used to determine whether the corresponding CB has been correctly decoded.

[0379] Channel coding of UL-SCH block: Each CB and CB-CRC can be encoded according to channel coding. For example, the CB and CB-CRC can be encoded using LDPC channel coding.

[0380] Rate matching block: Rate matching can be performed on encoded CBs and CB-CRCs based on the number of resources in which UL-SCH can be transmitted in PUSCH. The encoded CBs and CB-CRCs are rate matched based on the number of resources in which UL-SCH can be transmitted in PUSCH. That is, among the encoded CBs and CB-CRCs, the bits to be transmitted to PUSCH can be determined. Here, the resources in which UL-SCH can be transmitted in PUSCH may be resources excluding those transmitted to UCI. Therefore, the result of the rate matching block may vary depending on the number of resources occupied by UCI included in PUSCH.

[0381] Codeblock concatenation block: If multiple CBs are generated, the encoded bits (number determined in the rate matching block) corresponding to each CB and CB-CRC can be configured into a single bit stream. For example, if two CBs are generated, the encoded bits corresponding to the 0th CB and CB-CRC are {C 0,0 , C 0,1,..., C 0,M-1}, encoded bits corresponding to the 1st CB and CB-CRC {C 1,0 , C 1,1,..., C 1,M-1 When saying}, {C 0,0 , C 0,1,..., C 0,M-1 ,C 1,0 , C 1,1,..., C 1,M-1} can be generated.

[0382] UCI bit generation block: The terminal can generate UCI bits to be included in PUSCH according to instructions from the base station. Here, the UCI may include one or more types. FIG. 11 is a diagram showing an example of a single type of UCI.

[0383] Code block segmentation and CRC attachment block: If the UCI bits exceed a certain size, the terminal can divide the UCI into multiple UCI code blocks and attach a CRC to each UCI code block.

[0384] Channel coding of UCI block: UCI codeblocks and CRCs can be encoded according to channel coding. For example, UCI codeblocks and CRCs can be encoded using polar channel coding.

[0385] Rate matching block: The number of resources transmitted in PUSCH, consisting of encoded UCI codeblocks and CRCs, can be determined. Specifically, the terminal has a beta offset value corresponding to the UCI type ( ) and an alpha value (α) can be set (e.g., set via upper-layer signaling), and the number of resources transmitted in PUSCH can be determined based on these values. For example, if the UCI type is HARQ-ACK, the number of resources can be determined by the following formula. If the UCI type is HARQ-ACK, the resources for HARQ-ACK transmission are the number of coded modulation symbols for HARQ-ACK transmission determined by the following formula. It can be determined based on.

[0386] [Mathematical Formula 3]

[0387]

[0388] Here, is the number of HARQ-ACK bits, is the number of CRC bits, and is the beta offset value for HARQ-ACK, and is the number of CBs included in PUSCH (the number of CBs for UL-SCH of PUSCH transmission), and is the number of bits included in the CB (the size of the r-th CB for the UL-SCH of the PUSCH transmission (codeblock size)), represents the number of REs that can be used for UCI transmission in OFDM symbol l, and α is the alpha value, is the number of symbols included in PUSCH, and l_0 is the index of the OFDM symbol that does not contain a DMRS after the first DMRS (in a PUSCH transmission, the index of the first OFDM symbol that does not carry the DMRS of PUSCH after the first DMRS symbol).

[0389] Similarly, if the UCI type is CSI part 1 and CSI part 2, the number of resources ( ) can be determined by the following formula. If the UCI type is CSI part 1, the resource for CSI part 1 transmission is the number of coded modulation symbols for CSI part 1 transmission determined by the following formula. It can be determined based on. If the UCI type is CSI part 2, the resource for CSI part 2 transmission is the number of coded modulation symbols for CSI part 2 transmission determined by the following formula. It can be determined based on.

[0390] [Mathematical Formula 4]

[0391]

[0392] Here, When deciding, is the beta offset value corresponding to CSI part 1, and When deciding, may be a beta offset value corresponding to CSI part 2. is the number of CSI part 1 bits, is the number of CSI part 2 bits. is the number of CBs included in PUSCH (the number of CBs for UL-SCH of PUSCH transmission), and is the number of bits included in the CB (the size of the r-th CB for the UL-SCH of the PUSCH transmission (codeblock size)), represents the number of REs that can be used for UCI transmission in OFDM symbol l, and α is the alpha value, is the number of symbols included in PUSCH.

[0393] Codeblock concatenation block: If the UCI consists of multiple UCI codeblocks, each encoded UCI codeblock and CRC can be composed of a single bit stream.

[0394] Data and control multiplexing block: Encoded UCI and encoded UL-SCH can be multiplexed on PUSCH. In this case, the REs occupied by UCI on PUSCH can be determined according to the UCI-to-RE mapping method.

[0395] FIG. 12 is a diagram illustrating UCI-to-RE mapping when multiplexing UCI on PUSCH. With reference to FIG. 12, a specific UCI-to-RE mapping method and PUSCH may be as follows.

[0396] If the HARQ-ACK bits are greater than 2 bits, UCI and UL-SCH can be mapped onto PUSCH according to the following steps.

[0397] Step 1: HARQ-ACK bits are multiplexed on PUSCH using the first UCI-to-RE mapping method.

[0398] HARQ-ACK is mapped to available REs in the OFDM symbol following the first consecutive DMRS OFDM symbol. Here, if the number of REs required for HARQ-ACK transmission is greater than the number of REs included in the OFDM symbol, all REs are used for HARQ-ACK transmission; otherwise, some of the REs included in the OFDM symbol may be used for HARQ-ACK transmission.

[0399] Step 2: CSI part 1 bits are multiplexed on PUSCH using the second UCI-to-RE mapping method.

[0400] The CSI part 1 bits may start from the first available non-DMRS OFDM within the PUSCH allocation. If the number of REs for CSI part 1 transmission is greater than the number of REs included in the OFDM symbol, all REs may be used for CSI part 1 transmission. Otherwise, some of the REs included in the OFDM symbol may be used for CSI part 1 transmission. Here, if the OFDM symbol includes REs used for HARQ-ACK, said REs may be excluded.

[0401] Step 3: The CSI part 2 bits are multiplexed on PUSCH using the third UCI-to-RE mapping method.

[0402] The CSI part 2 bits may start from the first available non-DMRS OFDM within the PUSCH allocation. If the number of REs for CSI part 2 transmission is greater than the REs included in the OFDM symbol, all REs may be used for CSI part 2 transmission. Otherwise, some of the REs included in the OFDM symbol may be used for CSI part 2 transmission. Here, if the OFDM symbol includes REs used for HARQ-ACK, said REs may be excluded. Here, if the OFDM symbol includes REs used for CSI part 1, said REs may be excluded.

[0403] Step 4: UL-SCH is multiplexed onto PUSCH.

[0404] The terminal can transmit UL-SCH in REs where UL-SCH is transmittable among REs not occupied by HARQ-ACK, CSI part 1, or CSI part 2 on the PUSCH. If UL-SCH includes multiple CBs, the terminal can transmit CBs of a preceding index in the preceding symbol. Thus, CB#0 (CB with index 0) can be mapped along the frequency axis starting from the earliest OFDM symbol, and if there are no more remaining REs in one OFDM symbol, it can be mapped along the frequency axis to the next symbol. The above mapping method can be called a frequency-first, time-second mapping method.

[0405] Specific UCI-to-RE mapping methods and PUSCH generation methods can be found in Section 6.2.7 of the 3GPP standard document TS38.212.

[0406] FIG. 13 is a drawing illustrating the technical problem to be solved in the present disclosure.

[0407] Referring to FIG. 13, the PUSCH generation method described above may have the following problems.

[0408] The terminal is the number of modulation symbols occupied by the UCI (e.g., Q ACK , Q CSI-1 , Q CSI-2 Depending on the number of REs occupied by the UL-SCH, the number of REs may vary. Therefore, the terminal must re-rate-match the UL-SCH whenever the number of modulation symbols occupied by the UCI changes. Furthermore, since the UCI is transmitted at the beginning of the PUSCH (front OFDM symbols), all code blocks (CBs) of the UL-SCH must be newly rate-matched. For example, if an additional UCI is multiplexed into the PUSCH in FIG. 13, all N CB#0, ..., CB#(N-1) included in the PUSCH must be newly rate-matched. This can increase the computational complexity of the terminal.

[0409] As another problem, the terminal may fail to receive the DCI that schedules the UCI. Consequently, the number of modulation symbols occupied by the UCI multiplexed to the PUSCH by the terminal may differ from the value expected by the base station. Since the rate matching of the UL-SCH is determined by the number of modulation symbols occupied by the UCI, the result of the terminal's rate matching and the rate matching expected by the base station may differ. Therefore, the base station may fail to receive not only the UCI but also the UL-SCH.

[0410] A solution to this is to perform rate matching for UL-SCH independently of the number of modulation symbols occupied by UCI. More specifically, rate matching for UL-SCH is performed based on the resources of the scheduled PUSCH (number of OFDM symbols, number of RBs, MCS value, and number of MIMO layers), and the rate-matched UL-SCHs can be mapped onto the PUSCH. Furthermore, when UCI is multiplexed onto the PUSCH, UCI can be mapped to REs corresponding to the number of modulation symbols occupied by UCI. Since UL-SCH is mapped to the aforementioned REs on the PUSCH but UCI is mapped to those REs, UL-SCH may not be transmitted on the said REs. This can be described as UL-SCH being punctured.

[0411] According to the method described above, since UL-SCH is punctuated in some REs (REs mapped to UCI), the reception performance of UL-SCH may be degraded. In particular, if UL-SCH consists of multiple CBs, the reception performance of the CB affected by punctuation among the CBs may be degraded. Since the CBs are mapped to PUSCH in chronological order, the reception performance of CB#0 (the earliest CB among the CBs included in UL-SCH) may be degraded. Furthermore, if reception fails for even one CB among the UL-SCH included in PUSCH, the base station must request the terminal to retransmit the said UL-SCH. This may cause waste of uplink resources and unnecessary energy consumption by the terminal.

[0412] In the present disclosure, various methods are disclosed to prevent performance degradation of UL-SCH when UL-SCH is punctured.

[0413] Example 1. Allocating more redundancy to punctured CB(s)

[0414] In one embodiment of the present disclosure, the terminal may allocate more redundancy to specific CBs. Herein, the specific CBs may be CBs expected to be punctured due to the UCI. A more specific method is as follows.

[0415] According to the prior art, the same rate-matching is applied to multiple CBs included in the UL-SCH. The same rate-matching means that the number of bits transmitted after each CB is channel-coded is nearly the same. More specifically, the number of bits transmitted after the CBs are channel-coded can be determined as shown in Table 24.

[0416] [Table 24]

[0417]

[0418]

[0419] Referring to Table 24, based on the number of bits that can transmit UL-SCH over PUSCH, the number of G and CB, and C, the number of bits after rate matching is This or It may be. The above value may be determined regardless of whether it is punctuated according to the UCI.

[0420] FIG. 14 is a drawing of an example in which more redundancy is allocated to some CB(s) according to one embodiment of the present disclosure.

[0421] Referring to FIG. 14, the terminal can allocate more redundancy to CB(s) where punctuation is expected by the UCI. Here, if more redundancy is allocated to CB(s), the CB(s) may have a low code rate.

[0422] In one embodiment of the present disclosure, the terminal may allocate a larger number of redundancies to some CBs of the PUSCH. In other words, the terminal may allocate a larger E to some CBs of the PUSCH.r A value can be assigned. A method for doing this is disclosed.

[0423] The terminal can divide G, the number of bits that can transmit UL-SCH over PUSCH, into two. G UCI is a value for CBs affected by UCI transmission, and G noUCI can be a value for CBs that are not affected by UCI transmission. G = G UCI + G noUCI It may be. The terminal is E of CB r affected by UCI transmission r The value can be determined as follows.

[0424] or

[0425] The terminal is E of CB r that is not affected by UCI transmission r The value can be determined as follows.

[0426] or

[0427] Here, C UCI is the number of CBs affected by UCI transmission, and C noUCI can be the number of CBs unaffected by UCI transmission. And, C=C UCI +C noUCI It could be. C UCI =1 or, C UCI is a value set by the base station to the terminal, or it may be the number of CBs in which at least one RE is punctured during UCI multiplexing.

[0428] or or It can be determined as. It could be. That is, G UCIγ can be determined based on the ratio of the number of CBs affected by UCI (CUCI) to the total number of CBs (C). γ can be a factor for allocating more redundancy resources to CBs affected by UCI. Here, for values ​​where γ > 1, the terminal can be set by the base station (e.g., set via upper layer signaling) or instructed via DCI.

[0429] According to the present disclosure, rate-matching can be determined through Table 25.

[0430] [Table 25]

[0431]

[0432]

[0433] The effects of the present disclosure are explained through examples.

[0434] For example, PUSCH includes 4 CBs (C=4), and It is assumed that.

[0435] According to Table 24, the E of the four CBs r value silver It can be determined as such. That is, CBs can be rate-matched identically.

[0436] For example, assume that among the four CBs, the first two are CBs affected by UCI multiplexing. That is, C=4, C UCI =2, C noUCI = can be 4. γ=1.2 can be set. According to Table 25, , It could be. E of the 4 CBs r value silver It can be determined as such. In other words, CBs affected by the UCI and CBs not affected by the UCI can be rate-matched differently. CBs affected by the UCI have a larger E rSince it has a value, it can contain more redundancies. Therefore, even if some REs among the CBs affected by UCI are punctured, the CBs can still be successfully received.

[0437] According to the present disclosure, the terminal may selectively perform one of the rate-matching methods of PUSCH in Tables 24 and 25.

[0438] For example, if there is no UCI to be multiplexed on the PUSCH, the terminal can perform rate-matching as shown in Table 24, and if there is a UCI to be multiplexed on the PUSCH, it can perform rate-matching as shown in Table 25. That is, depending on whether UCI multiplexing is performed, the terminal can selectively perform one of the methods in Table 24 and Table 25.

[0439] For example, if the UCI to be multiplexed on PUSCH is shorter than a certain length, the terminal can perform rate-matching as shown in Table 24, and if the UCI to be multiplexed on PUSCH is longer than or equal to a certain length, the terminal can perform rate-matching as shown in Table 25. That is, depending on the length of the UCI bits being multiplexed, the terminal can selectively perform one of the methods in Table 24 and Table 25.

[0440] For example, the terminal can perform rate-matching as shown in Table 24 when the number of modulation symbols occupied by the UCI to be multiplexed in the PUSCH is less than a certain value, and can perform rate-matching as shown in Table 25 when the number of modulation symbols occupied by the UCI to be multiplexed in the PUSCH is greater than or equal to a certain value. That is, the terminal can selectively perform one of the methods in Table 24 and Table 25 depending on the number of modulation symbols occupied by the multiplexed UCI. Here, the certain value may be a value determined based on the number of REs included in the PUSCH. For example, the certain value may be determined based on the value obtained by multiplying the number of REs included in the PUSCH by θ. Here, θ can be set by the base station to the terminal as a positive number less than or equal to 1. Based on the value of θ, the terminal can selectively perform one of the methods in Table 24 and Table 25 based on how much of the PUSCH is affected by the UCI.

[0441] For example, a DCI scheduling PUSCH may specify one of the methods in Table 24 and Table 25. For example, the DCI may include a bit field specifying one of the methods in Table 24 and Table 25, and based on the value of said bit field, one of the methods in Table 24 and Table 25 may be specified. For example, whether the rate-matching method of PUSCH in Table 24 or Table 25 is performed may be determined by the set / specified value of γ. Table 24 may be the same as the case where γ=1. Therefore, if γ=1 is specified, Table 24 is used, and if γ>1 is specified, the method of Table 25 may be used.

[0442] In one embodiment of the present disclosure, the terminal is C UCI One cannot expect CBs exceeding CBs to be punctured by the UCI. That is, the terminal is at most C UCIOnly CBs can be determined to be punctured by the UCI. If, in PUSCH C UCI If CBs exceeding CBs are punctured by UCI, the terminal may not perform UCI multiplexing in the PUSCH.

[0443] FIG. 15 is a flowchart illustrating an example of a method for allocating more redundancy to some CB(s) according to an embodiment of the present disclosure. The flowchart of FIG. 15 illustrates an exemplary method that may be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0444] Referring to Fig. 15, the process of the terminal may be as follows.

[0445] Step 1 (1500): The terminal may receive configuration information from the base station via an upper layer signal (e.g., RRC signal) for allocating more redundancy to some CB(s) of the PUSCH. Here, the upper layer signal (e.g., RRC signal) may include a number of CBs to allocate more redundancy or a γ value corresponding to more redundancy.

[0446] Step 2 (1510): The terminal may determine whether to rate-match all CBs to have the same redundancy or rate-match some CBs to have more redundancy depending on the conditions. This may be determined based on at least one of the presence of a UCI multiplexed on the PUSCH, the length of the UCI, the number of modulated symbols occupied by the UCI, and an indication in the DCI format.

[0447] Step 3 (1520): The terminal can generate a PUSCH. A UL-SCH can be mapped to all REs of the PUSCH first. Here, in the case of different rate-matching, a specific CB(s) can be mapped to more REs than other CB(s). Here, in the case of the same rate-matching, the same number of REs can be mapped to all CB(s). If the terminal has a UCI to multiplex in the PUSCH, the UCI can be mapped to some REs of the PUSCH. Here, a UL-SCH can be mapped to the RE where the UCI is mapped, but the UL-SCH is punctured and the UCI is mapped.

[0448] Step 4 (1530): The terminal can transmit the generated PUSCH to the base station. The base station receives the PUSCH and can decode the UCI from the PUSCH. Here, the UCI can be obtained from the REs to which the UCI is mapped. The base station can determine the REs to which CBs are transmitted in the PUSCH based on the rate-matching method of the PUSCH (whether it is same rate-matching or different rate-matching). If it is same rate-matching, the CBs can be decoded based on the same number of REs. If it is different rate-matching, the specific CBs can be decoded based on a larger number of REs. At this time, the base station can decode the CBs by assuming that the UL-SCH was not transmitted in the REs to which the UCI is mapped.

[0449] Example 2. Soft Puncturing

[0450] In one embodiment of the present disclosure, a terminal may multiplex UCI and UL-SCH in an RE where UCI is mapped. According to the present disclosure, for a single RE, UL-SCH (partially or entirely) and UCI may be transmitted simultaneously. An embodiment of the present disclosure may be referred to as soft-puncturing. For reference, if not all UL-SCH is transmitted in an RE where UCI is mapped, it may be referred to as hard-puncturing.

[0451] FIG. 16 is a diagram of an example in which UL-SCH and UCI are transmitted simultaneously to a single RE according to one embodiment of the present disclosure.

[0452] Referring to Fig. 16, UCI and UL-SCH can be transmitted simultaneously in REs where UCI is mapped. Here, in REs where UCI is mapped, a higher modulation order is used compared to REs where UCI is not mapped, so that a larger number of bits can be transmitted.

[0453] bits corresponding to UL-SCH transmitted in RE j Modulated symbols Let's say that. And, the bits corresponding to the UCI transmitted from RE j Modulated symbols Let's say. Here is the modulation order of PUSCH. For example, when punctuation is applied, according to this, for RE j, is not transmitted, can be transmitted. Therefore, UL-SCH for RE j is not transmitted, UCI Only can be transmitted.

[0454] According to one embodiment of the present disclosure, a terminal can multiplex bits corresponding to UL-SCH and bits corresponding to UCI in a single RE and transmit them. More specifically, with respect to RE j, bits corresponding to UL-SCH bits corresponding to UCI It is multiplexed, and a single modulated symbol This can be transmitted. It can be modulated to a value higher than the modulation order of PUSCH.

[0455] The multiplexing method and the duplicating method may be one or more of the following.

[0456] In the first method, the terminal has bits corresponding to UL-SCH class Combine to form a single bit sequence It can generate. The terminal can modulate the bit sequence with a modulation of modulation order 2Qm. For example, if Qm=2 (QPSK(Quadrature Phase Shift Keying)), the terminal modulates to 2*Qm = 4 (16QAM(Quadrature Amplitude Modulation)), It can generate. For example, if Qm=4 (16QAM), modulate to 2*Qm = 8 (256QAM), It can generate.

[0457] In the second method, the terminal has bits corresponding to UL-SCH Some of them and A single bit sequence can be generated by combining them. For example, the leading half or the odd-numbered bits among the bits corresponding to UL-SCH can be selected. If the leading half of the bits are selected, as a single bit sequence It can generate. The terminal can modulate the bit sequence with a modulation of (Qm + Qm / 2). For example, if Qm=2 (QPSK), the terminal modulates to (Qm + Qm / 2) = 3 (8PSK (phase shift keying)), It can generate. For example, if the terminal Qm=4 (16QAM), it modulates to (Qm+ Qm / 2) = 6 (64QAM), It can generate. In the description of the second method described above, half of the bits corresponding to UL-SCH were used as an example, but this is an example and the present disclosure is not limited thereto. For example, only 1 / 4 of the bits corresponding to UL-SCH may be used, or only 2 bits of the bits corresponding to UL-SCH may be used.

[0458] In the third method, the terminal bits corresponding to UL-SCH bundling some of them A single bit sequence can be generated by combining them. The terminal is the bits corresponding to UL-SCH bundling some of them and other parts, A single bit sequence can be generated by combining them. For example, among the bits corresponding to UL-SCH, the preceding odd-numbered bits and even-numbered bits can be bundled. The terminal, with a single bit sequence It can generate. is an operator representing a direct sum. The terminal can modulate the above bit sequence with a modulation order of (Qm + Qm / 2). For example, if Qm=2 (QPSK), the terminal modulates to (Qm + Qm / 2) = 3 (8PSK), It can generate. For example, if the terminal Qm=4 (16QAM), it modulates to (Qm+ Qm / 2) = 6 (64QAM), It can generate.

[0459] In the fourth method, the terminal bits corresponding to UL-SCH Some of them and Some of them can be combined to generate a single bit sequence. For example, the leading half or odd-numbered bits among the bits corresponding to UL-SCH may be selected. Also, for example, the leading half or odd-numbered bits among the bits corresponding to UCI may be selected. If the leading half of the bits are selected, as a single bit sequence It can generate. The terminal can modulate the bit sequence with a modulation of modulation order Qm. For example, if Qm=2 (QPSK), the terminal modulates to Qm = 2 (QPSK), It can generate. For example, if the terminal is Qm=4 (16QAM), it modulates to Qm = 4 (16QAM), It can generate. In the fourth method, all REs in PUSCH can have the same modulation order.

[0460] According to the above-described embodiment, a first modulation order may be applied to an RE in which only UL-SCH is transmitted in PUSCH, and a second modulation order may be applied to an RE in which UCI and UL-SCH are transmitted simultaneously. Here, the second modulation order may be greater than or equal to the first modulation order.

[0461] According to the above-described embodiment, the terminal can transmit some or all of the UL-SCH even if the UCI is multiplexed in the PUSCH. For example, in the first method, all bits of the UL-SCH can be transmitted in the PUSCH. Punctuation may not occur. For example, in the second and third methods, some bits of the UL-SCH are punctured, while the remaining bits can be transmitted in the PUSCH. Thus, the performance degradation of the UL-SCH due to punctuation can be limited. According to the fourth method, some bits of the UL-SCH and some bits of the UCI of the terminal can be punctured. Therefore, from the perspective of the base station, higher UL-SCH reception performance can be achieved than when only the UL-SCH is punctured.

[0462] FIG. 17 is a flowchart illustrating an example of a soft-puncturing method according to an embodiment of the present disclosure. The flowchart of FIG. 17 illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0463] Referring to Fig. 17, the process of the terminal may be as follows.

[0464] Step 1 (1700): The terminal may receive configuration information related to soft-punctuing through a higher layer signal of the base station (e.g., an RRC signal). The configuration information related to soft-punctuing may include information on how UL-SCH bits and UCI bits are converted into a single modulation symbol in an RE where UCI is multiplexed. Based on the configuration information related to soft-punctuing, one of the first to fourth methods described above may be configured.

[0465] Step 2 (1710): The terminal can generate a PUSCH. A UL-SCH can be mapped first to all REs of the PUSCH. In the REs where only the UL-SCH is mapped, the UL-SCH can be modulated according to the modulation order of the PUSCH. If there is a UCI to be multiplexed in the PUSCH, the UCI can be mapped to some REs of the PUSCH. Here, in the RE where the UCI is mapped, the UL-SCH and the UCI can be modulated by a single modulation symbol. Here, according to one of the first to fourth methods described above, the UL-SCH and the UCI can be modulated by a single modulation symbol. Here, when the UL-SCH and the UCI are modulated, the modulation order may be greater than or equal to the modulation order of the PUSCH.

[0466] Step 3 (1720): The terminal can transmit PUSCH to the base station. The PUSCH may include REs that are multiplexed from UL-SCH and UCI.

[0467] For more specific details regarding the operation of a terminal according to one embodiment of the present disclosure described above, refer to the description of various embodiments of the present disclosure described above.

[0468] Embodiment 2 of the present disclosure described above may be used in combination with Embodiment 1. For example, a terminal may allocate many redundancy bits to CB(s) that are punctured or likely to be punctured, and allocate some bits to UCIs for modulation symbols transmitted from REs mapped to said CB(s). When used in combination, fewer redundancy bits may be added to CB(s) affected by puncturing than when Embodiment 1 is used alone. Reflecting this, the base station may set γ to a smaller value than when Embodiment 1 is used alone, in the method of Table 25, for the terminal.

[0469] Example 3. Punctured CB(s) retransmission

[0470] In a PUSCH, the reception performance of punctured CBs may be lower than that of non-punctured CBs. For example, if a PUSCH contains two CBs, and the first CB is punctured while the second CB is not, the base station may be able to successfully receive the second CB but may not be able to successfully receive the first CB. In this case, the base station may instruct the retransmission of the UL-SCH containing the first CB and the second CB. Here, the second CB does not require retransmission, but there is a problem that it must be retransmitted.

[0471] FIG. 18 is a drawing illustrating an example of a CB retransmission method according to one embodiment of the present disclosure.

[0472] According to one embodiment of the present disclosure, a terminal may retransmit only punctured CBs. More specifically, the terminal may receive a UL-SCH retransmission DCI from a base station. The DCI may instruct the retransmission of all CBs included in the UL-SCH, or instruct the retransmission of only CBs in the UL-SCH that have been punctured by a UCI. If the DCI instructs the retransmission of all CBs included in the UL-SCH, the PUSCH scheduled by the DCI may include all CBs of the UL-SCH. If the DCI instructs the retransmission of only CBs among the CBs included in the UL-SCH that have been punctured by a UCI, the terminal may include only CBs punctured by a UCI in the PUSCH scheduled by the DCI.

[0473] Here, CBs punctuated by UCI multiplexing can be determined as follows. For example, if at least one RE among the REs corresponding to a CB is punctuated by UCI, the terminal can determine that the CB is a CB punctuated by UCI multiplexing. For example, if a certain number (a certain ratio; for example, a certain number or a certain ratio may be predetermined and / or set and / or explicitly / implicitly indicated) or more of the REs corresponding to a CB are punctuated by UCI, the terminal can determine that the CB is a CB punctuated by UCI multiplexing. For example, CB#0 (the leading CB among UL-SCH) may be retransmitted regardless of the CBs punctuated by UCI. That is, the terminal does not determine that the CBs are actually punctuated by the UCI, and the terminal can always determine that the retransmission of CB#0 is a CB punctuated by UCI multiplexing (i.e., a CB that requires retransmission). Regardless of whether it is actually punctuated, the terminal can perform retransmission for CB#0 when retransmission is indicated by the UL-SCH.

[0474] DCI may include a 1-bit indicator. If the value of the 1-bit indicator is '0' (or '1'), all CBs included in UL-SCH may be retransmitted. If the value of the 1-bit indicator is '1' (or '0'), only the CBs (or CB#0) punctured by UCI among the CBs included in UL-SCH may be retransmitted.

[0475] DCI may not include a separate indicator. Instead, the terminal may determine which CBs to retransmit based on the values ​​of other fields of the DCI. For example, if PUSCH indicates retransmission (NDI is not toggling) and the value of DAI (downlink assignment index) is a specific value, the terminal may retransmit only the CBs (or CB#0) punctuated by the UCI among the CBs included in UL-SCH. For example, if PUSCH indicates retransmission (NDI is not toggling) and the value of the UL-SCH indicator is '0', the terminal may retransmit only the CBs (or CB#0) punctuated by the UCI among the CBs included in UL-SCH. As an example, only the CBs (or CB#0) punctured by UCI among the CBs included in UL-SCH can be retransmitted by a combination of values ​​of DCI fields other than the DCI field exemplified above.

[0476] FIG. 19 is a flowchart illustrating an example of a method for retransmitting punctured CBs according to an embodiment of the present disclosure. The flowchart of FIG. 19 illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0477] Referring to Fig. 19, the process of the terminal may be as follows.

[0478] Step 1 (1900): The terminal can receive configuration information for retransmitting CB(s) affected by UCI multiplexing from the base station's upper layer signal (e.g., RRC signal).

[0479] Step 2 (1910): After the terminal transmits the PUSCH with the UCI multiplexed, it can monitor the DCI format that directs the retransmission of the CB(s) affected (punctuated) by the UCI multiplexing.

[0480] Step 3 (1920): If the terminal receives a DCI format instructing the retransmission of CB(s) that have been affected (punctured) by UCI multiplexing, the terminal can determine which CB(s) need to be retransmitted. For example, a CB in which at least one RE has been punctured due to UCI multiplexing on the PUSCH, or a CB in which a certain number (a certain ratio) or more of REs have been punctured, or CB#0 may be determined as a CB that has been punctured due to UCI multiplexing (CBs that need to be retransmitted).

[0481] Step 4 (1930): The terminal can transmit a PUSCH containing CB(s) that need to be retransmitted from the PUSCH resource indicated by the DCI.

[0482] For more specific details regarding the operation of a terminal according to one embodiment of the present disclosure described above, refer to the description of various embodiments of the present disclosure described above.

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

[0484] Referring to FIG. 20, the terminal may include a transceiver (referring to a terminal receiver (2000) and a terminal transmitter (2010)), a memory (not shown), and a terminal processing unit (2005, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (2000, 2010), memory, and terminal processing unit (2005) 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.

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

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

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

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

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

[0490] Referring to FIG. 21, the base station may include a transceiver unit (referring to a base station receiver unit (2130) and a base station transmitter unit (2110), a memory (not shown), and a base station processing unit (2105, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (2100, 2110), memory, and base station processing unit (2105) 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, memory, and processor may be implemented in the form of a single chip.

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

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

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

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

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

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

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

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

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

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

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

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

[0503] Additionally, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the present disclosure.

[0504] 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. A method performed by a terminal in a communication system, A step of receiving information about parameter γ>1; A step of obtaining a transport block corresponding to the UL-SCH (uplink shared channel); A step of obtaining a plurality of code blocks based on dividing the transmission block, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is determined based on the parameter γ; A step of mapping the plurality of code blocks to REs (resource elements) corresponding to a PUSCH (physical uplink shared channel), wherein at least some of the REs corresponding to the PUSCH to which the one or more first code blocks are mapped are punctured and bits for UCI (uplink control information) are mapped; and A method comprising the step of transmitting the above PUSCH.

2. In Paragraph 1, The number of bits for the one or more first code blocks is determined based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and If the number of the above UCI bits is greater than or equal to the above specific threshold, (i) the number of bits for the above one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, If the number of the above UCI bits is less than the above specific threshold, the number of bits for the one or more first code blocks and the number of bits for the one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, And, G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of the above one or more second blocks, and C is the number of scheduled code blocks of the above transmission block, method.

3. In Paragraph 1, Information regarding the above parameter γ is received through upper-layer signaling or the first DCI (downlink control information), and A method in which the one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the one or more second code blocks are the remaining one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

4. In Paragraph 1, Step of receiving the second DCI; A step of determining retransmission for at least some of the code blocks of the one or more first code blocks corresponding to the punctured RE based on the second DCI; and The method includes the step of transmitting a PUSCH containing at least some of the code blocks mentioned above, and The retransmission of at least some of the code blocks mentioned above is: Determined based on a 1-bit indicator included in the second DCI that indicates whether to retransmit at least some of the code blocks, or It is determined based on the fact that the NDI (new data indicator) included in the above second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or A method in which the NDI included in the second DCI is not toggled and the UL-SCH indicator is determined based on a specific value.

5. In Paragraph 1, A method in which at least some of the REs corresponding to the above PUSCH are mapped to at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH, and at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH are based on the same modulation order, and said same modulation order is determined based on the modulation order indicated for the above UL-SCH.

6. In a terminal of a communication system, Transmitter / receiver; and It includes a processor connected to the above-mentioned transceiver, and the processor is: Receive information about parameter γ>1; Obtain a transport block corresponding to the UL-SCH (uplink shared channel); A plurality of code blocks are obtained based on dividing the transmission block, wherein the plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is determined based on the parameter γ; The plurality of code blocks are mapped to REs (resource elements) corresponding to PUSCH (physical uplink shared channel), at least some of the REs corresponding to PUSCH to which the one or more first code blocks are mapped are punctured and bits for UCI (uplink control information) are mapped; and A terminal configured to transmit the above PUSCH.

7. In Paragraph 6, The number of bits for the one or more first code blocks is determined based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and If the number of the above UCI bits is greater than or equal to the above specific threshold, (i) the number of bits for the above one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, If the number of the above UCI bits is less than the above specific threshold, the number of bits for the one or more first code blocks and the number of bits for the one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, And, G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of the above one or more second blocks, and C is the number of scheduled code blocks of the above transmission block, a terminal.

8. In Paragraph 6, Information regarding the above parameter γ is received through upper-layer signaling or the first DCI (downlink control information), and A terminal, wherein the above one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the above one or more second code blocks are the remaining one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

9. In claim 6, the processor is: Receive the 2nd DCI; Determining retransmission for at least some of the one or more first code blocks corresponding to the punctured RE based on the second DCI; and It is configured to transmit a PUSCH containing at least some of the code blocks mentioned above, and The retransmission of at least some of the code blocks mentioned above is: Determined based on a 1-bit indicator included in the second DCI that indicates whether to retransmit at least some of the code blocks, or It is determined based on the fact that the NDI (new data indicator) included in the above second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or A terminal included in the second DCI, determined based on the fact that the NDI is not toggled and the UL-SCH indicator is a specific value.

10. In Paragraph 6, A terminal in which at least some of the REs corresponding to the above PUSCH are mapped to at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH, and at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH are based on the same modulation order, and the same modulation order is determined based on the modulation order indicated for the above UL-SCH.

11. In a base station of a communication system, Transmitter / receiver; and It includes a processor connected to the above-mentioned transceiver, and the processor is: Transmit information about parameter γ>1; Receive PUSCH (physical uplink shared channel); Acquiring a plurality of code blocks mapped onto REs (resource elements) corresponding to the above PUSCH and bits for UCI (uplink control information); and It is configured to obtain a transport block corresponding to the UL-SCH (uplink shared channel) based on the above plurality of code blocks, and The plurality of code blocks include one or more first code blocks and one or more second code blocks, and the number of bits for the one or more first code blocks is based on the parameter γ, and A base station in which at least some of the REs corresponding to the above PUSCH, to which the above one or more first code blocks are mapped, are punctured, and bits for the above UCI are mapped to the above punctured REs.

12. In Paragraph 11, The number of bits for the one or more first code blocks is based on the parameter γ when the number of UCI bits is greater than or equal to a specific threshold, and If the number of the above UCI bits is greater than or equal to the above specific threshold, (i) the number of bits for the above one or more first code blocks is or Based on, and (ii) the number of bits for one or more second code blocks is or Based on, If the number of the above UCI bits is less than the above specific threshold, the number of bits for the one or more first code blocks and the number of bits for the one or more second code blocks or Based on, is the number of transmission layers to which the above transmission block is mapped, and is the modulation order, and , , or And, And, G is the total number of coded bits available for the transmission of the above transmission block, and is the number of the above one or more first code blocks, and is the number of the above one or more second blocks, and C is the number of scheduled code blocks of the above transmission block, a base station.

13. In Paragraph 11, Information regarding the above parameter γ is transmitted through upper-layer signaling or the first DCI (downlink control information), and A method in which the one or more first code blocks are a series of one or more code blocks including the code block with the lowest index among the plurality of code blocks, and the one or more second code blocks are the remaining one or more code blocks among the plurality of code blocks excluding the one or more first code blocks.

14. In claim 11, the processor is: Determining to request retransmission for at least some of the one or more first code blocks corresponding to the punctured RE; Transmitting a second DCI to request the above retransmission; and It is configured to transmit a PUSCH containing at least some of the code blocks mentioned above, and The above retransmission request is: Indicated based on a 1-bit indicator included in the second DCI that indicates whether to retransmit at least some of the code blocks, or Indicated based on the fact that the NDI (new data indicator) included in the above second DCI is not toggled and the DAI (uplink downlink assignment index) is a specific value, or A base station included in the second DCI, wherein the NDI is not toggled and the UL-SCH indicator is indicated based on a specific value.

15. In Paragraph 11, A base station in which at least some of the REs corresponding to the above PUSCH are mapped to at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH, and at least some of the bits for the above UCI and at least some of the bits for the above UL-SCH are based on the same modulation order, and the same modulation order is based on the modulation order indicated for the above UL-SCH.

Images