Method and device for transmitting uplink control information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. One embodiment of the present invention provides a method by which a terminal transmits uplink control information (UCI) to a base station.

Description

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

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for a terminal to transmit an uplink control signal 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 (IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for the integration of Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

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

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, 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 developments and advancements in mobile communication systems, it has become possible to provide a variety of services, and thus measures to effectively provide these services are required.

[0009] According to one embodiment of the invention, the invention aims to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0010] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0011] One embodiment of the present invention relates to a method in which a terminal transmits uplink control information (UCI) to a base station.

[0012] Based on the discussion described above, the present disclosure may provide a method for processing a control signal of a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

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

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

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

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

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

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

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

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

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

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

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

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

[0025] FIG. 11 is a flowchart illustrating a method of transmitting UL-SCH (or TB) and UCI through PUSCH according to one embodiment of the present disclosure.

[0026] FIG. 12 is a diagram illustrating UCI-to-RE mapping when multiplexing UCI on PUSCH according to one embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating the multiplexing of UCI bits prior to channel coding and UL-SCH bits prior to channel coding according to one embodiment of the present disclosure.

[0028] FIG. 14 is a diagram illustrating channel-coded UCI bits and channel-pre-coding UL-SCH bits multiplexing according to one embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating channel-coded UCI bits and channel-coded UL-SCH bits multiplexing according to one embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating UL-SCH bit multiplexing by grouping UCI bits according to one embodiment of the present disclosure.

[0031] FIG. 17 is a flowchart illustrating UCI grouping according to one embodiment of the present disclosure.

[0032] FIG. 18 is a diagram illustrating the process of multiplexing a UCI on a PUSCH according to one embodiment of the present disclosure.

[0033] FIG. 19 is a flowchart illustrating the multiplexing of UCI on a PUSCH according to one embodiment of the present disclosure.

[0034] FIG. 20 is a drawing illustrating a PUCCH including a PUSCH and a UCI according to one embodiment of the present disclosure.

[0035] FIG. 21 is a diagram illustrating UCI and UL-SCH processing of a terminal according to one embodiment of the present disclosure.

[0036] FIG. 22 is a flowchart illustrating the generation of UL-SCH and UCI of a terminal according to one embodiment of the present disclosure.

[0037] FIG. 23 is a flowchart related to a reference point according to an embodiment of the present disclosure.

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

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

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

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

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

[0043] 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 related functions or configurations 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 entire specification.

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

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

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

[0047] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Accordingly, 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. Furthermore, in the embodiment, the '~part' may include one or more processors.

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

[0049] 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, gNode 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.

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

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

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

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

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

[0055] [NR Time-Frequency Resources]

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

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

[0058] 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). A single subframe (110) can be composed of 1ms.

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

[0060] 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). A subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 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 shown as the subcarrier spacing setting value.

[0061] When μ=0 (204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1 (205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined as shown in Table 1 below.

[0062] [Table 1]

[0063]

[0064] [Bandwidth Section (BWP)]

[0065] Next, the Bandwidth Part (BWP) settings in 5G will be explained in detail with reference to the drawings.

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

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

[0068] [Table 2]

[0069]

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

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

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

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

[0074] Additionally, 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, the base station may set two bandwidth portions to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0075] In addition, according to one embodiment, 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 may 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.

[0076] Regarding the method of configuring the bandwidth part, 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), which schedules 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 this 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.

[0077] [Bandwidth Section (BWP) Change]

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

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

[0080] μNR Slot length (ms)BWP switch delay T BWP (slots)Type 1 Note 1 Type 2 Note 1 011310.52520.253930.125618Note 1: Depends on UE capability.Note 2: If the BWP switch involves changing of SCS, the BWP switch delay is determined by the larger one between the SCS before BWP switch and the SCS after BWP switch.

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

[0082] In accordance with the aforementioned requirements for the bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWPIt can be completed at a time no later than that, and transmission and reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0083] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) indicating 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 indicating 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).

[0084] [SS / PBCH Block]

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

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

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

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

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

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

[0091] The terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. The terminal can obtain MIB from PBCH and receive Control Resource Set (CORESET) #0 from it (which may correspond to a control resource set with a control resource set 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 Random Access Channel (RACH) required for initial connection from the received system information. The terminal can transmit 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.

[0092] [PDCCH: DCI related]

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

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

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

[0096] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for a Paging message can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying 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).

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

[0098] [Table 4]

[0099]

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

[0101] [Table 5]

[0102]

[0103]

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

[0105] [Table 6]

[0106]

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

[0108] [Table 7]

[0109]

[0110]

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

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

[0113] 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 an embodiment of the present disclosure. FIG. 4 illustrates an example of a control area (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 areas (Control Area #1 (401), Control Area #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) in the frequency axis and one slot (420) in the time axis. The control areas (401, 402) can be set in a specific frequency resource (403) within the entire terminal bandwidth part (410) in the frequency axis. The control areas (401, 402) can be set with one or more OFDM symbols in the time axis and can be defined as the control area length (Control Resource Set Duration, 404). Referring to the illustrated example in FIG. 4, control area #1 (401) is set to a control area length of 2 symbols, and control area #2 (402) is set to a control area length of 1 symbol.

[0114] The control domain in the aforementioned 5G system can be configured by the base station to the terminal through upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring the control domain means that the base station provides the terminal with information such as the control domain identifier (Identity), 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.

[0115] [Table 8]

[0116]

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

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

[0119] FIG. 5 shows an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. 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, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

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

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

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

[0123] In a 5G system, 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.

[0124] [Table 9]

[0125]

[0126]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0150] [Table 10]

[0151]

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

[0153] [Mathematical Formula 1]

[0154]

[0155] - L: Lamination Level

[0156] - n CI : Carrier Index

[0157] - N CCE,p : Total number of CCEs existing within control domain p

[0158] - : Slot Index

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

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

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

[0162] - , , A p= 39827 for p mod 3 = 0 , A p = 39829 for p mod 3 = 1 , A p = 39839 for p mod 3 = 2 , D= 65537

[0163] - n RNTI : Terminal identifier

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

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

[0166] In a 5G system, 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.

[0167] [PDCCH: BD / CCE limit]

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

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

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

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

[0172] [Table 11]

[0173]

[0174] [Table 12]

[0175]

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

[0177] As described above, depending on the setting value of the upper layer signaling, C, which is the maximum number of CCEs constituting the entire search space (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.

[0178] [Table 13]

[0179]

[0180] [Table 14]

[0181]

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

[0183] [PDCCH: Overbooking]

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

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

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

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

[0188] [Regarding Rate Matching / Puncturing]

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

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

[0191] Rate Matching Operation

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

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

[0194] Puncturing action

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

[0196] 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} is transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0197] In the following, a method for configuring rate matching resources is described for the purpose of 5G rate matching. 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.

[0198] FIG. 6 is a diagram illustrating a method for transmitting and receiving data by a base station and a terminal in consideration of a downlink data channel and rate matching resources according to one embodiment of the present disclosure.

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

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

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

[0202] RB symbol level

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

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

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

[0206] RE level

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

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

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

[0210] [Regarding LTE CRS rate match]

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

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

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

[0214] [Table 15]

[0215]

[0216]

[0217]

[0218] [Table 16]

[0219]

[0220] [PDSCH: Regarding Frequency Resource Allocation]

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

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

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

[0224] [Table 17]

[0225]

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

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

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

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

[0230] 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 regarding 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.

[0231] [Table 18]

[0232]

[0233] [Table 19]

[0234]

[0235] 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). For example, it may be indicated by the 'time domain resource allocation' field within the DCI. Based on the DCI received from the base station, the terminal may obtain time domain resource allocation information for PDSCH or PUSCH.

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

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

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

[0239] Referring to FIG. 9, when the subcarrier spacing of the data channel and the control channel is the same (9-00, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset by aligning with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different (9-05, μ PDSCH ≠μ PDCCH Since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset based on the subcarrier interval of the PDCCH and in accordance with a predetermined slot offset K0.

[0240] [PUSCH: Regarding transmission method]

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

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

[0243] [Table 20]

[0244]

[0245]

[0246] 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'.

[0247] 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 the PUSCH transmission via DCI format 0_0 within a BWP where the PUCCH resource containing pucch-spatialRelationInfo is not configured. If the terminal is not configured with txConfig within pusch-Config of [Table 21], the terminal does not expect to be scheduled via DCI format 0_1.

[0248] [Table 21]

[0249]

[0250]

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

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

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

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

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

[0256] 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 scheduled via DCI format 0_1.

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

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

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

[0260] 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 usage value 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.

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

[0262] [PUSCH: Preparation Process Time]

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

[0264] [Mathematical Formula 2]

[0265]

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

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

[0268] [Table 22]

[0269]

[0270] [Table 23]

[0271]

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

[0273] - : 64

[0274] - μ: μ DL or μ UL Middle, T proc,2 It follows the value that becomes larger. μ DL represents the numerology of the downlink through which a PDCCH containing a DCI scheduling PUSCH is transmitted, and μ UL represents the numerology of the uplink through which PUSCH is transmitted.

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

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

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

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

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

[0280] When the base station and terminal consider the time-axis resource mapping information of the PUSCH scheduled via DCI and the influence of uplink-downlink timing advance, from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, T proc,2 Subsequently, if the first symbol of the PUSCH starts before the first uplink symbol initiated by the CP, it is determined that the PUSCH preparation time is insufficient. 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.

[0281] [CA / DC Related]

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

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

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

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

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

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

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

[0289] Regarding the 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 SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support smooth service.

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

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

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

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

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

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

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

[0297] - Retransmission of PDCP SDUs

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

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

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

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

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

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

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

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

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

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

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

[0309] - Duplicate detection

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

[0311] - RLC SDU discard function

[0312] RLC re-establishment function

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

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

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

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

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

[0318] - Scheduling information reporting function

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

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

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

[0322] - MBMS service identification function

[0323] - Transport format selection function

[0324] - Padding

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

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

[0327] Referring to the descriptions regarding PDCCH and beam settings mentioned 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 invention 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.

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

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

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

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

[0332] 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 contents of the present disclosure are applicable to FDD and TDD systems.

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

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

[0335] - MIB (Master Information Block)

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

[0337] - RRC (Radio Resource Control)

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

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

[0340] - PDCCH (Physical Downlink Control Channel)

[0341] - DCI (Downlink Control Information)

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

[0343] - Group common DCI

[0344] - Common DCI

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

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

[0347] - PUCCH (Physical Uplink Control Channel)

[0348] - UCI (Uplink Control Information)

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

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

[0351] [UCI Multiplexing]

[0352] The terminal can transmit uplink control information (UCI) 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.

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

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

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

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

[0357] 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, low-priority HARQ-ACK information and high-priority HARQ-ACK information 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, ...

[0358] When a terminal transmits a UCI over a PUSCH, the PUSCH may include an UL-SCH (uplink shared channel). 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 terminal's upper layer to the terminal's physical layer and may consist of multiple bits. The terminal can transmit the UL-SCH to the base station via the PUSCH. The base station's physical layer can obtain the UL-SCH by receiving the PUSCH and transmit the UL-SCH to the base station's upper layer. The multiple bits constituting the UL-SCH at the physical layer can be referred to as a transport block (TB).

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

[0360] FIG. 11 is a flowchart illustrating a method of transmitting UL-SCH (or TB) and UCI through PUSCH according to one embodiment of the present disclosure.

[0361] 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. For example, the length of the TB-CRC may be 24 bits.

[0362] The PUSCH scheduling information used to determine the TB length includes the Modulation and Coding Scheme (MCS), Time Domain Resource Assignment (TDRA), Frequency Domain Resource Assignment (FDRA), DMRS configuration information, Antenna Port (AP) related information, or overhead related information (X oh It may include at least one of ).

[0363] 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 can be the same. Additionally, a CB-CRC can be attached to each CB. Here, when the base station decodes PUSCH, the CB-CRC can be used to determine whether the corresponding CB has been correctly decoded.

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

[0365] UL-SCH Rate Matching Block: Rate matching can be performed on encoded CBs and CB-CRCs based on the number of resources available for UL-SCH transmission in PUSCH. That is, among the encoded CBs and CB-CRCs, the bits to be transmitted to PUSCH can be determined. Here, the resources available for UL-SCH transmission in PUSCH may be resources excluding those transmitted to UCI. Therefore, the number of resources occupied by UCI included in PUSCH ( , , Depending on the, etc., the result of the rate matching block may vary.

[0366] More specifically, UL-SCH rate matching can be performed as follows. The terminal can determine the number of bits occupied by each CB after UL-SCH rate matching based on [Table 24]. Here, the number of bits occupied by CB r after rate-matching is or It could be.

[0367] Here, G represents the number of bits through which UL-SCH can be transmitted in PUSCH, and the value of G is the number of resources occupied by the UCI included in PUSCH ( , , It may be a value determined by (etc.). That is, UL-SCH rate-matching is the number of resources occupied by UCIs included in PUSCH ( , , It may change depending on the etc. When code block r is rate-matched, it may correspond to the number of bits after rate-matching, and It can be determined as shown in [Table 24].

[0368] [Table 24]

[0369]

[0370] UL-SCH CB 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 or concatenated. 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.

[0371] 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 may be a diagram for one type.

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

[0373] Channel coding of UCI blocks: UCI codebooks and CRCs can be encoded according to channel coding. For example, UCI codebooks and CRCs can be encoded using polar channel coding.

[0374] UCI 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 alpha value ( ) can be set, and the number of resources transmitted in PUSCH can be determined based on the above value. For example, if the type of UCI is HARQ-ACK, the number of resources can be determined by the following formula.

[0375] [Mathematical Formula 3]

[0376]

[0377] In mathematical formula 3, is the number of HARQ-ACK bits, is the number of CRC bits, and is the beta offset value for HARQ-ACK (the encoding rate of HARQ-ACK relative to the encoding rate of UL-SCH in PUSCH), and is the number of CBs included in PUSCH, and is the number of bits included in the CB, and represents the number of REs that can be used for UCI transmission in OFDM symbol l, and is the alpha value (the maximum proportion of resources included in PUSCH that can be used for HARQ-ACK), is the number of symbols included in PUSCH, and is the index of the OFDM symbol that does not contain a DMRS after the first DMRS.

[0378] Similarly, if the UCI type is CSI part 1 and CSI part 2, the number of resources ( , ) can be determined by mathematical formula 4 and mathematical formula 5, respectively.

[0379] [Mathematical Formula 4]

[0380]

[0381] [Mathematical Formula 5]

[0382]

[0383] In mathematical formula 4, When deciding, is the beta offset value corresponding to CSI part 1 (the encoding rate of CSI-part 1 relative to the encoding rate of PUSCH's UL-SCH), and in Equation 5, When deciding, may be a beta offset value corresponding to CSI part 2 (the encoding rate of CSI-part 2 relative to the encoding rate of UL-SCH of PUSCH).

[0384] According to one embodiment, with reference to mathematical formulas 4 and 5, the beta offset can be used for the following purposes.

[0385] The beta offset is used to determine the code rate of the UCI and can represent the relative value of the UCI code rate to the code rate of PUSCH's UL-SCH. More specifically, the code rate of PUSCH's UL-SCH can be expressed as (UL-SCH payload size) / (number of resources transmitted by UL-SCH * modulation order * number of MIMO layers). Referring to Equations 4 and 5, the code rate of PUSCH's UL-SCH is It may be. The coding rate of the UCI multiplexed in PUSCH can be expressed as (UCI payload size) / (number of resources transmitted by UCI * modulation order * number of MIMO layers). If the UCI is HARQ-ACK, refer to Equation 3, It can be expressed as follows. Beta offset is a value relative to the coding rate of UL-SCH, and can be expressed as follows. . thus, And, the first part of mathematical equation 3 can be derived.

[0386] The values ​​of the Beta offset of HARQ-ACK can be exemplified by [Table 25]. Referring to [Table 25], the value of the Beta offset at index 0 is 1. Therefore, UL-SCH and UCI (HARQ-ACK) can have the same encoding rate. The Beta offset at index 11 is 20. Therefore, the encoding rate of UCI (HARQ-ACK) can be 20 times lower than the encoding rate of UL-SCH. The Beta offset at index 19 is 0.1. Therefore, the encoding rate of UCI can be 10 times higher than the encoding rate of UL-SCH.

[0387] Index 01.00012.00022.50033.12544.00055.00066.25078.000810.000912.62 51015.8751120.0001231.0001350.0001480.00015126.000160.6170.418 0.2190.1200.0521Reserved22Reserved23Reserved24Reserved25Reserved26Reserved27Reserved28Reserved29Reserved30Reserved31Reserved

[0388] According to one embodiment, with reference to Equations 4 and 5, alpha may be used for the following purposes. If the resources included in PUSCH are used as UCI, the reception performance of UL-SCH may be degraded. Therefore, the base station may set for the terminal the maximum amount of resources within PUSCH that can be used as UCI. The above setting can be done through the alpha value. For example, based on the beta-offset, the number of resources to be used for UCI (HARQ-ACK) In this case, the base station can allocate the maximum number of resources available for UCI equal to the alpha ratio of the number of resources included in PUSCH. That is, the number of maximum resources available for UCI (HARQ-ACK) is It could be. Here, can be the number of resources included in PUSCH. Therefore, According to, based on the beta-offset, the number of resources to be used for UCI (HARQ-ACK) ( The maximum number of resources that ) can use in UCI ( If it exceeds ), N resources may be used. According to one embodiment, for CSI part 1 and CSI part 2, resources used by the UCIs mapped first may be excluded from the number of resources included by PUSCH. For example, since HARQ-ACK is mapped first in CSI part 1, the number of resources included by PUSCH - It can be. Since HARQ-ACK and CSI part 1 are mapped first in CSI part 2, the number of resources included in PUSCH is - - It may be. According to one embodiment, the result value of rate-matching for UCI (e.g., , , ...etc.) can be applied to rate-matching related to UL-SCH. This was explained in the UL-SCH Rate-matching block.

[0389] UCI concatenation block: If the UCI consists of multiple UCI code blocks, each encoded UCI code block and CRC can be combined into a single bit stream.

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

[0391] FIG. 12 is a diagram illustrating UCI-to-RE mapping when multiplexing UCI on PUSCH according to one embodiment of the present disclosure.

[0392] Referring to Fig. 12, a specific UCI-to-RE mapping method and PUSCH can be exemplified as follows.

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

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

[0395] Specifically, in the first UCI-to-RE mapping method, HARQ-ACK can be mapped to available REs in OFDM symbols 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 included in the OFDM symbol are used for HARQ-ACK transmission; otherwise, some of the REs included in the OFDM symbol may be used for HARQ-ACK transmission.

[0396] Step 2: CSI part 1 bits can be multiplexed on PUSCH using a second UCI-to-RE mapping method.

[0397] Specifically, in the second UCI-to-RE mapping method, 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 REs included in the OFDM symbol, all REs included in the OFDM symbol 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.

[0398] Step 3: The CSI part 2 bits can be multiplexed over PUSCH using a third UCI-to-RE mapping method.

[0399] Specifically, in the third UCI-to-RE mapping method, 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. Also, if the OFDM symbol includes REs used for CSI part 1, said REs may be excluded.

[0400] Step 4: UL-SCH can be multiplexed on PUSCH.

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

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

[0403] Referring to Fig. 12, the above UCI-to-RE mapping and PUSCH generation method may have the following problems.

[0404] As exemplified in relation to FIG. 12 above, up to three UCI-to-RE mappings (first stage (HARQ-ACK), second stage (CSI part 1), and third stage (CSI part 2)) may be defined for the terminal. If a new type of UCI is introduced, a fourth stage (new UCI type) must be defined to transmit the UCI to PUSCH (separate from the step of multiplexing the UL-SCH). Therefore, a new UCI-to-RE mapping method may need to be defined whenever a new type of UCI is introduced. Alternatively, the new type of UCI may use one of the existing up to three UCI-to-RE mapping methods. For example, the new type of UCI may have UCI-to-RE mapping performed based on the third stage (CSI part 2). In this case, PUSCH may not be able to multiplex and transmit CSI part 2 and the new type of UCI simultaneously.

[0405] In addition, when mapping the second UCI-to-RE in the second stage (CSI part 1), the REs used in the first stage (HARQ-ACK) may need to be taken into account. That is, since the second UCI-to-RE mapping may vary depending on the first UCI-to-RE mapping, if the number of HARQ-ACK bits transmitted on the PUSCH changes, the terminal must determine a new second UCI-to-RE mapping location. Also, when mapping the third UCI-to-RE in the third stage (CSI part 2), the REs used in the first stage (HARQ-ACK) and the REs used in the second stage (CSI part 2) may need to be taken into account.

[0406] As such, the interdependence between UCI types can be exemplified by the fact that when multiplexing a specific type of UCI to PUSCH, it is affected by the placement of other types of UCI (the result of UCI-to-RE). If new types of UCIs are multiplexed to PUSCH, a larger number of UCI-to-RE mappings must be considered, which can introduce complexity at the terminal side.

[0407] In this disclosure, a method of placing UCI and / or UL-SCH on PUSCH may be disclosed without defining UCI-to-RE mapping. In the following description, UCI bits and UL-SCH bits may be combined into a single bit stream, interleaving may be applied to said combined bit stream, and after interleaving, the bit stream may be mapped to PUSCH by a frequency-first time-second mapping method.

[0408] Accordingly, as a feature of the present disclosure, since no specific UCI-to-RE mapping is defined, the UCI bits may include various types of UCIs. And, they can be expanded without limitation on the number of types. In addition, since the UCI bits and UL-SCH are multiplexed as a bit stream, there may be no interdependence between different types of UCIs.

[0409] Specific UCI and UL-SCH multiplexing methods of the present disclosure can be illustrated through Examples 1 to 4.

[0410] Example 1. Method for multiplexing UCI bits and UL-SCH bits

[0411] In Example 1 of the present disclosure, various methods for multiplexing UCI bits and UL-SCH bits may be disclosed. A method for mapping a bit stream in which UCI bits and UL-SCH bits are multiplexed onto PUSCH will be described later.

[0412] [Method 1-1] Multiplexing pre-channel coding UCI bits and pre-channel coding UL-SCH bits

[0413] In method 1-1 of the present disclosure, the terminal can multiplex the UCI bits prior to channel coding and the UL-SCH bits prior to channel coding. For example, unencoded UCI bits and unencoded UL-SCH bits can be multiplexed.

[0414] FIG. 13 is a diagram illustrating the multiplexing of UCI bits prior to channel coding and UL-SCH bits prior to channel coding according to one embodiment of the present disclosure.

[0415] Referring to FIG. 13, a UCI-CRC corresponding to the UCI may be attached to the UCI. A TB-CRC corresponding to the TB may be attached to the TB.

[0416] The bit streams of {UCI, UCI-CRC} and {TB, TB-CRC} can be combined. Here, combining means that the two bit streams are connected consecutively to form a single bit stream. Here, at least one of UCI-CRC or TB-CRC may be omitted. For example, if the length of UCI is short, or if the length of TB is short, at least one of UCI-CRC or TB-CRC may be omitted.

[0417] A combined bit stream can be segmented into multiple CBs. When segmenting the combined bit stream into CBs, UCI and TB may not be distinguished. That is, the combined bit stream can be segmented into CBs equally (without distinguishing between UCI or UL-SCH and segmenting them differentially). For example, if the length of the combined bit stream is B and it is segmented into two CBs, the 0th CB may consist of B / 2 bits and the 1st CB may consist of B / 2 bits. Therefore, UCI may be included in a single CB or in multiple CBs. Also, UCI and TB may be included simultaneously in a single CB. In FIG. 13, a combined bit stream segmented into N CBs may be exemplified.

[0418] In the previously divided multiple CBs, a separate CRC (e.g., CB-CRC) may be attached to each CB. Each CB and CB-CRC may be encoded according to channel coding. Here, each CB and CB-CRC may be encoded with the same channel coding (e.g., LDPC channel coding). Alternatively, each CB and CB-CRC may be encoded with different channel coding. For example, if a CB contains at least one UCI bit, a separate channel coding may be applied to the CB and CB-CRC. Alternatively, a second channel coding (e.g., Polar channel coding) may be applied. Alternatively, if a CB does not contain UCI bits, the CB and CB-CRC may be encoded with a first channel coding (e.g., LDPC channel coding).

[0419] Each encoded CB and CB-CRC can be combined into a single bit stream. The bit stream may include UCI and UL-SCH. The bit stream, in which each encoded CB and CB-CRC is combined, can be interleaved and mapped onto PUSCH.

[0420] According to one embodiment, the same code rate may be applied to UCI and UL-SCH. Therefore, the reception performance of UCI and the reception performance of UL-SCH may be similar. For example, in the case of PUSCH scheduled to target a block error rate (BLER) of 1%, the probability of reception success or failure of CB including UCI is 1%, and the probability of reception failure of CB including UL-SCH may also be 1%. Alternatively, non-identical code rates may be applied.

[0421] For example, one method of applying unequal encoding rates may be as follows: PUSCH contains C CBs, and the number of CBs containing at least one bit of UCI among them is C UCI ...and the number of CBs excluding UCI is C UL-SCH When that is true, C=C UCI +C UL-SCH It is possible. The terminal can improve reception performance by allocating more resources to CBs containing UCI than to CBs without UCI. More specifically, E of CB r containing UCI r The (UCI) value can be determined as follows.

[0422] or

[0423] E of CB r excluding UCI r The (no UCI) value can be determined as follows.

[0424] or

[0425] Here, is the number of coded bits in PUSCH to which CBs including UCI are mapped, and can be the number of coded bits in PUSCH to which CBs not including UCI are mapped. The terminal or or It can be determined as. It could be. That is, G UCI is the number of CBs including UCI (C) out of the total number of CBs (C). UCI It can be determined according to the ratio of ). can be a factor for allocating more coded bits to CBs containing UCI. Here With this value, the terminal can be configured by the base station or instructed via DCI. Therefore, It could be.

[0426] In the case of UCI, relatively high reception performance may generally be required. Methods 1-2 to 1-3 may be exemplified as a method for this purpose.

[0427] [Method 1-2] Multiplexing channel-coded UCI bits and pre-channel-coded UL-SCH bits

[0428] In method 1-2 of the present disclosure, the terminal can multiplex channel-coded UCI bits and channel-pre-coded UL-SCH bits. For example, encoded UCI bits and unencoded UL-SCH bits can be multiplexed. By performing encoding on the UCI bits, higher reception performance can be ensured for the UCI.

[0429] FIG. 14 is a diagram illustrating channel-coded UCI bits and channel-pre-coding UL-SCH bits multiplexing according to one embodiment of the present disclosure.

[0430] Referring to FIG. 14, a UCI-CRC corresponding to the UCI may be attached to the UCI. A TB-CRC corresponding to the TB may be attached to the TB. Here, at least one of the UCI-CRC or the TB-CRC may be omitted. For example, if the length of the UCI is short, or if the length of the TB is short, at least one of the UCI-CRC or the TB-CRC may be omitted.

[0431] UCI and UCI-CRC can be encoded as channel codes. For example, UCI and UCI-CRC can be encoded as polar channel codes. Furthermore, the encoded UCI and UCI-CRC can be rate-matched based on beta offset values ​​or alpha values. Equations 3 to 5 represent the number of REs determined by rate-matching when UCI is HARQ-ACK or CSI part 1 or CSI part 2 ( , , ) can be provided. The value obtained by multiplying the above value by a modulation order (e.g., 2 for QPSK, 4 for 16QAM, 6 for 64QAM, 8 for 256QAM, 10 for 1024QAM) may be the length of the encoded UCI and UCI-CRC after rate-matching.

[0432] After rate-matching, 'encoded UCI, UCI-CRC' and 'TB, TB-CRC({TB, TB-CRC})' can be combined. Here, combining means that the bit stream corresponding to the encoded UCI and UCI-CRC after rate-matching and the bit stream corresponding to {TB, TB-CRC} are connected to form a single bit stream.

[0433] A combined bit stream can be segmented into multiple CBs. When segmenting the combined bit stream into CBs, UCI and TB may not be distinguished. That is, the combined bit stream can be segmented into CBs equally (without distinguishing between encoded UCI or UL-SCH and segmenting them differentially). For example, if the length of the combined bit stream is B and it is segmented into two CBs, the 0th CB may consist of B / 2 bits and the 1st CB may consist of B / 2 bits. Therefore, the encoded UCI may be included in a single CB or in multiple CBs. Also, a single CB may contain both UCI and TB simultaneously. In FIG. 14, a combined bit stream segmented into N CBs may be exemplified.

[0434] In the previously divided multiple CBs, a separate CRC (e.g., CB-CRC) may be attached to each CB. Each CB and CB-CRC may be encoded according to channel coding. Here, each CB and CB-CRC may be encoded with the same channel coding (e.g., LDPC channel coding). Alternatively, each CB and CB-CRC may be encoded with different channel coding. For example, if a CB contains at least one UCI bit, a separate channel coding may be applied to the CB and CB-CRC. Alternatively, a second channel coding (e.g., Polar channel coding) may be applied. Alternatively, if a CB does not contain UCI bits, the CB and CB-CRC may be encoded with a first channel coding (e.g., LDPC channel coding).

[0435] Each encoded CB and CB-CRC can be combined into a single bit stream. The bit stream may include UCI and UL-SCH. The bit stream, in which each encoded CB and CB-CRC is combined, can be interleaved and mapped onto PUSCH.

[0436] [Method 1-3] Multiplexing channel-coded UCI bits and channel-coded UL-SCH bits

[0437] In method 1-3 of the present disclosure, the terminal can multiplex channel-coded UCI bits and channel-coded UL-SCH bits. For example, encoded UCI bits and encoded UL-SCH bits can be multiplexed. By performing encoding on the UCI bits, higher reception performance can be ensured for the UCI.

[0438] FIG. 15 is a diagram illustrating channel-coded UCI bits and channel-coded UL-SCH bits multiplexing according to one embodiment of the present disclosure.

[0439] Referring to FIG. 15, a UCI-CRC corresponding to the UCI may be attached to the UCI. A TB-CRC corresponding to the TB may be attached to the TB. Here, at least one of the UCI-CRC or the TB-CRC may be omitted. For example, if the length of the UCI is short, or if the length of the TB is short, at least one of the UCI-CRC or the TB-CRC may be omitted.

[0440] UCI and UCI-CRC can be encoded using channel codes. For example, UCI and UCI-CRC can be encoded using second channel coding (e.g., Polar channel coding). Furthermore, the encoded UCI and UCI-CRC can be rate-matched based on a beta offset value or an alpha value. Equations 3 through 5 represent the number of resources determined by rate-matching when UCI is HARQ-ACK, CSI part 1, or CSI part 2 ( , , ) can be provided. The value obtained by multiplying the above value by the modulation order (e.g., 2 for QPSK, 4 for 16QAM, 6 for 64QAM, 8 for 256QAM, 10 for 1024QAM) and the number of MIMO layers (M L The value multiplied by ) may be the length of the encoded UCI and UCI-CRC after rate-matching.

[0441] A TB can be segmented into one or more CBs. According to one embodiment, one or more CBs may each be attached with a CRC (CB-CRC). Each CB and CB-CRC may be encoded with a channel code. Here, a first channel code (e.g., an LDPC code) may be used as the channel code. Alternatively, another channel code may be used.

[0442] According to one embodiment, the same or different encoding methods may be used for 'UCI and UCI-CRC' and each 'CB and CB-CRC'.

[0443] After rate-matching, the 'encoded UCI and UCI-CRC' and the 'encoded each CB and CB-CRC' can be combined into a single bit stream. The bit stream includes UCI and UL-SCH. The bit stream can be interleaved and mapped onto PUSCH.

[0444] When combined into a single bit stream in Methods 1-1 to 1-3, the combination order of UCI and UL-SCH is described in detail in Example 4.

[0445] Example 2. Grouping method of UCI bits

[0446] In the methods disclosed in Example 1, the UCI bits can be composed of various types of UCI.

[0447] For example, in Methods 1-1 through 1-3, the UCI may be composed of various types of UCI bits. The UCI-CRC exemplified in Methods 1-1 through 1-3 may be attached according to each UCI type. That is, a CRC may be attached for each UCI type.

[0448] In Method 1-2 or Method 1-3, a beta offset value and / or an alpha value may be set for each UCI type. When encoded by channel coding, each UCI type may be encoded individually (e.g., each with a separate encoding method applied). And during rate matching, rate matching may be performed based on the corresponding beta offset value and / or alpha value.

[0449] The following issues may arise with CRC attachment and channel coding depending on the type of UCI.

[0450] If the number of UCI types multiplexed in PUSCH increases, the CRC overhead may increase. For example, if a 16-bit CRC is attached for each UCI type, 3 * X = 48 bits when 3 UCI types are multiplexed, and 5 * X = 80 bits when 5 UCI types are multiplexed.

[0451] Alternatively, if channel coding is performed for each type of UCI multiplexed on the PUSCH, the number of channel codings may increase proportionally to the type of UCI multiplexed. For example, if there are 3 types of UCI multiplexed on the PUSCH, 3 channel codings may be performed. If there are 5 types of UCI multiplexed, 5 channel codings may be performed. The terminal may have a certain number of independent channel coding circuits for fast PUSCH generation processing. If the terminal has 3 independent channel coding circuits (i.e., capable of processing up to 3 channel codings simultaneously per PUSCH), up to 3 types of UCI may be multiplexed on the PUSCH, but more than 3 types of UCI may not be multiplexed on the PUSCH.

[0452] Alternatively, if channel coding is performed for each UCI type multiplexed in PUSCH, the channel coding gain may decrease. Generally, channel coding gain can be higher as the codeword length increases. If channel coding is performed for each UCI type and the length of each UCI type is short (i.e., the codeword length is short), the channel coding gain may decrease.

[0453] In order to solve at least one of the problems exemplified above, in one embodiment of the present disclosure, a terminal may group a plurality of UCI types into a single UCI group. For example, a plurality of UCI types included in the same UCI group may be combined and considered as a single UCI type. That is, the terminal may generate and attach a CRC for a plurality of UCI types included in the same UCI group and apply a single channel coding. During rate-matching, rate-matching may be performed based on a single beta offset value and / or alpha value.

[0454] According to one embodiment, different beta offset values ​​and / or alpha values ​​may be set for each of the plurality of UCI types included in the UCI group. In this case, one beta offset value and / or alpha value corresponding to the UCI group may be determined based on one of the following methods.

[0455] According to one embodiment, the terminal may receive a beta offset value and / or alpha value corresponding to a UCI group from a base station. According to the present method, when a plurality of UCI types are grouped into a single UCI group, the beta offset value and / or alpha value set for each UCI type is no longer used, and rate-matching can be performed using the beta offset value and / or alpha value set for the UCI group.

[0456] According to one embodiment, the terminal may use the beta offset value and / or alpha value of one of the UCI types included in the UCI group as the beta offset value and / or alpha value of the UCI group. Here, one of the UCI types included in the UCI group may be determined by at least one of the following methods, but is not limited thereto.

[0457] - If UCI types of different priorities are included, the highest priority UCI type may be selected. Here, priority refers to the priority of the physical layer and may correspond to the priority of the UCI type. For example, there may be low priority and high priority. If a UCI group includes a relatively low priority UCI type (e.g., HARQ-ACK) and a relatively high priority UCI type (e.g., HARQ-ACK), the high priority UCI type may be selected.

[0458] - If UCI types of the same priority are included, the terminal may select HARQ-ACK if there is HARQ-ACK among the UCI types. If there is no HARQ-ACK and there is CSI part 1, the terminal may select CSI part 1. If there is no HARQ-ACK and there is no CSI part 1 and there is CSI part 2, the terminal may select CSI part 2.

[0459] In one method, the terminal may select one of the beta offset values ​​or alpha values ​​corresponding to each type of UCI included in the UCI group. For example, the lowest value among the beta offset values ​​may be selected as the beta offset value corresponding to the UCI group. For example, the highest value among the beta offset values ​​may be selected as the beta offset value corresponding to the UCI group.

[0460] FIG. 16 is a diagram illustrating UL-SCH bit multiplexing by grouping UCI bits according to one embodiment of the present disclosure.

[0461] Referring to FIG. 16, the UCI may include multiple types of UCI. A UCI-CRC may be attached to the UCI. According to one embodiment, a CRC may be generated and attached for each type of UCI. Alternatively, the UCI-CRC may be generated and attached based on the entire UCI. Alternatively, the UCI-CRC may not be attached.

[0462] UCIs can be grouped into one or more groups. In FIG. 16, they can be grouped into two groups (group A, group B). UCI types can be included in one UCI group. A CRC (UCI group A-CRC or UCI group B-CRC) can be attached to each UCI group. According to one embodiment, the UCI group A-CRC may be a CRC generated based on the UCI types included in UCI group A, and the UCI group B-CRC may be a CRC generated based on the UCI types included in UCI group B.

[0463] According to one embodiment, the UCI included in each UCI group and the CRC of the UCI group can be encoded according to channel coding. According to FIG. 16, since two UCI groups are exemplified, two channel codings (e.g., polar coding) can be performed. The grouped UCI bits can each be channel coded independently. For example, UCI bits corresponding to UCI group A and UCI bits corresponding to UCI group B can each be channel coded, and the two channel coding processes can be independent. Here, "independent" may mean that each channel coding is performed as an independent process. Here, "independent" may mean that the result values ​​of each channel coding are not related. Here, "independent" may mean that the input values ​​of each channel coding are not related to each other.

[0464] Rate-matching can be performed after channel coding for each UCI group. Here, when performing rate-matching corresponding to UCI group A, the beta offset value and / or alpha value corresponding to UCI group A may be used, and when performing rate-matching corresponding to UCI group B, the beta offset value and / or alpha value corresponding to UCI group B may be used.

[0465] A TB may be divided into one or more CBs. According to one embodiment, one or more CBs may each have a CB-CRC attached. And each CB and CB-CRC may be encoded with a channel code (e.g., LDPC). Or other channel codes may be used.

[0466] The terminal can combine bits encoded by UCI group and encoded UL SCH (the above encoded CBs) to generate a single bit stream.

[0467] In one embodiment of the present disclosure, the method by which a terminal creates a UCI group may be at least one of the following methods.

[0468] [Method 2-1] UCI Grouping Based on Explicit Base Station Configuration

[0469] The terminal can receive a correspondence between UCI group and UCI type values ​​from the base station as an upper layer signal (e.g., receiving information about the correspondence from the base station). For example, if the terminal receives two UCI groups, it can receive UCI types included in UCI group A and UCI types included in UCI group B.

[0470] For example, if a terminal is configured with two UCI groups, it may be configured with UCI types included in UCI group A. UCI types that are not included in UCI group A may be included in UCI group B.

[0471] For example, if the UCIs to be multiplexed by the terminal via PUSCH are HARQ-ACK, CSI part 1, and CSI part 2, and two UCI groups are configured, HARQ-ACK may be configured to be included in UCI group A. And CSI part 1 and CSI part 2 may be configured to be included in UCI group B.

[0472] For example, if the UCIs to be multiplexed by the terminal via PUSCH are low priority HARQ-ACK, low priority CSI part 1, low priority CSI part 2, and high priority HARQ-ACK, and two UCI groups are configured, the high priority HARQ-ACK may be configured to be included in UCI group A. And the low priority HARQ-ACK, low priority CSI part 1, and low priority CSI part 2 may be configured to be included in UCI group B. Alternatively, the high priority HARQ-ACK and low priority HARQ-ACK may be configured to be included in UCI group A. And the low priority CSI part 1 and low priority CSI part 2 may be configured to be included in UCI group B.

[0473] The terminal may receive instructions from the base station regarding the correspondence between UCI group and UCI type values ​​in a DCI format corresponding to the UCI. For example, the DCI format corresponding to HARQ-ACK may indicate the UCI group corresponding to HARQ-ACK. The terminal may determine the UCI group corresponding to HARQ-ACK based on the above UCI group instructions. If the number of UCI groups to the terminal is 2, the indicator may be 1 bit, and if the number of UCI groups is 3 or 4, the indicator may be 2 bits. For example, if the number of UCI groups is U, the indicator may be ceil(log2(U)) bits.

[0474] [Method 2-2] UCI Grouping Based on Beta Offset Values

[0475] The terminal can receive beta offset values ​​for each UCI type (e.g., receiving information related to beta offset values ​​from a base station). The terminal can determine the UCI group based on the above beta offset values.

[0476] For example, one or more UCI types with the same beta offset value can be grouped into a single UCI group.

[0477] According to one embodiment, the terminal can receive a beta offset value corresponding to a UCI group from a base station.

[0478] According to one embodiment, one or more UCI groups can be determined based on the relationship between the beta offset value set for the UCI type and the beta offset value corresponding to the UCI group.

[0479] For example, in UCI group A is set, and in UCI group B If set ( < ), the beta offset value set in the UCI type is the above If greater than, it is included in UCI group B, and the beta offset value set in the UCI type is the above Smaller but If it is larger, it may be included in UCI group A. In this case, the terminal UCI types with smaller beta offset values ​​may not be expected.

[0480] For example, the terminal can receive a value from the base station to determine the UCI group. The UCI group can be determined based on the relationship between the beta offset value set for the UCI type and the value to determine the UCI group.

[0481] For example, if U=2 UCI groups are configured for a terminal, U-1=1 value may be configured. Assuming the above value is X, if the beta offset value configured for the UCI type is greater than X, it is included in UCI group B; if the beta offset value configured for the UCI type is less than or equal to X (or vice versa), it may be included in UCI group A. In other words, with X as the boundary, the UCI type may be included in UCI group A or UCI group B depending on the beta offset value.

[0482] [Method 2-3] UCI Grouping by UCI Priority

[0483] The terminal may be set a priority for a UCI type (e.g., receiving information related to the priority from a base station). According to one embodiment, the priority may be a priority corresponding to a UCI type as a physical layer priority.

[0484] For example, there can be relatively low priority and relatively high priority. UCI group A may include relatively low priority UCI types, and UCI group B may include relatively high priority UCI types.

[0485] The priority may be specified in the DCI format that triggers the UCI, or the priority may be specified in the upper-level settings associated with the UCI (e.g., RRC settings). For example, if a first priority is specified in the upper-level settings (e.g., RRC settings) and a second priority is specified in the DCI format, the terminal may prioritize the second priority.

[0486] For example, in the case of a HARQ-ACK for a Dynamic grant (DG) PDSCH, information indicating priority may be included in the DCI format that schedules the DG PDSCH. Or, in the case of an Aperiodic CSI, information indicating priority may be included in the DCI format that triggers the Aperiodic CSI. Or, in the case of a HARQ-ACK for a Semi-persistent scheduled (SPS) PDSCH, information indicating priority may be included in the SPS configuration information. Or, information indicating priority may be included in the DCI format that triggers the reception of the SPS PDSCH. Or, in the case of a Semi-persistent (SP) CSI, information indicating priority may be included in the SP CSI configuration information. Or, information indicating priority may be included in the DCI format that triggers the SP CSI. Alternatively, if there is no DCI format corresponding to the UCI (e.g., Periodic CSI), information indicating priority may be included in the UCI (Periodic CSI) settings.

[0487] According to one embodiment, information indicating priority in the DCI format may be included as a DCI field.

[0488] For example, if two priorities (e.g., low priority and high priority) are set for the terminal, a 1-bit DCI field may be included, and the priority may be indicated based on the 1-bit value.

[0489] In addition, information indicating priority in the DCI format can be determined based on the DCI format. For example, in the case of a fallback DCI format (DCI format 0_0 or DCI format 1_0, which is a DCI format monitored regardless of RRC settings), it can always be determined to have a relatively low priority.

[0490] In addition, information indicating priority in the DCI format can be determined based on the RNTI value corresponding to the DCI format. For example, a DCI format corresponding to C-RNTI can be judged to have a relatively low priority, and a DCI format corresponding to MCS-C-RNTI can be judged to have a relatively high priority. Here, when scheduling PDSCH or PUSCH, the DCI format corresponding to MCS-C-RNTI may use an MCS table with higher reliability.

[0491] [Method 2-4] UCI Grouping by UCI Bits

[0492] A terminal may group UCI bits of a length less than a certain length into a single UCI group. Here, the certain length may be a value set by a base station (e.g., receiving information related to the bit length from a base station) or a predetermined value. For example, the certain length may be a value corresponding to the minimum number of bits (e.g., 12 bits) required to use the Polar code, which is a channel coding.

[0493] According to the present disclosure, the terminal can determine the length of each of one or more UCI types multiplexed on the PUSCH.

[0494] For example, if the length of multiple UCI types is less than a certain length, the multiple UCI types may be included in a single UCI group. Alternatively, if the length of a UCI type is greater than or equal to a certain length, only the said UCI type may be included in a single UCI group. That is, if the length of a UCI type is greater than or equal to a certain length, it may not be grouped with other UCI types.

[0495] According to one embodiment, the number of UCI bits included in the UCI group may be greater than a certain length. Therefore, polar coding can be used for channel coding. In addition, as the number of UCI bits increases, a higher coding gain can be expected.

[0496] The UCI grouping disclosed in Methods 2-1 to 2-4 may have performance conditions.

[0497] The performance conditions exemplified below may be applied in combination of one or more conditions.

[0498] According to one embodiment, when UCIs are multiplexed on the PUSCH, UCI grouping can always be performed. For example, when UCI grouping is configured for a terminal, the terminal can always perform UCI grouping regardless of the types of UCIs multiplexed on the PUSCH and / or the number of types of UCIs.

[0499] According to one embodiment, when UCIs are multiplexed on a PUSCH, whether or not UCI grouping is performed can be determined based on the number of UCI types. For example, if the number of UCI types is less than or equal to a certain value, UCI grouping may not be performed. If the number of UCI types is greater than a certain value, UCI grouping may be performed. That is, the number of UCI groupings may be equal to or less than the number of UCI types. Accordingly, the number of channel coding (Polar coding) processes that the terminal must perform may be reduced.

[0500] According to one embodiment, when UCIs are multiplexed on a PUSCH, whether or not to group UCIs may be determined based on the type of UCI. For example, if a specific type of UCI is multiplexed on a PUSCH, the terminal may perform UCI grouping. Alternatively, if a specific type of UCI is not multiplexed on a PUSCH, the terminal may not perform UCI grouping.

[0501] According to one embodiment, when UCIs are multiplexed on a PUSCH, the length of the UCI type may be determined. For example, if the length of a certain UCI type is shorter than a certain length, the terminal may perform UCI grouping. If the length of a certain UCI type is greater than or equal to a certain length, the terminal may not perform UCI grouping.

[0502] According to one embodiment, when UCIs are multiplexed on a PUSCH, whether or not to perform UCI grouping may be indicated in the DCI format. The DCI format may be a DCI format for scheduling the PUSCH. Alternatively, the DCI format may be a DCI format corresponding to the UCI.

[0503] If there are multiple DCI formats corresponding to the UCI, UCI grouping execution information may be indicated from one of the multiple DCI formats. Here, the one DCI format may be the most recently received DCI format. Alternatively, if there are multiple DCI formats corresponding to the UCI, the multiple DCI formats may contain the same UCI grouping execution information. Therefore, the terminal can receive a single DCI format and obtain UCI grouping execution information.

[0504] [UE capability reporting and related terminal operations]

[0505] When multiplexing UCIs over the terminal's PUSCH, the maximum number of channel coding processes that the terminal can handle may be predetermined. This may be information related to the terminal's implementation.

[0506] For example, for a terminal with high computing power, the maximum number of channel coding processes may be 3, but for a terminal with low computing power, the maximum number of channel coding processes may be 2. Therefore, the base station may need to instruct or set up multiplexing of UCI on PUSCH based on the computing power of the terminal. To this end, the terminal may report the maximum number of channel coding processes in the terminal capability (UE capability) report.

[0507] According to one embodiment, if the number of maximum channel coding processes is not included in the terminal capability report, it can be assumed that the terminal supports a minimum number of specific processes.

[0508] The base station can set the maximum number of channel coding processes for the terminal based on the terminal capability report.

[0509] For example, if the terminal reports 3 as the maximum number of channel coding processes, the base station may set 1, 2, or 3 as the maximum number of channel coding processes to be used by the terminal. The maximum number of channel coding processes may be equal to the number of UCI groups.

[0510] The terminal can multiplex UCIs on the PUSCH based on the configured maximum number of channel coding processes (K). If UCI grouping is not applied, the terminal can multiplex up to K different UCI types on the PUSCH. If UCI grouping is applied, the terminal can multiplex up to K different UCI groups on the PUSCH.

[0511] If UCI grouping is not applied, and more than K UCI types are multiplexed on the PUSCH, the terminal may multiplex only up to K UCI types on the PUSCH and drop the remaining UCI types without multiplexing them. If UCI grouping is applied, the number of UCI groups may be equal to or less than the value of K. Therefore, no separate dropping may occur.

[0512] According to one embodiment, depending on the configuration of the base station, the terminal may apply UCI grouping when UCI types exceeding K are multiplexed on the PUSCH.

[0513] FIG. 17 is a flowchart illustrating UCI grouping according to one embodiment of the present disclosure.

[0514] In the first step, the terminal may transmit terminal capability information related to UCI multiplexing on PUSCH to the base station. The information may include at least one of information regarding whether UCI grouping can be performed with said terminal capability, information regarding the maximum number of UCI groups, and information regarding the maximum number of channel coding processes.

[0515] In the second stage, the terminal may receive information associated with a UCI group from the base station. For example, the terminal may receive at least one of the number of UCI groups, a beta offset value and / or alpha value corresponding to the UCI group, or information regarding the UCI grouping method.

[0516] In the third step, one or more UCI groups can be created or identified based on a UCI grouping method. The terminal can combine the types of UCIs included in the UCI group to create a single UCI payload corresponding to a single UCI group. Here, a CRC may be attached to the single UCI payload.

[0517] In the fourth step, the terminal may perform channel coding by allocating one channel coding process per UCI group. Channel coding may be performed on one UCI payload (or including CRC) corresponding to the UCI group. Additionally, rate-matching may be performed after channel coding, and said rate-matching may be performed based on a beta offset value and / or alpha value corresponding to the UCI group.

[0518] In the fifth step, the terminal can combine rata-matched bits for each UCI group to create a single UCI payload.

[0519] Example 3. Interleaver-based resource mapping method

[0520] Based on Example 1 or Example 2, the terminal can obtain a bit stream combined with UCI and UL-SCH. Example 3 may correspond to a method of mapping the bit stream onto PUSCH.

[0521] According to Example 3, the bit stream of the terminal may include a UCI and a UL-SCH. Unless otherwise noted, the UCI may be included at the beginning of the bit stream. This is because the base station can receive the UCI as quickly as possible to reduce the UCI latency. However, the present disclosure is not limited thereto. The position of the UCI in the bit stream is described in Example 4. Example 3 may be applied regardless of where the UCI is located in the bit stream.

[0522] For example, when a bit stream is mapped to PUSCH, the terminal may be mapped in a frequency-first time-second manner. That is, the first Q bits of the bit stream may correspond to the lowest RE in the frequency axis of the leading symbol of PUSCH. And the next Q bits may correspond to the second lowest RE in the frequency axis. According to one embodiment, Q may be a modulation order (1 for BPSK, 2 for QPSK, 4 for 16QAM, 6 for 64QAM, 8 for 256QAM, 10 for 1024QAM).

[0523] According to the above frequency-first time-second mapping method, the UCI can be mapped to consecutive REs. If the length of the UCI is short, the UCI may be contained only in a narrow frequency band, making it difficult to obtain frequency diversity gain.

[0524] According to one embodiment, an interleaver may be used to obtain frequency diversity. The interleaver is characterized by interleaving bits corresponding to one OFDM symbol of a bit stream along the frequency axis. For convenience, the interleaver may be exemplified as a per-symbol interleaver.

[0525] According to one embodiment, the number of OFDM symbols that can transmit a bit stream in PUSCH is N symb In this case, symbols that cannot be transmitted via a bit stream (e.g., when all REs are used as DMRS or are reserved resources) can be excluded. Additionally, the indices of OFDM symbols are l=0, 1, ..., N symbIt can be said to be -1. And the number of bits that can be transmitted in OFDM symbol l can be called B(l). For reference, B(0)+B(1)+...+B(N symb- 1) can be equal to the length of the bit stream.

[0526] According to one embodiment, the terminal has a bit stream N symb It can be divided into sets. The first set may contain B (0) bits, the second set may contain B (1) bits, ... N symb The i-th set is B(N symb -1) bits may be included. The B(0) bits of the first set are mapped to the first OFDM symbol of PUSCH, the B(1) bits of the second set are mapped to the second OFDM symbol of PUSCH, and N symb B(N) of the i-th set symb -1) bits are N symb It can correspond to the th OFDM symbol.

[0527] According to one embodiment, the terminal can perform interleaving for each set. For example, block interleaving can be performed for each set based on the number of bits included in the set. Specifically, block interleaving corresponding to B(0) can be applied to the B(0) bits of the first set. Block interleaving corresponding to B(1) can be applied to the B(1) bits of the second set. That is, N symb B(N) of the i-th set symb -1) bits contain B(N symb Block interleaving corresponding to -1) can be applied.

[0528] According to one embodiment, the terminal may receive or set information regarding the block interleaver from the base station. For example, the terminal may receive a setting for the number of rows (or columns) of the block interleaver. For example, the number of rows (N row) can be set to 2 or 4.

[0529] For example, a bit-unit block interleaver can be defined as follows.

[0530] bits of length B prior to interleaving {b0, b1, ..., b B-1 Let} be the bits of length B after interleaving, {d0, d1, ..., d B-1 Let's assume}. Block interleavering can be performed as follows. Block interleavering is d f(x) =b x , x=0, 1, ..., B-1. Here, f(x) can be equal to the following [Equation 6].

[0531] [Mathematical Formula 6]

[0532]

[0533] Here, B is N row It can be an integer multiple of . offset can be a value that the base station sets for the terminal. Alternatively, it can be fixed at offset=0. Depending on the offset, the result of the block interleaver performed by the terminal may vary.

[0534] bits with interleaved {d0, d1, ..., d B-1} can be modulated and matched in ascending order on the frequency axis starting from the lowest RE on the frequency axis.

[0535] According to one embodiment, B=20, N row When =4, offset=0, the result can be exemplified in the following [Table 26].

[0536] Referring to [Table 26], the terminal is bits {d0, d1, ..., d} of length B after block interleaving is applied. B-1} is {b0, b5, b 10 , b 15 , b1, b6, b 11 , b 16, b2, b7, b 12 , b 17 , b3, b8, b 13 , b 18 , b4, b9, b 14 , b 19 It can be. For example, if the UCI is {b0, b1, ..., b5} and Q=2, the above 6 bits can be mapped to the lowest consecutive REs (RE0, RE1, RE2) in the three frequency axes. However, through an interleaver, b0 and b5 can be transmitted at the first RE (RE0) in the frequency axis, b1 at the third RE (RE2), b2 at the fifth RE (RE4), b3 at the seventh RE (RE6), and b4 at the ninth RE (RE8). Therefore, since the UCI is transmitted at different REs in the frequency axis, frequency diversity can be achieved.

[0537] x (c,r)f(x)0 (0,0)01 (0,1)52 (0,2)103 (0,3)154 (1,0)15 (1,1)66 (1,2)117 (1,3)168 (2,0)29 (2,1)710 (2,2)1211 (2,3)1712 (3,0)313 (3,1)814 (3,2)1315 (3,3)1816 (4,0)417 (4,1)918 (4,2)1419 (4,3)19

[0538] According to one embodiment, a symbol unit block interleaver may be defined as follows. A bit stream of length B may be modulated according to the modulation method of PUSCH. The number of modulated symbols may be B / Q=M.

[0539] Modulated symbols of length M prior to interleaving are {s0, s1, ..., s M-1 Let} be the bits of length M after interleaving, {t0, t1, ..., t M-1 Let's assume}. A block interleaver can be performed as follows. The block interleaver is t g(x)=s x , x=0, 1, ..., M-1. Here, g(x) can be equal to the following [Equation 7].

[0540] [Mathematical Formula 7]

[0541]

[0542] In [Equation 7], M is N row It can be an integer multiple of . offset can be a value that the base station sets for the terminal. Alternatively, it can be fixed at offset=0. Depending on the offset, the result of the block interleaver performed by the terminal may vary.

[0543] Modulated symbols with interleaved {b0, b1, ..., b B-1} can be matched in ascending order on the frequency axis starting from the lowest RE on the frequency axis.

[0544] For example, B=20, N row If =2, offset=0, Q=2, {b0, b1, ..., b 19} is modulated according to the modulation method, and the modulated symbols B / Q=M=10 can be represented as {s0, s1, ..., s9}. After applying block interleaving, the terminal may have modulated symbols of length M=10 {t0, t1, ..., t9} as {s0, s5, s1, s6, s2, s7, s3, s8, s4, s9}. For example, if the modulated symbols mapped by UCI are {s0, s1, s2}, the three modulated symbols can be mapped to the lowest consecutive REs (RE0, RE1, RE2) in the three frequency axes. However, through the interleaver, s0 can be transmitted to the first RE (RE0) in the frequency axis, s1 to the third RE (RE2) in the frequency axis, and s2 to the fifth RE (RE4) in the frequency axis. Therefore, since UCI is transmitted from different REs in the frequency axis, frequency diversity can be achieved.

[0545] According to one embodiment, the block interleaver described above can be applied when the MIMO layer of PUSCH is 1. If PUSCH has multiple MIMO layers (N L In the case of >1), the block interleaver can be applied to bits corresponding to each MIMO layer. For example, if PUSCH includes two MIMO layers, block interleaver can be performed on bits corresponding to the first MIMO layer in one OFDM symbol based on [Equation 6], and block interleaver can be performed on bits corresponding to the second MIMO layer based on [Equation 6]. Block interleaver can be performed on modulated symbols corresponding to the first MIMO layer in one OFDM symbol based on [Equation 7], and block interleaver can be performed on modulated symbols corresponding to the second MIMO layer based on [Equation 7].

[0546] FIG. 18 is a diagram illustrating the process of multiplexing a UCI on a PUSCH according to one embodiment of the present disclosure.

[0547] The terminal can receive a PUSCH from the base station. For example, the PUSCH may include two OFDM symbols that can send UCI or UL-SCH, excluding DMRS symbols.

[0548] The terminal can determine the type of UCI to be multiplexed with the above PUSCH. For example, the type of UCI may include HARQ-ACK, CSI part 1, CSI part 2, or other new types of UCIs.

[0549] The terminal may include multiple UCI types in one or more UCI groups. For example, it may be included in two UCI groups. In one embodiment, CRC attachment, channel coding, and rate-matching may be performed on each of the two UCI groups.

[0550] The UCI group and UL-SCH, for which channel coding and rate-matching have been performed, can be combined into a single bit stream (e.g., Multiplexed payload). For example, according to FIG. 18, the UCI group for which channel coding and rate-matching have been performed in the bit stream can be placed ahead of the UL-SCH.

[0551] The terminal can modulate the bit stream according to the modulation method. In addition, the modulated symbols can be interleaved through a per-symbol block interleaver.

[0552] For example, a per-symbol block interleaver can be applied to the symbols corresponding to the first OFDM symbol among the modulated symbols, and to the symbols corresponding to the second OFDM symbol, respectively. As an example, if the UCI corresponds only to the first OFDM symbol, the symbols occupied by the UCI among the symbols corresponding to the first OFDM symbol can be distributed according to the per-symbol block interleaver.

[0553] The terminal can place or map interleaved symbols to PUSCH using a frequency-first time-second method.

[0554] FIG. 19 is a flowchart illustrating the multiplexing of UCI on a PUSCH according to one embodiment of the present disclosure.

[0555] In FIG. 11, an example is shown of mapping UCI to PUSCH first and UL-SCH to time-second using a UCI-to-RE mapping method according to one embodiment in the Data and control multiplexing block following the UL-SCH CB concatenation block and the UCI concatenation block.

[0556] Refer to Fig. 11 for the UL-SCH CB concatenation block and the UCI concatenation block in Fig. 19, and furthermore in Fig. 19, the step of combining the UL-SCH CB and UCI into a single bit stream and the step of performing a per-symbol block interleaver may be exemplified, after which the interleaved bit stream or modulated symbols are mapped to PUSCH in a frequency-first time-second manner.

[0557] Example 4. Method for determining the location of a UCI in a bit stream

[0558] In Examples 1 to 3, the UCI is placed at an earlier position in the bit stream. This may be to allow the base station to receive the UCI quickly. However, if the UCI is placed at an earlier position in the bit stream, it may affect the processing of the subsequently placed UL-SCH. Additionally, if the UCI is placed at the very earlier position, the terminal may need to complete the UCI generation before the PUSCH generation time.

[0559] According to one embodiment, if the UCI is located in the middle of the bit stream, there may be room for UCI generation. For example, if UL-SCH is transmitted, the terminal may generate a UCI during the preceding symbols of PUSCH. Thus, the position of the UCI in the bit stream may vary depending on the conditions. Methods for this are disclosed.

[0560] [Method for Determining Reference Points]

[0561] According to one embodiment, information related to processing time, etc. for determining a reference point in Method 4-1 or Method 4-2 may be received from a base station, pre-set, or determined by a terminal.

[0562] [Method 4-1] Symbol-based

[0563] According to one embodiment, the terminal can determine the earliest symbol among the symbols satisfying the processing time as a reference point.

[0564] According to one embodiment, the terminal can determine the earliest symbol among the PUSCH symbols that overlap with PUCCH as a reference point.

[0565] Here, DMRS symbols may be excluded.

[0566] [Method 4-2] Symbol set (mini-slot or sub-slot) unit based

[0567] According to one embodiment, the terminal may determine the first symbol of the earliest symbol set among the symbol sets satisfying the processing time as a reference point. Additionally, if all symbols within a symbol set satisfy the processing time, it may be considered a symbol set satisfying the processing time.

[0568] For example, whether the processing time is satisfied can be determined based on the reception time of the DCI scheduling the PUSCH. For instance, if the processing time is N symbols, it can be determined that symbols N symbols after the reception time of the DCI (one of the symbols for which the DCI is received, e.g., the last symbol) satisfy the processing time.

[0569] Whether the processing time is satisfied can be determined based on the reception time of the DCI scheduling the UCI. For example, if the processing time is M symbols, symbols after M symbols from the reception time of the DCI (one of the symbols for which the DCI is received, e.g., the last symbol) can be determined to be symbols that satisfy the processing time.

[0570] The satisfaction of processing time can be determined when both of the two aforementioned conditions (based on the reception time of the DCI scheduling PUSCH and based on the reception time of the DCI scheduling UCI) are satisfied. For example, processing time can be determined to be satisfied if at least one of the conditions related to processing time satisfaction is satisfied.

[0571] According to one embodiment, the terminal may determine the first symbol of the earliest symbol set among the symbol sets of PUSCH that overlap with PUCCH as a reference point. Additionally, if all symbols within a symbol set overlap with PUCCH or symbols after PUCCH, it may be considered a symbol set that overlaps with PUCCH.

[0572] According to one embodiment, during PUSCH frequency hopping, the symbol set may be determined by the OFDM symbols included in the first frequency hop and the OFDM symbols included in the second frequency hop. For reference, DMRS symbols may be excluded when determining whether the symbol set is satisfied.

[0573] According to one embodiment, the terminal can determine CBs mapped to OFDM symbols scheduled by the PUSCH. If there is a CB that is transmitted for the first time in subsequent OFDM symbols from the OFDM symbol corresponding to the reference point (i.e., a CB that was not transmitted in the OFDM symbol prior to the OFDM symbol corresponding to the reference point), the CB and subsequent CBs may be exemplified as impacted CBs. And the CBs prior to the CB may be exemplified as non-impacted CBs.

[0574] According to one embodiment, the terminal may include a UCI between the last bit of the non-impacted CBs and the first bit of the impacted CBs. If there are no non-impacted CBs, the UCI may be included before the first bit of the impacted CB. If there are no impacted CBs, the terminal may not multiplex the UCI in the PUSCH.

[0575] FIG. 20 is a drawing illustrating a PUCCH including a PUSCH and a UCI according to one embodiment of the present disclosure.

[0576] Referring to FIG. 20, PUSCH may include CB#0, CB#1, CB#2, and CB#3. The terminal may determine a reference point based on the scheduling of PUSCH and PUCCH. Referring to FIG. 20, the reference point may be an OFDM symbol including CB#2 and CB#3. Thus, CB#0 and CB#1 may be non-impacted CBs, and CB#2 and CB#3 may be impacted CBs. In FIG. 20, UCI may be included in the OFDM symbol containing the impacted CBs exemplified above.

[0577] FIG. 21 is a diagram illustrating UCI and UL-SCH processing of a terminal according to one embodiment of the present disclosure.

[0578] Referring to FIGS. 20 and FIG. 21, the terminal may include four CBs (CB#0, CB#1, CB#2, CB#3) prior to UCI multiplexing in PUSCH. Depending on a determined reference point, CB#0 and CB#1 may be non-impacted CBs, and CB#2 and CB#3 may be impacted CBs. Thus, the UCI may be inserted between the last bit of CB#1 and the first bit of CB#2.

[0579] According to one embodiment, the non-impacted CBs included in PUSCH may be CBs that are unaffected by UCI multiplexing. Accordingly, the rate-matching and PUSCH resource mapping of the non-impacted CBs may not change. Here, since CB#0 and CB#1 are non-impacted CBs, the CBs may be transmitted in the first OFDM symbol regardless of UCI multiplexing.

[0580] According to one embodiment, the impacted CBs included in the PUSCH may be CBs affected by UCI multiplexing. Accordingly, rate-matching of the impacted CBs may be performed anew. In this case, rate-matching may be determined based on the amount of resources occupied by the UCI (e.g., determined by the beta offset and / or alpha value). For example, CB#2 and CB#3 may be newly rate-matched based on the amount of resources occupied by the UCI. The UCI, CB#2, and CB#3 may be transmitted in the second OFDM symbol. Additionally, modulation may be performed after rate-matching.

[0581] According to one embodiment, the terminal can transmit PUSCH using an interleaving and frequency-priority time-lane resource mapping method.

[0582] FIG. 22 is a flowchart illustrating the generation of UL-SCH and UCI of a terminal according to one embodiment of the present disclosure.

[0583] Compared to Fig. 19, the result value of UCI generation and UCI rate-matching (e.g., Q ACK ) can only affect impacted CBs. Non-impacted CBs may not be affected depending on UCI generation and UCI rate-matching.

[0584] For other blocks, refer to the description in FIG. 11 or FIG. 19.

[0585] FIG. 23 is a flowchart related to a reference point according to an embodiment of the present disclosure.

[0586] In the first step, the terminal can determine a reference point when the UCI is multiplexed to the PUSCH. For example, the reference point may be determined based on the processing timeline, the PUSCH, the symbols for which the PUCCH including the UCI is scheduled, etc.

[0587] In the second step, the terminal may determine non-impacted CBs and impacted CBs based on the reference point. For non-impacted CBs, the terminal may not change the rate-matching and / or PUSCH mapping. For impacted CBs, the terminal may change the rate-matching and / or PUSCH mapping based on the UCI multiplexed to PUSCH.

[0588] In the third step, the terminal may place the UCI between the non-impacted CBs and the impacted CBs. Additionally, the terminal may transmit a bit stream containing the UCI and the CBs of UL-SCH to PUSCH using modulation, interleaving, and / or PUSCH resource mapping according to one embodiment.

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

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

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

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

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

[0594] In addition, 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.

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

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

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

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

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

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

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

[0602] 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 embodiments described in the claims or specification of this disclosure.

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

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

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

[0606] 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, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

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

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

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

[0610] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will understand that modifications can be easily made to other specific forms 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 their equivalents should be interpreted as being included within the scope of the present disclosure.

Claims

In a method performed by a terminal of a communication system, A step of identifying a transport block (TB) for uplink transmission; A step of identifying uplink control information (UCI); A step of performing first channel coding on the above transmission block; A step of performing second channel coding on the above uplink control information; A step of mapping a bit sequence to PUSCH (physical uplink shared channel); and The step of transmitting the above PUSCH to a base station, A method characterized in that the above bit sequence is a transmission block in which the first channel coding is performed and the uplink control information in which the second channel coding is performed are multiplexed. In Article 1, A step of identifying at least one group of uplink control information included in the uplink control information; and The method includes the step of performing the second channel coding for each of the above at least one uplink control information group, The above transmission block includes at least one code block (CB), and A method characterized by the above multiplexing including concatenation. In Article 2, A method characterized in that the above-mentioned at least one uplink control information group is grouped based on at least one of a setting by the base station, a beta offset value, a priority, or the number of bits. In Article 1, A step of transmitting capability information related to the multiplexing to the base station; and A method further comprising the step of receiving information related to an uplink control information group from the above base station. In Article 1, The mapping step above includes the step of performing interleaving on the bit sequence, and A method characterized in that the above interleaving is performed based on OFDM (orthogonal frequency division multiplexing) symbol units. In Article 1, The position of the uplink control information where the second channel coding is performed in the above bit sequence is determined based on a reference point, and A method characterized in that the above reference point is determined based on at least one of the symbol where PUCCH (physical uplink control channel) and PUSCH overlap, or the boundary of the code blocks (CB) included in the transmission block. In a method performed by a base station of a communication system, A step of receiving capability information related to multiplexing from a terminal; A step of transmitting information related to an uplink control information group to the above terminal; and The method includes the step of receiving a PUSCH (physical uplink shared channel) mapped to a bit sequence from the terminal, and A method characterized in that the bit sequence above is a transport block (TB) with first channel coding performed and uplink control information (UCI) with second channel coding performed are multiplexed. In a terminal of a communication system, Transmitter / receiver; and The above-mentioned transceiver is connected to the above-mentioned transport block, identifies a transport block (TB) for uplink transmission, identifies uplink control information (UCI), performs first channel coding on the transport block, performs second channel coding on the uplink control information, maps a bit sequence to a PUSCH (physical uplink shared channel), and includes a control unit that transmits the PUSCH to a base station. The above bit sequence is a terminal characterized by the transmission block in which the first channel coding is performed and the uplink control information in which the second channel coding is performed being multiplexed. In Article 8, The control unit identifies at least one group of uplink control information included in the uplink control information, and For each of the above at least one uplink control information group, the second channel coding is performed, and The above transmission block includes at least one code block (CB), and The above multiplexing is a terminal characterized by including a connection. In Article 9, A terminal characterized in that the above-mentioned at least one uplink control information group is grouped based on at least one of a setting by the base station, a beta offset value, a priority, or the number of bits. In claim 8, the control unit transmits capability information related to the multiplexing to the base station, and the terminal receives information related to an uplink control information group from the base station. In Article 8, The control unit above performs interleaving on the bit sequence, and A terminal characterized in that the above interleaving is performed based on OFDM (orthogonal frequency division multiplexing) symbol units. In Article 8, The position of the uplink control information where the second channel coding is performed in the above bit sequence is determined based on a reference point, and A terminal characterized in that the above reference point is determined based on at least one of the symbol where PUCCH (physical uplink control channel) and PUSCH overlap, or the boundary of code blocks (CB) included in the transmission block. In a base station of a communication system, Transmitter / receiver; and It includes a control unit connected to the above-mentioned transceiver, receiving capability information related to multiplexing from a terminal, transmitting information related to an uplink control information group to the terminal, and receiving a PUSCH (physical uplink shared channel) with a bit sequence mapped from the terminal. The above bit sequence is a base station characterized by the multiplexing of a transport block (TB) in which first channel coding is performed and uplink control information (UCI) in which second channel coding is performed.

Images