Method and apparatus for uplink transmission considering uplink transport block in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to the operation of a terminal and a base station in a wireless communication system and, more specifically, to a method for transmitting and receiving an uplink reference signal in a wireless communication system, and an apparatus capable of performing same. The present disclosure provides an apparatus and a method capable of providing services effectively in a mobile communication system.

Description

Uplink transmission method and device considering an uplink transmission block in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for transmitting an uplink data channel using an 8 UL Tx antenna and an apparatus capable of performing the same.

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

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

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

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating 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] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0009] The present invention, for solving the above-mentioned problems, is characterized in that a method for processing a control signal in a wireless communication system comprises: a step of receiving a first control signal transmitted from a base station; a step of processing the received first control signal; and a step of transmitting a second control signal generated based on the processing to the base station.

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

[0011] FIG. 1 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates data that can be transmitted as 1 TB as 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0012] FIG. 2 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 2 TB using data and dummy bits that can be transmitted as 1 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0013] FIG. 3 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 2 TB using data and padding bits that can be transmitted as 1 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0014] FIG. 4 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal divides data that can be transmitted as 1 TB to create 2 TB, and transmits the created 2 TB through a 2 TB PUSCH composed of layers larger than 4.

[0015] FIG. 5 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal repeats data that can be transmitted as 1 TB to generate 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0016] FIG. 6 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal generates a second TB composed of zero bits, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0017] FIG. 7 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal divides the 1 TB data transmitted from the upper layer to generate 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0018] FIG. 8 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal generates 2 TB by repeating the 1 TB data transmitted from the upper layer, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0019] FIG. 9 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, and the physical layer of the terminal transmits only the 1 TB transmitted from the upper layer using only a portion of a 2 TB PUSCH composed of layers greater than 4.

[0020] FIG. 10 illustrates an example of a method for transmitting only 1 TB composed of 2 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

[0021] FIG. 11 illustrates an example of a method for transmitting only 1 TB composed of 2 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

[0022] FIG. 12 illustrates an example of a method for reconstructing and transmitting a TB to be transmitted in 2 layers into 1 TB composed of 4 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0029] Hereinafter, a 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. A 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, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

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

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

[0032] 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. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

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

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

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

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

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

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

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

[0040] Hereinafter, a / b may be understood as at least one of a or b.

[0041] [PUSCH: Regarding transmission method]

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

[0043] Configured grant Type 1 PUSCH transmissions can be configured semi-statically by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 1], 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 1], 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 1], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 2]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 1], the terminal applies tp-pi2BPSK in pusch-Config of [Table 2] to PUSCH transmissions operated by configured grant.

[0044] [Table 1]

[0045]

[0046]

[0047] 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 2], the upper signaling, is 'codebook' or 'nonCodebook'.

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

[0049] [Table 2]

[0050]

[0051]

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

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

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

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

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

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

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

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

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

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

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

[0063] [PUSCH: Regarding TPMI]

[0064] Next, we will explain the TPMI (Transmit Precoding Matrix Indicator) indicated by the DCI from the base station during codebook-based PUSCH transmission.

[0065] If the terminal is configured to receive a 1-layer transmission via DCI or higher layer signaling from the base station using a single PUSCH antenna port, the TPMI can be defined as W=1; otherwise, that is, if the terminal is configured to receive a PUSCH scheduling of 1-layer or more via DCI or higher layer signaling from the base station using multiple PUSCH antenna ports, the TPMI W can be defined through [Table 3] to [Table 9] below.

[0066] [Table 3]

[0067]

[0068] [Table 3] above shows TPMI in 1-layer when the terminal has two PUSCH antenna ports. In [Table 3] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to one of TPMI index 0 and 1, and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to one of TPMI index 0 to 5.

[0069] [Table 4]

[0070]

[0071] [Table 4] above describes a 1-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is used (i.e., when a DFTS-OFDM waveform is used). In [Table 4] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 3; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 11; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 27.

[0072] [Table 5]

[0073]

[0074] [Table 5] above describes a 1-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when a CP-OFDM waveform is used). In [Table 5] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 3; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 11; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 27.

[0075] [Table 6]

[0076]

[0077] [Table 6] above describes a 2-layer TPMI in which the terminal has two PUSCH antenna ports and transform precoding is not used (i.e., when a CP-OFDM waveform is used). In [Table 6] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0, and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2.

[0078] [Table 7]

[0079]

[0080] [Table 7] above describes a 2-layer TPMI in which the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when a CP-OFDM waveform is used). In [Table 7] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 5; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 13; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal with one of TPMI indices 0 to 21.

[0081] [Table 8]

[0082]

[0083] [Table 8] above describes a 3-layer TPMI where the terminal has four PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In [Table 8] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 6.

[0084] [Table 9]

[0085]

[0086] [Table 9] above describes a 4-layer TPMI where the terminal has 4 PUSCH antenna ports and transform precoding is not used (i.e., when CP-OFDM waveforms are used). In [Table 9] above, if the terminal has a non-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0; if the terminal has a partial-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 2; and if the terminal has a full-coherent antenna structure and reports a corresponding terminal capability to the base station, the base station may select and instruct the terminal to TPMI index 0 to 4.

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

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

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

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

[0091] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be described uniformly as TRP (transmission reception point), beam, or TCI state. Accordingly, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.

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

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

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

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

[0096] - MIB (Master Information Block)

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

[0098] - RRC (Radio Resource Control)

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

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

[0101] - PDCCH (Physical Downlink Control Channel)

[0102] - DCI (Downlink Control Information)

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

[0104] - Group common DCI

[0105] - Common DCI

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

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

[0108] - PUCCH (Physical Uplink Control Channel)

[0109] - UCI (Uplink Control Information)

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

[0111] The term "slot" used in the present disclosure below is a general term that may refer to a specific time unit corresponding to TTI (Transmit Time Interval), and specifically, it may refer to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

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

[0113] If there is no UL (uplink) traffic to be transmitted by the terminal to the base station (which may mean that the upper layer of the terminal does not transmit UL data to be transmitted to the base station to the physical layer (which may be expressed as physical layer, phy layer, or physical layer), and the base station has scheduled UL physical resources to the terminal (meaning resources of a physical channel for transmitting UL traffic, which may, for example, mean time resources and frequency resources of a PUSCH scheduled by the base station), the terminal may skip PUSCH transmission according to the conditions described below. Hereinafter, the operation of the terminal skipping PUSCH transmission according to the presence of UL traffic and the conditions described below is defined as UL skipping. Meanwhile, in this disclosure, the expression "transmitting UL traffic through a UL channel" may be used interchangeably with similar expressions such as "transmitting a UL channel," "transmitting UL traffic," "transmitting UL data," or "performing UL transmission" for convenience, and may mean substantially the same operation.

[0114] If a terminal performs UL skipping because it has no UL traffic to transmit to the base station, terminal power saving (UE power saving) is possible because the terminal does not perform unnecessary UL transmissions. However, since the base station has scheduled UL transmission for the terminal and expects to receive a UL channel from the terminal, the base station must determine whether the terminal has transmitted a UL channel or performed UL skipping. As such, because the base station cannot know which of the different possible actions (transmitting a UL channel or performing UL skipping) the terminal has performed, it must perform blind decoding and, based on this, perform a hypothesis to determine whether the terminal has received a UL channel or performed UL skipping. Therefore, complexity increases when the base station receives a UL channel from the terminal.

[0115] A terminal can transmit to a base station the RRC parameter skipUplinkTxDynamic included in a terminal capability report (UE capability report) by setting it to 'supported' in order to report to the base station that it can support UL skipping (hereinafter referred to as DG-based UL skipping) for UL transmission based on a dynamic grant (hereinafter referred to as DG) scheduled by DCI. The base station can confirm that the terminal can support DG-based UL skipping by referring to the UE capability reported by the terminal, and the base station can set the RRC parameter skipUplinkTxDynamic at the MAC Cell group level to 'true' for terminals capable of performing DG-based UL skipping (i.e., set the Boolean value of skipUplinkTxDynamic in MAC-CellGroupConfig to true ('1')). If a DG-based PUSCH transmission is scheduled for the terminal and skipUplinkTxDynamic is set to 'true', and the following conditions are met, the terminal's upper layer does not generate a MAC PDU (Medium Access Control Protocol Data Unit) for the HARQ entity for the scheduled DG-based PUSCH.

[0116] - The corresponding PUSCH transmission does not execute the aperiodic CSI report based on the aperiodic CSI request.

[0117] - The MAC PDU contains zero MAC SDUs (Medium Access Control Service Data Units). This means that there is no data to transmit from the terminal's upper layer to the base station.

[0118] - The MAC PDU contains only periodic BSRs (buffer status reports) and there is no data available for a specific LCG (Logical Channel Group), or the MAC PDU contains only padded BSRs. In other words, this means that the BSRs included in the MAC PDU contain no information whatsoever.

[0119] DG-based UL skipping behavior is limited to dynamic grant-based PUSCH (hereinafter DG PUSCH) scheduled by DCI. Meanwhile, as described above, if the RRC parameter (e.g., a parameter included within MAC-CellGroupConfig in the RRC message) skipUplinkTxDynamic is set (e.g., set to true) to support UL skipping behavior and the upper layer of the terminal does not generate a transport block (TB, i.e., data to be transmitted via PUSCH) to be transmitted, and the DG PUSCH scheduled by DCI and the PUCCH for transmitting CSI and / or HARQ-ACK overlap in the time domain, the terminal behavior may not be defined. Furthermore, if the upper layer of the terminal does not transmit the TB to be transmitted through the resources allocated for uplink transmission without grant, the terminal does not transmit anything through the resources configured by the RRC parameter configuredGrantConfig.

[0120] The DG-based UL skipping operation supported by the setting of skipUplinkTxDynamic (for example, parameters included in MAC-CellGroupConfig within the RRC message) may cause ambiguity in some operations of the terminal (as described above, when the terminal does not generate a TB but a PUCCH for transmitting CSI and / or HARQ-ACK overlaps), and an enhanced UL skipping operation may be supported to alleviate the complexity of the base station regarding blind decoding. The enhanced UL skipping operation can be divided into an enhanced UL skipping operation for dynamic grant (hereinafter DG) based UL transmission scheduled by DCI (hereinafter referred to as DG-based enhanced UL skipping) and a UL skipping operation for configured grant (hereinafter CG) based UL transmission scheduled by RRC parameters (hereinafter referred to as CG-based enhanced UL skipping), and the UE capability report and RRC parameter setting for supporting each enhanced UL skipping operation are performed individually. A terminal can transmit to a base station the RRC parameter enhancedSkipUplinkTxDynamic included in the UE capability report to 'supported' in order to report to the base station that it can support DG-based enhanced UL skipping. The base station can support DG-based enhanced UL skipping for the terminal by referring to the UE capability reported by the terminal, and the base station can set the RRC parameter enhancedSkipUplinkTxDynamic at the MAC Cell group level to 'true' for terminals capable of performing DG-based enhanced UL skipping.And / or the terminal may transmit to the base station the RRC parameter enhancedSkipUplinkTxConfigured included in the UE capability report set to 'supported' to report to the base station that it can support CG-based enhanced UL skipping. The base station may support CG-based enhanced UL skipping for the terminal by referring to the UE capability reported by the terminal, and the base station may set the RRC parameter 'enhancedSkipUplinkTxConfigured' at the MAC Cell group level to 'true' for terminals capable of performing CG-based enhanced UL skipping. If a DG-based PUSCH transmission is scheduled for the terminal and enhancedSkipUplinkTxDynamic is set to 'true', or if a CG-based PUSCH transmission is scheduled for the terminal and enhancedSkipUplinkTxConfigred is set to 'true', and the following conditions are satisfied, the terminal does not generate a MAC PDU for a HARQ entity for a DG-based PUSCH scheduled at the upper layer or for a HARQ entity for a CG-based PUSCH.

[0121] - There is no multiplexed UCI in the corresponding PUSCH transmission

[0122] - The corresponding PUSCH transmission does not execute the aperiodic CSI report based on the aperiodic CSI request.

[0123] - The MAC PDU contains zero MAC SDUs (Medium Access Control Service Data Units). This means that there is no data to transmit from the terminal's upper layer to the base station.

[0124] - The MAC PDU contains only periodic BSRs (buffer status reports) and there is no data available for a specific LCG (Logical Channel Group), or the MAC PDU contains only padded BSRs. In other words, this means that the BSRs included in the MAC PDU contain no information whatsoever.

[0125] If the base station and the terminal support enhanced UL skipping and the upper layer of the terminal does not generate a TB to be transmitted, and the scheduled CG PUSCH or DG PUSCH and the PUCCH for transmitting CSI and / or HARQ-ACK overlap in the time domain, the terminal may multiplex the UCI to the PUSCH (limited to cases where the UCI is multiplexed to the PUSCH according to the UL channel overlap rule) and transmit the PUSCH.

[0126] UL MIMO using more UL antennas can be supported on devices capable of supporting high-performance wireless access functions, such as CPE (customer premise equipment) or FWA (fixed wireless access). Since these devices have a larger form factor than handheld devices (e.g., smartphones) and operate from a fixed location, they can utilize many transmitting antennas. Therefore, enhanced UL MIMO operation can be supported to support terminals that support more UL transmitting antennas than 4Tx UL antennas (e.g., 8Tx UL antennas). If the terminal supports 4Tx UL antennas, it can support UL transmission of up to 4 layers. If the terminal supports 8Tx UL antennas, it can support a number of layers greater than 4, and can support UL transmission of up to 8 layers. In this case, if it supports UL transmission of a number of layers greater than 4, the terminal transmits two TBs instead of one TB, taking into account the maximum supportable length of the channel coding. For example, if the terminal transmits a Layer 5 PUSCH, the terminal transmits the first TB using the first two layers and transmits the second TB using the remaining three layers. If the terminal transmits a Layer 6 PUSCH, the terminal transmits the first TB using the first three layers and transmits the second TB using the remaining three layers. If the terminal transmits a Layer 7 PUSCH, the terminal transmits the first TB using the first three layers and transmits the second TB using the remaining four layers. If the terminal transmits a Layer 8 PUSCH, the terminal transmits the first TB using the first four layers and transmits the second TB using the remaining four layers.The two TBs transmitted by the terminal can be scheduled with the same or different MCS (modulation and coding scheme) and can be scheduled with the same HARQ process number but managed by different HARQ processes within the same HARQ process ID. That is, a retransmission buffer can be managed separately for each TB, and a NDI (new data indicator) can be indicated separately. Additionally, the redundancy version (RV) of each TB can be indicated differently. In other words, if a PUSCH to transmit 2 TB is scheduled as a DCI, the DCI scheduling that PUSCH includes the MCS field, the NDI field, and the RV field for each TB.

[0127] A base station may use a dynamic grant-based scheduling method to schedule PUSCH of more than four layers to a terminal supporting an 8Tx UL antenna. PUSCH of more than four layers cannot be scheduled through configured grant-based scheduling using RRC parameters and activation DCI (limited to cases where CG type 2 PUSCH is supported). However, PUSCH transmission techniques using up to four layers of an 8Tx UL antenna can be supported through configured grant-based scheduling. Based on the above characteristics, PUSCH of more than four layers capable of transmitting two TBs can only be scheduled using a dynamic grant-based scheduling method utilizing DCI.

[0128] The base station cannot accurately determine the UL traffic that the terminal will transmit. However, the base station can determine the amount of resources for PUSCH to be scheduled by referring to the BSR (buffer status report) reported by the terminal using MAC CE. For example, if the buffer size of the BSR reported by the terminal is small, the base station can schedule a small amount of PUSCH resources. This is determined by comprehensively assessing the amount of available UL resources at the time the base station schedules PUSCH and other factors, but it can be assumed that the decision is based on the buffer size of the BSR reported by the terminal. As another example, if the base station determines that PUSCH can be transmitted to a high layer because the buffer size of the BSR reported by the terminal is large and the quality of the UL channel is good, the base station can schedule PUSCH resources to the terminal that allow for the transmission of more than four layers to transmit 2 TB to the terminal. If a base station schedules a PUSCH resource capable of transmitting more than 4 layers to transmit 2 TB to a terminal, the terminal transmits PUSCH to the base station based on the base station's scheduling information.

[0129] However, the BSR reported by the terminal may be inaccurate and difficult to accurately convey the terminal's buffer status to the base station. The reason it is difficult to convey the terminal's accurate buffer status through the BSR is that the reporting cycle of the BSR is long, making it difficult to accurately report the changing buffer status of the terminal, and the generation of UL data to be transmitted by the terminal may also be irregular. For this reason, the base station may schedule a small PUSCH resource for the terminal, but the UL data traffic to be transmitted by the terminal may be large. Conversely, the base station may schedule a large PUSCH resource for the terminal, but the UL data traffic to be transmitted by the terminal may be small. If the terminal has been scheduled a small PUSCH resource but the UL data traffic to be transmitted is large, it may transmit some UL data to the base station and then transmit the remaining UL data to the base station using an additionally scheduled PUSCH (the terminal may transmit a PUCCH to the base station for scheduling purposes to receive the corresponding PUSCH). On the other hand, if a terminal is scheduled to have a large amount of PUSCH resources but has little UL data traffic to transmit, the operation of the terminal may vary depending on whether it supports UL skipping (or enhanced UL skipping).

[0130] If the terminal does not support UL skipping (or enhanced UL skipping), the terminal transmits the PUSCH by generating UL data and dummy bits for many scheduled PUSCH resources, or transmits the PUSCH by generating UL data and padding bits (0 or some padding information). Alternatively, depending on the amount of resources for the scheduled PUSCH, the terminal may transmit the channel coding code rate for the UL data at a lower rate without generating separate dummy or padding bits. If the terminal does not support UL skipping (or enhanced UL skipping) and many PUSCH resources capable of transmitting 2 TB (where the number of layers of the scheduled PUSCH is greater than 4) are scheduled for the terminal, and only UL data for 1 TB exists in the terminal's buffer, the terminal may transmit UL data to one TB of the 2 TB and transmit dummy or padding bits to the remaining TB. The terminal may select one TB out of the 2 TB to transmit UL data to. For example, if UL data is transmitted to only one of the two TBs, the terminal can transmit UL data to the first of the two TBs. Or, if UL data is transmitted to only one of the two TBs, the terminal can transmit UL data to the second of the two TBs. Or, if UL data is transmitted to only one of the two TBs, the terminal can transmit UL data to the TB scheduled with the higher MCS of the two TBs.

[0131] If a terminal supports UL skipping (or enhanced UL skipping) and the number of TBs to be transmitted via a PUSCH scheduled by the base station differs from the number of TBs to be transmitted for UL data delivered by the terminal's upper layer, ambiguity may arise in the terminal's operation. For example, if a terminal supports UL skipping (or enhanced UL skipping) and the base station has scheduled many PUSCH resources capable of transmitting 2 TBs (where the number of layers in the scheduled PUSCH is greater than 4) to the terminal, and only 1 TB of UL data exists in the terminal's buffer, it may be ambiguous whether the terminal will transmit only 1 TB and not transmit the remaining TBs according to the UL skipping operation, or whether it will generate dummy or padding bits and transmit all 2 TBs, just as in the case where the terminal does not support UL skipping, because it needs to transmit 1 TB. Even if a terminal supports UL skipping and a PUSCH resource capable of transmitting 2 TB is scheduled, if there is no UL data to transmit in the terminal's buffer, the terminal may not transmit the PUSCH according to the UL skipping operation (assuming the case where UCI is not multiplexed). However, if a PUSCH for transmitting 2 TB is scheduled but only UL data for 1 TB exists in the buffer, the terminal's action regarding whether to perform UL skipping on a TB-by-TB basis may be ambiguous.

[0132] In this case, we propose a method for defining the operation of a terminal and transmitting a PUSCH in the event that a PUSCH for 2 TB transmission is scheduled to a terminal that supports UL skipping, but only data to be transmitted in the terminal's buffer exists in the terminal's buffer.

[0133] <1st Embodiment: Method for always configuring and transmitting 2 TB at the upper layer of a terminal>

[0134] In the first embodiment, even if only UL data capable of transmitting 1 TB exists in the buffer of the terminal, the upper layer of the terminal generates 2 TB and transmits data to be transmitted to the physical layer of the terminal, and the physical layer of the terminal transmits a PUSCH capable of transmitting 2 TB scheduled to the base station to the base station, and the base station receives this is described in detail.

[0135] To transmit data from the upper layer of the terminal (e.g., the MAC layer) to the base station, a MAC PDU is generated, configured into a TB (transport block), and passed to the physical layer. The terminal's physical layer transmits the TB received from the upper layer to the base station. The terminal's physical layer supports the operation of transmitting the scheduling information and the TB received from the upper layer, and transmits the UL channel in the same manner as the scheduling information. For example, the base station may have scheduled a PUSCH to transmit Layer 4 to the terminal and may instruct the TPMI (assuming it supports codebook-based PUSCH) to support Layer 4 via the DCI. If the upper layer of the terminal generated a TB to transmit data to Layer 4 and passed it to the terminal's physical layer, or if the terminal does not support UL skipping and therefore a TB composed of dummy (or padding) bits was passed to the terminal's physical layer, the terminal's physical layer transmits the Layer 4 PUSCH to the base station using the scheduled PUSCH resources and the instructed transmission method. In other words, the physical layer of the terminal prepares and transmits the PUSCH based on the scheduling information for the PUSCH transmission scheduled by the base station for the terminal.

[0136] As described above, if only UL data capable of transmitting 1 TB exists in the terminal's buffer, the upper layer of the terminal can generate 2 TB through the following methods and transmit it to the terminal's physical layer, and the terminal's physical layer can transmit it to the base station via the 2 TB transmitted from the upper layer and a PUSCH determined based on scheduling information:

[0137] [Method 1] The upper layer of the terminal can generate a second TB and transmit 2 TB to the physical layer of the terminal. Here, the second TB may consist of values ​​other than zero padding bits or dummy bits. [Method 1] is a method of generating a TB by configuring the data in the terminal's buffer, which is to be transmitted as a single TB, into 2 TB by improving the MAC SDU or MAC PDU generation method of the upper layer of the terminal. According to [Method 1], the upper layer (e.g., MAC layer) can configure the TB based on the data in the terminal's buffer and the scheduling information of the base station. For example, even if the data in the terminal's buffer can be transmitted as 1 TB, the upper layer of the terminal (e.g., MAC layer) can configure the data in the buffer as 2 TB. The specific method may be based on the implementation of the terminal, and information indicating that the data that can be transmitted as 1 TB has been configured as 2 TB may be included in the upper layer information and transmitted to the base station. Subsequently, the upper layer of the terminal transmits the generated 2 TB to the physical layer of the terminal, and the physical layer transmits the received 2 TB to the base station via a scheduled PUSCH. The physical layer of the base station receives and decodes the PUSCH consisting of 2 TB transmitted by the terminal. The physical layer of the base station transmits the decoded 2 TB to the upper layer of the base station, and the upper layer of the base station interprets the received 2 TB to determine that the terminal transmitted data that should have been transmitted as 1 TB as 2 TB.

[0138] FIG. 1 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates data that can be transmitted as 1 TB as 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0139] Referring to FIG. 1, data to be transmitted to a base station, stored in the terminal’s buffer (101), is stored in two HARQ processes (102, 103) managed by the same HARQ process number. At this time, depending on the implementation of the terminal and the rules between the base station and the terminal, the data in the terminal’s buffer (101) may be stored in the two HARQ processes (102, 103), and may be stored in a divided manner, for example. This is merely an example, and the data may be stored in each HARQ process by repeating the storage or through other methods. The upper layer (100) of the terminal may generate a MAC PDU1 (104) based on the data of the first HARQ process (102). The upper layer (100) of the terminal may generate a MAC PDU2 (105) based on the data of the second HARQ process (103). The upper layer (100) of the terminal can generate two TBs (106, 107) using the two generated MAC PDUs (104, 105) respectively, and can transmit them to the physical layer (110) of the terminal (116, 117). The physical layer (110) of the terminal transmits the two TBs (116, 117) transmitted from the upper layer (100) via a scheduled PUSCH (118).

[0140] [Method 2] The upper layer of the terminal can generate a second TB composed of dummy bits and deliver 2 TBs to the physical layer of the terminal. The upper layer of the terminal can generate a single MAC PDU using data within the terminal's buffer and configure the generated MAC PDU into a single TB. Alternatively, the upper layer of the terminal can generate a second MAC PDU using bits composed of dummy bits and configure the MAC PDU generated through the dummy bits into another TB. Subsequently, the upper layer of the terminal delivers the two generated TBs to the physical layer of the terminal.

[0141] The physical layer of the terminal that receives 2 TB transmits a PUSCH consisting of 2 TB to the base station. The physical layer of the base station receives the PUSCH consisting of 2 TB transmitted by the terminal, decodes it, and passes the result to the upper layer of the base station. The upper layer of the base station can verify the received decoding result to confirm that the first TB consists of data and the second TB consists of dummy data. To confirm that the second of the two received TBs consists of dummy data, the upper layer of the base station may refer to subheaders, etc., that can be identified at the MAC layer. For example, a MAC subPDU can be identified from a MAC PDU, and the subheader corresponding to the MAC subPDU may be composed of a new subheader to indicate that the TB is dummy data (for example, it may be composed of a subheader with a new format, or information indicating that the TB is dummy data may be included by using reserved code points or new bits in an existing subheader format). For example, the upper layer of the base station can determine that the TB is configured as a dummy by interpreting the MAC PDU or the MAC subPDU included in the MAC PDU or the subheader of the MAC SDU constituting the MAC subPDU from the second TB received from the terminal, and checking the value indicated in the LCID or eLCID constituting the MAC subheader or MAC cubheader.

[0142] FIG. 2 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 2 TB using data and dummy bits that can be transmitted as 1 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0143] Referring to FIG. 2, data to be transmitted to the base station, stored in the terminal’s buffer (201), is stored in the first HARQ process (202) of the two HARQ processes (202, 203). The upper layer (200) of the terminal can generate MAC PDU1 (204) based on the data from the first HARQ process (202). Since there is no data in the second HARQ process (203), the upper layer (200) of the terminal can generate dummy bits to generate MAC PDU2 (205). The upper layer (200) of the terminal can generate two TBs (206, 207) using the two generated MAC PDUs (204, 205) respectively, and can transmit them to the physical layer (210) of the terminal (216, 217). The physical layer (210) of the terminal transmits the two TBs (216, 217) transmitted from the upper layer (200) via a scheduled PUSCH (218).

[0144] [Method 3] The upper layer of the terminal can generate a second TB padded with zeros and deliver 2 TBs to the physical layer of the terminal. The upper layer of the terminal can generate a single MAC PDU using data within the terminal's buffer and configure the generated MAC PDU into a single TB. Alternatively, the upper layer of the terminal can generate a second MAC PDU using padding bits consisting of zeros (or any other value) and configure the MAC PDU generated through the padding bits into another TB. Subsequently, the upper layer of the terminal delivers the two generated TBs to the physical layer of the terminal.

[0145] The physical layer of the terminal that received 2 TB transmits a PUSCH consisting of 2 TB to the base station. The physical layer of the base station receives the PUSCH consisting of 2 TB transmitted by the terminal, decodes it, and passes the result to the upper layer of the base station. The upper layer of the base station checks the received decoding result to confirm that the first TB is data and the second TB consists of bits padded with zero (or some other value). The upper layer of the base station can determine that the second of the two received TBs consists of padding bits by checking subheaders added by the MAC layer, etc., or by confirming that all values ​​within the TB are zero (or some other single value or an array of other values, etc.).

[0146] FIG. 3 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 2 TB using data and padding bits that can be transmitted as 1 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0147] Referring to FIG. 3, data to be transmitted to the base station, stored in the terminal’s buffer (301), is stored in the first HARQ process (302) of the two HARQ processes (302, 303). The upper layer (300) of the terminal can generate MAC PDU1 (304) based on the data from the first HARQ process (302). Since there is no data in the second HARQ process (303), the upper layer (300) of the terminal can generate MAC PDU2 (305) by generating padding bits consisting of zero (or any other value). The upper layer (300) of the terminal can generate two TBs (306, 307) using the two generated MAC PDUs (304, 305), respectively, and can transmit them to the terminal’s physical layer (310) (316, 317). The physical layer (310) of the terminal transmits the two TBs (316, 317) transmitted from the upper layer (300) via a scheduled PUSCH (318).

[0148] [Method 4] The upper layer of the terminal can divide the data to be transmitted (in half) to create a first TB and a second TB, and deliver the created 2 TBs to the physical layer of the terminal. The upper layer of the terminal can divide the data within the terminal's buffer to create two MAC PDUs. The divided data within the terminal's buffer may be managed by the same HARQ process, or the divided data may be managed by different HARQ processes. In this case, a new upper layer operation of the terminal may be defined to divide the data that should consist of a single TB and to create two MAC PDUs using the divided data. For example, the upper layer of the terminal can divide the data within the buffer in half to create two MAC PDUs. Alternatively, the data may be divided at a specific ratio to create two MAC PDUs, and the specific ratio may be defined in advance so that the base station and the terminal have the same understanding, or the terminal may receive information regarding the specific ratio from the base station in advance via an RRC message, MAC CE, or DCI, etc. Subsequently, the terminal's upper layer generates two TBs based on the two generated MAC PDUs and transmits the generated two TBs to the terminal's physical layer. Upon receiving the 2 TBs, the terminal's physical layer transmits a PUSCH consisting of 2 TBs to the base station. The base station's physical layer receives the PUSCH consisting of 2 TBs transmitted by the terminal, decodes it, and transmits the result to the base station's upper layer. The base station's upper layer must verify that the terminal has split data intended for transmission into 1 TB and transmitted it as 2 TBs. In other words, additional information is required to confirm that the data has been split in order to combine the split data.Therefore, the upper layer of the terminal can configure additional information within the MAC PDU to indicate that data has been split into one TB or both TBs of the 2 TBs, thereby generating two MAC PDUs. For example, a new MAC subheader, a new MAC CE or MAC SDU to indicate whether the data has been split, or a new information format can be added to the MAC PDU. The upper layer of the base station receives and interprets this, and based on this, can confirm that the two MAC PDUs were generated by splitting the data within the terminal's buffer. Subsequently, the base station can merge the two split MAC PDUs into a single data.

[0149] FIG. 4 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal divides data that can be transmitted as 1 TB to create 2 TB, and transmits the created 2 TB through a 2 TB PUSCH composed of layers larger than 4.

[0150] Referring to FIG. 4, data to be transmitted to a base station stored in the terminal’s buffer (401) is stored in the first HARQ process (402) of the two HARQ processes (402, 403) and managed as a single HARQ process. Unlike the example illustrated in FIG. 4, the data stored in the terminal’s buffer (401) may be divided and stored in each of the two HARQ processes (402, 403). The upper layer (400) of the terminal may divide the data stored in the first HARQ process (402) to generate a first MAC PDU1 (404) and a second MAC PDU2 (405). The upper layer (400) of the terminal may generate two TBs (406, 407) using the two generated MAC PDUs (404, 405) respectively, and transmit them to the terminal’s physical layer (410) (416, 417). The physical layer (410) of the terminal transmits the two TBs (416, 417) transmitted from the upper layer (400) via a scheduled PUSCH (418).

[0151] [Method 5] The upper layer of the terminal may repeat the data to be transmitted to generate two TBs and deliver the generated 2 TBs to the physical layer of the terminal. The upper layer of the terminal may repeat the data within the terminal's buffer to generate two MAC PDUs. The repeated data within the terminal's buffer may be managed by the same HARQ process, or the repeated data may be managed by different HARQ processes. In this case, a new upper layer operation of the terminal may be defined to repeat the data that should consist of one TB to generate two MAC PDUs. The upper layer of the terminal generates two TBs based on the two generated MAC PDUs and delivers the two TBs to the physical layer of the terminal. Upon receiving the 2 TBs, the physical layer of the terminal transmits a PUSCH consisting of 2 TBs to the base station. The physical layer of the base station receives the PUSCH consisting of 2 TBs transmitted by the terminal, decodes it, and delivers the result to the upper layer of the base station. The upper layer of the base station must verify that the terminal has repeated data intended for transmission as 1 TB and transmitted it as 2 TB. In other words, additional information confirming that the data has been repeated may be required to combine the repeated data or process it as identical data. For example, the upper layer of the base station can confirm that the two TBs have been repeated by verifying that the received 2 TBs consist of identical bits. Alternatively, the upper layer of the terminal may configure additional information within the MAC PDU to indicate that two MAC PDCUs were generated using repeated data for either one of the 2 TBs or both TBs. For instance, a new MAC subheader, a new MAC CE or MAC SDU to indicate whether the data is repeated, or a new information format may be added to the MAC PDU.The upper layer of the base station receives and interprets this, and based on this, can determine that the two MAC PDUs were generated by repeating the data within the terminal's buffer. Subsequently, the base station can combine the two repeatedly transmitted MAC PDUs into a single data. Alternatively, without combining them, if one MAC PDU is successfully received, the other MAC PDU may be skipped.

[0152] FIG. 5 illustrates an example of an operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal repeats data that can be transmitted as 1 TB to generate 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0153] Referring to FIG. 5, data to be transmitted to a base station, stored in the terminal’s buffer (501), is stored in the first HARQ process (502) of the two HARQ processes (502, 503) and managed as a single HARQ process. Unlike the example illustrated in FIG. 5, the data stored in the terminal’s buffer (501) may be repeated and stored in each of the two HARQ processes (502, 503). The upper layer (500) of the terminal can repeat the data stored in the first HARQ process (502) to generate the first MAC PDU1 (504) and the second MAC PDU2 (505). The upper layer (500) of the terminal can generate two TBs (506, 507) using the two generated MAC PDUs (504, 505) respectively, and can transmit them to the terminal’s physical layer (510) (516, 517). The physical layer (510) of the terminal transmits the two TBs (516, 517) transmitted from the upper layer (500) via a scheduled PUSCH (518).

[0154] In the above-described methods 1 through 5, for some methods (i.e., methods 2 and 3), it was explained that the terminal constructs the first TB using data and constructs the second TB using dummy bits or padding bits, etc. However, the terminal may construct the second TB using data and construct the first TB using dummy bits or padding bits, etc., and may generate the TB with the higher MCS among the two TBs using data. Alternatively, the terminal may generate a TB according to other conditions using data.

[0155] If the above-described Method 2 or Method 3 is supported, there is a characteristic that UL resources are wasted when the terminal transmits a TB in which no data is transmitted. Additionally, when the terminal transmits a PUSCH consisting of 2 TBs, the terminal's power is wasted in transmitting dummy bits or padding bits because the same transmission power is allocated to all layers. To compensate for this, the upper layer of the terminal can inform the terminal's physical layer that 1 TB out of the 2 TBs consists of dummy bits or padding bits rather than data. For example, the terminal's upper layer can add a new bit when configuring the TB to indicate whether the TB consists of dummy bits or padding bits or data. Alternatively, it may be defined so that the terminal's physical layer can implicitly check the bit sequence of the TB to verify that it consists of a specific bit or a specific bit sequence, and identify that the TB consists of dummy bits or padding bits. If the physical layer of the terminal determines that 1 TB out of 2 TBs consists of bits rather than data, the physical layer of the terminal can increase the transmission power for the TB transmitting data (power boost) and decrease the transmission power for the TB transmitting bits rather than data. For example, the terminal transmits 2 TBs via Layer 8 PUSCH, transmitting the first TB transmitting data using Layers 1 through 4, and transmitting the second TB transmitting bits rather than data using Layers 5 through 8. If all TBs transmit data, the transmission power per layer can be determined as P / 8 based on the transmission power P, since the same transmission power is allocated to all layers.However, since 1 TB out of 2 TB transmits bits rather than data, the terminal can reduce the transmission power of that layer and increase the transmission power of the layer transmitting data. For example, the terminal can transmit data through Layers 1 to 4 with a transmission power per layer of P / 4 and transmit data through Layers 5 to 8 with a transmission power per layer of 0 (i.e., the terminal may not transmit data through Layers 5 to 8). Alternatively, the terminal can transmit data through Layers 1 to 4 with a transmission power per layer of 3P / 16 and transmit TB through Layers 5 to 8 with a transmission power per layer of P / 16 (i.e., the terminal can reduce the transmission power per layer of the TB transmitted through Layers 5 to 8 by half). In addition to the examples described above, the terminal can transmit PUSCH by increasing the transmission power of the layer where data is transmitted and decreasing the transmission power of the layer where non-data bits are transmitted, depending on the terminal implementation or predefined rules between the base station and the terminal.

[0156] <Second Embodiment: Method for configuring and transmitting 1 TB transmitted from the upper layer of the terminal into 2 TB at the physical layer>

[0157] In the second embodiment, when only UL data capable of transmitting 1 TB exists in the buffer of the terminal and the upper layer of the terminal generates 1 TB and transmits it to the physical layer of the terminal, a method for transmitting a PUSCH capable of transmitting 2 TB from the physical layer of the terminal to the base station and a method for the base station to receive it are described in detail.

[0158] If only UL data capable of transmitting 1 TB exists in the terminal's buffer, the terminal's upper layer (e.g., MAC layer) can generate 1 TB and deliver it to the terminal's physical layer. That is, even if the base station has scheduled a PUSCH to transmit 2 TB to the terminal, the terminal's upper layer can generate only 1 TB based on the UL data traffic stored in the buffer and deliver it to the terminal's physical layer. As described in the first embodiment, the terminal's physical layer can generate 2 TB from the 1 TB delivered by the terminal's upper layer using the following options to transmit the PUSCH to the base station, in order to transmit the 2 TB PUSCH identical to the information scheduled by the base station.

[0159] [Option 1] The physical layer of the terminal can generate a second TB consisting entirely of zeros (or all dummy bits) to transmit a 2 TB PUSCH to the base station. The upper layer of the terminal that supports UL skipping generates only 1 TB based on the UL traffic stored in the terminal's buffer and does not generate the remaining TB. The upper layer of the terminal delivers the generated 1 TB to the terminal's physical layer. To transmit the 2 TB PUSCH, the terminal's physical layer generates another 1 TB to be transmitted along with the 1 TB delivered from the terminal's upper layer. At this time, the terminal's physical layer generates the TB by configuring all bits within the TB as zeros (or dummy bits). The terminal's physical layer transmits the 2 TB PUSCH based on the 1 TB for transmitting UL data and the 1 TB composed of zero bits (or dummy bits). At this time, the 1 TB for transmitting data can be determined as the first TB of the 2 TBs. Alternatively, 1 TB for data transmission may be determined as the second TB out of 2 TBs. Alternatively, 1 TB for data transmission may be defined as one TB out of 2 TBs determined according to a rule. For example, based on the base station's scheduling information, the TB with the larger MCS indicator value (the larger value among values ​​other than the MCS value for reserved or retransmission, etc.) out of 2 TBs may be determined as the TB for data transmission. Alternatively, based on the base station's scheduling information, the TB with the smaller MCS indicator value out of 2 TBs may be determined as the TB for data transmission.

[0160] The physical layer of the base station can decode a PUSCH consisting of 2 TBs transmitted by the terminal. The physical layer of the base station can verify that only one of the 2 TBs transmitted by the terminal contains data, and the remaining TBs consist of zero bits (or dummy bits). To identify the TBs consisting of zero bits (or dummy bits), specific bits of the TB (the first bit, the last bit, a bit at a certain position, or a bit sequence of a certain length at a certain position) may be configured to indicate whether the TB contains data or contains zero bits (or dummy bits). These bit sequences may be configured similarly to CG-UCI (configured grant-uplink control information), and a field may be added to indicate that they consist of zero bits or dummy bits. Alternatively, the physical layer of the base station may implicitly understand that a TB does not contain data based on the fact that all bits of a certain TB consist of zeros (or a specific bit sequence that can be identified as dummy).

[0161] The physical layer of the base station can decode the PUSCH consisting of 2 TB transmitted by the terminal and pass it to the upper layer of the base station. The upper layer of the base station may also verify that only one TB of the 2 TB contains data and the remaining TB contains zero bits (or dummy bits). The method by which the upper layer of the base station verifies that data is contained only in a specific TB of the 2 TB may be the same as the method by which the physical layer of the base station verifies that data is contained only in a specific TB of the 2 TB.

[0162] FIG. 6 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal generates a second TB composed of zero bits, and transmits the generated 2 TB through a 2 TB PUSCH composed of a layer greater than 4.

[0163] Referring to FIG. 6, data to be transmitted to the base station, stored in the terminal's buffer (601), is stored in the first HARQ process (602). The second HARQ process is not used. The upper layer (600) of the terminal can generate a MAC PDU1 (604) based on the data from the first HARQ process (602). The upper layer (600) of the terminal can generate a TB (606) using the generated MAC PDU1 (604) and transmit it to the terminal's physical layer (610) (616).

[0164] The physical layer (610) of the terminal can generate additional zero bits to create a second TB (617) in which all bits within the TB are zero bits. The physical layer (610) of the terminal transmits the first TB (616) transmitted from the upper layer (600) and the second TB (616) in which all bits generated by the physical layer (610) are zero bits via a scheduled PUSCH (618). This is just one example, and the TB to transmit data may be determined as the second TB (617). Additionally, the physical layer (610) may generate the second TB by configuring it with dummy bits instead of zero bits.

[0165] [Option 2] The physical layer of the terminal divides the 1 TB delivered by the upper layer (e.g., MAC layer) to create 2 TB and transmits the 2 TB PUSCH to the base station. The upper layer of the terminal that supports UL skipping creates only 1 TB based on the UL traffic stored in the terminal's buffer and does not create the remaining TB. The upper layer of the terminal delivers the created 1 TB to the physical layer of the terminal. The physical layer of the terminal divides the TB delivered by the upper layer of the terminal to transmit the 2 TB PUSCH. The physical layer of the terminal transmits 1 TB containing a portion of the TB delivered by the upper layer and another 1 TB containing the remainder of the TB delivered by the upper layer via the 2 TB PUSCH. At this time, a new physical layer operation of the terminal may be defined to divide one TB and create two TBs using the divided TB. For example, the physical layer of the terminal can divide the TB transmitted from the terminal's upper layer in half to create two new TBs. Alternatively, the terminal can divide the TB at a specific ratio to create two new TBs, and the specific ratio may be predefined so that the base station and the terminal have the same understanding, or the terminal may receive information regarding the specific ratio from the base station in advance via an RRC message, MAC, or DCI, etc. For example, the terminal (or the terminal's physical layer) can divide the TB transmitted from the terminal's upper layer in proportion to the size of the two scheduled TBs. The terminal's physical layer can manage the 2 TBs created based on the 1 TB transmitted from the upper layer with their respective HARQ process IDs.That is, the terminal can assign a HARQ process ID to each generated TB and store it in the terminal's physical layer buffer, and support retransmission for the TB requested by the base station using the HARQ process ID corresponding to each TB. Alternatively, the terminal's physical layer may manage 2 TBs generated based on 1 TB transmitted from the upper layer using a single HARQ process ID. If the base station requests retransmission for any TB, the terminal can regenerate the TB requested by the base station using the information stored in the single HARQ process ID, or load the TB stored in the buffer and retransmit it to the base station.

[0166] The physical layer of the base station can decode a PUSCH consisting of 2 TB transmitted by the terminal. The physical layer of the base station can verify that the 2 TB of data transmitted by the terminal was split from 1 TB. To verify that the 2 TB of data transmitted by the terminal was split from 1 TB, a certain N-bit sequence (where N represents the length of the bit sequence used to identify the split) may be added to the two TBs transmitted by the terminal. The physical layer of the base station can verify that the two TBs consist of split data by interpreting a specific bit sequence (e.g., the first N bits within the TB or the last N bits within the TB) in either one TB (e.g., the first TB or the second TB) or both TBs transmitted by the terminal. This bit sequence may be configured similarly to CG-UCI (configured grant-uplink control information), and a field may be added to indicate that the 2 TBs were generated by splitting.

[0167] Alternatively, the physical layer of the base station may decode the PUSCH consisting of 2 TB transmitted by the terminal and forward it to the upper layer of the base station. The upper layer of the base station may also verify that the received 2 TB consists of fragmented data. The method by which the upper layer of the base station verifies that the 2 TB consists of fragmented data may be the same as the method by which the physical layer of the base station verifies that the 2 TB consists of fragmented data.

[0168] FIG. 7 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal divides the 1 TB data transmitted from the upper layer to generate 2 TB, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0169] Referring to FIG. 7, data to be transmitted to the base station, stored in the terminal's buffer (701), is stored in the first HARQ process (702). The second HARQ process is not used. The upper layer (700) of the terminal can generate a MAC PDU1 (704) based on the data from the first HARQ process (702). The upper layer (700) of the terminal can generate a TB (706) using the generated MAC PDU1 (704) and transmit it to the terminal's physical layer (710).

[0170] The physical layer (710) of the terminal divides the 1 TB (706) transmitted from the upper layer (700) of the terminal to create two TBs (716, 717) each consisting of half of the data. Dividing the 1 TB (706) in half is just one example, and it may be divided equally, divided proportionally to the size of each TB, divided according to a predefined rule, or divided by a method determined based on an RRC message received from the base station or DCI. The physical layer (710) of the terminal transmits the two TBs (716, 717) created by dividing the 1 TB (706) transmitted from the upper layer (700) via a scheduled PUSCH (718).

[0171] If you use [Option 2] to divide 1 TB of data to create 2 TB, the data coding rate will decrease (meaning that more resources are used to transmit the data), and reliability can be improved.

[0172] [Option 3] The terminal's physical layer repeats the 1 TB delivered by the upper layer (e.g., MAC layer) to generate 2 TB and transmits the 2 TB PUSCH to the base station. The terminal's upper layer, which supports UL skipping, generates only 1 TB based on the UL traffic stored in the terminal's buffer and does not generate the remaining TB. The terminal's upper layer delivers the generated 1 TB to the terminal's physical layer. The terminal's physical layer can repeat the TB delivered by the terminal's upper layer to generate 2 TB in order to transmit the 2 TB PUSCH. The terminal's physical layer generates the first TB using the TB delivered from the upper layer and generates the second TB using the TB delivered from the same upper layer. The terminal repeats the 1 TB delivered from the terminal's upper layer to generate 2 TB and transmits it via the scheduled 2 TB PUSCH. At this time, a new physical layer operation of the terminal can be defined to generate two TBs by repeating one TB. For example, if the sizes of the two TBs scheduled by the base station are the same, the physical layer of the terminal can configure 2 TBs to transmit a 2 TB PUSCH by repeating the 1 TB delivered by the upper layer. Alternatively, without additional constraints, the physical layer of the terminal can configure 2 TBs to transmit a 2 TB PUSCH by repeating the 1 TB delivered by the upper layer. As another example, when the physical layer of the terminal generates 2 TBs by repeating the 1 TB delivered from the upper layer, it can generate 2 TBs using the same RV (redundancy version). In this case, among the RV fields for each TB of the DCI scheduling the 2 TB PUSCH, the RV field for the first TB may be referenced.Alternatively, among the RV fields for each TB of the DCI scheduling the 2 TB PUSCH, the RV field for the second TB may be referenced. Or, when the physical layer of the terminal constructs 2 TB by repeating the 1 TB transmitted from the upper layer, it may generate 2 TB using the same or different RVs by referencing the RV fields for each TB of the DCI scheduling the 2 TB PUSCH. The physical layer of the terminal may manage the 2 TB generated based on the 1 TB transmitted from the upper layer with individual HARQ process IDs. That is, each HARQ process ID may be assigned to each TB, stored in the physical layer buffer of the terminal, and retransmission for the TB requested by the base station may be supported using the HARQ process ID corresponding to each TB. Alternatively, the physical layer of the terminal may manage the 2 TB generated based on the 1 TB transmitted from the upper layer with a single HARQ process ID. If a base station requests retransmission for a TB, the information stored in a single HARQ process ID can be used to regenerate the TB for which the base station requested retransmission, or to load the TB stored in the buffer and retransmit it to the base station.

[0173] The physical layer of the base station can decode a PUSCH consisting of 2 TB transmitted by the terminal. The physical layer of the base station can verify that the 2 TB of data transmitted by the terminal consists of 1 TB repeated. To verify that the 2 TB of data transmitted by the terminal consists of 1 TB repeated, the physical layer of the base station may add an N-bit sequence (where N represents the length of the bit sequence used to identify repeated transmission) to the two TBs transmitted by the terminal. The physical layer of the base station can verify that the two TBs consist of identically repeated data by interpreting a specific bit sequence (e.g., the first N bits within the TB or the last N bits within the TB) in either one TB (e.g., the first TB or the second TB) or both TBs transmitted by the terminal. This bit sequence may be configured similarly to CG-UCI (configured grant-uplink control information), and a field may be added to indicate that the 2 TBs were generated repeatedly. Or, if 2 TB is generated using the same RV, the physical layer of the base station can determine that TB of the same RV has been transmitted by comparing the bit sequence of the decoded 2 TB.

[0174] Alternatively, the physical layer of the base station may decode the PUSCH consisting of 2 TB transmitted by the terminal and forward it to the upper layer of the base station. The upper layer of the base station may also verify that the received 2 TB consists of identically repeated data. The method by which the upper layer of the base station verifies that the 2 TB consists of identically repeated data may be the same as the method by which the physical layer of the base station determines that the 2 TB consists of identically repeated data.

[0175] FIG. 8 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, a physical layer of the terminal generates 2 TB by repeating the 1 TB data transmitted from the upper layer, and transmits the generated 2 TB through a 2 TB PUSCH composed of layers greater than 4.

[0176] Data to be transmitted to the base station, stored in the terminal's buffer (801), is stored in the first HARQ process (802). The second HARQ process is not used. The terminal's upper layer (800) can generate a MAC PDU1 (804) based on the data from the first HARQ process (802). The terminal's upper layer (800) can generate one TB (806) using the generated MAC PDU1 (804) and transmit it to the terminal's physical layer (810). The terminal's physical layer (810) repeats the 1 TB (806) transmitted from the terminal's upper layer (800) to generate two TBs (816, 817). At this time, the two TBs (816, 817) generated by repetition may be generated using the same RV or may be generated using different RVs. The physical layer (810) of the terminal repeats the 1 TB (806) transmitted from the upper layer (800) to generate two TBs (816, 817) via scheduled PUSCH (818).

[0177] If 1 TB of data is repeated to generate 2 TB using [Option 3], all data from the terminal can be received even if combining is performed due to repeated transmission or only one of the TBs is successfully received, so reliability performance gains due to diversity and / or combining can be expected. Alternatively, if the base station detects that 1 TB is being transmitted as a repetition of 2 TB and successfully receives one of the TBs, the complexity of base station operation or base station energy can be reduced by not receiving (or decoding) the remaining TB.

[0178] <Third Embodiment: Method for transferring a PUSCH scheduled for 2 TB to 1 TB>

[0179] In the third embodiment, when only UL data capable of transmitting 1 TB exists in the buffer of the terminal and the upper layer of the terminal generates 1 TB and transmits it to the physical layer of the terminal, the method of transmitting using only the PUSCH resource capable of transmitting 1 TB among the scheduled PUSCH resources capable of transmitting 2 TB at the physical layer of the terminal, and the method of the base station receiving it are described in detail.

[0180] If only UL data capable of transmitting 1 TB exists in the terminal's buffer, the terminal's upper layer (e.g., MAC layer) can generate 1 TB and deliver it to the terminal's physical layer. That is, even if the base station has scheduled a PUSCH to transmit 2 TB to the terminal, the terminal's upper layer can generate only 1 TB based on the UL data traffic stored in the buffer and deliver it to the terminal's physical layer. Unlike what was described in the first and second embodiments, the terminal's physical layer can transmit a 1 TB PUSCH instead of a 2 TB PUSCH, unlike the information scheduled by the base station.

[0181] FIG. 9 illustrates an example of operation in which, according to one embodiment of the present disclosure, an upper layer of a terminal generates 1 TB using data that can be transmitted as 1 TB, and the physical layer of the terminal transmits only the 1 TB transmitted from the upper layer using only a portion of a 2 TB PUSCH composed of layers greater than 4.

[0182] Referring to FIG. 9, data to be transmitted to the base station, stored in the terminal's buffer (901), is stored in the first HARQ process (902). The second HARQ process is not used. The upper layer (900) of the terminal can generate a MAC PDU1 (904) based on the data from the first HARQ process (902). The upper layer (900) of the terminal can generate a TB (906) using the generated MAC PDU1 (904) and transmit it to the terminal's physical layer (910).

[0183] The physical layer (910) of the terminal generates 1 TB (916) using the 1 TB (906) transmitted by the upper layer (900) of the terminal. At this time, the physical layer (910) of the terminal does not generate any additional TB. The physical layer (910) of the terminal transmits 1 TB using only some of the resources (i.e., some layers) of the PUSCH resources scheduled by the base station to transmit 2 TB (918).

[0184] That is, the physical layer of the terminal can transmit a PUSCH consisting of the same number of TBs as the number of TBs transmitted from the upper layer of the terminal, and when 1 TB is transmitted from the upper layer of the terminal to the physical layer of the terminal, the terminal can transmit a 1 TB PUSCH using the PUSCH transmission information scheduled by the base station and the following additional method.

[0185] [Additional Method 1] The terminal's physical layer transmits the TB received from the terminal's upper layer using one of the two TBs, and transmits zero-modulated symbols (hereinafter zero-modulated symbols) for the remaining TB so that no information is transmitted. For example, the terminal's physical layer may transmit the TB received from the upper layer as the first TB and transmit the second TB including zero-modulated symbols. If a PUSCH of the M+N layer (where the sum of M and N is greater than 4 and less than or equal to 8, and M and N are greater than or equal to 2 and less than or equal to 4, and M is less than or equal to N) is scheduled, the terminal transmits the first TB through the first M layer and the second TB through the remaining N layer. The transmission signal of the M+N layer transmitted by the terminal's physical layer It can be represented as follows.

[0186] [Mathematical Formula 1]

[0187]

[0188] Here, the superscript T signifies the transpose operation, so represents the column vector. Transmission signal The first M components are modulated symbols with a modulation order scheduled by the base station and are non-zero values. On the other hand, the transmitted signal Since the remaining N components have a value of 0, the actual terminal does not perform UL transmission through the remaining N layers. If the terminal supports codebook-based PUSCH transmission, the signal transmitted as shown in the following [Equation 2] It can represent.

[0189] [Mathematical Formula 2]

[0190]

[0191] Here Is Meaning the nth antenna port is the maximum number of ports of the terminal. For example, can be defined as 8. represents an uplink precoder for transmitting M+N layers, and the terminal selects and applies the precoder by referring to the TPMI field of the DCI that schedules PUSCH (referring to the 'Precoding information and number of layers' field included in DCI format 0_1 ​​of TS 38.212). According to [Equation 2], Since the first M columns are multiplied by the non-zero y component, the terminal transmits to each antenna port It is included in. On the other hand, Since the N columns are multiplied by the y component which is 0, they become 0, so the terminal transmits to each antenna port It is not included in. Therefore, the terminal can be configured to transmit data corresponding to 1 TB transmitted from the upper layer by mapping it to a non-zero y component and to set the transmission symbols of the remaining TB to 0 so that no information is transmitted.

[0192] [Mathematical Formula 2] If we look at it, to fix the norm of the entire precoding matrix to 1, each column It can be divided into. Here is the number of non-zero coefficients in the precoder column corresponding to each layer (i.e., It can be expressed as the product of the number of coefficients having non-zero values ​​and the total number of layers (i.e., M+N). In this case, since information is not actually transmitted through N layers out of the M+N layers, if the terminal When transmitting PUSCH using a precoder normalized to, compared to the actual transmitted power The PUSCH is transmitted with the power of . Therefore, the terminal Instead of normalizing to Larger It is possible to transmit by normalizing to a value less than or equal to boosting the transmission power of the layer that actually transmits.

[0193] FIG. 10 illustrates an example of a method for transmitting only 1 TB composed of 2 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

[0194] Referring to FIG. 10, the base station can schedule a codebook-based PUSCH consisting of 5 layers to the terminal, and the base station can instruct the terminal to an 8 Tx-based 5-layer partial coherent precoder (1001). Each column of the partial coherent precoder for 5-layer transmission represents a precoder vector for each layer, and a marked (colored) square represents a non-zero coefficient, and an unmarked (uncolored) square represents a zero coefficient. That is, the precoder vector of each layer consists of two non-zero coefficients, and the terminal can coherently transmit a UL signal (1011) using an antenna port corresponding to the two non-zero coefficients. The UL signal (1011) transmitted by the terminal consists of a 2-layer (1012) where data is transmitted and a symbol (1013) modulated to zero. The terminal multiplies the UL signal (1011) to be transmitted by the precoder (1001) instructed by the base station and transmits the transmission signal to each antenna port. It can be calculated, and the terminal transmits a signal (1012) with a non-zero coefficient through a signal multiplied by a precoder (1002) for the first two layers, and the precoder (1003) for the remaining three layers is not transmitted because it is multiplied by 0.

[0195] [Additional Method 2] The physical layer of the terminal uses only one of the 2 TBs to transmit the TB received from the terminal's upper layer, and does not transmit the remaining TB. Unlike what was described above in [Additional Method 1], [Additional Method 2] omits the layer corresponding to the second TB and applies only the precoder for transmitting the first TB among the precoders for transmitting the 2 TBs instructed by the base station, while ignoring the precoder for transmitting the second TB. As shown in the following [Equation 3], the terminal configures only the M layer for the actual data to be transmitted to the transmission signal You can prepare.

[0196] [Mathematical Formula 3]

[0197]

[0198] Unlike [Equation 1], only the non-zero coefficient y, which is actually transmitted, constitutes the transmission signal, and the layer corresponding to TB, which is not actually transmitted, is ignored. If the terminal supports codebook-based PUSCH transmission, the signal transmitted as shown in the following [Equation 4] It can represent.

[0199] [Mathematical Formula 4]

[0200]

[0201] The precoder indicated by the TPMI field within the DCI scheduling PUSCH as described in [Additional Method 1] It refers to a subset of precoders composed solely of the precoder vectors of the layer where TB is transmitted for data transmission. In other words, It consists of M+N columns It can be defined as a matrix composed of the first M columns. If [Equation 2] The precoder for the first M column of and [Equation 4] If is identical and the non-zero component of the transmitted signal y is identical, the signal transmitted by the terminal is identical. The value for normalizing the precorder at is the number of non-zero coefficients in the precoder column corresponding to each layer, identical to what was explained in [Mathematical Equation 1] (i.e., It can be defined as the product of the number of coefficients (which have non-zero values) and the total number of layers (i.e., M+N). Alternatively, considering only the actual number of transmitted layers. may also be defined as the product of the number of non-zero coefficients in the precoder column corresponding to the transmitting layer and the number of transmitting layers (i.e., M). Or silver Larger It may also be defined as a value less than or equal to.

[0202] FIG. 11 illustrates an example of a method for transmitting only 1 TB composed of 2 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

[0203] Referring to FIG. 11, the base station can schedule a codebook-based PUSCH consisting of 8 Tx-based 5 layers to the terminal, and the base station can instruct the terminal to an 8 Tx-based 5-layer partial coherent precoder (1101). Each column of the partial coherent precoder for 5-layer transmission represents a precoder vector for each layer, and a marked (colored) square represents a non-zero coefficient, and an unmarked (uncolored) square represents a zero coefficient. That is, the precoder vector of each layer consists of two non-zero coefficients, and the terminal can coherently transmit a UL signal (1111) using an antenna port corresponding to the two non-zero coefficients. The UL signal (1111) transmitted by the terminal consists only of 2 layers (1112) where data is transmitted. The terminal can calculate the transmission signal to be transmitted to each antenna port by multiplying only the part (1102) corresponding to layer 2 of the precoder (1101) instructed by the base station by the UL signal (1111) to be transmitted, and the terminal transmits the UL signal (1111) through the signal multiplied by the precoder (1102) for the first 2 layers.

[0204] [Additional Method 3] If the upper layer of the terminal transmits only one TB out of 2 TB to the physical layer of the terminal, the physical layer of the terminal can transmit the 1 TB transmitted from the upper layer using the maximum number of layers (e.g., 4 layers) capable of transmitting 1 TB. Below, the maximum number of layers capable of transmitting 1 TB is described using 4 as an example, but the maximum number of layers capable of transmitting 1 TB may be changed.

[0205] According to [Additional Method 3], the terminal can transmit 1 TB delivered from the upper layer using Layer 4, even if the layer of the PUSCH for transmitting 2 TB is scheduled to be Layer 5, 6, or 7. This is different from the operation of transmitting the first TB using Layer 2 for a PUSCH scheduled to Layer 5, or transmitting the first TB using Layer 3 for a PUSCH scheduled to Layer 6 or 7, so that the terminal can transmit the first TB using Layer 4. Furthermore, the terminal does not perform transmission using any remaining scheduled layers other than the layer used to transmit the first TB. [Additional Method 3] may be available under specific conditions, or the terminal may transmit 1 TB using Layer 4 under the assumption of specific conditions. As an example of a specific condition, if the terminal is scheduled with 2 TB of PUSCH scheduled by the base station with the same MCS field (or / and NDI field or / and RV field) and the terminal's upper layer transmits only 1 TB, the terminal can transmit 1 TB through the Layer 4 PUSCH according to [Additional Method 3]. Alternatively, if the terminal is scheduled with 2 TB by the base station but the terminal's upper layer transmits only 1 TB, the terminal's physical layer determines the MCS by referring to the scheduling information for one of the 2 TBs (i.e., the scheduling information for the first TB or the scheduling information for the second TB) and uses this to generate TB that can be transmitted using Layer 4. The physical layer of the terminal maps the TB that can be transmitted to the 4th layer using the calculated 4th layer, and applies a precoder matrix consisting of the first 4 columns for transmitting the 4th layer among the precoders scheduled by the base station to transmit the 4th layer 1 TB PUSCH to the base station.

[0206] FIG. 12 illustrates an example of a method for reconstructing and transmitting a TB to be transmitted in 2 layers into 1 TB composed of 4 layers using a precoder indicated for 5-layer transmission according to one embodiment of the present disclosure.

[0207] Referring to FIG. 12, the base station can schedule a codebook-based PUSCH consisting of 8 Tx-based 5 layers to the terminal, and the base station can instruct the terminal to an 8 Tx-based 5-layer partial coherent precoder (1201). Each column of the partial coherent precoder for 5-layer transmission represents a precoder vector for each layer, and a marked (colored) square represents a non-zero coefficient, while an unmarked (uncolored) square represents a zero coefficient. That is, the precoder vector of each layer consists of two non-zero coefficients, and the terminal can coherently transmit a UL signal (1211) using an antenna port corresponding to the two non-zero coefficients. The UL signal (1211) transmitted by the terminal can be configured so that 1 TB transmitted via layer 2 is regenerated by the terminal's physical layer into 1 TB transmitted via layer 4, allowing it to be transmitted via layer 4 (1212). The terminal can calculate the transmission signal to be transmitted to each antenna port by multiplying only the part (1202) corresponding to the 4th layer of the precoder (1201) instructed by the base station by the UL signal (1211) to be transmitted, and the terminal transmits the UL signal (1211) through the signal multiplied by the precoder (1202) for the first 4 layers.

[0208] In the aforementioned [Additional Method 1], [Additional Method 2], or [Additional Method 3], a method was described in which the physical layer of the terminal transmits PUSCH using the precoder vector for the first M or the first 4 layers among the precoders for the M+N layers scheduled by the base station. However, considering coherent antenna groups, a column may be selected to transmit to different antenna groups, or PUSCH may be transmitted using the precoder vector for the last M or 4 layers instead of the precoder vector for the first M or 4 layers.

[0209] <Fourth Embodiment: Method to eliminate ambiguity in terminal operation by performing UL skipping according to conditions>

[0210] In the fourth embodiment, a method for eliminating the ambiguity of the terminal operation described above is specifically explained by defining that UL skipping is performed when additional conditions are satisfied.

[0211] As described above, if the upper layer of the terminal has RRC parameters (enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured, or skipUplinkTxDynamic) set and there is no UCI, aperiodic CSI, or UL data (MAC SDU or MAC PDU) transmitted via the corresponding PUSCH, the terminal may perform UL skipping, that is, not transmit the PUSCH. Additionally, the terminal may determine whether to perform UL skipping by considering the following additional conditions.

[0212] [Table 10]

[0213]

[0214] [Table 11]

[0215]

[0216] As described above, if the base station schedules a PUSCH to transmit 2 TB, the terminal may not perform UL skipping.

[0217] Alternatively, you may define UL skipping to be performed only when the terminal does not transmit all 2 TB as follows.

[0218] [Table 12]

[0219]

[0220] [Table 13]

[0221]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1. In the method of the terminal, A step of receiving two uplink grants from a base station via a PDCCH (physical downlink control channel) that schedules a first TB (transport block) and a second TB; A step of generating a first MAC PDU (medium access control protocol data unit) based on data from a first HARQ (hybrid automatic repeat request) process and generating a second MAC PDU based on data from a second HARQ process; A step of generating a first TB based on the first MAC PDU and generating a second TB based on the second MAC PDU; A method characterized by including the step of transmitting the first TB and the second TB to the base station via PUSCH (physical uplink shared channel).

2. In Paragraph 1, Data within the buffer of the above terminal is divided and stored in the first HARQ process and the second HARQ process, or is repeatedly stored in the first HARQ process and the second HARQ process, and The above 2nd TB is: zero padding bit, or dummy bit A method characterized by being composed of values ​​other than .

3. In Paragraph 1, The data in the buffer of the above terminal is stored in the first HARQ process, and A method characterized in that the above-mentioned second TB is composed of dummy bits or zero padding bits.

4. In Paragraph 1, The upper layer of the above terminal instructs the physical layer of the above terminal whether the second TB is composed of zero padding bits or dummy bits, and A method characterized by reducing the transmission power for the second TB when the second TB is composed of zero padding bits or dummy bits.

5. Regarding the base station method, The step of transmitting two uplink grants to a terminal via a physical downlink control channel (PDCCH) that schedules a first TB (transport block) and a second TB; and The method includes the step of receiving the first TB and the second TB from the terminal via a PUSCH (physical uplink shared channel), The above first TB is based on the first MAC PDU, and the above second TB is based on the second MAC PDU, and A method characterized in that the first MAC PDU is based on data from a first HARQ (hybrid automatic repeat request) process, and the second MAC PDU is based on data from a second HARQ process.

6. In Paragraph 5, Data within the buffer of the above terminal is divided and stored in the first HARQ process and the second HARQ process, or is repeatedly stored in the first HARQ process and the second HARQ process, and The above 2nd TB is: zero padding bit, or dummy bit A method characterized by being composed of values ​​other than .

7. In Paragraph 5, The data in the buffer of the above terminal is stored in the first HARQ process, and A method characterized in that the above-mentioned second TB is composed of dummy bits or zero padding bits.

8. In Paragraph 5, The upper layer of the above terminal instructs the physical layer of the above terminal whether the second TB is composed of zero padding bits or dummy bits, and A method characterized by reducing the transmission power for the second TB when the second TB is composed of zero padding bits or dummy bits.

9. Regarding the terminal, Transmitter / receiver; and Receive two uplink grants from the base station via a PDCCH (physical downlink control channel) that schedules the first TB (transport block) and the second TB, and A first MAC PDU (medium access control protocol data unit) is generated based on data from a first HARQ (hybrid automatic repeat request) process, and a second MAC PDU is generated based on data from a second HARQ process. A first TB is generated based on the first MAC PDU, and a second TB is generated based on the second MAC PDU, and A terminal characterized by including a control unit configured to transmit the first TB and the second TB to the base station via a PUSCH (physical uplink shared channel).

10. In Paragraph 9, Data within the buffer of the above terminal is divided and stored in the first HARQ process and the second HARQ process, or is repeatedly stored in the first HARQ process and the second HARQ process, and The above 2nd TB is: zero padding bit, or dummy bit A terminal characterized by being composed of a value other than 11. In Paragraph 9, The data in the buffer of the above terminal is stored in the first HARQ process, and A terminal characterized in that the above-mentioned second TB is composed of dummy bits or zero padding bits.

12. In Paragraph 9, The upper layer of the above terminal instructs the physical layer of the above terminal whether the second TB is composed of zero padding bits or dummy bits, and A terminal characterized by reducing transmission power for the second TB when the second TB is composed of zero padding bits or dummy bits.

13. Regarding base stations, Transmitter / receiver; and To the terminal, transmit two uplink grants via a PDCCH (physical downlink control channel) scheduling the first TB (transport block) and the second TB, and It includes a control unit configured to receive the first TB and the second TB from the terminal via a PUSCH (physical uplink shared channel), The above first TB is based on the first MAC PDU, and the above second TB is based on the second MAC PDU, and A base station characterized in that the first MAC PDU is based on data from a first HARQ (hybrid automatic repeat request) process, and the second MAC PDU is based on data from a second HARQ process.

14. In Paragraph 13, Data within the buffer of the above terminal is divided and stored in the first HARQ process and the second HARQ process, or is repeatedly stored in the first HARQ process and the second HARQ process, and The above 2nd TB is: zero padding bit, or dummy bit A base station characterized by being composed of values ​​other than .

15. In Paragraph 13, The data in the buffer of the above terminal is stored in the first HARQ process, and A base station characterized in that the above-mentioned second TB is composed of dummy bits or zero padding bits.

Images