Method and apparatus for data transmission and reception in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system, the method including receiving higher layer signaling from a base station, the higher layer signaling including information enabling multiplexing of first Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information, receiving first Downlink Control Information (DCI) from the base station, the first DCI schedules a physical uplink shared channel (PUSCH) repetition, after the first DCI, receives a second DCI indicating a physical uplink control channel (PUCCH) from the base station, and transmits the first HARQ-ACK information to the base station by multiplexing the first HARQ-ACK information on at least one PUSCH repetition other than the first PUSCH repetition among the PUSCH repetition.

Description

TECHNICAL FIELD

[0001] The disclosure relates to operations of a terminal and a base station in a wireless communication system. More particularly, the disclosure relates to a method for configuring and reporting data in a wireless communication system and a device capable of performing the method. BACKGROUND

[0002] 5G mobile communication technologies define wide frequency bands so that high transmission rates and new services are possible, and are implemented not only in "Sub 6 GHz" bands but also in "Above 6 GHz" bands (mmWave). Also, 6G mobile communication technologies are being discussed, which are implemented in Terahertz bands of 95 GHz to 3 MHz.

[0003] At the time when the development of 5G mobile communication technologies is in progress, there are ongoing standardization efforts regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, support of numerology (for example, operation of multiple subcarrier spacings) for effective utilization of mmWave resources and time slots, initial access technologies for supporting multi-beam transmission and wide bands, definition and operation of BWP (Band Width Part), new channel coding method (such as a LDPC (Low Density Parity Check) code for large amounts of data transmission and a polar code for highly reliable transmission of control information), L2 pre-processing, and network slicing for providing a dedicated network specialized to specific services.

[0004] At present, in view of services to be supported by 5G mobile communication technologies, discussions are in progress regarding improvement and performance enhancement of initial 5G mobile communication technologies, and there are ongoing standardization efforts regarding physical layer technologies such as V2X (Vehicle-to-everything) for assisting autonomous vehicles in driving determination based on information about positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aiming to comply with various regulation-related requirements for system operation in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) that is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] Further, there has been ongoing standardization in the air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying a random access procedure in the 5G mobile communication system. There has also been ongoing standardization of a system architecture / service for combination of Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies (e.g., service-based architecture or service-based interface) and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As the 5G mobile communication system is commercialized, connected devices, which have increased exponentially, will be connected to the communication network, and accordingly, it is expected that enhanced functionality and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, new research related to extended reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), and the like, 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication is planned.

[0007] Further, such development of the 5G mobile communication system will serve as a basis not only for developing, as a new waveform for providing coverage in a terahertz band for 6G mobile communication technology, a multi-antenna transmission technology such as Full Dimensional MIMO (FD-MIMO), array antenna, and massive MIMO, a lens and an antenna based on metamaterial for improving coverage of terahertz band signals, a high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also for developing, for improving frequency efficiency of 6G mobile communication technology and improving a system network, a full-duplex technology, an AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from a design stage and internalizing end-to-end AI support functions, and a next-generation distributed computing technology for implementing services by utilizing super-high-performance communication and computing resources at a complexity level exceeding the limitation of UE operating capability.

[0008] As the above-described wireless communication system advances, various services are implemented, and thus a method capable of smoothly providing the services is required.

[0009] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether the above information constitutes prior art. SUMMARY

[0010] SOLUTION TO PROBLEM

[0011] The disclosure relates to a wireless communication network, and in particular, to a terminal in a wireless communication system and a communication method thereof.

[0012] According to an aspect of the disclosure, there is provided a method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving, from a base station, a higher layer signaling including information for enabling multiplexing of first hybrid automatic repeat request acknowledgement (HARQ-ACK) information; receiving, from the base station, a first downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) repetition; after receiving the first DCI, receiving, from the base station, a second downlink control information (DCI) indicating a physical uplink control channel (PUCCH); and transmitting, to the base station, the first HARQ-ACK information by multiplexing the first HARQ-ACK information on at least one of the PUSCH repetitions other than a first PUSCH repetition among the PUSCH repetitions.

[0013] ADVANTAGEOUS EFFECTS OF THE INVENTION

[0014] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method of implementing efficient communication in a wireless communication system. BRIEF DESCRIPTION OF DRAWINGS

[0015] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0016] Figure 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to an embodiment of the disclosure;

[0017] Figure 2 is a diagram illustrating a structure of a frame, a subframe, and a slot in a wireless communication system according to an embodiment of the disclosure;

[0018] Figure 3 is a diagram illustrating a physical uplink shared channel (PUSCH) repetition transmission type B in a wireless communication system according to an embodiment of the disclosure;

[0019] Figure 4 is a diagram illustrating a method of aperiodic channel state information (CSI) reporting according to an embodiment of the disclosure;

[0020] Figure 5A 、 Figure 5B and Figure 5CFIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0021] Figure 6 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0022] Figure 7 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0023] Figure 8 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0024] Figure 9 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0025] Figure 10 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0026] Figure 11 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure;

[0027] Figure 12 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure; and

[0028] Figure 13 FIG. 1 illustrates mapping uplink control information to a physical uplink shared channel (PUSCH) according to various embodiments of the disclosure.

[0029] In all the drawings, the same reference denotations will be employed for the same elements throughout the several views. DETAILED DESCRIPTION

[0030] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal in a wireless communication system and a communication method thereof.

[0031] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal in a wireless communication system and a communication method thereof.

[0032] Another aspect of the present disclosure is to provide a method for configuring and reporting data in a wireless communication system and a device capable of performing the method according to an embodiment of the present disclosure.

[0033] Another aspect of the present disclosure is to provide a device and method capable of efficiently providing a service in a mobile communication system.

[0034] Additional aspects will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the description and / or the drawings, or can be learned by practice of the presented embodiments.

[0035] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the present disclosure.

[0036] Inventive Modes

[0037] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those skilled in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions can be omitted for clarity and conciseness.

[0038] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0039] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0040] In describing embodiments of the present disclosure, descriptions related to technical contents well-known in the related art and not directly related to the present disclosure will be omitted. Omission of such unnecessary descriptions is intended to prevent obscuring the main idea of the present disclosure and to more clearly convey the main idea.

[0041] For the same reason, in the drawings, some elements can be exaggerated, omitted, or schematically shown. In addition, the size of each element does not completely reflect the actual size. In the corresponding drawings, the same or corresponding elements have the same or corresponding reference numerals.

[0042] The advantages and features of the present disclosure and a method for achieving the advantages and features will become apparent from the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various forms. The embodiments are provided only to completely disclose the present disclosure and to fully enable the scope of the present disclosure to those skilled in the art, the scope of the present disclosure being defined only by the scope of the claims. Throughout the specification, like or similar components are denoted by like or similar reference numerals. Also, in describing the present disclosure, if it is determined that detailed description of known functions or configurations makes the subject matter of the present disclosure unnecessarily unclear, the detailed description will be omitted. The terms to be described below are terms defined based on functions in the present disclosure, and can be different depending on the user, the user's intention, or the usage habit. Therefore, the definition of the terms should be understood based on the overall content of the specification.

[0043] In the following description, a base station is an entity that allocates resources to a terminal, and can be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a network node. The terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, "downlink (DL)" refers to a radio link used for a base station to transmit a signal to a terminal, and "uplink (UL)" refers to a radio link used for a terminal to transmit a signal to a base station. Also, in the following description, an example of a long term evolution (LTE) or an LTE-Advanced (LTE-A) system is explained, but embodiments of the present disclosure are also applicable to other communication systems similar to the technical background or channel type of the present disclosure. Examples of such communication systems include a fifth generation mobile communication technology (5G, new radio, NR) developed on the basis of LTE-A, and in the present description, "5G" encompasses the concept of existing LTE, LTE-A, and other similar services. Also, those skilled in the art can apply the present disclosure to other communication systems by appropriate modification without departing from the scope of the present disclosure.

[0044] It should be understood that each of the blocks of the flowchart illustrations, and combinations of blocks in the flowcharts, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions can also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in aFigure 1 An article of manufacture of instruction components that specify functions in one or more frames. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby generating a process implemented by the computer, such that the executed instructions provide for implementing the process. Figure 1 The steps that specify the function in one or more boxes.

[0045] Furthermore, each box in the flowchart diagram may represent a module, segment, or code section, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur out of order. For example, depending on the functions involved, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0046] As used in the embodiments of this disclosure, "unit" refers to a software element or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, "unit" is not always limited to software or hardware. A "unit" may be configured to be stored in an addressable storage medium or to execute one or more processors. Thus, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "unit" may be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, elements and "units" may be implemented to reproduce one or more CPUs within a device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0047] Wireless communication systems are evolving into broadband wireless communication systems to provide high-speed, high-quality packet data services using communication standards, including High Speed ​​Packet Access (HSPA) of the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-Pro, High Rate Packet Data (HRPD) of 3GPP2, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.16e, and typical voice-based services.

[0048] As a typical example of a broadband wireless communication system, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and employs a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink refers to a wireless link used by a user equipment (UE) or a mobile station (MS) to transmit data or control signals to a base station (BS) or an eNode B, and the downlink refers to a wireless link used by the base station to transmit data or control signals to the UE. The above-described multiple access scheme can separate data or control information of each user by allocating and operating a time-frequency domain resource for transmitting data or control information for each user to avoid overlapping each other, i.e., to achieve orthogonality.

[0049] Since the 5G communication system is a communication system after the LTE, it must flexibly meet the diverse needs of users, service providers, and the like, and thus must support services satisfying a variety of requirements. Services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low-latency communication (URLLC), and the like.

[0050] The eMBB aims to provide a higher data rate than that supported by the existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, the eMBB needs to provide a peak data rate of 20 Gbps in a downlink and 10 Gbps in an uplink for a single base station. In addition, the 5G communication system must provide a higher user-perceived data rate to the UE in addition to providing the highest rate. To meet the above-described requirements, transmission / reception techniques including an enhanced multiple input multiple output (MIMO) transmission technique need to be further improved. In addition, the data rate required for the 5G communication system can be achieved by using a frequency bandwidth of more than 20 MHz in a frequency band of 3 to 6 GHz or more than 6 GHz, rather than using a signal transmission method of using a maximum transmission bandwidth of 20 MHz in a frequency band of 2 GHz as in the LTE.

[0051] Further, mMTC is being considered for supporting application services, such as Internet of Things (IoT) in a 5G communication system. In order to efficiently provide the Internet of Things, mMTC has requirements such as supporting connection of a large number of UEs in a cell, enhancing UE coverage, prolonging battery life, reducing UE cost, and the like. Since the Internet of Things operates while providing communication functions to various sensors and various devices, a large number of UEs (e.g., 1,000,000 UEs / km2) in a cell must be supported. Further, a UE supporting mMTC can need a wider coverage than other services provided by the 5G communication system, because the UE can be located in a signal shadow area, such as a basement of a building, which is difficult to be covered by a cell due to service characteristics. The UE supporting mMTC must be configured to be low-cost, and can need a very long battery life, such as 10 to 15 years, because it is difficult to frequently replace a UE battery.

[0052] Finally, URLLC is a kind of mission-critical wireless communication service based on a cell. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, drones, telemedicine, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 ms, and can also need a packet error rate of 10-5 or less. Therefore, for a service supporting URLLC, the 5G system must provide a shorter transmission time interval (TTI) than other services, and can also need to design a mechanism for allocating a large amount of resources in a frequency band to ensure reliability of a communication link.

[0053] The three services in 5G, eMBB, URLLC, and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception techniques and transmission / reception parameters can be used between different services to meet different requirements of each service. Of course, 5G is not limited to the three services described above.

[0054] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. In the following description, a base station is an entity that allocates resources to a terminal, and can be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, and a network node. The terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the following description, embodiments of the disclosure will be described taking a 5G system as an example, but embodiments of the disclosure are also applicable to other communication systems having a similar technical background or channel type. Examples of such communication systems include an LTE or LTE-A mobile communication system and a mobile communication technology developed after 5G. Therefore, embodiments of the disclosure can be applied to other communication systems by appropriate modification based on the judgment of those skilled in the art without deviating significantly from the scope of the disclosure. The details of the disclosure can be applied to frequency division duplex (FDD) and time division duplex (TDD) systems.

[0055] Further, in describing the disclosure, if it is determined that a detailed description of a known function or configuration can make the subject matter of the disclosure unnecessarily unclear, the detailed description will be omitted. The terms to be described below are terms defined based on the functions in the disclosure, and can differ depending on the user, the user's intention, or the usage habit. Therefore, the definition of the terms should be understood based on the overall content of the specification.

[0056] In the following description of the disclosure, upper layer signaling can refer to signaling corresponding to at least one of the following signaling, or a combination of one or more thereof.

[0057] - Master Information Block (MIB)

[0058] - System Information Block (SIB) or SIB X (X = 1, 2,...)

[0059] - Radio Resource Control (RRC)

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

[0061] Further, L1 signaling can refer to signaling corresponding to at least one of the following physical layer channel or signaling method using the same, or a combination of one or more thereof.

[0062] - Physical Downlink Control Channel (PDCCH)

[0063] - Downlink Control Information (DCI)

[0064] - UE-specific DCI

[0065] - Group-common DCI

[0066] - Common DCI

[0067] Scheduling DCI (e.g., DCI for scheduling downlink or uplink data)

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

[0069] - Physical Uplink Control Channel (PUCCH)

[0070] - Uplink Control Information (UCI)

[0071] Hereinafter, determining the priority between A and B can be described as, for example, selecting a higher-priority entity according to a predetermined priority rule and performing a corresponding operation, or omitting or discarding an operation regarding a lower-priority entity.

[0072] Hereinafter, the above-described examples can be described through a plurality of embodiments of the disclosure, but the embodiments are not independent of each other, and one or more embodiments can be applied simultaneously or in combination.

[0073] [NR time-domain-frequency domain resource]

[0074] Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the accompanying drawings.

[0075] It should be understood that the blocks in each flowchart and combinations of the flowcharts can be executed by one or more computer programs including computer-executable instructions. The whole of the one or more computer programs can be stored in a single memory device, or the one or more computer programs can be divided into a plurality of parts and stored in different plurality of memory devices.

[0076] Any function or operation described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is a circuit for performing processing, including an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a wireless fidelity (Wi-Fi) chip, a Bluetooth TM chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driving integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a micro processing unit (MPU), a system on chip (SoC), an IC, or the like.

[0077] Figure 1 A basic structure of a time-frequency domain in a wireless communication system according to an embodiment of the disclosure is shown.

[0078] Referring to Figure 2 , a basic structure of one subframe 110 including a time-frequency domain, which is a radio resource domain for transmitting data or a control channel in a 5G system, can be described.

[0079] In Figure 2 , a horizontal axis represents a time domain, and a vertical axis represents a frequency domain. A basic resource unit in the time-frequency domain is a resource element (RE) 101, which is defined as one orthogonal frequency division multiplexing (OFDM) symbol 102 on a time axis and one subcarrier 103 on a frequency axis. In the frequency domain, (e.g., 12) consecutive REs can constitute one resource block (RB) 104.

[0080] Figure 2 A structure of a frame, a subframe, and a slot in a wireless communication system according to an embodiment of the disclosure is illustrated.

[0081] Referring to Figure 2 , Figure 3 A structure example of one frame 200, a subframe 201, and a slot 202 is illustrated. One frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms. Accordingly, one frame 200 can include a total of ten subframes 201. One slot 202 or 203 can be defined as 14 OFDM symbols (i.e., a number of OFDM symbols per slot = 14). One subframe 201 can include one or more slots 202 and 203, and the number of slots 202 and 203 per subframe 201 can vary according to a configuration value μ of a subcarrier spacing 204 or 205. Examples in Figure 3 illustrate a case where a subcarrier spacing configuration value is μ = 0 (204) and a case where μ = 1 (205). When μ = 0 (204), one subframe 201 can include one slot 202; when μ = 1 (205), one subframe 201 can include two slots 203. For example, the number of slots per subframe may vary according to the subcarrier spacing configuration value μ, and the number of slots per frame also varies. and may be defined according to each subcarrier spacing configuration μ in Table 1 below.

[0082] [Table 1]

[0083]

[0084] [PDCCH: About DCI]

[0085] Next, downlink control information (DCI) in a 5G system will be described in detail.

[0086] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a UE through DCI. The UE can monitor a fallback DCI format and a non-fallback DCI format with respect to the PUSCH or the PDSCH. The fallback DCI format can include a fixed field predefined between the base station and the UE, and the non-fallback DCI format can include a configurable field.

[0087] The DCI can be subjected to channel coding and modulation processing, and then transmitted through a physical downlink control channel (PDCCH). A cyclic redundancy check is attached to a DCI message payload, and the CRC can be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used according to the purpose of the DCI message (e.g., UE-specific data transmission, power control command, random access response, etc.). For example, the RNTI can be included in the CRC calculation process and then transmitted, rather than being explicitly transmitted. When receiving the DCI message transmitted through the PDCCH, the UE can identify the CRC by using the allocated RNTI. If the CRC identification result is correct, the UE can know that the corresponding message has been transmitted to the UE.

[0088] For example, the DCI for scheduling the PDSCH with respect to system information (SI) can be scrambled by an SI-RNTI. The DCI for scheduling the PDSCH with respect to a random access response (RAR) message can be scrambled by an RA-RNTI. The DCI for scheduling the PDSCH with respect to a paging message can be scrambled by a P-RNTI. The DCI for notifying a slot format indicator (SFI) can be scrambled by an SFI-RNTI. The DCI for notifying transmission power control (TPC) can be scrambled by a TPC-RNTI. The DCI for scheduling a UE-specific PDSCH or PUSCH can be scrambled by a cell RNTI (C-RNTI).

[0089] The DCI format 0_0 can be used as a fallback DCI for scheduling the PUSCH, and the CRC can be scrambled by the C-RNTI. For example, the DCI format 0_0 in which the CRC is scrambled by the C-RNTI can include the following information segments.

[0090] [Table 2]

[0091]

[0092] The DCI format 0_1 can be used as non-fallback DCI for scheduling a PUSCH, and the CRC can be scrambled by a C-RNTI. For example, the DCI format 0_1 in which the CRC is scrambled by the C-RNTI can include the following information field.

[0093] [Table 3]

[0094]

[0095]

[0096]

[0097] The DCI format 1_0 can be used as fallback DCI for scheduling a PDSCH, and the CRC can be scrambled by a C-RNTI. For example, the DCI format 1_0 in which the CRC is scrambled by the C-RNTI can include the following information field.

[0098] [Table 4]

[0099]

[0100] The DCI format 1_1 can be used as non-fallback DCI for scheduling a PDSCH, and the CRC can be scrambled by a C-RNTI. For example, the DCI format 1_1 in which the CRC is scrambled by the C-RNTI can include the following information field.

[0101] [Table 5]

[0102]

[0103]

[0104] [PDSCH: Processing Time]

[0105] Next, a PDSCH processing time (PDSCH processing procedure time) will be described. When a base station schedules a UE to receive a PDSCH by using a DCI format 1_0, 1_1, or 1_2, the UE can need to apply a PDSCH processing time for receiving the PDSCH according to a transmission mode (e.g., a modulation / demodulation and coding scheme index (MCS), demodulation reference signal related information, frequency domain resource allocation information, etc.) indicated by the DCI. Based on this, a PDSCH processing time has been defined in a 5G communication system. The PDSCH processing time of the UE can follow Equation 1 shown below

[0106] Tproc,1=(N1+d1,1+d2)(2048+144)κ2-μ Tc+Text

[0107] ... Equation 1

[0108] Each parameter of Tproc,1 described in Equation 1 above has the following meaning.

[0109] - N1: The number of symbols determined according to UE processing capability 1 or 2 based on UE capability and numerology μ. If UE processing capability 1 is reported according to UE capability report, N1 takes the value in Table 6; if UE processing capability 2 is reported and the availability of UE processing capability 2 is configured through upper layer signaling, N1 takes the value in Table 7. The numerology μ takes the minimum value among μPDCCH, μPDSCH, μUL to maximize Tproc,1; and μPDCCH, μPDSCH, μUL represent the numerology of PDCCH scheduling PDSCH, the numerology of scheduled PDSCH, and the numerology of uplink channel for transmitting HARQ-ACK, respectively. Table 6 includes information of PDSCH processing time in case of PDSCH processing capability 1.

[0110] [Table 6]

[0111]

[0112] Table 7 includes information of PDSCH processing time in case of PDSCH processing capability 2.

[0113] Table 7

[0114]

[0115] - κ: 64

[0116] - Text: If the UE employs a shared spectrum channel access scheme, the UE can calculate Text and apply it to the PDSCH processing time. Otherwise, Text is 0 by default.

[0117] - If l1 representing the PDSCH DMRS position value is 12, the value of N1,0 in Table 6 above is 14; otherwise, it is 13.

[0118] - For PDSCH mapping type A, if the last symbol of PDSCH is the i-th symbol in the slot where PDSCH is transmitted, and if i < 7, d1,1 = 7 - i; otherwise, d1,1 = 0.

[0119] - d2: If a PUCCH with a high priority index overlaps in time with another PUCCH or a PUSCH with a low priority index, d2 for the PUCCH with the high priority index can be configured to the value reported by the UE. Otherwise, d2 is 0.

[0120] - If PDSCH mapping type B is used with respect to UE processing capability 1, the d1,1 value can be determined by the number of symbols of the scheduled PDSCH (L) and the number of overlapping symbols between the PDCCH scheduling the PDSCH and the scheduled PDSCH, as follows.

[0121] - If L ≥ 7, d1,1 = 0.

[0122] - If 4 < L ≤ 6, d1,1 = 7 - L.

[0123] - If L = 3, d1,1 = min(d,1).

[0124] - If L = 2, d1,1 = 3 + d.

[0125] - If PDSCH mapping type B is used with respect to UE processing capability 2, the d1,1 value can be determined by the number of symbols of the scheduled PDSCH (L) and the number of overlapping symbols between the PDCCH scheduling the PDSCH and the scheduled PDSCH, as follows

[0126] - If L ≥ 7, d1,1 = 0.

[0127] - If 4 < L ≤ 6, d1,1 = 7 - L.

[0128] - If L = 2,

[0129] - If the scheduling PDCCH is present within a CORESET comprising three symbols and the CORESET has the same starting symbol as the scheduled PDSCH, d1,1 = 3.

[0130] - Otherwise, d1,1 = d.

[0131] - In case of a UE supporting capability 2 within a given serving cell, if processingType2Enabled (higher layer signaling) is configured as "enable" with respect to the corresponding cell, the UE can apply PDSCH processing time based on UE processing capability 2.

[0132] If the position of the first uplink transmission symbol of the PUCCH including the HARQ-ACK information (with respect to this position, K1 is defined as the HARQ-ACK transmission time point, the PUCCH resource for transmitting the HARQ-ACK, and the timing advance effect needs to be considered) is not earlier than the first uplink transmission symbol coming after Tproc,1 time from the last symbol of the PDSCH, the UE needs to send a valid HARQ-ACK message. For example, the UE needs to send the PUCCH including the HARQ-ACK only when the PDSCH processing time is sufficient. Otherwise, the UE cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. Tproc,1 can be used for normal or extended CP cases. For a PDSCH in which two PDSCH transmission positions are configured within one slot, d1,1 should be calculated with reference to the first PDSCH transmission position within the slot.

[0133] [PDSCH: reception preparation time when cross-carrier scheduling]

[0134] Next, in cross-carrier scheduling, if the numerology (μPDCCH) used by the scheduling PDCCH is different from the numerology (μPDSCH) used by the PDSCH scheduled by the PDCCH, the PDSCH reception preparation time (Npdsch) of the UE defined based on the time interval between the PDCCH and the PDSCH will be described.

[0135] If μPDCCH<μPDSCH, the scheduled PDSCH cannot be transmitted before the first symbol of the next slot after Npdsch symbols from the last symbol of the PDCCH scheduling the PDSCH. The transmission symbols of the scheduled PDSCH can include DM-RS.

[0136] If μPDCCH>μPDSCH, the scheduled PDSCH can be transmitted after Npdsch symbols from the last symbol of the PDCCH scheduling the PDSCH. The transmission symbols of the scheduled PDSCH can include DM-RS. In Table 8, Npdsch has at least one of the values listed in Table 8 according to the subcarrier spacing of the scheduling PDCCH.

[0137] Table 8

[0138]

[0139] [PUSCH: on transmission scheme]

[0140] Next, a PUSCH transmission scheduling scheme will be described. The PUSCH transmission can be dynamically scheduled by an UL grant in DCI or implemented by a configured grant Type 1 or Type 2. A dynamic scheduling indication for the PUSCH transmission can be implemented by DCI format 0_0 or 0_1.

[0141] The PUSCH transmission of the configured grant Type 1 can be semi-statically configured by the configuredGrantConfig including rrc-ConfiguredUplinkGrant in Table 9 through upper layer signaling without receiving an UL grant in DCI. The PUSCH transmission of the configured grant Type 2 can be semi-persistently scheduled by an UL grant within DCI after receiving the configuredGrantConfig not including rrc-ConfiguredUplinkGrant in Table 9 through upper layer signaling. If the PUSCH transmission is scheduled by the configured grant, parameters applied to the PUSCH transmission can be configured by the configuredGrantConfig (upper layer signaling) in Table 9, but dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH except for these parameters are provided by pusch-Config (upper layer signaling) in Table 10. If transformPrecoder is configured in the configuredGrantConfig (upper layer signaling) of Table 14, the UE can apply tp-pi2BPSK in pusch-Config of Table 15 to the PUSCH transmission triggered by the configured grant.

[0142] Table 9

[0143]

[0144]

[0145]

[0146]

[0147] Subsequently, a PUSCH transmission method will be described. The DMRS antenna port for the PUSCH transmission is the same as the antenna port for the SRS transmission. The PUSCH transmission can follow a codebook-based transmission method and a non-codebook-based transmission method according to whether the value of txConfig within pusch-Config in Table 10 is “codebook” or “nonCodebook”, pusch-Config within txConfig is upper layer signaling.

[0148] As described above, a PUSCH transmission can be dynamically scheduled by a DCI format 0_0 or 0_1, and a PUSCH transmission can be semi-statically configured by a configured grant. When an indication about scheduling of a PUSCH transmission is received by a DCI format 0_0, a UE can perform a beam configuration for the PUSCH transmission by using a pucch-spatialRelationInfo ID corresponding to a UE-specific PUCCH resource corresponding to a smallest ID within an activated uplink BWP within a serving cell, and the PUSCH transmission can be based on a single antenna port. A UE can not expect scheduling about a PUSCH transmission by a DCI format 0_0 within a BWP without a configured PUCCH resource including pucch-spatialRelationInfo. If a UE is not configured with txConfig within pusch-Config in Table 10, the UE can not expect scheduling by a DCI format 0_1.

[0149] Table 10

[0150]

[0151]

[0152]

[0153] A codebook-based PUSCH transmission can be dynamically scheduled by a DCI format 0_0 or 0_1, and a codebook-based PUSCH transmission can be semi-statically operated by a configured grant. If a codebook-based PUSCH is dynamically scheduled by a DCI format 0_1 or semi-statically configured by a configured grant, a UE can determine a precoder for a PUSCH transmission according to an SRS resource indicator (SRI), a transmission precoding matrix indicator (TPMI), and a transmission rank (a number of PUSCH transmission layers).

[0154] The SRI can be given by SRS resource indicator (a field inside DCI) or configured by srs-ResourceIndicator (higher layer signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured for it and at most two SRS resources configured for it. If the SRI is provided to the UE by DCI, the SRS resource indicated by the SRI can refer to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. In addition, the TPMI and the transmission rank can be given by "precoding information and number of layer" (a field inside DCI) or configured by precodingAndNumberOfLayers (higher layer signaling). The TPMI can be used to indicate the precoder applied to the PUSCH transmission. If one SRS resource is configured for the UE, the TPMI can be used to indicate the precoder applied in the configured SRS resource. If multiple SRS resources are configured for the UE, the TPMI can be used to indicate the precoder applied in the SRS resource indicated by the SRI.

[0155] The precoder for PUSCH transmission can be selected from an uplink codebook with the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config (higher layer signaling). In conjunction with codebook-based PUSCH transmission, the UE can determine the codebook subset according to codebookSubset and TPMI in pusch-Config (higher layer signaling). The codebookSubset in pusch-Config (higher layer signaling) can be configured to be one of “fullyAndPartialAndNonCoherent”, “partialAndNonCoherent”, or “noncoherent” according to the UE capability reported by the UE to the base station. If the UE capability reported by the UE is “partialAndNonCoherent”, the UE should not expect the value of codebookSubset (higher layer signaling) to be configured as “fullyAndPartialAndNonCoherent”. Furthermore, if the UE capability reported by the UE is “nonCoherent”, the UE should not expect the value of codebookSubset (higher layer signaling) to be configured as “fullyAndPartialAndNonCoherent” or “partialAndNonCoherent”. If nrofSRS-Ports in SRS-ResourceSet (higher layer signaling) indicates two SRS antenna ports, the UE should not expect the value of codebookSubset (higher layer signaling) to be configured as “partialAndNonCoherent”.

[0156] The UE can have one SRS resource set configured for it with the value of usage in SRS-ResourceSet (higher layer signaling) being “codebook” and one SRS resource can be indicated by SRI within the SRS resource set. If multiple SRS resources are configured within the SRS resource set with the value of usage within SRS-ResourceSet (higher layer signaling) being “codebook”, the UE should expect the value of nrofSRS-Ports in SRS-Resource (higher layer signaling) to be the same for all SRS resources.

[0157] A UE can send one or more SRS resources included in a SRS resource set to a base station, where a usage value is configured as "codebook" through upper layer signaling, the base station can select one from the SRS resources sent by the UE, and instruct the UE to send a PUSCH using the transmission beam information of the corresponding SRS resource. In the codebook-based PUSCH transmission, SRI can be used as information to select one SRS resource index, and can be included in DCI. In addition, the base station can add information indicating the rank and TPMI used by the UE for PUSCH transmission to the DCI. The UE can apply the precoder indicated by the rank and TPMI based on the transmission beam of the SRS resource indicated by the SRI, thereby performing PUSCH transmission.

[0158] Next, non-codebook-based PUSCH transmission will be described. Non-codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically operated through a configured grant. If at least one SRS resource is configured in a SRS resource set with a usage value of "nonCodebook" in SRS-ResourceSet (upper layer signaling), non-codebook-based PUSCH transmission can be scheduled for a UE through DCI format 0_1.

[0159] For a SRS resource set with a usage value of "nonCodebook" in SRS-ResourceSet (upper layer signaling), one associated NZP CSI-RS resource (non-zero power CSI-RS) can be configured for a UE. A user equipment (UE) can calculate a precoder for SRS transmission by measuring the NZP CSI-RS resource associated with 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 in the UE is less than 42 symbols, the UE should not expect the precoder information for SRS transmission to be updated.

[0160] If the configured value of resourceType in SRS-ResourceSet (higher layer signaling) is "aperiodic", the connected NZP CSI-RS can be indicated by SRS request field in DCI format 0_1 or 1_1. If the connected NZP CSI-RS resource is aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS can be indicated when the value of SRS request (field in DCI format 0_1 or 1_1) is not "00". The corresponding DCI shall not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of SRS request indicates the presence of NZP CSI-RS, the NZP CSI-RS can be located in the slot in which the PDCCH including the SRS request field is transmitted. In this case, the TCI state configured for the scheduled subcarriers shall not be configured as QCL-TypeD.

[0161] If a periodic or semi-persistent SRS resource set is configured, the NZP CSI-RS can be indicated by associatedCSI-RS in SRS-ResourceSet (higher layer signaling). For non-codebook-based transmission, the UE shall not expect that the higher layer signaling spatialRelationInfo for SRS resource is configured simultaneously with associatedCSI-RS within SRS-ResourceSet (higher layer signaling).

[0162] If multiple SRS resources are configured for a UE, the UE can determine the precoder and transmission rank applied for PUSCH transmission according to the SRI indicated by the base station. The SRI can be indicated by SRS resource indicator (one field in DCI) or configured by srs-ResourceIndicator (higher layer signaling). Similar to the above codebook-based PUSCH transmission, if the SRI is provided to the UE by DCI, the SRS resource indicated by the SRI can refer to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within one SRS resource set and the total number of SRS resources are determined by the UE capability reported to the base station by the UE. The SRS resources transmitted simultaneously by the UE can occupy the same RB. The UE can configure one SRS port for each SRS resource. There can be only one configured SRS resource set with the value of usage within SRS-ResourceSet (higher layer signaling) being "nonCodebook", and at most four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0163] A base station can transmit one NZP-CSI-RS connected to a SRS resource set to a UE, and the UE can calculate a precoder used when transmitting one or more SRS resources in the SRS resource set based on a measurement result of the received NZP-CSI-RS. The UE can apply the calculated precoder when transmitting one or more SRS resources in the SRS resource set to the base station, where the configured usage is 'nonCodebook', and the base station can select one or more SRS resources from the received one or more SRS resources. In a non-codebook-based PUSCH transmission, an SRI can indicate an index representing one SRS resource or a combination of multiple SRS resources, and the SRI can be included in DCI. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the UE can transmit the PUSCH by applying a precoder applied to the SRS resource transmission to each layer.

[0164] [PUSCH: preparation time]

[0165] Next, a PUSCH preparation time will be described. If a base station schedules a UE to transmit a PUSCH by using DCI format 0_0, 0_1, or 0_2, the UE needs a PUSCH preparation time in order to transmit the PUSCH by applying a transmission method (SRS resource transmission precoding method, number of transmission layers, spatial domain transmission filter) indicated by the DCI. Accordingly, a PUSCH preparation time is defined in a 5G communication system. The PUSCH preparation time of the UE can follow Equation 2 shown below.

[0166] Tproc,2 = max ((N2 + d2,1 + d2,2) (2048 + 144) κ2 - μ Tc + Text + Tswitch, d2,2)

[0167] … Equation 2

[0168] Each parameter in Tproc,2 described in Equation 2 above can have the following meaning.

[0169] - N2: number of symbols determined based on UE processing capability 1 or 2, based on UE capability and numerology μ. If UE processing capability 1 is reported according to a UE capability report, N2 has the value in Table 11; if UE processing capability 2 is reported and the availability of UE processing capability 2 is configured through upper layer signaling, N2 has the value in Table 12.

[0170] [Table 11]

[0171]

[0172] [Table 12]

[0173]

[0174] - d2,1: If all resource elements of the first OFDM symbol of the PUSCH transmission include DM-RS, the number of symbols is determined to be 0, otherwise 1.

[0175] - κ: 64

[0176] - μ: take and the larger one of Tproc,2. - TTI: refers to the numerology of the downlink used to transmit the PDCCH including the DCI scheduling the PUSCH, - TTI: refers to the numerology of the uplink used to transmit the PUSCH.

[0177] - Tc: has , ,

[0178] - d2,2: If the DCI scheduling the PUSCH indicates a BWP switch, d2,2 follows the BWP switching time, otherwise 0.

[0179] - d2: If there is an OFDM symbol overlap in time domain between the PUSCH with a high priority index and the PUCCH with a low priority index, the d2 value of the high priority index PUSCH is used. Otherwise, d2 is 0.

[0180] - Text: If the UE uses a shared spectrum channel access scheme, the UE can calculate Text and include it in the PUSCH preparation time. Otherwise, Text is 0 by default.

[0181] - Tswitch: If an uplink switching interval has been triggered, Tswitch is assumed to be the switching interval time. Otherwise, Tswitch is assumed to be 0.

[0182] Taking into account the timing advance between uplink and downlink and the impact of the time domain resource mapping information of the PUSCH scheduled by the DCI, if the starting time of the first symbol of the PUSCH is earlier than the first uplink symbol starting Tproc,2 after the last symbol of the PDCCH including the DCI scheduling the PUSCH, the base station and the UE can determine that the PUSCH preparation procedure time is not sufficient. Otherwise, the base station and the UE can determine that the PUSCH preparation procedure time is sufficient. The UE can only transmit the PUSCH when the PUSCH preparation procedure time is sufficient; if the PUSCH preparation procedure time is not sufficient, the UE can ignore the DCI scheduling the PUSCH.

[0183] [PUSCH: on repeated transmission]

[0184] The repetition transmission of the uplink data channel in the 5G system will be described in detail below. The 5G system can support two repetition transmission methods of the uplink data channel: PUSCH repetition Type A and PUSCH repetition Type B. One of the PUSCH repetition Type A and the PUSCH repetition Type B can be configured for the UE through upper layer signaling.

[0185] PUSCH repetition Type A

[0186] - As described above, the symbol length and the position of the starting symbol of the uplink data channel can be determined in one slot through the time domain resource allocation method, and the base station can inform the UE of the number of repetitions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0187] - Based on the number of repetitions received from the base station, the UE can repeatedly transmit the uplink data channel having the same length and the starting symbol of the configured uplink data channel in consecutive slots. If the base station configures the slot as the downlink of the UE, or if at least one symbol of the uplink data channel configured for the UE is configured as the downlink, the UE can omit the transmission of the uplink data channel, but can count the number of repetitions of the uplink data channel.

[0188] PUSCH repetition Type B

[0189] - As described above, the starting symbol and the length of the uplink data channel can be determined in one slot through the time domain resource allocation method, and the base station can inform the UE of the number of repetitions (numberofrepetitions) through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0190] - Based on the previously configured starting symbol and length of the uplink data channel, the nominal repetition of the uplink data channel is determined as follows. The slot in which the nth nominal repetition starts is given by , and the symbol in which it starts in the slot is given by . The slot in which the nth nominal repetition ends is given by

[0191] , and the symbol in which it ends in the slot is given by . Here, n = 0, …, numberofrepetitions-1, S can refer to the starting symbol of the configured uplink data channel, and L can refer to the symbol length of the configured uplink data channel. refers to the slot in which the PUSCH transmission starts, and refers to the number of symbols per slot.

[0192] - The UE can determine invalid symbols for PUSCH repetition Type B transmission. Symbols configured as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as invalid symbols for PUSCH repetition Type B transmission. In addition, invalid symbols can be configured by a higher layer parameter (e.g., InvalidSymbolPattern). The higher layer parameter (e.g., InvalidSymbolPattern) can provide a symbol level bitmap across one or two slots, thereby configuring invalid symbols. In the bitmap, 1 can represent invalid symbols. In addition, the period and pattern of the bitmap can be configured by a higher layer parameter (e.g., InvalidSymbolPattern). If the higher layer parameter (e.g., InvalidSymbolPattern) is configured and the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 indicates 1, the UE can apply the invalid symbol pattern; if the above parameter indicates 0, the UE can not apply the invalid symbol pattern. If the higher layer parameter (e.g., InvalidSymbolPattern) is configured and the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 is not configured, the UE can apply the invalid symbol pattern.

[0193] After determining the invalid symbols, the UE can consider symbols other than the invalid symbols as valid symbols for each nominal repetition. If one or more valid symbols are included in each nominal repetition, the nominal repetition can include one or more actual repetitions. Each actual repetition includes a set of consecutive valid symbols available for PUSCH repetition Type B transmission in one slot.

[0194] Figure 4 A PUSCH repetition Type B transmission in a wireless communication system according to embodiments of the disclosure is illustrated.

[0195] Reference Figure 4, the UE can receive the following configuration: the starting symbol S of the uplink data channel is 0, the length L of the uplink data channel is 14, and the number of repeated transmissions is 16. In this case, nominal repetitions can occur in 16 consecutive slots (301). Thereafter, the UE can determine that the symbols configured as downlink symbols in each nominal repetition 301 are invalid symbols. In addition, the UE can determine that the symbols configured as 1 in the invalid symbol pattern 302 are invalid symbols. If the valid symbols other than the invalid symbols in each nominal repetition constitute one or more consecutive symbols in a slot, they can be configured and transmitted as actual repetitions (303).

[0196] In addition, with respect to PUSCH repetition transmission, additional methods with respect to UL grant-based PUSCH transmission and configuration grant-based PUSCH transmission across slot boundaries can be defined in NR Release 16 as follows:

[0197] - Method 1 (micro-slot level repetition): Through one UL grant, two or more PUSCH repetition transmissions can be scheduled within one slot or across the boundaries of consecutive slots. In addition, in connection with Method 1, the time domain resource allocation information within the DCI can indicate the resources of the first repetition transmission. In addition, the time domain resource information of the remaining repetition transmissions can be determined from the time domain resource information of the first repetition transmission and the uplink or downlink direction determined for each symbol of each slot. Each repetition transmission can occupy consecutive symbols.

[0198] - Method 2 (multi-segment transmission): Through one UL grant, two or more PUSCH repetition transmissions can be scheduled in consecutive slots. Transmission number 1 can be specified for each slot, and the starting point or repetition length can be different between the respective transmissions. In addition, in Method 2, the time domain resource allocation information within the DCI can indicate the starting point and repetition length of all repetition transmissions. In addition, when repetition transmission is performed within a single slot through Method 2, if there can be multiple consecutive uplink symbol bundles in the corresponding slot, the respective repetition transmissions can be performed for each uplink symbol bundle. If there is a single bundle of consecutive uplink symbols in the corresponding slot, one PUSCH repetition transmission can be performed according to the method of NR Release 15.

[0199] - Method 3: Two or more PUSCH repetition transmissions can be scheduled in consecutive slots through two or more UL grants. Transmission number 1 can be specified for each slot, and the nth UL grant can be received before the PUSCH transmission scheduled by the (n-1)th UL grant ends.

[0200] - Method 4: One or more PUSCH repetition transmissions within a single slot or two or more PUSCH repetition transmissions across consecutive slot boundaries can be supported by one UL grant or one configured grant. The number of repetitions indicated to the UE by the base station is only a nominal value, and the UE can actually perform more PUSCH repetition transmissions than the nominal number of repetitions. The time domain resource allocation information in the DCI or the configured grant can indicate the resources for the first repetition transmission indicated by the base station. The time domain resource information for the remaining repetition transmissions can be determined with reference to the resource information for the first repetition transmission and the uplink or downlink direction of the symbol. If the time domain resource information for the repetition transmissions indicated by the base station crosses the slot boundary or includes an uplink / downlink switching point, the corresponding repetition transmission can be divided into multiple repetition transmissions. One repetition transmission can be included in one slot for each uplink period.

[0201] [PUSCH: frequency hopping processing]

[0202] Hereinafter, frequency hopping of a physical uplink shared channel (PUSCH) in a 5G communication system will be described in detail.

[0203] The 5G communication system can support two PUSCH frequency hopping methods with respect to each PUSCH repetition transmission type. First, in the PUSCH repetition transmission type A, intra-slot frequency hopping and inter-slot frequency hopping can be supported; in the PUSCH repetition transmission type B, inter-repetition frequency hopping and inter-slot frequency hopping can be supported.

[0204] The inter-slot frequency hopping method supported in the PUSCH repetition transmission type A can be a method in which the UE transmits the allocated resources in the frequency domain by two times of frequency hopping in one slot after changing the resources to a configured frequency offset. The starting RB of each hop related to intra-slot frequency hopping can be represented by Equation 3 below:

[0205] Equation 3

[0206] In Equation 3, i=0 and i=1 can indicate the first hop and the second hop, respectively, and can represent the starting RB in the UL BWP, and The calculation can be made according to the frequency domain resource allocation method. The frequency offset between the two hops can be indicated by a higher layer parameter. The number of symbols of the first hop can be represented as , and the number of symbols of the second hop can be represented as represents the number of OFDM symbols corresponding to the PUSCH transmission length in one slot.

[0207] Next, the inter-slot frequency hopping method supported in PUSCH repetition transmission Type A and B can be a method in which the UE transmits the allocated resources in the frequency domain after changing the resources according to a configured frequency offset in each slot. The inter-slot frequency hopping related The starting RB during a slot can be represented by Equation 4 below. Equation 4

[0208] In

[0209] ... Equation 4

[0210] In Equation 4, may refer to the current slot number during multi-slot PUSCH transmission, and may be calculated according to the frequency domain resource allocation method. may refer to the frequency offset between two frequency hops set by a higher layer parameter.

[0211] Next, the inter-repetition frequency hopping method supported in PUSCH repetition transmission Type B can be a method in which, in each nominal repetition, the resources allocated in the frequency domain for one or more actual repetitions are transmitted after being moved by a configured frequency offset. With respect to one or more actual repetitions in the nth nominal repetition, the index of the starting RB in the frequency domain Equation 5 given below should be followed.

[0212]

[0213] ... Equation 5

[0214] In Equation 5, n can refer to the index of the nominal repetition, and may refer to the RB offset between two frequency hops configured by a higher layer parameter.

[0215] [PUSCH: Multiplexing rule during AP / SP CSI reporting]

[0216] Hereinafter, a method of measuring and reporting channel state in a 5G communication system will be described in detail. Channel state information (CSI) can include a channel quality indicator (channel quality information (CQI)), a precoding matrix index (precoding matrix indicator (PMI)), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), a reference signal received power (L1-RSRP), and / or the like. A base station can control the time and frequency domain resources for a terminal to perform the above-described CSI measurement and reporting.

[0217] For the above CSI measurement and reporting, the terminal can be configured by higher layer signaling with N (N≥1) pieces of setting information of CSI report (CSI-ReportConfig), M (M≥1) pieces of setting information of RS transmission resource (CSI-ResourceConfig), and a list information of one or two trigger states (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList). The above configuration information for CSI measurement and reporting can be more specifically described as in Table 13 to Table 18 and the related descriptions thereof.

[0218] CSI-ReportConfig

[0219] The IE CSI-ReportConfig is used to configure a periodic or semi-persistent report transmitted over PUCCH on the cell including the CSI-ReportConfig, or to configure a semi-persistent or aperiodic report triggered by DCI and transmitted over PUSCH on the cell including the CSI-ReportConfig (in this case, the cell where the report is transmitted is determined by the received DCI). See TS 38.214

[19] , clause 5.2.1.

[0220] CSI-ReportConfig information element

[0221] -- ASN1START

[0222] -- TAG-CSI-REPORTCONFIG-START

[0223] CSI-ReportConfig ::= SEQUENCE {

[0224] reportConfigId CSI-ReportConfigId,

[0225] carrier ServCellIndex OPTIONAL, -- Need S

[0226] resourcesForChannelMeasurement CSI-ResourceConfigId,

[0227] csi-IM-ResourcesForInterference CSI-ResourceConfigIdOPTIONAL, -- Need R

[0228] nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigIdOPTIONAL, -- Required R

[0229] reportConfigType CHOICE {

[0230] periodic SEQUENCE {

[0231] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0232] pucch-CSI-ResourceList SEQUENCE (SIZE(1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0233] },

[0234] semiPersistentOnPUCCH SEQUENCE {

[0235] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0236] pucch-CSI-ResourceList SEQUENCE (SIZE(1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0237] },

[0238] semiPersistentOnPUSCH SEQUENCE {

[0239] reportSlotConfig ENUMERATED {sl5,sl10, sl20, sl40, sl80, sl160, sl320},

[0240] reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32),

[0241] p0alpha P0-PUSCH-AlphaSetId

[0242] },

[0243] aperiodic SEQUENCE {

[0244] reportSlotOffsetList SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF INTEGER(0..32)

[0245] }

[0246] },

[0247] reportQuantity CHOICE {

[0248] none NULL,

[0249] cri-RI-PMI-CQI NULL,

[0250] cri-RI-i1 NULL,

[0251] cri-RI-i1-CQI SEQUENCE {

[0252] pdsch-BundleSizeForCSI ENUMERATED {n2, n4}OPTIONAL -- Required S

[0253] },

[0254] cri-RI-CQI NULL,

[0255] cri-RSRP NULL,

[0256] ssb-Index-RSRP NULL,

[0257] cri-RI-LI-PMI-CQI NULL

[0258] },

[0259] reportFreqConfiguration SEQUENCE {

[0260] cqi-FormatIndicator ENUMERATED {widebandCQI, subbandCQI} OPTIONAL, -- Required R

[0261] pmi-FormatIndicator ENUMERATED {widebandPMI, subbandPMI} OPTIONAL, -- Required R

[0262] csi-ReportingBand CHOICE {

[0263] subbands3 BIT STRING(SIZE(3)),

[0264] subbands4 BIT STRING(SIZE(4)),

[0265] subbands5 BIT STRING(SIZE(5)),

[0266] subbands6 BIT STRING(SIZE(6)),

[0267] subbands7 BIT STRING(SIZE(7)),

[0268] subbands8 BIT STRING(SIZE(8)),

[0269] subbands9 BIT STRING(SIZE(9)),

[0270] subbands10 BIT STRING(SIZE(10)),

[0271] subbands11 BIT STRING(SIZE(13)),

[0272] subbands12 BIT STRING(SIZE(12)),

[0273] subbands13 BIT STRING(SIZE(4)),

[0274] subbands14 BIT STRING(SIZE(13)),

[0275] subbands15 BIT STRING(SIZE(12)),

[0276] subbands16 BIT STRING(SIZE(13)),

[0277] subbands17 BIT STRING(SIZE(17)),

[0278] subbands18 BIT STRING(SIZE(18)),

[0279] …,

[0280] subbands19-v1530 BIT STRING(SIZE(19))

[0281] } OPTIONAL -- Need S

[0282] } OPTIONAL, -- Need R

[0283] timeRestrictionForChannelMeasurements ENUMERATED{configured, notConfigured},

[0284] timeRestrictionForInterferenceMeasurements ENUMERATED{configured, notConfigured},

[0285] codebookConfig CodebookConfig OPTIONAL, -- Need R

[0286] dummy ENUMERATED {n1,n2} OPTIONAL, -- Need R

[0287] groupBasedBeamReporting CHOICE {

[0288] enabled NULL,

[0289] disabled SEQUENCE {

[0290] nrofReportedRS ENUMERATED {n1,n2, n3, n4} OPTIONAL -- Need S

[0291] }

[0292] },

[0293] cqi-Table ENUMERATED {table1, table2, table3,spare1} OPTIONAL, -- Need R

[0294] subbandSize ENUMERATED {value1, value2},

[0295] non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R

[0296] …, [[

[0298] semiPersistentOnPUSCH-v1530 SEQUENCE {

[0299] reportSlotConfig-v1530 ENUMERATED {sl4, sl8,sl16}

[0300] } OPTIONAL -- Need R

[0301] ]], [[

[0303] semiPersistentOnPUSCH-v1610 SEQUENCE {

[0304] reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R

[0305] reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R

[0306] } OPTIONAL, -- Need R

[0307] aperiodic-v1610 SEQUENCE {

[0308] reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R

[0309] reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R

[0310] } OPTIONAL, -- Need R

[0311] reportQuantity-r16 CHOICE {

[0312] cri-SINR-r16 NULL,

[0313] ssb-Index-SINR-r16 NULL

[0314] } OPTIONAL, -- Need R

[0315] codebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R ]]

[0317] }

[0318] CSI-ReportPeriodicityAndOffset ::= CHOICE {

[0319] slots4 INTEGER(0..3),

[0320] slots5 INTEGER(0..4),

[0321] slots8 INTEGER(0..7),

[0322] slots10 INTEGER(0..9),

[0323] slots16 INTEGER(0..15),

[0324] slots20 INTEGER(0..19),

[0325] slots40 INTEGER(0..39),

[0326] slots80 INTEGER(0..79),

[0327] slots160 INTEGER(0..159),

[0328] slots 320 INTEGER (0..319)

[0329] }

[0330] PUCCH-CSI-Resource ::= SEQUENCE {

[0331] uplinkBandwidthPartId BWP-Id,

[0332] pucch-Resource PUCCH-ResourceId

[0333] }

[0334] PortIndexFor8Ranks ::= CHOICE {

[0335] portIndex8 SEQUENCE{

[0336] rank1-8 PortIndex8 OPTIONAL, -- Need R

[0337] rank2-8 SEQUENCE(SIZE(2)) OFPortIndex8 OPTIONAL, -- Need R

[0338] rank3-8 SEQUENCE(SIZE(3)) OFPortIndex8 OPTIONAL, -- Need R

[0339] rank4-8 SEQUENCE(SIZE(4)) OFPortIndex8 OPTIONAL, -- Need R

[0340] rank5-8 SEQUENCE(SIZE(5)) OFPortIndex8 OPTIONAL, -- Need R

[0341] rank6-8 SEQUENCE(SIZE(6)) OFPortIndex8 OPTIONAL, -- Need R

[0342] rank7-8 SEQUENCE(SIZE(7)) OFPortIndex8 OPTIONAL, -- Need R

[0343] rank8-8 SEQUENCE(SIZE(8)) OFPortIndex8 OPTIONAL -- Need R

[0344] },

[0345] portIndex4 SEQUENCE{

[0346] rank1-4 PortIndex4 OPTIONAL, -- Need R

[0347] rank2-4 SEQUENCE(SIZE(2)) OFPortIndex4 OPTIONAL, -- Need R

[0348] rank3-4 SEQUENCE(SIZE(3)) OFPortIndex4 OPTIONAL, -- Need R

[0349] rank4-4 SEQUENCE(SIZE(4)) OFPortIndex4 OPTIONAL -- Need R

[0350] },

[0351] portIndex2 SEQUENCE{

[0352] rank1-2 PortIndex2 OPTIONAL, -- Need R

[0353] rank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL -- Need R

[0354] },

[0355] portIndex1 NULL

[0356] }

[0357] PortIndex8 ::= INTEGER (0..7)

[0358] PortIndex4 ::= INTEGER (0..3)

[0359] PortIndex2 ::= INTEGER (0..1)

[0360] -- TAG-CSI-REPORTCONFIG-STOP

[0361] -- ASN1STOP

[0362] [Table 13]

[0363]

[0364]

[0365]

[0366]

[0367]

[0368]

[0369] CSI-ResourceConfig

[0370] The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and / or CSI-SSB-ResourceSet.

[0371] CSI-ResourceConfig information element

[0372] -- ASN1START

[0373] -- TAG-CSI-RESOURCECONFIG-START

[0374] CSI-ResourceConfig ::= SEQUENCE {

[0375] csi-ResourceConfigId CSI-ResourceConfigId,

[0376] csi-RS-ResourceSetList CHOICE {

[0377] nzp-CSI-RS-SSB SEQUENCE {

[0378] nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE(1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId

[0379] OPTIONAL, -- Need R

[0380] csi-SSB-ResourceSetList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL-- Need R

[0381] },

[0382] csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId

[0383] },

[0384] bwp-Id BWP-Id,

[0385] resourceType ENUMERATED { aperiodic,semiPersistent, periodic}, ...

[0387] }

[0388] -- TAG-CSI-RESOURCECONFIG-STOP

[0389] -- ASN1STOP

[0390] [Table 14]

[0391]

[0392] NZP-CSI-RS-ResourceSet

[0393] IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters.

[0394] NZP-CSI-RS-ResourceSet information element

[0395] -- ASN1START

[0396] -- TAG-NZP-CSI-RS-RESOURCESET-START

[0397] NZP-CSI-RS-ResourceSet ::= SEQUENCE {

[0398] nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,

[0399] nzp-CSI-RS-Resources SEQUENCE (SIZE(1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,

[0400] repetition ENUMERATED { on, off} OPTIONAL, -- Need S

[0401] aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S

[0402] trs-Info ENUMERATED {true} OPTIONAL, -- Need R

[0403] …, [[

[0405] aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S ]]

[0407] }

[0408] -- TAG-NZP-CSI-RS-RESOURCESET-STOP

[0409] -- ASN1STOP

[0410] [Table 15]

[0411]

[0412] CSI-SSB-ResourceSet

[0413] IE CSI-SSB-ResourceSet is used to configure one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block resource set, the resource set points to the SS / PBCH indicated in ServingCellConfigCommon.

[0414] CSI-SSB-ResourceSet information element

[0415] -- ASN1START

[0416] -- TAG-CSI-SSB-RESOURCESET-START

[0417] CSI-SSB-ResourceSet ::= SEQUENCE {

[0418] csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,

[0419] csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index, ...

[0421] }

[0422] -- TAG-CSI-SSB-RESOURCESET-STOP

[0423] -- ASN1STOP

[0424] CSI-IM-ResourceSet

[0425] IE CSI-IM-ResourceSet is used to configure one or more CSI interference management (IM) resources (their IDs) and set-specific parameters.

[0426] CSI-IM-ResourceSet information element

[0427] -- ASN1START

[0428] -- TAG-CSI-IM-RESOURCESET-START

[0429] CSI-IM-ResourceSet ::= SEQUENCE {

[0430] csi-IM-ResourceSetId CSI-IM-ResourceSetId,

[0431] csi-IM-Resources SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId, ...

[0433] }

[0434] -- TAG-CSI-IM-RESOURCESET-STOP

[0435] -- ASN1STOP

[0436] [Table 16]

[0437]

[0438] CSI-AperiodicTriggerStateList

[0439] CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state. Upon receiving a value associated with a trigger state, the UE shall perform measurements on CSI-RS and make aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList of the trigger state.

[0440] CSI-AperiodicTriggerStateList information element

[0441] -- ASN1START

[0442] -- TAG-CSI-APERIODICTRIGGERSTATELIST-START

[0443] CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState

[0444] CSI-AperiodicTriggerState ::= SEQUENCE {

[0445] associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ...

[0447] }

[0448] CSI-AssociatedReportConfigInfo ::= SEQUENCE {

[0449] reportConfigId CSI-ReportConfigId,

[0450] resourcesForChannel CHOICE {

[0451] nzp-CSI-RS SEQUENCE {

[0452] resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

[0453] qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- CondAperiodic

[0454] },

[0455] csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)

[0456] },

[0457] csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference

[0458] nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ...

[0460] }

[0461] -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP

[0462] -- ASN1STOP

[0463] [Table 17]

[0464]

[0465]

[0466]

[0467] CSI-SemiPersistentOnPUSCH-TriggerStateList

[0468] The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure a list of trigger states for channel state information semi-persistent reporting on L1 signaling for a UE. See also TS 38.214

[19] , clause 5.2.

[0469] [Table 18]

[0470]

[0471] Regarding the aforementioned CSI reporting settings (CSI-ReportConfig), each reporting setting CSI-ReportConfig can be associated with one downlink (DL) bandwidth part, which is identified by the higher layer parameter bandwidth part identifier (bwp-id) provided by the CSI resource setting CSI-ResourceConfig associated with the corresponding reporting setting. For the time domain reporting of each reporting setting CSI-ReportConfig, the “aperiodic”, “semi-persistent” and “periodic” schemes can be supported, which can be configured for the terminal by the base station through the high layer configured parameter reportConfigType. The semi-persistent CSI reporting method can support the “PUCCH-based semi-persistent (semi-PersistentOnPUCCH)” method and the “PUSCH-based semi-persistent (semi-PersistentOnPUSCH)” method. For the periodic or semi-persistent CSI reporting method, the PUCCH or PUSCH resource where the CSI is sent can be configured for the terminal by the base station through high layer signaling. The periodicity and slot offset of the PUCCH or PUSCH resource where the CSI is sent can be given by the numerology of the uplink (UL) bandwidth part configured for the CSI reporting transmission. For the aperiodic CSI reporting method, the PUSCH resource where the CSI is sent can be scheduled for the terminal by the base station via L1 signaling (e.g., the aforementioned DCI format 0_1).

[0472] Regarding the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI report configuration CSI-ReportConfig can include S (≥1) CSI resource sets (e.g., given by higher layer parameter csi-RS-ResourceSetList). The CSI resource set list can include a non-zero power (NZP) CSI-RS resource set and a SS / PBCH block set, or can include a CSI-interference measurement (CSI-IM) resource set. Each CSI resource setting can be located in a downlink (DL) bandwidth part identified by a higher layer parameter bwp-id, and can be connected to a CSI report setting in the same downlink bandwidth part. The time domain operation of a CSI-RS resource in a CSI resource setting can be configured as one of "aperiodic", "periodic", or "semi-persistent" indicated by a higher layer parameter resourceType. Regarding a periodic or semi-persistent CSI resource setting, the number of CSI-RS resource sets can be limited to S (S=1), and the configured periodicity and slot offset can be determined based on the numerology of the downlink bandwidth part identified by bwp-id. A base station can configure one or more CSI resource settings for channel or interference measurement for a terminal via higher layer signaling, for example, at least one CSI resource setting can include at least one of the following CSI resources.

[0473] - CSI-IM resource for interference measurement

[0474] - NZP CSI-RS resource for interference measurement

[0475] - NZP CSI-RS resource for channel measurement

[0476] Regarding the CSI-RS resource set associated with a resource setting configured as "aperiodic", "periodic", or "semi-persistent" by a higher layer parameter resourceType, the trigger state of a CSI report setting with reportType configured as "aperiodic", and the resource setting for channel or interference measurement on one or more component carriers (CCs), can be configured via a higher layer parameter CSI-AperiodicTriggerStateList.

[0477] Aperiodic CSI reporting of a terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, semi-persistent CSI reporting can be performed using PUSCH when triggered or activated via DCI, and can be performed using PUCCH after activated via MAC control element (MAC CE). As described above, the CSI resource setting can also be configured to be aperiodic, periodic, or semi-persistent. The combination between the CSI reporting setting and the CSI resource configuration can be supported based on Table 19 (Table 5.2.1.4-1: Triggering / activation of CSI reporting for possible CSI-RS configurations).

[0478] [Table 19]

[0479]

[0480] Aperiodic CSI reporting can be triggered by the "CSI request" field in the above-described DCI format 0_1, which corresponds to scheduling DCI for PUSCH. The terminal can monitor the PDCCH, acquire the DCI format 0_1, and acquire the scheduling information for PUSCH and the CSI request indicator. The CSI request indicator can be configured to have NTS(=0, 1, 2, 3, 4, 5, or 6) bits, and can be determined through higher layer signaling (reportTriggerSize). One of one or more aperiodic CSI reporting trigger states that can be configured via higher layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0481] - When all bits in the CSI request field are 0, this can indicate that no CSI reporting is requested.

[0482] - If the number M of CSI trigger states configured in CSI-AperiodicTriggerStateLite is greater than 2NTs-1, the M CSI trigger states can be mapped to 2NTs-1 trigger states according to a predefined mapping relationship, and one of the 2NTs-1 trigger states can be indicated by the CSI request field.

[0483] - If the number M of CSI trigger states configured in CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states can be indicated by the CSI request field.

[0484] Table 20 below can show an example of the relationship between the CSI request indicator and the CSI trigger state that can be indicated by the indicator.

[0485] [Table 20]

[0486]

[0487] The terminal can measure the CSI resource in the CSI triggering state triggered via the CSI request field, and then generate the CSI (including at least one of the above-mentioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) based on the measurement result. The terminal can transmit the acquired CSI by using the PUSCH scheduled via the corresponding DCI format 0_1. If one bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 indicates "1", the terminal can multiplex the uplink data (UL-SCH) and the acquired CSI on the PUSCH resource scheduled by the DCI format 0_1 to transmit both. If one bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 indicates "0", the terminal can map only the CSI to the PUSCH resource scheduled by the DCI format 0_1 without including the uplink data (UL-SCH) to transmit the CSI.

[0488] Figure 4 A schematic diagram of an aperiodic CSI reporting method according to an embodiment of the disclosure is shown.

[0489] Referring to Figure 4 , the terminal can acquire the DCI format 0_1 by monitoring the PDCCH 401, and acquire the scheduling information for the PUSCH 405 and the CSI request information therefrom. The terminal can acquire the resource information of the CSI-RS 402 to be measured from the received CSI request indicator. The terminal can determine the time point at which the terminal needs to measure the CSI-RS 402 resource based on the time point at which the DCI format 0_1 is received, and the offset parameter 403 or 413 (for example, the aforementioned aperiodicTriggeringOffset) in the CSI resource set configuration (for example, the NZP-CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the terminal can be configured with the offset X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station via higher layer signaling, and the configured offset X can refer to the offset between the time slot in which the DCI for triggering the aperiodic CSI reporting is received and the time slot in which the CSI-RS resource is transmitted. For example, there can be a mapping relationship between the value of the parameter aperiodicTriggeringOffset and the offset X as shown in Table 21.

[0490] [Table 21]

[0491]

[0492] Figure 4 The example 400 in FIG. 13 illustrates a case where the aforementioned offset X is configured as 0 (X = 0). In this case, the terminal can receive the CSI-RS 402 in the slot (corresponding to Figure 4 slot 0 406 of FIG. 13) in which the DCI format 0_1 triggering the aperiodic CSI report is received, and report the CSI information measured based on the received CSI-RS to the base station via the PUSCH 405. The terminal can acquire the scheduling information of the PUSCH 405 for the CSI report from the DCI format 0_1 (i.e., the scheduling information corresponding to each field in the aforementioned DCI format 0_1). For example, in the DCI format 0_1, the terminal can acquire the slot information in which the PUSCH 405 is to be transmitted from the aforementioned time domain resource allocation information of the PUSCH 405. In Figure 4 the example 400 of FIG. 13, the terminal acquires 3 as the K2 value 404 and 414 corresponding to the slot offset from the PDCCH to the PUSCH, and thus, the PUSCH 405 can be transmitted in slot 3 409, which is spaced apart by 2 slots from the slot 1 407 and by 3 slots from the slot 0 406, i.e., the point in time at which the PDCCH 401 has been received.

[0493] In the example 410 of FIG. 14, Figure 4 the terminal can acquire the DCI format 0_1 by monitoring the PDCCH 411, and can acquire the scheduling information for the PUSCH 415 and the CSI request information therefrom. The terminal can acquire the resource information of the CSI-RS 412 to be measured from the received CSI request indicator. Figure 5A The example 410 of FIG. 14 illustrates an example in which the aforementioned offset X of the CSI-RS is configured as 1 (X = 1). In this case, the terminal can receive the CSI-RS 412 in the slot (corresponding to Figure 5A slot 0 416 of FIG. 14, followed by slot 1 417, slot 2 418, and slot 3 419) in which the DCI format 0_1 triggering the aperiodic CSI report is received, and can report the CSI information measured based on the received CSI-RS to the base station via the PUSCH 415.

[0494] The aperiodic CSI reporting can include at least one or both of CSI part 1 and CSI part 2, and when the aperiodic CSI reporting is transmitted via the PUSCH, the aperiodic CSI reporting can be multiplexed on a transport block. After the CRC is inserted into the input bits for the multiplexed aperiodic CSI, encoding and rate matching can be performed, and then transmission can be performed by mapping to resource elements within the PUSCH in a specific pattern. The CRC insertion can be omitted depending on the encoding method or the length of the input bits. The number of modulation symbols calculated for rate matching during multiplexing of the CSI part 1 or the CSI part 2 included in the aperiodic CSI reporting can be calculated as shown in Table 22.

[0495] [Table 22]

[0496]

[0497]

[0498]

[0499] In particular, for the repetition PUSCH transmission schemes A and B, the terminal can multiplex the aperiodic CSI reporting only on the first repetition transmission among the repetition PUSCH transmissions to ensure that the same content is transmitted. This is because the multiplexed aperiodic CSI reporting information is encoded using a polar code scheme, in which case, if the data is to be transmitted on multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation; and since each actual repetition can have a different OFDM symbol length, in particular for the PUSCH repetition transmission type B, the aperiodic CSI reporting can be multiplexed and transmitted only on the first PUSCH repetition.

[0500] In addition, for the repetition PUSCH transmission scheme B, when the terminal receives the DCI for activating the semi-persistent CSI reporting or scheduling the aperiodic CSI reporting but does not schedule the transport block, even if the number of repetition PUSCH transmissions configured via the higher layer signaling is greater than 1, the value of the nominal repetition number can be assumed to be 1. In addition, when the aperiodic or semi-persistent CSI reporting is scheduled or activated based on the repetition PUSCH transmission scheme B but the transport block is not scheduled, the terminal can expect that the first nominal repetition is the same as the first actual repetition. For the PUSCH transmitted including the semi-persistent CSI, based on the repetition PUSCH transmission scheme B, if the first nominal repetition is different from the first actual repetition after the semi-persistent CSI reporting is activated by the DCI but is not subsequently scheduled by the DCI, the transmission for the first nominal repetition can be ignored.

[0501] PUCCH: UCI on PUSCH

[0502] In the 5G communication system, when an uplink control channel overlaps with an uplink data channel and a transmission time condition is satisfied, or when L1 signaling or higher layer signaling indicates transmission of uplink control information via the uplink data channel, the uplink control information can be included in the uplink data channel so as to be transmitted. In this case, a total of three pieces of uplink control information of HARQ-ACK, CSI part 1, and CSI part 2 can be transmitted via the uplink data channel, and each piece of uplink control information can be mapped to the PUSCH according to a predetermined multiplexing rule.

[0503] More specifically, in the first operation, if the number of HARQ-ACK information bits to be included in the PUSCH is 2 bits or less, the terminal can reserve the REs for HARQ-ACK transmission. In this case, the method of determining the resources to be reserved by the terminal is the same as in the second operation. However, the number and location of the REs to be reserved can be determined by assuming that the number of HARQ-ACK bits is 2. For example, in Equation 12-A below, the terminal can perform the calculation based on Oack=2. In the second operation, if the number of HARQ-ACK information bits to be transmitted by the terminal is greater than 2 bits, the terminal can map the HARQ-ACK from the first OFDM symbol after the first DMRS symbol, excluding the DMRS. In the third operation, the terminal can map the CSI part 1 to the PUSCH. In this case, the CSI part 1 can be mapped from the first OFDM symbol excluding the DMRS, and can not be mapped to the REs reserved in the first operation and the REs to which the HARQ-ACK is mapped in the second operation.

[0504] In the fourth operation, the terminal can map the CSI part 2 to the PUSCH. In this case, the CSI part 2 can be mapped from the first OFDM symbol excluding the DMRS, and can not be mapped to the REs in which the CSI part 1 is located and the REs to which the HARQ-ACK mapped in the second operation. However, the CSI part 2 can be mapped to the REs reserved in the first operation. When there is an UL-SCH, the terminal can map the UL-SCH to the PUSCH. In this case, the UL-SCH can be mapped from the first OFDM symbol excluding the DMRS, and can not be mapped to the REs in which the CSI part 1 is located, the REs to which the HARQ-ACK mapped in the second operation, and the REs in which the CSI part 2 is located. However, the CSI part 2 can be mapped to the REs reserved in the first operation.

[0505] In the fifth operation, if the HARQ-ACK is less than 2 bits, the terminal can puncture the HARQ-ACK and map it to the REs reserved in the first operation. The number of REs to which the HARQ-ACK is mapped can be calculated based on the actual number of HARQ-ACK. For example, the number of REs to which the HARQ-ACK is actually mapped can be less than the number of REs reserved in the first operation. Puncturing means that even if the CSI part 2 or the UL-SCH has been mapped to the REs in which the HARQ-ACK needs to be mapped in the fourth operation, the mapped CSI part 2 or UL-SCH is replaced with ACK. The CSI part 1 can not be mapped to the reserved REs, so that puncturing by the HARQ-ACK does not occur. This can indicate that the CSI part 1 has a higher priority than the CSI part 2 and can be better decoded. If the number of bits (or the number of modulation symbols) of the uplink control information to be mapped to the PUSCH is greater than the number of bits (or REs) available for uplink control information mapping in the corresponding OFDM symbol to be mapped, the frequency axis RE interval d between the modulation symbols of the uplink control information to be mapped can be configured as d = 1. If the number of bits (or the number of modulation symbols) of the uplink control information to be mapped to the PUSCH is less than the number of bits (or RE0) available for uplink control information mapping in the corresponding OFDM symbol to be mapped, the frequency axis RE interval d between the modulation symbols of the uplink control information to be mapped can be configured as d = floor (available number of bits on l-OFDM symbol / un-mapped UCI bit number at the start of l-OFDM symbol).

[0506] Figure 5A 、 5B and 5C illustrates uplink control information mapped to a PUSCH according to various embodiments of the disclosure.

[0507] Reference is made to Figure 5A 、 5B and 5C, in Figure 5B 、 5B and 5C, the number of HARQ-ACK symbols to be mapped to the PUSCH can be assumed to be 5, and the PUSCH can be assumed to be configured or scheduled with one resource block. First, with reference to Figure 5C , the terminal can map the 5 symbols of HARQ-ACK 501 on the frequency axis with an interval of d = floor (12 / 5) = 2 from the lowest RE index (or the highest RE index) of the first OFDM symbol 504, which does not include a DMRS after the first DMRS. Subsequently, with reference to Figure 6 , the terminal can map the CSI part 1 502 from the first OFDM symbol 505 except for the DMRS 500. Finally, with reference to Figure 6, the terminal can map the CSI part 2503 from the first OFDM symbol 506 not including the DMRS to the REs of the CSI part 1 and HARQ-ACK is not mapped to.

[0508] When the HARQ-ACK is transmitted on the PUSCH (or CG-PUSCH), the number of coded modulation symbols can be determined by Equation 12-A below.

[0509]

[0510] … Equation 12-A

[0511] Here, may denote the number of bits of the HARQ-ACK payload, and may denote the number of CRC bits. More specifically, , otherwise , , , , , and may denote the r-th code block size of the UL-SCH, and may denote the number of subcarriers per OFDM symbol available for UCI transmission in the PUSCH configured or scheduled by the base station. In addition, and are values configured by the base station, and can be determined through higher layer signaling or L1 signaling. More specifically, , i.e., beta offset, is a defined value for determining the number of resources when the HARQ-ACK information is multiplexed and transmitted with other UCI information to the PUSCH (or CG-PUSCH). If the fallback DCI (or DCI format 0_0) or non-fallback DCI (or DCI format 0_1) indicating the PUSCH transmission does not have the beta_offset indicator field, and the terminal is configured with the beta offset as "semi-static" through the higher layer, the terminal can be configured with one beta offset via the higher layer configuration. In this case, the beta offset can have values as shown in Table 23, the index of the corresponding value can be indicated via the higher layer configuration, and according to the HARQ-ACK information bits, the index 、 and The beta offset can correspond to the case where the HARQ-ACK information bits are less than or equal to 2, the HARQ-ACK information bits are greater than 2 and less than or equal to 11, and the HARQ-ACK information bits are greater than 11, respectively. In addition, the beta offset can also be configured for CSI-1 and CSI-2 in the same manner. The code rate of the UCI can be adjusted by the beta offset with respect to the effective code rate of the UL-SCH. For example, when the beta offset is 2 (e.g., index = 1), the code rate of the UCI can be configured to be transmitted at a code rate that is 1 / 2 lower than the effective code rate of the UL-SCH.

[0512] [Table 23]

[0513]

[0514]

[0515] If the base station schedules the PUSCH transmission of the terminal by using the non-fallback DCI (or DCI format 01) and the non-fallback DCI includes the beta offset indicator field, i.e., the beta offset is set to "dynamic" via higher layer configuration, the base station can configure the beta offset for the four sets as shown in Table 24 (with , or ) in the case of HARQ-ACK, and configure the same value for the terminal. The terminal can indicate the beta offset used for HARQ-ACK multiplexing through the beta_offset indicator field. Each index can be determined in the same manner as the above-described method according to the HARQ-ACK information bits. The terminal can indicate the sets of and in the same manner.

[0516] [Table 24]

[0517]

[0518] For the HARQ-ACK transmission on the actual repetition of the PUSCH with Type B repetition of the UL-SCH, the number of coded modulation symbols per layer for the HARQ-ACK transmission ( ), denoted as , is determined as follows:

[0519]

[0520] … Equation 12-B

[0521] In Equation 12-B,

[0522] - is the OFDM symbol the number of resource elements available for transmission of UCI in an OFDM symbol In a PUSCH transmission assuming nominal repetitions without segmentation, and is the total number of OFDM symbols in the nominal repetitions of PUSCH, including all OFDM symbols used for DMRS;

[0523] - for any OFDM symbol of the PUSCH assuming nominal repetitions without segmentation that carries DMRS, ;

[0524] - for any OFDM symbol of the PUSCH assuming nominal repetitions without segmentation that does not carry DMRS, where is the number of subcarriers in the OFDM symbols carrying PTRS in a PUSCH transmission assuming nominal repetitions without segmentation ;

[0525] - the number of resource elements available for transmission of UCI in an OFDM symbol , for , in an actual repetition of the PUSCH transmission, and is the total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols used for DMRS;

[0526] - for any OFDM symbol of the actual repetition of the PUSCH transmission that carries DMRS, ;

[0527] - for any OFDM symbol of the actual repetition of the PUSCH transmission that does not carry DMRS, where is the number of subcarriers in the OFDM symbols carrying PTRS in an actual repetition of the PUSCH transmission ; and

[0528] - for PUSCH not using repetition Type B, the remaining symbols in the equation are defined to be the same.

[0529] When HARQ-ACK is transmitted on PUSCH (or CG-PUSCH), if there is no UL-SCH, the number of coded modulation symbols can be determined by the following Equation 12-C.

[0530]

[0531] … Equation 12-C

[0532] In Equation 12-C, R is a code rate of the PUSCH, which is a value configured by a base station and can be determined via a higher layer signaling or an L1 signaling. Also, Q m may represent an order of a PUSCH modulation scheme.

[0533] Based on the determination of the UCI information size in Equation 12-A and Equation 12-B , the number of code word bits of ACK may be obtained.

[0534] Figure 6 is a schematic diagram illustrating a process of transmitting and / or receiving UCI information between a terminal and a base station via a PUSCH according to an embodiment of the disclosure.

[0535] Referring to Figure 6 , in operation 600, the terminal can generate UCI information. In operation 602, the terminal can determine a UCI information size, and if the size is 11 bits or less, CRC can not be included. On the other hand, if the size is greater than 12 bits, the terminal can additionally perform code block segmentation according to the UCI information size, or CRC can be included. In operation 604, if the UCI information size is 11 bits or less, the terminal can perform channel coding of a small block length. On the other hand, if the size is greater than 12 bits, the terminal can perform polar coding. In operation 606, the terminal can perform rate matching according to Equation 6 to Equation 12-C according to a UCI information type to calculate the number of coded modulation symbols. In operation 608, the terminal can combine code blocks. In operation 610, the terminal can multiplex coded UCI bit information on a PUSCH. In operation 612, after the terminal transmits the modulated PUSCH to the base station, the base station can demodulate the PUSCH received from the terminal and perform de-multiplexing of the coded UCI bits in the PUSCH. In operation 614, the base station can divide the received information into code blocks. In operation 616, the base station can perform rate de-matching. In operation 618, the base station can perform decoding according to a coded channel coding scheme according to the UCI information size. In operation 620, the base station can combine the decoded code blocks and acquire UCI information. The UCI information can be transmitted and / or received by being included in the PUSCH via the above-described series of processes. Figure 7 The flowchart described in the above Figure 7 may be omitted under certain conditions. Also, it is possible to perform operations by adding blocks other than the operations 600 to 622 included in the flowchart described in the above

[0536] Subsequently, in Table 25, a description of a process of multiplexing uplink data and control information will be provided.

[0537] [Table 25]

[0538]

[0539]

[0540]

[0541] In the process of Table 25 described above, the terminal can determine whether HARQ-ACK exists, and perform resource reservation determination or rate matching according to the HARQ-ACK. Then, the terminal can sequentially determine the presence or absence of CG-UCI, the presence or absence of CSI part 1, and the presence or absence of CSI part 2. The terminal can determine the presence or absence based on information indicating that at least one symbol of the PUCCH overlaps with the PUSCH allocated resource, or information including specific UCI information in the DCI for PUSCH scheduling. Then, the terminal can map the data resource, and if the HARQ-ACK has 2 bits or less, the terminal can map the control information to the reserved resource.

[0542] [PUCCH / PUSCH: priority]

[0543] Hereinafter, a terminal transmission scheme according to priority information of PUCCH and PUSCH will be described.

[0544] When one terminal supports eMBB and URLLC at the same time, the terminal can transmit eMBB data or control information through PUSCH or PUCCH, and can transmit URLLC data or control information through PUSCH or PUCCH. The needs of the two services are different, and generally the URLLC service is prioritized over the eMBB service, so when at least one symbol in the channel allocated to eMBB overlaps with the channel allocated to URLLC, the terminal can select at least one of the URLLC or eMBB channel to perform transmission. More specifically, the priority information of PUSCH or PUCCH can be indicated by high layer signaling or L1 signaling, and the priority information value can be 0 or 1. The PUCCH or PUSCH indicated by 0 can be considered for eMBB, and the PUCCH or PUSCH indicated by 1 can be considered for URLLC. Of course, the present disclosure is not limited to the above-described example.

[0545] For PUSCH, when there is a field in DCI that can indicate priority information, the priority of the PUSCH can be determined by the value indicated by the field. Even for the PUSCH scheduled by DCI, if there is no field in the DCI indicating the priority, the terminal can consider the PUSCH to have a priority value of 0. The PUSCH scheduled by DCI applies to the case including aperiodic CSI or semi-persistent CSI, as well as the case not including aperiodic CSI or semi-persistent CSI. For a configured grant PUSCH that is periodically transmitted and / or received without DCI, its priority can be determined by higher layer signaling.

[0546] For PUCCH, the PUCCH for transmitting and / or receiving SR information, and the PUCCH including HARQ-ACK information for a semi-persistent scheduling (SPS) PDSCH, its priority can be determined by higher layer signaling. For the PUCCH including HARQ-ACK information on a PDSCH scheduled by DCI, when there is a priority field in the DCI, the terminal can apply the priority value indicated by the priority field. If there is no priority field, the terminal can consider the PUCCH including HARQ-ACK information to have a priority value of 0. In addition, the terminal can consider the PUCCH including semi-persistent CSI or periodic CSI to always have a priority value of 0.

[0547] When PUSCH or PUCCH resources indicated by L1 signaling such as DCI or higher layer signaling overlap, and at least part of the PUCCH or PUSCH has different priority information, the terminal can first resolve the overlap between the PUCCH and the PUSCH with a priority information value of 0. For example, a series of procedures of adding UCI information included in the PUCCH to the PUSCH can be included. Then, when the overlapping PUCCH or PUSCH resource finally determined via the low-priority PUCCH or PUSCH is referred to as a second PUCCH or a second PUSCH, and the high-priority PUCCH or PUSCH is referred to as a first PUCCH or a first PUSCH, if the second PUCCH or the second PUSCH overlaps the first PUCCH or the first PUSCH in time resources, the terminal can cancel the transmission of the second PUCCH and the second PUSCH. The terminal can expect the transmission of the first PUCCH or the first PUSCH to be performed in After that, i.e., at least after the last symbol of the PDCCH reception including the DCI scheduling the transmission. Otherwise, the terminal can consider it as an error case. The value proposed in Equation 2 can be used value of.

[0548] According to the above description, the PUCCH for the HARQ-ACK information of the PDSCH including the eMBB data can have a low priority value 0, and the PUCCH for the HARQ-ACK information of the PDSCH including the URLLC data can have a high priority value 1. Thus, when the PUCCH having the priority value 0 overlaps with the PUCCH having the priority value 1 in a time resource, the terminal can discard the PUCCH having the priority value 0 and transmit the PUCCH having the priority value 1. Thus, from the perspective of the base station, since the HARQ-ACK information of the PDSCH including the eMBB data is received in failure, the base station cannot determine whether the terminal correctly received the eMBB data, and thus can need to retransmit the eMBB data. Thus, there can be a possibility of degradation in transmission and / or reception efficiency of the eMBB data.

[0549] For convenience of description, the HARQ-ACK information for the PDSCH including the eMBB data can be referred to as a low priority (LP) HARQ-ACK, and the HARQ-ACK information for the PDSCH including the URLLC data can be referred to as a high priority (HP) HARQ-ACK. The LP HARQ-ACK can refer to the HARQ-ACK information having the priority value 0, and the HP HARQ-ACK can refer to the HARQ-ACK information having the priority value 1. Of course, the present disclosure is not limited to the above-described example. A method of preventing degradation in transmission and / or reception efficiency of the eMBB data can include multiplexing the HP HARQ-ACK and the LP HARQ-ACK on one PUCCH or PUSCH channel at the same time. Thus, when the HP HARQ-ACK is multiplexed with the LP HARQ-ACK on the PUCCH or the PUSCH, there can be a case of multiplexing with the existing CSI part 1 and CSI part 2. If the base station or the terminal supports multiplexing of at most three pieces of UCI information on the PUCCH or the PUSCH, a method of determining information to be discarded among four pieces of information and selecting the remaining information is needed.

[0550] Hereinafter, in an embodiment of the present disclosure, a method of multiplexing UCI information on a PUSCH in an environment in which there are a HP HARQ-ACK and a LP HARQ-ACK will be described. Further, even if the HP HARQ-ACK and the LP HARQ-ACK are the same HARQ-ACK information, the two have different requirements, and thus the HP HARQ-ACK can need to be transmitted more reliably than the LP HARQ-ACK, and accordingly different coding and rate matching methods can be employed. For example, when the number of coded modulation symbols of the HP HARQ-ACK and the LP HARQ-ACK is determined according to Equation 12-A, at least or different values. In addition, when HP HARQ-ACK and LP HARQ-ACK are multiplexed on one PUSCH, HP HARQ-ACK can adopt Equation 12-A, while the number of coded modulation symbols (N^mod) for LP HARQ-ACK transmission on PUSCH (or CG-PUSCH) can be determined by Equation 13-A.

[0551] Equation 13-A

[0552] For HARQ-ACK LP transmission on actual repetitions of PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK LP transmission is determined as follows:

[0553]

[0554] In addition, when there is no UL-SCH but there is CSI part 1, the number of coded modulation symbols (N^mod) can be determined by Equation 13-B.

[0555] Equation 13-B

[0556] In addition, when there is no UL-SCH but there is CSI part 1, the number of coded modulation symbols (N^mod) can be determined by Equation 13-B.

[0557] Equation 13-C

[0558] is a value determined based on Equation 12-A, Equation 12-B, or Equation 12-C, and can represent the number of coded modulation symbols per layer for HARQ-ACK, CG-UCI, or HARQ-ACK / CG-UCI transmission.

[0559] [PUCCH: Type 1 HARQ-ACK codebook]

[0560] Hereinafter, a description will be provided for a semi-static HARQ-ACK codebook (or Type 1 HARQ-ACK codebook).

[0561] Figure 7 is a schematic diagram illustrating a method of configuring a semi-static HARQ-ACK codebook (or Type 1 HARQ-ACK codebook) in a 5G communication system according to an embodiment of the disclosure.

[0562] Referring to Figure 7 ​​​​In a case where the HARQ-ACK PUCCH that the terminal can transmit in one slot is limited to 1, when receiving the configuration via the semi-static HARQ-ACK codebook high layer signaling, the terminal can report the HARQ-ACK information on the SPS PDSCH release or the PDSCH reception in the HARQ-ACK codebook in the slot indicated by the PDSCH-to-HARQ_feedback timing indicator value in the DCI format 1_x. The terminal can report the NACK for the HARQ-ACK information bit value within the HARQ-ACK codebook in the slot not indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format 1_x. If the terminal reports only the HARQ-ACK information for one PDSCH reception or one SPS PDSCH release in the case of the MAC (e.g., a set of PDSCH reception candidate cases in the serving cell c) case for the candidate PDSCH reception, and when reporting is scheduled by the DCI format 1_0 including the information indicating the counter DACI field value as 1 in the PCell, the terminal can determine one HARQ-ACK codebook for the PDSCH reception or the SPS PDSCH release.

[0563] Otherwise, the HARQ-ACK codebook can be determined following the method described below.

[0564] When the set of PDSCH reception candidate cases in the serving cell c is M A,c , M A,c can be obtained via the following [pseudo code 1] operation.

[0565] [Start of pseudo code 1]

[0566] - Operation 1: Initialize j to 0 and M A,c to an empty set. Initialize k (i.e., the HARQ-ACK transmission timing index) to 0.

[0567] - Operation 2: Configure R as a set of each corresponding row in a table including PDSCH mapping slot information, starting symbol information, and symbol length or number information. If each value indicated in R indicates a PDSCH-capable mapping symbol configured as an UL symbol according to the DL and UL configuration configured via the high layer signaling, delete the corresponding row from R.

[0568] - Operation 3-1: If the terminal can receive at most one unicast PDSCH in one slot, and R is a non-empty set, add one unicast PDSCH to the set M A,c .

[0569] - Operation 3-2: If the terminal can receive multiple unicast PDSCHs within a time slot, count the number of PDSCHs that can be allocated to different symbols in the calculated R, and add the corresponding number of unicast PDSCHs to M. A,c .

[0570] - Operation 4: Increment k by 1 and restart the operation from Operation 2.

[0571] [End of Pseudocode 1]

[0572] Using the aforementioned pseudocode 1 as... Figure 8 For example, to perform a HARQ-ACK PUCCH transmission in time slot #k 708, all candidate time slots capable of transmitting the HARQ-ACK timing indication to time slot #k 708 via PDSCH can be considered. Figure 8 In this context, it can be assumed that, based on the combination of PDSCH to HARQ-ACK timings, only PDSCHs scheduled in time slots #n 702, #n+1 704, and #n+2 706 can be transmitted via HARQ-ACK in time slot #k 708. Furthermore, based on the time-domain resource configuration information of the PDSCHs that can be scheduled in time slots 702, 704, and 706, and information indicating whether the symbols within the time slots are downlink or uplink, the terminal can deduce the maximum number of schedulable PDSCHs for each time slot. For example, when a maximum of two PDSCHs can be scheduled in time slot 702, a maximum of three PDSCHs in time slot 704, and a maximum of two PDSCHs in time slot 706, the maximum total number of PDSCHs included in the HARQ-ACK codebook transmitted in time slot 708 is seven. This can be referred to as the cardinality of the HARQ-ACK codebook.

[0573] [PUCCH: Type 2 HARQ-ACK codebook]

[0574] The following text will describe the dynamic HARQ-ACK codebook (or type 2 HARQ-ACK codebook).

[0575] Figure 8 This is a schematic diagram of a method for configuring a dynamic HARQ-ACK codebook (or a type 2 HARQ-ACK codebook) in a 5G communication system according to an embodiment of the present disclosure.

[0576] Reference Figure 8, a PDSCH-to-HARQ_feedback timing value for a PUCCH transmission based on HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release, and K0 as transmission slot position information of a PDSCH scheduled in DCI format 1_x, the terminal can transmit HARQ-ACK information through one PUCCH in slot n. Specifically, for the above HARQ-ACK information transmission, the terminal can determine a HARQ-ACK codebook for a PDCCH transmitted in a slot determined by K0 and the PDSCH-to-HARQ_feedback timing based on a downlink assignment index (DAI) included in a DCI indicating a PDSCH or SPS PDSCH release.

[0577] In an embodiment of the disclosure, the DAI can include a counter DAI and a total DAI. The counter DAI is information indicating a position of HARQ-ACK information corresponding to a PDSCH scheduled in DCI format 1_x within a HARQ-ACK codebook. Specifically, the counter DAI value in DCI format 1_x can indicate a cumulative value of SPS PDSCH release or PDSCH reception scheduled by DCI format 1_x in a specific cell c. The cumulative value can be configured based on a serving cell in which the scheduling DCI is located and a PDCCH monitoring occasion. Of course, the disclosure is not limited to the above example.

[0578] In an embodiment of the disclosure, the total DAI can be a value indicating a HARQ-ACK codebook size. Specifically, the total DAI value can indicate the total number of previously scheduled PDSCHs or SPS PDSCH releases including the time when the DCI is scheduled. In addition, the total DAI can be a parameter used when HARQ-ACK information in a serving cell c further includes HARQ-ACK information for a PDSCH scheduled in other cells including the serving cell c in a carrier aggregation (CA) scenario. In other words, there can be no total DAI parameter in a system operating in a single cell. Of course, the disclosure is not limited to the above example.

[0579] An operation example of the DAI can be seen in Figure 7 . Figure 8The change in values of the counter DAI (C-DAI) and total DAI (T-DAI) indicated by the DCI retrieved for each PDCCH monitoring occasion configured for each carrier is shown when the terminal transmits the HARQ-ACK codebook selected based on the DAI on the PUCCH 820 of the nth time slot of carrier 0 802 in the case in which two carriers are configured. First, in the DCI retrieved at m = 0 806, both the C-DAI and the T-DAI can indicate a value (812) of 1. In the DCI retrieved at m = 1 808, both the C-DAI and the T-DAI can indicate a value (814) of 2. In the DCI retrieved in carrier 0 (c = 0) 802 at m = 2 810, the C-DAI can indicate a value (816) of 3. In the DCI retrieved in carrier 1 (c = 1) 804 at m = 2 810, the C-DAI can indicate a value (818) of 4. In this case, when carrier 0 and carrier 1 are scheduled at the same monitoring occasion, all T-DAI can be indicated as 4.

[0580] Referring to Figure 9 and Figure 9 , the determination of the HARQ-ACK codebook can be performed in the case in which only one PUCCH including HARQ-ACK information is transmitted per slot, and can be referred to as mode 1. As an example of a method of determining one PUCCH transmission resource in one slot, when PDSCHs scheduled in different DCIs are multiplexed into one HARQ-ACK codebook and transmitted in the same slot, the PUCCH resource selected for HARQ-ACK transmission can be determined as the PUCCH resource designated by the PUCCH resource field indicated by the DCI that performs the last PDSCH scheduling. For example, the PUCCH resource designated by the PUCCH resource field indicated by the DCI scheduled before the current DCI can be ignored.

[0581] Hereinafter, a HARQ-ACK codebook determination method and device in a case where two or more PUCCHs including HARQ-ACK information can be transmitted in one slot will be defined, and can be referred to as mode 2. The terminal can operate only in mode 1 (transmit only one HARQ-ACK PUCCH in one slot), or operate only in mode 2 (transmit one or more HARQ-ACK PUCCHs in one slot). Alternatively, for a terminal that simultaneously supports mode 1 and mode 2, the base station can configure operation in only one mode via higher layer signaling, or can implicitly determine mode 1 and mode 2 by DCI format, RNTI, DCI specific field value, scrambling, etc. For example, PDSCH scheduled by DCI format A and HARQ-ACK information related thereto can be based on mode 1, and PDSCH scheduled by DCI format B and HARQ-ACK information related thereto can be based on mode 2. Of course, the present disclosure is not limited to the above example.

[0582] [PUCCH: Type 3 HARQ-ACK codebook]

[0583] Hereinafter, a type 3 HARQ-ACK codebook will be described.

[0584] Unlike the Type 1 and Type 2 HARQ-ACK codebooks, the Type 3 HARQ-ACK codebook is a scheme in which the terminal reports all HARQ-ACK information corresponding to all configured serving cells, HARQ process numbers, the number of TBs per HARQ process, and the number of CBGs per TB. For example, when there are 2 serving cells, each serving cell has 16 HARQ processes, each HARQ process has 1 TB, and each TB has 2 CBGs, the terminal can report a total of 64 (= 2 x 16 x 1 x 2) HARQ-ACK information bits. In addition, according to independent configuration, the terminal can also report the most recently received NDI value for each HARQ-ACK information and HARQ process related to the HARQ-ACK information. Via the NDI value reported by the terminal, the base station can determine (or identify) whether the PDSCH received by the terminal for each HARQ process is determined as an initial transmission or as a retransmission. When there is no independent NDI value report, if the terminal has already reported HARQ-ACK information for a specific HARQ process before the base station receives DCI for requesting a Type 3 HARQ-ACK codebook, the terminal maps the HARQ process as NACK; otherwise, the terminal maps the HARQ-ACK information bit to the PDSCH received for each corresponding HARQ process. The number of serving cells, HARQ process numbers, the number of TBs, and the number of CBGs can be configured independently. When the number of serving cells, HARQ process numbers, the number of TBs, and the number of CBGs are not independently configured, the terminal can default the number of serving cells to 1, the HARQ process number to 8, the number of TBs to 1, and the number of CBGs to 1. In addition, the HARQ process numbers of each serving cell can be different. In addition, the number of TBs can have different values for each serving cell or for each BWP within a serving cell. In addition, the number of CBGs can be different between different serving cells. Of course, the present disclosure is not limited to the above examples.

[0585] One of the reasons for requiring a Type 3 HARQ-ACK codebook is that there is a case where the terminal cannot transmit a PUCCH or PUSCH including HARQ-ACK information corresponding to a PDSCH due to channel connection failure, collision with a high priority channel, etc. Therefore, it is reasonable for the base station to request to report only HARQ-ACK information without re-scheduling a separate PDSCH. Therefore, the base station can schedule a Type 3 HARQ-ACK codebook and a PUCCH resource including the corresponding codebook via higher layer signaling or L1 signaling (e.g., a specific field in DCI).

[0586] If the terminal searches for a DCI format including 1 as a field value for requesting a single-time HARQ-ACK, a PUCCH or PUSCH resource for multiplexing a type 3 HARQ-ACK codebook in a specific slot indicated by the DCI can be determined. Further, the terminal can multiplex only a type 3 HARQ-ACK codebook for transmission within a PUCCH or PUSCH of the corresponding slot. For example, if two PUCCHs overlap, one of which is a type 1 HARQ-ACK codebook (or a type 2 HARQ-ACK codebook) and the other is a type 3 HARQ-ACK codebook, the terminal multiplexes only the type 3 HARQ-ACK codebook on the PUCCH or PUSCH. This is because the type 3 HARQ-ACK codebook includes HARQ-ACK information bits for all serving cells, all HARQ process numbers, all transport blocks, and all code block groups configured for the terminal, and thus the information of the type 1 HARQ-ACK codebook and the type 2 HARQ-ACK codebook can be considered to be already included in the type 3 HARQ-ACK codebook.

[0587] However, since the type 3 HARQ-ACK codebook includes all HARQ-ACK information bits based on information configured for all terminals, even if the HARQ-ACK information bits are mapped as NACK, the HARQ-ACK information bits for PDSCHs actually not scheduled can need to be included in the above-described codebook, thereby possibly causing a problem of a large information bit size. Accordingly, when the uplink control information bit size increases, there can be a possibility that uplink transmission coverage or transmission reliability decreases. Accordingly, a HARQ-ACK codebook having a size smaller than the type 3 HARQ-ACK codebook can be required. In the present disclosure, the HARQ-ACK codebook can be considered as different from the existing type 3 HARQ codebook, and for convenience, can be referred to as an enhanced type 3 HARQ-ACK codebook (or a type 4 HARQ-ACK codebook). However, it is entirely possible that the HARQ-ACK codebook is replaced with other names. For example, the enhanced type 3 HARQ-ACK codebook can be configured in the following manner. Of course, the present disclosure is not limited to the following example.

[0588] - Type A: subset of total set of (configured) serving cells

[0589] - Type B: subset of total set of (configured) HARQ process numbers

[0590] - Type C: subset of total set of (configured) TB indices

[0591] - Type D: subset of total set of (configured) CBG indices

[0592] - Type E: combination of at least two of Type A to Type D

[0593] An enhanced Type 3 HARQ-ACK codebook can have at least one feature of Type A to Type E and can be configured by one or more sets. An enhanced Type 3 HARQ-ACK codebook can include the total set of Type A to Type E, not a subset thereof. Regarding the meaning of multiple sets, for example, Type A and Type B can exist at the same time, or different subsets can exist even for Type A. Based on Type A to Type E, an enhanced Type 3 HARQ-ACK codebook can be indicated via higher layer signaling, L1 signaling, or a combination thereof. For example, as shown in Table 26 below, the set configuration of HARQ-ACK information bits to be reported in each enhanced Type 3 HARQ-ACK codebook can be indicated via higher layer signaling, and one of the values can be indicated by L1 signaling. As shown in Table 26, the type of the enhanced Type 3 HARQ-ACK codebook configured for each index can be separately configured via higher layer signaling. In addition, a Type 3 HARQ-ACK codebook for reporting all HARQ-ACK information bits can be used for a specific index, such as index 3. If not separately indicated via higher layer signaling or higher layer signaling does not exist, the use of a Type 3 HARQ-ACK codebook can be determined based on a default value (e.g., ACK or NACK status for all HARQ process numbers).

[0594] [Table 26]

[0595]

[0596] The terminal can receive a value for a one-shot HARQ-ACK feedback field, and when receiving a value indicated by index 1 in Table 26, the terminal can report a total of 8 bits of HARQ-ACK information for service cell i, HARQ process number (#1 to #8), and TB 1. The terminal can receive a value for a one-shot HARQ-ACK feedback field, and when receiving a value indicated by index 2 in Table 26, the terminal can report a total of 4 bits of HARQ-ACK information for service cell i, HARQ process number (#1 to #4), and TB 1. The terminal can receive a value for a one-shot HARQ-ACK feedback field, and when receiving a value indicated by index 3 in Table 26, the terminal can calculate the total number of HARQ-ACK bits by considering the service cell set, the total number of HARQ processes for each service cell i, the number of TBs for each HARQ process, and the number of CBGs for each TB. Of course, the disclosure is not limited to the above-described example. For example, the above-described Table 26 is merely an example, and the total number of indexes can be more or less than this number, and the range of HARQ process values indicated by each index and / or information included in the enhanced Type 3 HARQ-ACK codebook can be different. In addition, Table 26 can be information indicated by higher layer signaling, and a specific index can be notified via DCI. In addition, in addition to the above-described Table 26, HARQ-ACK information indicated via a specific index value or a one-shot HARQ-ACK feedback field (or another L1 signaling) can be used for the following purpose: when specific HARQ-ACK information scheduled in advance for the terminal to transmit is discarded in addition to HARQ-ACK information for a specific (or all) HARQ process number, retransmitting specific HARQ-ACK information for the terminal to transmit. This can be referred to as discarded HARQ-ACK retransmission. Here, when overlapping with another PUCCH or PUSCH having a higher priority than the PUCCH or PUSCH including the HARQ-ACK information occurs, the discard can occur. Alternatively, when at least one symbol of the PUCCH or PUSCH including the HARQ-ACK information has been pre-indicated as a downlink symbol by higher layer signaling, the discard can occur. Alternatively, when the PUCCH or PUSCH including the HARQ-ACK information overlaps with at least a part of the resource indicated by the DCI including the uplink cancellation information for the purpose of canceling the uplink transmission, the discard can occur.When the terminal supports both the dropped HARQ-ACK retransmission and the (enhanced) type 3 HARQ codebook-based transmission, the terminal can report the HARQ-ACK information by selecting at least one of the dropped HARQ-ACK retransmission and the (enhanced) type 3 HARQ codebook-based transmission via at least one of information or a combination of MCS, RV, NDI, HARQ process ID, etc., priority information in the DCI field, a search space type in which the DCI is searched, or CRC and scrambling RNTI information of the DCI. Alternatively, a specific index value in Table 26 can be configured and used for the dropped HARQ-ACK retransmission. The specific index selection in Table 26 can be indicated by at least one of the HARQ process number, the MCS, the NDI, the RV, the frequency domain resource allocation information, or the time resource allocation information in the DCI field or a combination of two or more thereof. The DCI bit field size indicating the specific index in Table 26 can be configured by. is determined. In this case, may represent the total number of indexes in Table 26 configured through higher layer signaling.

[0597] The total number N of HARQ-ACK bits can be represented as Equation 14 below.

[0598] Equation 14

[0599] In Equation 14, n(c) can represent the total number of serving cells c, Hc can represent the number of HARQ process numbers configured in the serving cell c, represents the number of TBs configured for each HARQ process in the BWP b and the serving cell c, and Bc can represent the number of CBGs configured in the serving cell c. In addition, when the terminal searches for the DCI format having the single HARQ-ACK request field value of 1, the terminal can determine the PUCCH or PUSCH resource for multiplexing the corresponding type 3 HARQ-ACK codebook (or enhanced type 3 HARQ-ACK codebook). In addition, the terminal can multiplex only the type 3 HARQ-ACK codebook (or enhanced type 3 HARQ-ACK codebook) on the PUCCH or PUSCH resource determined for transmission in the corresponding slot. If there is a PUCCH or PUSCH including SR information or CSI information and overlapping the PUCCH or PUSCH, the terminal can drop the SR information or the CSI information without multiplexing. For example, the terminal can multiplex only the type 3 HARQ-ACK information and drop the other UCI of the SR and the CSI.

[0600] [PUCCH power control]

[0601] Hereinafter, the PUCCH power control will be described. Equation 15 below is an equation for determining the PUCCH transmission power.

[0602]

[0603] [dBm]…Equation 15

[0604] In Equation 15, is a reference configuration transmission power configuration value, which can have different values according to different transmission types , and can be adjusted through higher layer signaling (such as RRC or MAC CE). If the value is changed via MAC CE, the terminal can determine to apply the changed value from the slot , when the slot in which HARQ-ACK has been transmitted is k, with respect to the PDSCH on which the MAC CE is received. may have different values according to subcarrier spacing, respectively, and can be exemplified in 3ms. is the size of the frequency domain resource region to which the PUCCH is allocated. is the estimated path attenuation value of the terminal, which the terminal can calculate based on a specific reference signal among various CSI-RSs or SS / PBCHs according to the type and configuration via higher layer signaling. The same can be applied to the PUCCH repeatedly transmitted. The same can be applied to the PUCCH repeatedly transmitted.

[0605] For PUCCH formats 2, 3, and 4, when the UCI size is greater than or equal to 11, the value of in Equation 15 is determined by the following Equation 16.

[0606]

[0607] …Equation 16

[0608] In Equation 16, may be 6, indicates the number of HARQ-ACK bits, the parameter indicates the number of SR bits, indicates the number of CSI bits, indicates the number of resource elements (REs) of the PUCCH.

[0609] [PDSCH: SPS]

[0610] Hereinafter, SPS operation will be described. When a terminal supports two or more activated DL SPS operations in one cell and / or one BWP, a base station can configure two or more DL SPS configurations for one terminal. The reason for supporting two or more DL SPS configurations is that when a terminal supports multiple types of services, each service can have a different MCS, time / frequency domain resource allocation, or periodicity, and thus it can be advantageous to configure a corresponding DL SPS for each service purpose.

[0611] The terminal can receive at least a part of the configuration information for the DL SPS via higher layer signaling as shown in Table 27 below.

[0612] [Table 27]

[0613]

[0614] In the configuration information of the higher layer signaling, the SPS index can be used to indicate the SPS indicated by the DCI (e.g., L1 signaling) for the activation or deactivation of the SPS. Specifically, in the case where two SPSs are configured in one cell and / or one BWP via higher layer signaling, in order for the terminal to identify which of the two SPSs is specifically indicated for activation by the DCI indicating the activation of the SPS, it is necessary to provide index information for indicating the specific SPS activation in the SPS higher layer information. For example, for the terminal, the HARQ process number field in the DCI indicating the activation or deactivation of the SPS can indicate the index of the specific SPS, thereby achieving activation or deactivation. Specifically, as shown in Table 28, when the DCI including the CRC scrambled by the CG-RNTI includes at least one of the information in Table 28, and the New Data Indicator (NDI) field of the DCI including the CRC scrambled by the CG-RNTI indicates 0, the terminal can determine that the pre-activated specific SPS PDSCH release (deactivation) is indicated.

[0615] [Table 28]

[0616]

[0617] In Table 28, one HARQ process number can indicate one SPS index or multiple SPS indexes. In addition to the HARQ process number field, another DCI field (time resource field, frequency domain resource field, MCS, RV, PDSCH-to-HARQ timing field, etc.) can be used to indicate one or more SPS indexes. Basically, one SPS can be activated or deactivated by one DCI. The location of the Type 1 HARQ-ACK codebook for HARQ-ACK information on the DCI indicating SPS PDSCH release can be the same as the location of the Type 1 HARQ-ACK codebook corresponding to the SPS PDSCH reception location. When the location of the HARQ-ACK codebook corresponding to the candidate SPS PDSCH reception in a slot is k1, the location of the HARQ-ACK codebook for the DCI indicating SPS PDSCH release is also k1. Thus, when the DCI indicating SPS PDSCH release is transmitted in slot k, the terminal can not expect to receive PDSCH scheduling corresponding to the HARQ-ACK codebook location k1 in the same slot k. Here, the terminal can consider this as an error case. In Table 28 above, DCI formats 0_0 and 1_0 are used as examples. However, Table 28 can also be applied to DCI formats 0_1 and 1_1, and can be sufficiently extended and applied to other DCI formats 0_x and 1_x. Based on the above operation, the terminal can receive SPS PDSCH higher layer signaling and receive a DCI indicating SPS PDSCH activation, so that at least one SPS PDSCH can operate concurrently in the same cell and / or the same BWP. Then, the terminal can periodically receive activated SPS PDSCH in one cell / one BWP, and can transmit HARQ-ACK information corresponding to the SPS PDSCH. The HARQ-ACK information corresponding to the SPS PDSCH can be determined by the terminal based on the slot interval information of the PDSCH-to-HARQ-ACK timing included in the activation DCI information, the accurate time-frequency information in the corresponding slot based on the n1PUCCH-AN information included in the configuration information of the SPS higher layer signaling, and the PUCCH format information. If the PDSCH-to-HARQ-ACK timing field is not included in the DCI information, the terminal can assume that one value pre-configured via higher layer signaling is a default value, and determine that the default value has been applied.

[0618] Alternatively, at least one of the following DL SPS configuration information can be configured for the terminal via higher layer signaling.

[0619] - periodicity: DL SPS transmission periodicity

[0620] - nrofHARQ-Processes: HARQ process number configured for DL SPS

[0621] - n1PUCCH-AN: HARQ resource configuration for DL SPS

[0622] - mcs-Table: MCS table configuration information applied to DL SPS

[0623] In the disclosure, all DL SPS configuration information can be configured per PCell or SCell, or per frequency bandwidth part (BWP). In addition, one or more DL SPSs can be configured per a specific cell or BWP.

[0624] The terminal can determine the configuration information of the grant-free transmission and / or reception via reception of high layer signaling for DL SPS. The terminal can transmit and / or receive data in the configured resource region after reception of DCI indicating DL SPS activation; but cannot transmit and / or receive data in the resource region before reception of DCI indicating activation. In addition, the terminal cannot receive data in the resource region after reception of DCI indicating release.

[0625] When the following two conditions are satisfied, the terminal can verify the DL SPS assignment PDCCH for SPS scheduling activation or release.

[0626] - Condition 1: a case where the CRC bits of the DCI format transmitted on the PDCCH are scrambled by the CS-RNTI configured via high layer signaling

[0627] - Condition 2: a case where the NDI field for the transport block for activation is configured as 0

[0628] When certain fields of the DCI format transmitted on the DL SPS assignment PDCCH are the same as the fields shown in Table 29 or Table 30, the terminal can determine the information in the DCI format as a valid activation or valid release of DL SPS. For example, when the terminal detects the DCI format including the information shown in Table 29, the terminal can determine that the DL SPS has been activated. As another example, when the terminal detects the DCI format including the information shown in Table 30, the terminal can determine that the DL SPS has been released.

[0629] When certain fields of the DCI format transmitted on the DL SPS assignment PDCCH are not the same as the fields shown in Table 29 (special field configuration information for DL SPS activation) or Table 30 (special field configuration information for DL SPS release), the terminal can determine that a CRC mismatch with the DCI format has been detected.

[0630] [Table 29]

[0631]

[0632] [Table 30]

[0633]

[0634] When the terminal receives the PDSCH without receiving the PDCCH or receives the PDCCH indicating the release of the SPS PDSCH, the terminal can generate the corresponding HARQ-ACK information bit. In addition, at least in the Rel-15 5G communication system, the terminal can not expect to transmit the HARQ-ACK information for receiving two or more SPS PDSCHs in one PUCCH resource. In other words, at least in the Rel-15 5G communication system, the terminal can include only the HARQ-ACK information for receiving one SPS PDSCH in one PUCCH resource.

[0635] The DL SPS can also be configured in the primary (P) cell and the secondary (S) cell. For example, the parameters configured via the DL SPS higher layer signaling can be as follows.

[0636] - periodicity: DL SPS transmission periodicity

[0637] - nrofHARQ-Processes: HARQ process number configurable for DL SPS

[0638] - n1PUCCH-AN: PUCCH HARQ resource configuration for DL SPS, and the base station configures the resource as PUCCH format 0 or 1.

[0639] The above Table 29 and Table 30 can be fields available in the case where only one DL SPS can be configured per cell or BWP. In the case where multiple DL SPSs are configured for each cell and BWP, the DCI field for activating (or releasing) each DL SPS resource can be different. The present disclosure can provide a method for solving such a case.

[0640] In the present disclosure, not all of the DCI formats described in Table 29 and Table 30 can be used to activate or release the DL SPS resource, respectively. For example, the DCI format 1_0 and the DCI format 1_1 for PDSCH scheduling can be used to activate the DL SPS resource. For example, the DCI format 1_0 for PDSCH scheduling can be used to release the DL SPS resource.

[0641] [PDSCH: Scheduling Restriction]

[0642] The terminal can identify PDSCH resource and PUCCH resource information for transmitting HARQ-ACK information of the PDSCH resource via DL DCI received from the base station. Further, the terminal can determine PUSCH resource information via UL DCI received from the base station. If the PUCCH resource and the PUSCH resource overlap at least one symbol in time resources, the terminal can multiplex HARQ-ACK information included in the PUCCH on the PUSCH and transmit it to the base station by using only the PUSCH resource. For example, in this case, the terminal does not perform PUCCH resource transmission. In the above-described case, if the DL DCI is scheduled first and then the UL DCI is scheduled, the terminal can multiplex the HARQ-ACK information on the PUSCH. However, conversely, if the DL DCI is scheduled after the UL DCI is scheduled, when a TB to be transmitted in the PUSCH resource is generated, the terminal cannot determine whether to include UCI information such as HARQ-ACK information, and thus a problem can occur in the terminal processing aspect. Therefore, after the UL DCI is scheduled, the terminal can not expect to receive the DL DCI, and if this occurs, the terminal can consider this as an error case. Alternatively, if the terminal receives a DCI format for scheduling PUSCH transmission in a slot n in advance, and the terminal multiplexes HARQ-ACK information in the PUSCH transmission, the terminal can not expect to receive a DCI format associated with HARQ-ACK information reporting or PDSCH reception scheduling in the slot n for a resource for PUCCH transmission including the HARQ-ACK information. Here, the terminal can consider this as an error case. However, when repeated PUSCH transmission is performed in a time division duplex (TDD) case, a scheduling restriction for a PUCCH including HARQ-ACK information for a PDSCH can occur.

[0643] Figure 9 is a diagram illustrating a control and data information scheduling scenario according to an embodiment of the disclosure.

[0644] Referring to Figure 9 In a case where the UL DCI 900 has scheduled four repeated PUSCH transmissions 902, 904, 906, and 908, since the scheduling of the DL DCI 910 is earlier than the UL DCI 900, and the PUCCH 912 includes HARQ-ACK information for the DL DCI 910, the terminal can multiplex and transmit the HARQ-ACK information for the DL DCI 910 on the PUSCH 902. However, subsequently, for the PUCCH 922 including HARQ-ACK information for the DL DCI 920, since the DL DCI 920 is scheduled after the UL DCI 900, when a TB to be transmitted in the PUSCH resource is generated, the terminal cannot determine whether to include UCI information such as HARQ-ACK information, and thus a problem can occur in the terminal processing aspect. Therefore, after the UL DCI is scheduled, the terminal can not expect to receive the DL DCI, and if this occurs, the terminal can consider this as an error case. Figure 9The PUCCH 922 described in the middle is multiplexed with the PUSCH 906, the terminal considers this as an error case, so that the base station can need to avoid such scheduling. Therefore, when the UL resources are less than the DL resources in the TDD case and in the case where the repeated PUSCH transmission is performed, the base station can pre-schedule all the DL DCIs before the UL DCI for the PUSCH scheduling or perform scheduling so that the PUCCH including the HARQ-ACK information for the DL DCI is transmitted after the repeated PUSCH transmission ends. The former (e.g., pre-scheduling all the DL DCIs before the UL DCI for the PUSCH scheduling) can be a method that can be employed when the base station pre-predicts all the traffics to be transmitted to the terminal. In the latter (e.g., performing scheduling so that the PUCCH including the HARQ-ACK information for the DL DCI is transmitted after the repeated PUSCH transmission ends), since the terminal needs to receive the HARQ-ACK information for the DL DCI after the repeated PUSCH transmission is completed, unnecessary delay time can occur. Therefore, in order to solve the problem that the unnecessary delay time occurs, as shown in Figure 9 , even after the UL DCI 900 for scheduling the PUSCH 906, the DL DCI 920 for scheduling the PUCCH 922 including the HARQ-ACK information overlapping with the PUSCH 906 can need to be allowed. The following embodiments provide a solution to the problem occurring in the above-described situation.

[0645] [Embodiment 1]

[0646] As shown in Figure 9 , in order to allow the DL DCI 920 for scheduling the PUCCH 922 including the HARQ-ACK information overlapping with the PUSCH 906, an independent UE capability can be reported. Therefore, the base station can determine the terminal allowing the separate UE capability report and the terminal not allowing the separate UE capability report. In addition to the UE capability report, even if the terminal has reported the UE capability by the independent higher layer signaling configuration (such as RRC signaling) of the base station, the base station can determine whether to allow the scheduling as shown in Figure 9 . Therefore, even if the terminal has reported the independent UE capability, the base station can prohibit the scheduling such as the DL DCI 920 unless it is configured via the higher layer signaling; and when the base station provides the configuration to the terminal having reported the UE capability via the higher layer signaling, the scheduling such as the DL DCI 920 can be performed. Figure 9 Figure 9 If the terminal does not report the separate UE capability allowing the scheduling such as the DL DCI 920, the base station can not perform the scheduling such as the DL DCI 920.

[0647] If the terminal does not report the separate UE capability allowing the scheduling such as the DL DCI 920, the base station can not perform the scheduling such as the DL DCI 920. Figure 10 ​indicated by the high layer signaling configuration, or when the value of the operation is not received from the base station, in case of type 1 HARQ-ACK codebook configured via high layer signaling, when the terminal starts in the PDCCH search region after the PDCCH search region where the DCI format for PUSCH scheduling is located, the HARQ-ACK information corresponding to PDSCH reception, SPS PDSCH release and TCI state update detected by the terminal should be configured as NACK value in the HARQ-ACK codebook. Figure 10

[0648] Figure 10 is a schematic diagram showing a method of determining HARQ-ACK information according to an embodiment of the disclosure.

[0649] Referring to Figure 10 When the terminal receives the UL DCI 1000 for scheduling the PUSCH 1002, if the DL DCI 1010 for scheduling the PUCCH 1018 including HARQ-ACK information overlapping with the PUSCH 1002 is received before the UL DCI 1000, the terminal can generate the decoding result of the PDSCH 1012 scheduled by the DL DCI 1010 as ACK or NACK, and multiplex the ACK or NACK on the PUSCH 1002 and transmit it. The type 1 HARQ-ACK codebook can be generated based on k1 (e.g., offset or difference between the time slot of scheduling PDSCH and the time slot of scheduling HARQ-ACK PUCCH) pre-configured via high layer signaling, the maximum number of PDSCH that can be non-overlappingly scheduled in a certain DL time slot, TDD configuration, and UL and DL inter-subcarrier difference, and the generation process is independent of the actual scheduling situation. For example, in Figure 10 , up to 3 PDSCHs can be scheduled in the DL time slot n, and if the HARQ-ACK information can be transmitted in the UL time slot k where the PUSCH 1002 or the PUCCH 1018 can be transmitted, up to 3 HARQ-ACK information bit sizes of the PDSCHs scheduled in the time slot can be generated based on the DL time slot n. However, in Figure 9 ​In the middle, since there is one PDSCH, i.e., PDSCH 1012 actually scheduled in DL slot n before UL DCI scheduling, the terminal can map NACK to PDSCH candidates 1014 and 1016 for generating HARQ-ACK information. Thus, the HARQ-ACK information bits for DL slot n can be 3 bits in total, and the terminal can multiplex the HARQ codebook for DL slot n with (ACK, NACK, NACK) or (NACK, NACK, NACK) on PUSCH 1002 and report it to the base station. In Figure 9 In the middle, since there is one PDSCH, i.e., PDSCH 1012 actually scheduled in DL slot n before UL DCI scheduling, the terminal can map NACK to PDSCH candidates 1014 and 1016 for generating HARQ-ACK information. Thus, the HARQ-ACK information bits for DL slot n can be 3 bits in total, and the terminal can multiplex the HARQ codebook for DL slot n with (ACK, NACK, NACK) or (NACK, NACK, NACK) on PUSCH 1002 and report it to the base station. In

[0650] On the other hand, when the terminal reports the UE capability allowing scheduling as shown in Figure 10 , or reports the UE capability and receives the related higher layer signaling configuration information from the base station (or indicates the value allowing Figure 10 operation via higher layer signaling configuration), in the case where Type 1 HARQ-ACK codebook has been configured by higher layer signaling, even after receiving UL DCI 1000 as shown in Figure 10 , a DL DCI scheduling PUCCH including HARQ-ACK information overlapping with PUSCH 1002 can be received. Thus, it can not be always necessary to map NACK to the above-mentioned PDSCH candidates 1014 and 1016. Instead, the terminal can provide at least one of the following methods or a combination of some of them. When a combination of multiple methods is possible, the terminal can perform determination through UE capability reporting or higher layer signaling configuration.

[0651] - Method A-1: The terminal can map NACK to PDSCH candidates not scheduled by DL DCI or DL SPS. For example, when generating HARQ-ACK information included in PUCCH 1018 overlapping with PUSCH 1002, regardless of whether UL DCI is received, the terminal can map ACK or NACK to the actually scheduled PDSCH and map NACK to other PDSCH candidates for Type 1 HARQ-ACK codebook generation.

[0652] - Method A-2: The terminal can map NACK to PDSCH candidates overlapping with at least one symbol within T mux time before the earliest symbol in time of PUSCH 1002 scheduled by UL DCI and PUCCH 1018 overlapping with the PUSCH. In Figure 10For example, since PDSCH candidate 1016 is the earliest symbol before the T in PUSCH 1002 and PUCCH 1018 resources... mux The overlap occurs within 1020 seconds, therefore the terminal can map the NACK to at least PDSCH candidate 1016. This is likely because the terminal requires a minimum processing time to multiplex and send HARQ-ACK information on the PUSCH, and the later the PDSCH used for HARQ-ACK information determination is received, the more difficult it is to meet the terminal's minimum processing time requirement. mux 1020 is the minimum processing time for the terminal. Specifically, it refers to the minimum time required to send all uplink control information or data information scheduled by the corresponding downlink control information after receiving the last downlink control information or data information. Therefore, when PDSCH candidate 1016 is scheduled and its PDSCH HARQ-ACK information needs to be sent on PUSCH 1002, the time difference between the last symbol of PDSCH candidate 1016 and the first symbol of PUSCH 1002 is T. mux Within the range of 1020, the terminal is unable to multiplex and send HARQ-ACK information on the PUSCH because it exceeds its minimum processing time. Optionally, when generating the type 1 HARQ-ACK codebook, the terminal can assume that it corresponds to T mux The time is configured via higher-level signaling for the UL time slot to generate the Type 1 HARQ-ACK codebook for DL ​​time slot n.

[0653] - Method A-3: The method is similar to Method A-2, but it is not T. mux 1020, but can be used as a standalone application for the terminal. mux 'To determine whether to map NACK. T mux 'Can be at least equal to or greater than T' mux The value can be reported via independent higher-layer signaling or UE capabilities. For example, if T mux The value of ' is greater than T mux And determined in advance through the UE capability report, or through one of the values ​​reported in the UE capability report and determined by higher-layer signaling, then when it has a value similar to T mux 'The PDSCH candidate of at least one overlapping symbol is Figure 9 When NACK is 1014 and 1016, the terminal can map NACK to PDSCH candidates 1014 and 1016 and multiplex them on PUSCH to perform transmission. Optionally, when generating a type 1 HARQ-ACK codebook, the terminal can assume that it corresponds to T mux The time is the UL time slot configured via higher-level signaling to generate the type 1 HARQ-ACK codebook for DL ​​time slot n.

[0654] - Method A-4: When a slot in which the PUSCH 1002 is transmitted is referred to as slot k, the terminal can map NACK to PDSCH candidates included in slots k-1 to k-m. If m=1, only k-1 is applicable. The above-described method can be applied only in the case where scheduling is performed after a point in time at which the UL DCI 1000 for PUSCH 1002 scheduling is transmitted and / or received. As Figure 9 illustrated, if the DL slot n is a slot immediately before a slot in which the PUSCH is transmitted and / or received, and the DL DCI 1010 is not transmitted and / or received before the UL DCI 1000, the terminal can map NACK because there is no actual scheduling on the PDSCH 1012 including the PDSCH candidates 1014 and 1016. However, if the DL DCI 1010 is scheduled before the UL DCI 1000, and the DL DCI 1010 provides information of the PDSCH 1012, the terminal can generate ACK or NACK information for the PDSCH 1012. The m value can be determined via a UE capability report, or via high layer signaling configuration.

[0655] When the terminal does not report the UE capability allowing scheduling as Figure 10 illustrated, or even if the UE capability is reported but relevant high layer signaling configuration information is not received from the base station (or a value not allowing the Figure 10 operation to be performed is received via high layer signaling configuration), since one PDSCH (i.e., the PDSCH 1012) is actually scheduled in the DL slot n before UL DCI scheduling in Figure 9 , the terminal can map NACK to the PDSCH candidates 1014 and 1016 in which information is generated. Accordingly, the HARQ-ACK information bits for the DL slot n can be a total of 3 bits, and the terminal can multiplex the HARQ codebook for the DL slot n with (ACK, NACK, NACK) or (NACK, NACK, NACK) on the PUSCH 1002, and report the HARQ codebook. In Figure 9 , the description is limited to a specific DL slot n. However, the present disclosure is not limited thereto, and can be extended and applied when a plurality of DL slots can be mapped to the UL slot to which the PUSCH 1002 belongs.

[0656] [Embodiment 2]

[0657] The Type 2 HARQ-ACK codebook corresponds to a method of pre-indicating a HARQ-ACK information size by using DL DCI or UL DCI. Specifically, the HARQ-ACK codebook size can be indicated by a DAI value in the DL DCI or the UL DCI. For example, in Figure 9In the case of repeated transmissions of four PUSCHs 902, 904, 906 and 908 indicated by UL DCI, when the DAI indication of UL DCI is 2, at least one of the following methods may be applied to the HARQ-ACK size included in the repeatedly transmitted PUSCHs.

[0658] - Method B-1: The size of the HARQ-ACK multiplexed based on the repeatedly transmitted PUSCH can be different from each other. Specifically, the HARQ-ACK size can be N bits with a value of mod(N / 4) = 2. For example, the size of the HARQ-ACK bits multiplexed on PUSCH 902 can be 2 bits, the size of the HARQ-ACK bits multiplexed on PUSCH 904 can be 6 bits, and the size of the HARQ-ACK bits multiplexed on PUSCH 906 can be 10 bits.

[0659] - Method B-2: The size of the HARQ-ACK multiplexed based on the repeatedly transmitted PUSCHs needs to be the same. For example, if the HARQ-ACK information is multiplexed on PUSCH 904, 906, and 908, and the size of the HARQ-ACK bits multiplexed on PUSCH 902 is 2 bits, then the size of the HARQ-ACK bits for the remaining PUSCH 904, 906, and 908 can also be 2 bits. For example, the size of the HARQ-ACK bits for PUSCH 904, 906, and 908 can follow the bit size determined by the first PUSCH 902.

[0660] Method B-3: Regardless of the size of the HARQ-ACK bits multiplexed on the first PUSCH 902, the size of the HARQ-ACK bits multiplexed on the other PUSCHs 904, 906, and 908 can correspond to the method of obtaining N=2, where N=2 is the smallest natural number that satisfies mod(N / 4)=2. For example, even if the size of the HARQ-ACK bits multiplexed on the first PUSCH 902 is 6 bits, the size of the HARQ-ACK bits multiplexed on the other PUSCHs 904, 906, and 908 can be 2 bits.

[0661] The methods described above assume a UL DCI DAI value of 2, but these methods are also applicable to other values. At least one or a combination of the methods described above can be applied. For example, when the terminal does not report... Figure 9 Method B-1 can be applied when the UE capabilities shown are allowed for scheduling, or when the UE capabilities have been reported but relevant higher-layer signaling configuration information has not been received from the base station. Furthermore, for example, when the terminal reports, as shown in the example... Figure 11 The UE capabilities allowed for scheduling are shown, and relevant higher-layer signaling configuration information is received from the base station (or permitted to be executed via higher-layer signaling configuration instructions).Figure 11 Method B-2 or Method B-3 can also be applied when the value of the operation is not equal to 0.

[0662] Figure 9 is a flowchart illustrating a method of scheduling control and data information by a terminal according to an embodiment of the disclosure.

[0663] Referring to Figure 9 , when the terminal allows scheduling as shown in Figure 12 , the terminal can report UE capability to the base station in operation 1100, and the base station can receive the UE capability. Then, the base station can provide information including whether to allow scheduling as shown in Figure 12 in operation 1102 via independent higher layer signaling configuration information, and the terminal can receive the information including whether to allow scheduling. The base station can transmit information on scheduling of control and data information to the terminal via a PDCCH, and the terminal can receive the information on scheduling of control and data information from the base station in operation 1104. According to the UE capability and the higher layer signaling configuration information, the terminal can multiplex control information and data information based on scheduling information from the base station in operation 1106, and transmit the multiplexed control and data information to the base station. In this case, the terminal can operate based on Embodiment 1 and Embodiment 2 described above.

[0664] Figure 13 A structure of a UE in a wireless communication system according to an embodiment of the disclosure is illustrated.

[0665] Referring to Figure 13 , the UE can include a transceiver (collectively referring to the UE receiver 1200 and the UE transmitter 1210), a memory (not shown), and a UE processor 1205 (or a UE controller or a processor). The UE receiver 1200 and the UE transmitter 1210, the memory, and the UE processor 1205 can operate according to the communication method of the UE. The components of the UE are not limited to the above-described examples. For example, the UE can include a greater or smaller number of components than the above-described components. Also, the transceiver, the memory, and the processor can be implemented as a single chip. The UE receiver 1200 and the UE transmitter 1210 can perform transmission and reception of signals with the base station. The signals can include control information and data. To this end, the UE receiver 1200 and the UE transmitter 1210 can include an RF transmitter configured to up-convert and amplify a frequency of a transmission signal, an RF receiver configured to amplify a received signal and down-convert a frequency thereof, etc. This is only an embodiment of the UE receiver 1200 and the UE transmitter 1210, and the components of the UE receiver 1200 and the UE transmitter 1210 are not limited to the RF transmitter and the RF receiver.

[0666] Further, the UE receiver 1200 and the UE transmitter 1210 can receive a signal through a wireless channel, output it to the processor, and transmit a signal output from the processor through a wireless channel.

[0667] The memory can store programs and data required for operations of the UE. Further, the memory can store control information or data included in a signal transmitted / received by the UE. The memory can include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Further, the UE can include a plurality of memories. Further, according to an embodiment of the disclosure, the memory can store programs for performing the above-described control information and data transmission / reception method.

[0668] Further, the UE processor 1205 can control a series of processes to enable the UE to operate according to the above-described embodiments. For example, the UE processor 1205 can control components of the UE to receive DCI configured in two layers to enable simultaneous reception of a plurality of PDSCHs. The UE can include a plurality of processors, and the UE processor 1205 can complete the control operation of the components of the UE by executing programs stored in the memory. The UE processor 1205 can control the UE components to implement the embodiments of the disclosure by executing programs stored in the memory. Further, the UE processor 1205 can be an application processor (AP), a communication processor (CP), a circuit, a dedicated circuit, or at least one processor.

[0669] Figures 1 to 4 A structure of a base station in a wireless communication system according to an embodiment of the disclosure is illustrated.

[0670] Reference Figure 5A The base station can include a transceiver, a memory (not shown), and a base station processor 1305 (or a base station controller or processor), the transceiver collectively referring to the base station receiver 1300 and the base station transmitter 1310. The base station receiver 1300 and the base station transmitter 1310, the memory, and the base station processor 1305 can operate according to the above-described communication method of the base station. The components of the base station are not limited to the above-described examples. For example, the base station can include more or less components than the above-described components. Further, the transceiver, the memory, and the processor can be implemented as a single chip.

[0671] The base station receiver 1300 and the base station transmitter 1310 can exchange signals with the UE. The signals can include control information and data. To this end, the base station receiver 1300 and the base station transmitter 1310 can include an RF transmitter configured to up-convert and amplify the frequency of a transmitted signal, an RF receiver configured to low-noise amplify a received signal and down-convert the frequency thereof, etc. This is merely an embodiment of the base station receiver 1300 and the base station transmitter 1310, and the components of the base station receiver 1300 and the base station transmitter 1310 are not limited to the RF transmitter and the RF receiver.

[0672] In addition, the base station receiver 1300 and the base station transmitter 1310 can receive a signal through a wireless channel, output it to the base station processor 1305, and transmit a signal output from the base station processor 1305 through a wireless channel.

[0673] The memory can store programs and data required for the operation of the base station. In addition, the memory can store control information or data included in a signal transmitted / received by the base station. The memory can include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. In addition, the base station can include a plurality of memories. In addition, according to an embodiment of the disclosure, the memory can store a program for performing the above-described control information and data transmission / reception method.

[0674] The base station processor 1305 can control a series of processes so that the base station can operate according to the above-described embodiments of the disclosure. For example, the processor can control the components of the base station so as to configure DCI including allocation information about a plurality of PDSCHs in two layers and transmit the DCI. The base station can include a plurality of base station processors 1305, and the base station processor 1305 can perform the base station component control operation by executing a program stored in the memory. The base station processor 1305 can control the UE component to perform the embodiments of the disclosure by executing a program stored in the memory. In addition, the base station processor 1305 can be an application processor (AP), a communication processor (CP), a circuit, a dedicated circuit, or at least one processor.

[0675] It should be noted that the above-described configuration diagrams, diagrams of control / data signal transmission methods, diagrams of operation flows, and structural diagrams shown in Figure 5B , Figure 5C , Figures 6 to 13 , Figures 1 to 4 and Figure 5A are not intended to limit the scope of protection of the disclosure. For example, in Figure 5B , Figure 5C , Figures 6 to 13 , ​ and ​ , the above-described configuration diagrams, diagrams of control / data signal transmission methods, diagrams of operation flows, and structural diagrams are not limited to the embodiments of the disclosure.All constituent elements, entities, or operation steps shown and described in the above embodiments should not be construed as essential elements for implementing the present disclosure, and the present disclosure can be implemented without impairing the essence of the present disclosure even if only some of the elements are included.

[0676] The method according to the embodiments described in the claims or specification of the present disclosure can be implemented in software, hardware, or a combination of hardware and software.

[0677] As for software, a computer-readable storage medium storing one or more programs (software modules) can be provided. The one or more programs stored in the computer-readable storage medium can be configured to be executed by one or more processors of an electronic device. The one or more programs can include instructions for instructing the electronic device to execute the method according to the embodiments described in the claims or specification of the present disclosure.

[0678] Such programs (software modules, software) can be stored in a random access memory, a nonvolatile memory including a flash memory, a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a magnetic disc storage device, a compact disc (CD-ROM), a digital versatile disc (DVD), or other optical storage devices, and a magnetic cassette. Alternatively, it can be stored in a memory that combines some or all of the above-described recording media. A plurality of memories can be included.

[0679] In addition, the program can be stored in an attachable storage device accessible through a communication network including the Internet, an intranet, a local area network (LAN), a wireless local area network (WLAN), or a storage area network (SAN), or a communication network composed of combinations of these networks. Such a storage device can access a device that executes the embodiments of the present disclosure through an external port. In addition, a separate storage device on the communication network can access a device that executes the embodiments of the present disclosure.

[0680] In the specific embodiments of the present disclosure, the components included in the present disclosure are expressed in singular or plural. However, the expression in singular or plural is appropriately selected for convenience of explanation according to the proposed scenario, and the present disclosure is not limited to a single component or multiple components, and the components expressed in plural can be configured as a single component, and the components expressed in singular can be configured as multiple components.

[0681] Meanwhile, although specific embodiments have been described in the specification of the present disclosure, it should be noted that various modifications can be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure is not limited by the embodiments, but is determined by the scope of the following claims, and includes equivalents thereof.

[0682] The embodiments of the disclosure described and illustrated in the specification and drawings are provided merely for the purpose of understanding the technical content of the disclosure, and are intended to help understand the disclosure, and are not intended to limit the scope of the disclosure. For example, it will be apparent to those skilled in the art that other variations can be implemented based on the technical idea of the disclosure. In addition, each of the above-described embodiments can be used in combination as needed. For example, a part of one embodiment of the disclosure can be combined with a part of another embodiment to operate a base station and a terminal. As an example, a part of Embodiment 1 of the disclosure can be combined with a part of Embodiment 2 to operate a base station and a terminal. In addition, although the above-described embodiments are proposed based on the FDD LTE system, other variations based on the technical idea of the above-described embodiments can also be implemented in other systems, such as the TDD LTE, 5G, or NR system.

[0683] In the drawings describing the method of the disclosure, the order of description does not always correspond to the order of execution of each method step, the order relationship between the steps can be adjusted, or the steps can be executed in parallel.

[0684] Optionally, in the drawings describing the method of the disclosure, part of the elements can be omitted or only part of the elements can be included without departing from the essential spirit and scope of the disclosure.

[0685] In addition, in the method of the disclosure, part or all of the contents of each embodiment can be implemented in combination without departing from the essential spirit and scope of the disclosure.

[0686] It should be understood that, according to the disclosure of the claims and description in the specification, various embodiments of the disclosure can be implemented in the form of hardware, software, or a combination of hardware and software.

[0687] Any such software can be stored in a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules) including computer executable instructions, which, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of the disclosure.

[0688] Any such software can be stored in the form of volatile or non-volatile storage such as a storage device (e.g., a ROM, whether erasable or rewritable or not, such as a disc, cartridge, or the like); or in the form of memory such as a RAM, storage chip, device, or integrated circuit; or stored as embodied in an optical or magnetic medium, such as a compact disc (CD), digital versatile disc (DVD), magnetic disk storage or tape, etc. It is understood that the storage devices and media are various embodiments of non-transitory machine- readable storage that are suitable for storing a computer program or multiple computer programs comprising instructions that, when executed, implement various embodiments of the present disclosure. Accordingly, embodiments provide a program comprising code for implementing an apparatus or a method as claimed in any claim of this specification, and a non-transitory machine-readable storage storing the program.

[0689] While the present disclosure has been illustrated and described with reference to various embodiments thereof, it will be understood that various modifications have been made to the form and details thereof, without departing from the spirit and scope of the disclosure, as defined in the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receives higher-layer signaling from the base station, the higher-layer signaling including information enabling the multiplexing of a first hybrid automatic repeat request acknowledgment (HARQ-ACK) message; The base station receives a first downlink control information (DCI), which schedules the Physical Uplink Shared Channel (PUSCH) to repeat. Following the first DCI, a second DCI indicating the Physical Uplink Control Channel (PUCCH) is received from the base station; as well as The first HARQ-ACK information is sent to the base station by multiplexing the first HARQ-ACK information on at least one PUSCH repeat other than the first PUSCH repeat.

2. The method according to claim 1, further comprising: The UE capability information is sent to the base station, and the UE capability information includes information indicating whether the UE supports the multiplexing.

3. The method according to claim 1, wherein, The first HARQ-ACK information is for the Physical Downlink Shared Channel (PDSCH) scheduled by the second DCI.

4. The method according to claim 1, further comprising: Send a second HARQ-ACK message, including a negative acknowledgment (NACK) value, to the base station.

5. A method performed by a base station in a wireless communication system, the method comprising: Send higher-layer signaling to the user equipment (UE), the higher-layer signaling including information enabling the multiplexing of the first hybrid automatic repeat request acknowledgment (HARQ-ACK) information; Send a first downlink control information (DCI) to the UE, wherein the first DCI schedules repeated Physical Uplink Shared Channel (PUSCH); After the first DCI, a second DCI indicating the Physical Uplink Control Channel (PUCCH) is sent to the UE; as well as The first HARQ-ACK information is received from the UE, wherein the first HARQ-ACK information is multiplexed in at least one PUSCH repeat other than the first PUSCH repeat.

6. The method of claim 5, further comprising: The UE receives UE capability information, which includes information indicating whether the UE supports the multiplexing.

7. The method according to claim 5, wherein, The first HARQ-ACK information is for the Physical Downlink Shared Channel (PDSCH) scheduled by the second DCI.

8. The method of claim 5, further comprising: The UE receives a second HARQ-ACK message, which includes a negative acknowledgment (NACK) value.

9. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as At least one processor, coupled to the transceiver and configured to: The system receives higher-layer signaling from the base station, the higher-layer signaling including information enabling the multiplexing of a first hybrid automatic repeat request acknowledgment (HARQ-ACK) message. The base station receives first downlink control information (DCI), and the first DCI schedules repeated Physical Uplink Shared Channel (PUSCH). Following the first DCI, a second DCI indicating the Physical Uplink Control Channel (PUCCH) is received from the base station, and... The first HARQ-ACK information is sent to the base station by multiplexing the first HARQ-ACK information on at least one PUSCH repeat other than the first PUSCH repeat.

10. The UE according to claim 9, wherein, The at least one processor is further configured to: The UE capability information is sent to the base station, and the UE capability information includes information indicating whether the UE supports the multiplexing.

11. The UE according to claim 9, wherein, The first HARQ-ACK information is for the Physical Downlink Shared Channel (PDSCH) scheduled by the second DCI.

12. The UE according to claim 9, wherein, The at least one processor is further configured to: Send a second HARQ-ACK message, including a negative acknowledgment (NACK) value, to the base station.

13. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: Send higher-layer signaling to the user equipment (UE), the higher-layer signaling including information enabling the multiplexing of the first hybrid automatic repeat request acknowledgment (HARQ-ACK) information. The first downlink control information (DCI) is sent to the UE, and the first DCI schedules the Physical Uplink Shared Channel (PUSCH) to repeat. After the first DCI, a second DCI indicating the Physical Uplink Control Channel (PUCCH) is sent to the UE; as well as The first HARQ-ACK information is received from the UE, wherein the first HARQ-ACK information is multiplexed in at least one PUSCH repeat other than the first PUSCH repeat.

14. The base station according to claim 13, wherein, The at least one processor is further configured to: The UE receives UE capability information, which includes information indicating whether the UE supports the multiplexing.

15. The base station according to claim 13, wherein, The first HARQ-ACK information is for the Physical Downlink Shared Channel (PDSCH) scheduled by the second DCI.

Images