KR20230013594A - Method and apparatus for harq feedback transmission in wireless communication system - Google Patents

Abstract

The present disclosure relates to a communication technique and a system for converging a 5G communication system for supporting a higher data rate than a 4G system with Internet of things (IoT) technology. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technology, such as smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, smart retails, and security and safety services. The present disclosure proposes a method and an apparatus for transmitting uplink control information and/or uplink data according to a plurality of priorities of a terminal and receiving uplink control information and/or uplink data according to a plurality of priorities of a base station. According to the present invention, a method for processing control signals in a wireless communication system comprises the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal, generated on the processing, to the base station. Therefore, provided are the method and the method for effectively providing services in a mobile communication system.

Description

Method and apparatus for transmitting HARQ feedback in a wireless communication system

The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for configuring/reporting uplink control information in a wireless communication system and an apparatus capable of performing the same.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system to meet the growing demand for wireless data traffic after the commercialization of the 4G communication system. For this reason, the 5G communication system or pre-5G communication system is being called a system after a 4G network (Beyond 4G Network) communication system or an LTE system (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a mmWave band (eg, a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, to improve the network of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation etc. are being developed. In addition, in the 5G system, advanced coding modulation (Advanced Coding Modulation: ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), SCMA (sparse code multiple access), and the like are being developed.

On the other hand, the Internet is evolving from a human-centered connection network in which humans create and consume information to an Internet of Things (IoT) network in which information is exchanged and processed between distributed components such as things. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with a cloud server, etc., is also emerging. In order to implement IoT, technical elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, sensor networks for connection between objects and machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new values in human life by collecting and analyzing data generated from connected objects can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system (5th generation communication system or New Radio (NR)) to the IoT network. For example, technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna, which are 5G communication technologies. . The application of the cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 3eG technology and IoT technology.

As various services can be provided according to the above and the development of wireless communication systems, a method for smoothly providing these services is required.

The disclosed embodiments are intended to provide an apparatus and method capable of effectively providing services in a mobile communication system.

The present invention for solving the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

According to the disclosed embodiments, it is possible to effectively provide services in a mobile communication system.

1 is a diagram showing a basic structure of a time-frequency domain in a wireless communication system according to an embodiment of the present disclosure.
2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to an embodiment of the present disclosure.
3 is a diagram illustrating an example of PUSCH repeated transmission type B in a wireless communication system according to an embodiment of the present disclosure.
4 is a diagram illustrating an example of an aperiodic CSI reporting method according to an embodiment of the present disclosure.
5 illustrates an example of mapping uplink control information to a PUSCH according to an embodiment of the present disclosure.
6 is a diagram illustrating a processing procedure for transmitting and receiving UCI information between a terminal and a base station through a PUSCH according to an embodiment of the present disclosure.
7 is a diagram illustrating a method of setting a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook) according to an embodiment of the present disclosure.
8 is a diagram illustrating a method of setting a dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) according to an embodiment of the present disclosure.
9 is a diagram showing a situation in which a plurality of different HARQ-ACK codebooks are overlapped according to an embodiment of the present disclosure.
10 is a block diagram illustrating a PUCCH or PUSCH transmission operation of a UE according to an embodiment of the present disclosure.
11 is a diagram showing an SPS PDSCH and HARQ-ACK information transmission relationship thereto according to an embodiment of the present disclosure.
12a is a block diagram illustrating an operation of transmitting and receiving an SPS PDSCH and a HARQ-ACK PUCCH of a UE according to an embodiment of the present disclosure.
12B is a diagram illustrating a resource configuration process through which a PUCCH can be transmitted and received semi-statically according to an embodiment of the present disclosure.
12c is a diagram illustrating an operation for switching a PUCCH transmission carrier according to an embodiment of the present disclosure.
13 is a diagram illustrating a structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.
14 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary description.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is given to the same or corresponding component.

Advantages and features of the present disclosure, and methods of achieving them, will become clear with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, only the present embodiments make the disclosure of the present disclosure complete, and common knowledge in the art to which the present disclosure belongs. It is provided to fully inform the person who has the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification. In addition, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, a base station is a subject that performs resource allocation of a terminal, and may 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, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. In the present disclosure, downlink (DL) is a radio transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a radio transmission path of a signal transmitted from a terminal to a base station. In addition, although an LTE or LTE-A system may be described below as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) or the 6th generation mobile communication technology (6G) developed after LTE-A may be included in this, and the following 5G or 6G is the existing LTE, LTE-A And it may be a concept including other similar services. In addition, the present disclosure can be applied to other communication systems through some modifications within a range that does not greatly deviate from the scope of the present disclosure as determined by those skilled in the art.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible that two blocks shown in succession may in fact be performed substantially concurrently, or that the blocks may sometimes be performed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' performs certain roles. do. However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, as an example, '~unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card. Also, in the embodiment, '~ unit' may include one or more processors.

The wireless communication system has moved away from providing voice-oriented services in the early days and, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e, a broadband wireless network that provides high-speed, high-quality packet data services. evolving into a communication system.

As a representative example of the broadband wireless communication system, in the LTE system, an Orthogonal Frequency Division Multiplexing (OFDM) method is employed in downlink (DL), and SC-FDMA (Single Carrier Frequency Division Multiplexing) in uplink (UL) Access) method is used. Uplink refers to a radio link in which a terminal (UE (User Equipment) or MS (Mobile Station)) transmits data or control signals to a base station (eNode B or base station (BS)), and downlink refers to a radio link in which a base station transmits data or a control signal to a terminal. A radio link that transmits data or control signals. The multiple access scheme as described above can distinguish data or control information of each user by allocating and operating time-frequency resources to carry data or control information for each user so that they do not overlap each other, that is, so that orthogonality is established. can

As a future communication system after LTE, that is, a 5G communication system, since it should be able to freely reflect various requirements such as users and service providers, a service that satisfies various requirements at the same time must be supported. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra reliability low latency communication (URLLC), etc. there is

eMBB aims to provide a data transmission rate that is more improved than that supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, an eMBB must be able to provide a peak data rate of 20 Gbps in downlink and a peak data rate of 10 Gbps in uplink from the perspective of one base station. In addition, the 5G communication system should provide a maximum transmission rate and, at the same time, an increased user perceived data rate of the terminal. In order to satisfy these requirements, improvements in various transmission and reception technologies including a more advanced multi-input multi-output (MIMO) transmission technology are required. In addition, while signals are transmitted using a maximum 20MHz transmission bandwidth in the 2GHz band used by LTE, the 5G communication system uses a frequency bandwidth wider than 20MHz in a frequency band of 3 to 6GHz or 6GHz or higher, thereby providing data required by the 5G communication system. transmission speed can be satisfied.

At the same time, mMTC is being considered to support application services such as Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires access support for large-scale terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal cost. Since the Internet of Things is attached to various sensors and various devices to provide communication functions, it must be able to support a large number of terminals (eg, 1,000,000 terminals/km2) in a cell. In addition, since a terminal supporting mMTC is likely to be located in a shadow area that is not covered by a cell, such as the basement of a building due to the nature of the service, it may require a wider coverage than other services provided by the 5G communication system. A terminal supporting mMTC must be composed of a low-cost terminal, and since it is difficult to frequently replace a battery of the terminal, a very long battery life time such as 10 to 15 years may be required.

Finally, in the case of URLLC, it is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmaned aerial vehicles, remote health care, emergency situations A service used for emergency alert or the like may be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC needs to satisfy an air interface latency of less than 0.5 milliseconds, and at the same time has a requirement of a packet error rate of 10 ^-5 or less. Therefore, for a service that supports URLLC, a 5G system must provide a smaller transmit time interval (TTI) than other services, and at the same time, a design that allocates wide resources in the frequency band to secure the reliability of the communication link. items may be requested.

The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. At this time, different transmission/reception techniques and transmission/reception parameters may be used between services in order to satisfy different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

Hereinafter, embodiments of the present disclosure will be described in detail with accompanying drawings. Hereinafter, a base station is a subject that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. Hereinafter, an embodiment of the present disclosure is described using a 5G system as an example, but the embodiment of the present disclosure can be applied to other communication systems having a similar technical background or channel type. For example, LTE or LTE-A mobile communication and mobile communication technology developed after 5G may be included in this. Accordingly, the embodiments of the present disclosure may be applied to other communication systems through some modification without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of this disclosure are applicable to FDD and TDD systems.

In addition, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, in describing the present disclosure, higher layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

- MIB (Master Information Block)

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

- Radio Resource Control (RRC)

- MAC (Medium Access Control) CE (Control Element)

Also, L1 signaling may be signaling corresponding to at least one or a combination of one or more of signaling methods using the following physical layer channels or signaling.

- PDCCH (Physical Downlink Control Channel)

- Downlink Control Information (DCI)

- UE-specific DCI

- Group common DCI

- Common DCI

- Scheduling DCI (eg DCI used for the purpose of scheduling downlink or uplink data)

- Non-scheduling DCI (eg, a DCI that is not intended to schedule downlink or uplink data)

- PUCCH (Physical Uplink Control Channel)

- UCI (Uplink Control Information)

Hereinafter, in the present disclosure, determining the priority between A and B means selecting a higher priority according to a predetermined priority rule and performing a corresponding operation or lower priority. It may be variously referred to as omitting or dropping an operation for.

Hereinafter, in the present disclosure, the above examples are described through a plurality of embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination.

[NR time-frequency resource]

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

1 is a diagram showing the basic structure of a time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.

(일례로 12)개의 연속된 RE들은 하나의 자원 블록(Resource Block, RB, 104)을 구성할 수 있다. 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which is defined as 1 Orthogonal Frequency Division Multiplexing (OFDM) symbol 102 in the time axis and 1 subcarrier 103 in the frequency axis. It can be. in the frequency domain

(For example, 12) consecutive REs may constitute one resource block (Resource Block, RB, 104).

2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to an embodiment of the present disclosure.

)=14). 1 서브프레임(201)은 하나 또는 복수 개의 슬롯(202, 203)으로 구성될 수 있으며, 1 서브프레임(201)당 슬롯(202, 203)의 개수는 부반송파 간격에 대한 설정 값 μ(204, 205)에 따라 다를 수 있다. 도 2의 일 예에서는 부반송파 간격 설정 값으로 μ=0(204)인 경우와 μ=1(205)인 경우가 도시되어 있다. μ=0(204)일 경우, 1 서브프레임(201)은 1개의 슬롯(202)으로 구성될 수 있고, μ=1(205)일 경우, 1 서브프레임(201)은 2개의 슬롯(203)으로 구성될 수 있다. 즉 부반송파 간격에 대한 설정 값 μ에 따라 1 서브프레임 당 슬롯 수(

)가 달라질 수 있고, 이에 따라 1 프레임 당 슬롯 수(

)가 달라질 수 있다. 각 부반송파 간격 설정 μ에 따른

및

는 하기의 표 1로 정의될 수 있다.2 shows an example of the structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, and therefore, one frame 200 may consist of a total of 10 subframes 201 . One slot (202, 203) may be defined as 14 OFDM symbols (that is, the number of symbols per slot (

)=14). One subframe 201 may consist of one or a plurality of slots 202 and 203, and the number of slots 202 and 203 per one subframe 201 is a set value for the subcarrier interval μ(204, 205 ) may vary. In an example of FIG. 2 , a case where μ=0 (204) and a case where μ=1 (205) are shown as the subcarrier interval setting value. When μ = 0 (204), 1 subframe 201 may consist of one slot 202, and when μ = 1 (205), 1 subframe 201 may consist of two slots 203 may consist of That is, the number of slots per 1 subframe according to the setting value μ for the subcarrier interval (

) may vary, and accordingly, the number of slots per frame (

) may vary. According to each subcarrier spacing setting μ

and

Can be defined in Table 1 below.

[Table 1]

[PDCCH: DCI related]

Next, downlink control information (DCI) in the 5G system will be described in detail.

Scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) in a 5G system is provided through DCI It is transmitted from the base station to the terminal. The UE may monitor the DCI format for fallback and the DCI format for non-fallback with respect to PUSCH or PDSCH. The contingency DCI format may be composed of a fixed field predefined between the base station and the terminal, and the non-preparation DCI format may include a configurable field.

DCI may be transmitted through a physical downlink control channel (PDCCH) through channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC may be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used according to the purpose of the DCI message, eg, UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly but is included in the CRC calculation process and transmitted. Upon receiving the DCI message transmitted on the PDCCH, the UE checks the CRC using the allocated RNTI, and if the CRC check result is correct, the UE can know that the corresponding message has been transmitted to the UE.

For example, DCI scheduling a PDSCH for system information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a paging message may be scrambled with a P-RNTI. DCI notifying SFI (Slot Format Indicator) may be scrambled with SFI-RNTI. DCI notifying TPC (Transmit Power Control) can be scrambled with TPC-RNTI. DCI scheduling UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. DCI format 0_0 in which CRC is scrambled with C-RNTI may include, for example, the following information.

[Table 2]

DCI format 0_1 can be used as a non-backup DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. DCI format 0_1 in which CRC is scrambled with C-RNTI may include, for example, the following information.

[Table 3]

DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. DCI format 1_0 in which CRC is scrambled with C-RNTI may include, for example, the following information.

[Table 4]

DCI format 1_1 can be used as a non-backup DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. DCI format 1_1 in which CRC is scrambled with C-RNTI may include, for example, the following information.

[Table 5]

[PDSCH: Processing Time]

Next, PDSCH processing procedure time will be described. When the base station schedules the terminal to transmit the PDSCH using DCI format 1_0, 1_1, or 1_2, the terminal uses the DCI-instructed transmission method (modulation and coding instruction index (MCS), demodulation reference signal related information, time and PDSCH processing time for receiving PDSCH by applying frequency resource allocation information, etc.) may be required. In NR, the PDSCH processing time was defined in consideration of this. The PDSCH processing time of the UE may follow [Equation 1] below.

[Equation 1]

T _proc,1 = (N _One + d _1,1 + d ₂ )( 2048 + 144 ) κ2 ^-μ T _c +T _ext

In T _proc,1 described above with [Equation 1], each variable may have the following meaning.

- N ₁ : The number of symbols determined according to UE processing capability 1 or 2 and numerology μ according to the capabilities of the UE. If it is reported as UE processing capability 1 according to the UE's capability report, it has the value of [Table 6], and it is reported as UE processing capability 2 and it is set through higher layer signaling that UE processing capability 2 can be used [Table 7] can have a value of The numerology μ may correspond to the minimum value among μ _PDCCH , μ _{PDSCH , and} μ _UL so as to maximize the T _proc,1 , and μ _PDCCH , μ _{PDSCH , and} μ _UL are the numerology and schedule of the PDCCH for which the PDSCH is scheduled, respectively. It may mean the numerology of the received PDSCH and the numerology of the uplink channel through which the HARQ-ACK will be transmitted.

[Table 6]

[Table 7]

- κ: 64

- T _ext : When the UE uses the shared spectrum channel access method, the UE may calculate T _ext and apply it to the PDSCH processing time. Otherwise, T _ext is assumed to be zero.

- If l ₁ representing the PDSCH DMRS location value is 12, N1,0 in [Table x2-2] has a value of 14, otherwise it has a value of 13.

- For PDSCH mapping type A, the last symbol of the PDSCH is the ith symbol in the slot in which the PDSCH is transmitted, and if i < 7, d _1,1 is 7-i, otherwise d _1,1 is 0.

-d ₂ : When a PUCCH with a high priority index and a PUCCH or PUSCH with a low priority index overlap in time, d ₂ of the PUCCH with a high priority index may be set to a value reported from the UE. Otherwise, d ₂ is 0.

- When PDSCH mapping type B is used for UE processing capability 1, the value of d _1,1 is the number of symbols L, which is the number of symbols of the scheduled PDSCH, and the PDCCH scheduling the PDSCH and the scheduled PDSCH. Depending on d, the number of overlapping symbols can be determined

- If L ≥ 7, then d _1,1 = 0.

- if L ≥ 4 and L ≤ 6, then d _1,1 = 7 - L.

- if L = 3, then d _1,1 = min (d, 1).

- If L = 2, then d _1,1 = 3 + d.

- When PDSCH mapping type B is used for UE processing capability 2, the value of d _1,1 is the number of symbols L of the scheduled PDSCH and the number of overlapping symbols between the PDCCH scheduling the PDSCH and the scheduled PDSCH as follows. Depending on d can be determined

- If L ≥ 7, then d _1,1 = 0.

- if L ≥ 4 and L ≤ 6, then d _1,1 = 7 - L.

- if L = 2,

- If the scheduling PDCCH exists in a CORESET consisting of 3 symbols, and the CORESET and the scheduled PDSCH have the same start symbol, d _1,1 = 3.

- otherwise, d _1,1 = d.

- In the case of a UE supporting capability 2 within a given serving cell, PDSCH processing time according to UE processing capability 2 can be applied when the UE sets processingType2Enabled, which is higher layer signaling, to enable for the corresponding cell.

If the position of the first uplink transmission symbol of the PUCCH including HARQ-ACK information is (the corresponding position is defined as the HARQ-ACK transmission time K ₁ - , the PUCCH resource used for HARQ-ACK transmission, and the timing advance effect can be considered) If it does not start earlier than the first uplink transmission symbol that appears after a time of T _proc,1 from the last symbol of the PDSCH, the UE must transmit a valid HARQ-ACK message. That is, the UE must transmit the PUCCH including the HARQ-ACK only when the PDSCH processing time is sufficient. Otherwise, the terminal cannot provide valid HARQ-ACK information corresponding to the scheduled PDSCH to the base station. The above T- _proc,1 can be used for both general and extended CP cases. In the case of a PDSCH composed of two PDSCH transmission positions within one slot, d _1,1 is calculated based on the first PDSCH transmission position within the corresponding slot.

[PDSCH: Receive preparation time for cross-carrier scheduling]

In the case of cross-carrier scheduling in which μ _PDCCH , which is the numerology through which PDCCH to be scheduled next is transmitted, and μ _PDSCH , which is the numerology through which PDSCH scheduled through the corresponding PDCCH is transmitted, are different from each other, the UE defined for the time interval between the PDCCH and the PDSCH The PDSCH reception preparation time of N- _pdsch is described.

If μ _PDCCH < μ _PDSCH , the scheduled PDSCH cannot be transmitted earlier than the first symbol of the slot following N _pdsch symbols from the last symbol of the PDCCH that scheduled the corresponding PDSCH. A transmission symbol of the corresponding PDSCH may include a DM-RS.

If μ _PDCCH > μ _PDSCH , the scheduled PDSCH may be transmitted from N _pdsch symbols after the last symbol of the PDCCH that scheduled the corresponding PDSCH. A transmission symbol of the corresponding PDSCH may include a DM-RS.

[Table 8]

[PUSCH: related to transmission method]

Next, a scheduling method for PUSCH transmission will be described. PUSCH transmission can be dynamically scheduled by a UL grant in DCI or operated by configured grant Type 1 or Type 2. Dynamic scheduling indication for PUSCH transmission is available in DCI format 0_0 or 0_1.

Configured grant Type 1 PUSCH transmission can be set semi-statically through reception of configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 9] through higher signaling without reception of UL grant in DCI. Configured grant Type 2 PUSCH transmission can be scheduled semi-persistently by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 9] through upper signaling. When PUSCH transmission operates by a configured grant, parameters applied to PUSCH transmission are [Except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by push-Config of [Table 10], which is an upper signaling. It is applied through configuredGrantConfig, which is the upper signaling of Table 9]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 9], the terminal applies tp-pi2BPSK in push-Config of [Table 10] to PUSCH transmission operated by the configured grant.

ConfiguredGrantConfig ::= SEQUENCE {
frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,
cg-DMRS-Configuration DMRS-UplinkConfig,
mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH } OPTIONAL, -- Need M
resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch },
rbg-Size ENUMERATED {config2} OPTIONAL, -- Need S
powerControlLoopToUse ENUMERATED {n0, n1},
p0-PUSCH-Alpha P0-PUSCH-AlphaSetId;
transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S
nrofHARQ-Processes INTEGER(1..16),
repK ENUMERATED {n1, n2, n4, n8},
repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need R
periodicity ENUMERATED {
sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,
sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,
sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,
sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,
sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,
sym1280x12, sym2560x12
},
configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need R
rrc-ConfiguredUplinkGrant SEQUENCE {
timeDomainOffset INTEGER (0..5119),
timeDomainAllocation INTEGER (0..15),
frequencyDomainAllocation BIT STRING (SIZE(18)),
antennaPort INTEGER (0..31),
dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R
precodingAndNumberOfLayers INTEGER (0..63),
srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R
mcsAndTBS INTEGER (0..31),
frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R
pathlossReferenceIndex INTEGER(0..maxNrofPUSCH-PathlossReferenceRSs-1),
...
} OPTIONAL, -- Need R
...
}

Next, a PUSCH transmission method will be described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission may follow a codebook-based transmission method or a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in push-Config of [Table x2-4], which is an upper signaling, is 'codebook' or 'nonCodebook'. As described above, PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically set by configured grant. If the UE is instructed to schedule PUSCH transmission through DCI format 0_0, the UE performs PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the uplink BWP activated in the serving cell. Beam configuration for transmission is performed, and at this time, PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission through DCI format 0_0 in a BWP in which PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE is not configured with txConfig in push-Config of [Table 10], the UE does not expect to be scheduled in DCI format 0_1.

PUSCH-Config ::= SEQUENCE {
dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need S
txConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need S
dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M
dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M

pushch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need M
frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S
frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)
OPTIONAL, -- Need M
resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},
pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M
pusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S
mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S
codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}
OPTIONAL, -- Cond codebookBased
maxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBased
rbg-Size ENUMERATED { config2} OPTIONAL, -- Need S
uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need M
tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S
...
}

Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can operate quasi-statically by configured grant. If the codebook-based PUSCH is dynamically scheduled by DCI format 0_1 or quasi-statically configured by configured grant, the UE uses the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (PUSCH transmission layer number), a precoder for PUSCH transmission is determined. At this time, SRI may be given through a field SRS resource indicator in DCI or set through higher signaling, srs-ResourceIndicator. When transmitting codebook-based PUSCH, the UE receives at least one SRS resource and can set up to two SRS resources. When a UE receives SRI through DCI, the SRS resource indicated by the corresponding SRI means an SRS resource corresponding to the SRI among SRS resources transmitted prior to the PDCCH including the corresponding SRI. In addition, TPMI and transmission rank may be given through a field precoding information and number of layers in DCI or set through precodingAndNumberOfLayers, which is an upper level signaling. TPMI is used to indicate a precoder applied to PUSCH transmission. If the UE is configured with one SRS resource, TPMI is used to indicate a precoder to be applied in the configured one SRS resource. If the UE is configured with a plurality of SRS resources, TPMI is used to indicate a precoder to be applied in the SRS resource indicated through the SRI.

A precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config, which is higher signaling. In codebook-based PUSCH transmission, the UE determines a codebook subset based on TPMI and codebookSubset in push-Config, which is higher signaling. CodebookSubset in push-Config, which is higher signaling, may be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of codebookSubset, which is an upper level signaling, to be set to 'fullyAndPartialAndNonCoherent'. In addition, if the terminal reports 'nonCoherent' as the UE capability, the terminal does not expect the value of codebookSubset, which is higher signaling, to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. When nrofSRS-Ports in SRS-ResourceSet, which is higher signaling, indicates two SRS antenna ports, the UE does not expect the value of codebookSubset, which is higher signaling, to be set to 'partialAndNonCoherent'.

The terminal can receive one SRS resource set in which the value of usage in the SRS-ResourceSet, which is higher signaling, is set to 'codebook', and one SRS resource in the corresponding SRS resource set can be indicated through SRI. If several SRS resources are set in an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the UE sets the same value for all SRS resources in the nrofSRS-Ports value in the upper signaling SRS-Resource. expect this to be set.

The terminal transmits one or more SRS resources included in the SRS resource set in which the value of usage is set to 'codebook' to the base station according to higher signaling, and the base station selects one of the SRS resources transmitted by the terminal to correspond to the SRS Instructs the UE to perform PUSCH transmission using the transmission beam information of the resource. At this time, in codebook-based PUSCH transmission, SRI is used as information for selecting an index of one SRS resource and is included in DCI. Additionally, the base station includes information indicating the TPMI and rank to be used by the terminal for PUSCH transmission in the DCI. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI and applying the rank indicated by the transmission beam of the corresponding SRS resource and the precoder indicated by the TPMI.

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 operate quasi-statically by configured grant. When at least one SRS resource is set in an SRS resource set in which the value of usage in the SRS-ResourceSet, which is higher signaling, is set to 'nonCodebook', the terminal can receive non-codebook based PUSCH transmission scheduling through DCI format 0_1.

For an SRS resource set in which the value of usage in the SRS-ResourceSet, which is higher signaling, is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE may calculate a precoder for SRS transmission through measurement of NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource associated with the SRS resource set and the first symbol of aperiodic SRS transmission in the UE is less than 42 symbols, the UE updates the information on the precoder for SRS transmission. don't expect to be

When the value of resourceType in SRS-ResourceSet, which is higher signaling, is set to 'aperiodic', the connected NZP CSI-RS is indicated by SRS request, which is a field in DCI format 0_1 or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the connected NZP CSI-RS exists when the value of the field SRS request in DCI format 0_1 or 1_1 is not '00' will point to At this time, the corresponding DCI must not indicate cross carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the existence of the NZP CSI-RS, the corresponding NZP CSI-RS is located in the slot where the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS may be indicated through associatedCSI-RS in the SRS-ResourceSet, which is higher signaling. For non-codebook based transmission, the UE does not expect spatialRelationInfo, which is higher signaling for SRS resource, and associatedCSI-RS in SRS-ResourceSet, which is higher signaling, to be set together.

When a plurality of SRS resources are configured, the UE may determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, SRI may be indicated through a field SRS resource indicator in DCI or set through higher signaling srs-ResourceIndicator. Similar to the above codebook-based PUSCH transmission, when a UE receives SRI through DCI, the SRS resource indicated by the corresponding SRI selects the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH including the corresponding SRI. it means. The UE can use one or a plurality of SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. It is decided. At this time, SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set in which the value of usage in the SRS-ResourceSet, which is an upper signaling, is set to 'nonCodebook' can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

The base station transmits one NZP-CSI-RS associated with the SRS resource set to the terminal, and the terminal transmits one or more SRS resources in the corresponding SRS resource set based on the measurement result when receiving the corresponding NZP-CSI-RS Calculate the precoder to use when transmitting. The terminal applies the calculated precoder when transmitting one or more SRS resources in the SRS resource set with usage set to 'nonCodebook' to the base station, and the base station uses one or more of the one or more SRS resources received. Select SRS resource. At this time, in non-codebook based PUSCH transmission, SRI indicates an index capable of expressing a combination of one or a plurality of SRS resources, and the SRI is included in DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the UE transmits the PUSCH by applying a precoder applied to transmission of the SRS resource to each layer.

[PUSCH: Preparatory Course Hours]

Next, the PUSCH preparation procedure time will be described. When the base station schedules the UE to transmit the PUSCH using DCI format 0_0, 0_1, or 0_2, the UE uses the DCI-instructed transmission method (transmission precoding method of SRS resource, number of transmission layers, spatial domain transmission filter) A PUSCH preparation process time may be required to transmit the PUSCH by applying . NR defined the PUSCH preparation process time considering this. The UE's PUSCH preparation process time may follow [Equation 2] below.

[Equation 2]

T _proc,2 = max(( N ₂ + d _2,1 + d ₂ )( 2048 + 144 ) κ2 ^-μ T _c + T _ext + T _switch , d _2,2 )

In T _proc,2 described above with [Equation 2], each variable may have the following meaning.

-N ₂ : The number of symbols determined according to UE processing capability 1 or 2 and numerology μ according to the capabilities of the UE. When reported as UE processing capability 1 according to the capability report of the UE, with the value of [Table 11], when reported as UE processing capability 2 and capable of using UE processing capability 2 is set through higher layer signaling [Table 12] can have a value of

[Table 11]

[Table 12]

-d _2,1 : The number of symbols determined as 0 when all resource elements of the first OFDM symbol of PUSCH transmission are set to consist of only DM-RS, and 1 otherwise.

- κ: 64

- μ: Follows the larger value of T _proc,2 , either μ _DL or μ _UL . μ _DL means downlink numerology through which PDCCH including DCI scheduling PUSCH is transmitted, and μ _UL means uplink numerology through which PUSCH is transmitted.

,

,

를 가진다.- T _c :

,

,

have

-d _2,2 : Follows the BWP switching time when the DCI scheduling the PUSCH indicates BWP switching, otherwise has 0.

- d ₂ : When OFDM symbols of a PUCCH, a PUSCH with a high priority index, and a PUCCH with a low priority index overlap in time, the d ₂ value of the PUSCH with a high priority index is used. Otherwise, d ₂ is 0.

- T _ext : If the UE uses the shared spectrum channel access method, the UE can calculate T _ext and apply it to the PUSCH preparation process time. Otherwise, T _ext is assumed to be zero.

- T _switch : When an uplink switching interval is triggered, T _switch is assumed to be the switching interval time. otherwise, it is assumed to be 0.

When the base station and the terminal consider the time axis resource mapping information of the PUSCH scheduled through the DCI and the effect of the uplink-downlink timing advance, from the last symbol of the PDCCH including the DCI scheduled the PUSCH to after T _proc,2 If the first symbol of the PUSCH starts before the first uplink symbol that the CP starts, it is determined that the PUSCH preparation process time is not sufficient. If not, the base station and the terminal determine that the PUSCH preparation process time is sufficient. The UE may transmit the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI for scheduling the PUSCH when the PUSCH preparation time is not sufficient.

[PUSCH: related to repetitive transmission]

Hereinafter, repetitive transmission of an uplink data channel in a 5G system will be described in detail. The 5G system supports two types, PUSCH repeated transmission type A and PUSCH repeated transmission type B, as repeated transmission methods of an uplink data channel. The UE may be configured with either PUSCH repetitive transmission type A or B through higher layer signaling.

PUSCH repetitive transmission type A

- As described above, the symbol length of the uplink data channel and the location of the start symbol are determined by the time domain resource allocation method within one slot, and the base station sets the number of repeated transmissions through higher layer signaling (eg, RRC signaling) or L1 signaling ( For example, the UE may be notified through DCI).

- The terminal may repeatedly transmit an uplink data channel having the same length and start symbol in consecutive slots based on the number of repeated transmissions received from the base station. At this time, when at least one symbol of a slot set by the base station to the terminal as downlink or a symbol of an uplink data channel configured by the terminal is set to downlink, the terminal skips transmission of the uplink data channel, but uplink The number of repeated transmissions of the data channel is counted.

PUSCH repetitive transmission type B

- As described above, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method within one slot, and the base station transmits the number of repetitions numberofrepetitions through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI) may notify the UE.

에 의해 주어지고 그 슬롯에서 시작하는 심볼은

에 의해 주어진다. n번째 nominal repetition이 끝나는 슬롯은

에 의해 주어지고 그 슬롯에서 끝나는 심볼은

에 의해 주어진다. 여기서 n=0, ..., numberofrepetitions-1 이고 S는 설정 받은 상향링크 데이터 채널의 시작 심볼 L은 설정 받은 상향링크 데이터 채널의 심볼 길이를 나타낸다. K_s는 PUSCH 전송이 시작하는 슬롯을 나타내고

는 슬롯당 심볼의 수를 나타낸다. - The nominal repetition of the uplink data channel is determined as follows based on the start symbol and length of the uplink data channel that is set first. The slot where the nth nominal repetition starts is

The symbol given by and starting in that slot is

given by The slot where the nth nominal repetition ends is

The symbol given by and ending in that slot is

given by Here, n = 0, ..., numberofrepetitions-1, S is the start symbol of the configured uplink data channel, L represents the symbol length of the configured uplink data channel. K _s represents a slot in which PUSCH transmission starts

represents the number of symbols per slot.

- The UE determines an invalid symbol for PUSCH repetitive transmission type B. A symbol configured for downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is determined as an invalid symbol for PUSCH repeated transmission type B. Additionally, invalid symbols can be set in higher-level parameters (e.g. InvalidSymbolPattern). A higher layer parameter (e.g. InvalidSymbolPattern) provides a symbol-level bitmap spanning one slot or two slots so that invalid symbols can be set. 1 in the bitmap represents an invalid symbol. Additionally, the period and pattern of the bitmap may be set through a higher layer parameter (for example, periodicityAndPattern). If a higher layer parameter (eg InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If the upper layer parameter (eg InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies the invalid symbol pattern.

After the invalid symbol is determined, for each nominal repetition, the terminal may consider symbols other than the invalid symbol as valid symbols. If more than one valid symbol is included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition includes a contiguous set of valid symbols that can be used for PUSCH repeated transmission type B in one slot.

3 is a diagram illustrating an example of PUSCH repeated transmission type B in a wireless communication system according to an embodiment of the present disclosure. The terminal may set the start symbol S of the uplink data channel to 0 and the length L of the uplink data channel to 14, and set the number of repeated transmissions to 16. In this case, nominal repetition is indicated in 16 consecutive slots (301). After that, the terminal may determine a symbol set as a downlink symbol in each nominal repetition 301 as an invalid symbol. In addition, the terminal determines symbols set to 1 in the invalid symbol pattern 302 as invalid symbols. In each nominal repetition, when valid symbols, not invalid symbols, consist of one or more consecutive symbols in one slot, they are set as actual repetitions and transmitted (303).

In addition, for repeated PUSCH transmission, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmission and configured grant-based PUSCH transmission across slot boundaries.

-Method 1 (mini-slot level repetition): Through one UL grant, two or more repeated PUSCH transmissions are scheduled within one slot or across the boundary of consecutive slots. Also, for method 1, time domain resource allocation information in DCI indicates resources of the first repeated transmission. In addition, time domain resource information of the remaining repeated transmissions may be determined according to time domain resource information of the first repeated transmission and an uplink or downlink direction determined for each symbol of each slot. Each repeated transmission occupies consecutive symbols.

- Method 2 (multi-segment transmission): Two or more repeated PUSCH transmissions are scheduled in consecutive slots through one UL grant. At this time, one transmission is designated for each slot, and different start points or repetition lengths may be different for each transmission. Also, in method 2, the time domain resource allocation information in the DCI indicates the start point and repetition length of all repeated transmissions. In addition, when repeated transmission is performed within a single slot through method 2, if there are several bundles of consecutive uplink symbols in the corresponding slot, each repeated transmission is performed for each bundle of uplink symbols. If a bundle of consecutive uplink symbols exists uniquely in the corresponding slot, one repetition of PUSCH transmission is performed according to the method of NR Release 15.

- Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive slots through two or more UL grants. At this time, one transmission is designated for each slot, and the n-th UL grant can be received before the PUSCH transmission scheduled for the n-1-th UL grant ends.

-Method 4: Through one UL grant or one configured grant, one or several PUSCH repeated transmissions within a single slot, or two or more PUSCH repeated transmissions across the boundary of consecutive slots Can be supported. . The number of repetitions indicated by the base station to the terminal is only a nominal value, and the number of repeated PUSCH transmissions actually performed by the terminal may be greater than the nominal number of repetitions. Time domain resource allocation information within the DCI or within the configured grant means the resource of the first repeated transmission indicated by the base station. Time domain resource information of the remaining repeated transmissions may be determined by referring to resource information of at least the first repeated transmission and uplink or downlink directions of symbols. If the time domain resource information of repeated transmission indicated by the base station spans a slot boundary or includes an uplink/downlink switching point, the repeated transmission may be divided into a plurality of repeated transmissions. In this case, one repetitive transmission may be included for each uplink period in one slot.

[PUSCH: frequency hopping process]

In the following, frequency hopping of a physical uplink shared channel (PUSCH) in a 5G system will be described in detail.

In 5G, as a frequency hopping method of an uplink data channel, two methods are supported for each PUSCH repeated transmission type. First, PUSCH repetition transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, and PUSCH repetition transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

The intra-slot frequency hopping method supported by PUSCH repetitive transmission type A is a method in which a UE changes and transmits allocated resources in a frequency domain by a set frequency offset in two hops within one slot. In intra-slot frequency hopping, the starting RB of each hop can be expressed through Equation 4.

[Equation 4]

는 UL BWP안에서 시작 RB를 나타내고 주파수 자원 할당 방법으로부터 계산된다.

은 상위 계층 파라미터를 통해 두개의 홉 사이에 주파수 오프셋을 나타난다. 첫번째 홉의 심볼 수는

로 나타낼 수 있고, 두번째 홉의 심볼 수는

으로 나타낼 수 있다.

은 한 슬롯 내에서의 PUSCH 전송의 길이로, OFDM 심볼 수로 나타난다. In Equation 4, i = 0 and i = 1 represent the first hop and the second hop, respectively,

denotes the starting RB in the UL BWP and is calculated from the frequency resource allocation method.

represents a frequency offset between two hops through an upper layer parameter. The number of symbols in the first hop is

, and the number of symbols in the second hop is

can be expressed as

is the length of PUSCH transmission within one slot and is represented by the number of OFDM symbols.

슬롯 동안 시작 RB는 수학식 5를 통해 나타낼 수 있다.Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the UE changes and transmits allocated resources in the frequency domain by a set frequency offset for each slot. In Inter-slot frequency hopping

A starting RB during a slot can be expressed through Equation 5.

[Equation 5]

는 multi-slot PUSCH 전송에서 현재 슬롯 번호,

는 UL BWP안에서 시작 RB를 나타내고 주파수 자원 할당 방법으로부터 계산된다.

은 상위 계층 파라미터를 통해 두개의 홉 사이에 주파수 오프셋을 나타낸다.In Equation 5,

is the current slot number in multi-slot PUSCH transmission,

denotes the starting RB in the UL BWP and is calculated from the frequency resource allocation method.

represents a frequency offset between two hops through a higher layer parameter.

Next, the inter-repetition frequency hopping method supported by PUSCH repeated transmission type B moves and transmits resources allocated in the frequency domain for one or a plurality of actual repetitions within each nominal repetition by a set frequency offset. RB _start (n), which is an index of a start RB in the frequency domain for one or a plurality of actual repetitions within the n-th nominal repetition, may follow Equation 6 below.

[Equation 6]

은 상위 계층 파라미터를 통해 두 개의 홉 사이에 RB 오프셋을 나타낸다.In Equation 6, n is the index of nominal repetition,

represents an RB offset between two hops through a higher layer parameter.

[PUSCH: multiplexing rule for AP/SP CSI reporting]

In the following, a method of measuring and reporting a channel state in a 5G communication system will be described in detail. Channel state information (CSI) includes channel quality information (CQI), precoding matrix index (PMI), CSI-RS resource indicator (CRI), SS /PBCH block resource indicator (SS / PBCH block resource indicator, SSBRI), layer indicator (LI), rank indicator (rank indicator, RI), and / or L1-RSRP (Reference Signal Received Power), etc. may be included there is. The base station may control time and frequency resources for the aforementioned CSI measurement and reporting of the terminal.

For the above-described CSI measurement and reporting, the UE sets setting information for N (≥1) CSI reports (CSI-ReportConfig), M≥1) RS transmission resource setting information (CSI-ResourceConfig), One or two trigger state (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) list information can be set through higher layer signaling. The setting information for the aforementioned CSI measurement and reporting may be as follows described in [Table 13] to [Table 18] in more detail.

[Table 13] CSI-ReportConfig

The IE CSI-ReportConfig is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI-ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214 [19], clause 5.2.1.

CSI-ReportConfig information element

CSI-ReportConfig field descriptions

carrier

Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration.

codebookConfig

Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network does not configure codebookConfig and codebookConfig-r16 simultaneously to a UE

cqi-FormatIndicator

Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI. (see TS 38.214 [19], clause 5.2.1.4).

cqi-Table

Which CQI table to use for CQI calculation (see TS 38.214 [19], clause 5.2.2.1).

csi-IM-ResourcesForInterference

CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

csi-ReportingBand

Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise, the number of sub bands can be from 3 (24 PRBs, sub band size 8) to 18 (72 PRBs, sub band size 4).

dummy

This field is not used in the specification. If received it shall be ignored by the UE.

groupBasedBeamReporting

Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4).

non-PMI-PortIndication

Port indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2).

The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI -RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI -RS-ResourceSetList of the same CSI-ResourceConfig, and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig. Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on.

nrofReportedRS

The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is either 2 or 4 depending on UE capability.

(see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1.

nzp-CSI-RS-ResourcesForInterference

NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

p0alpha

Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2).

pdsch-BundleSizeForCSI

PRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2).

pmi-FormatIndicator

Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4).

pucch-CSI-ResourceList

Indicates which PUCCH resource to use for reporting on PUCCH.

reportConfigType

Time domain behavior of reporting configuration.

reportFreqConfiguration

Reporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4).

reportQuantity

The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix).

reportSlotConfig

Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).

reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2

Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the push-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity.

Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the push-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetList applies to DCI format 0_0, the field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1).

resourcesForChannelMeasurement

Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.

subbandSize

Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2. If csi-ReportingBand is absent, the UE shall ignore this field.

timeRestrictionForChannelMeasurements

Time domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1).

timeRestrictionForInterferenceMeasurements

Time domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1).

[Table 14] CSI-ResourceConfig

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

CSI-ResourceConfig information element

CSI-ResourceConfig field descriptions

bwp-Id

The DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214 [19], clause 5.2.1.2.

csi-IM-ResourceSetList

List of references to CSI-IM resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2).

csi-ResourceConfigId

Used in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig.

csi-SSB-ResourceSetList

List of references to SSB resources used for beam measurement and reporting in a CSI-RS resource set (see TS 38.214 [19], clause 5.2.1.2).

nzp-CSI-RS-ResourceSetList

List of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2).

resourceType

Time domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList.

[Table 15] NZP-CSI-RS-ResourceSet

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

NZP-CSI-RS-ResourceSet information element

NZP-CSI-RS-ResourceSet field descriptions

aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16

Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset, the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16, the value indicates the number of slots. The network configures only one of the fields. When neither field is included, the UE applies the value 0.

nzp-CSI-RS-Resources

NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214 [19], clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set.

repetition

Indicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP or "no report".

trs-Info

Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214 [19], clause 5.2.2.3.1).

[Table 16-1] CSI-SSB-ResourceSet

The IE CSI-SSB-ResourceSet is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon.

CSI-SSB-ResourceSet information element

[Table 16-2] CSI-IM-ResourceSet

The IE CSI-IM-ResourceSet is used to configure a set of one or more CSI Interference Management (IM) resources (their IDs) and set-specific parameters.

CSI-IM-ResourceSet information element

CSI-IM-ResourceSet field descriptions

csi-IM-Resources

CSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214 [19], clause 5.2)

[Table 17] CSI-AperiodicTriggerStateList

The 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 reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state.

CSI-AperiodicTriggerStateList information element

CSI-AssociatedReportConfigInfo field descriptions

csi-IM-ResourcesForInterference

CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in nzp-CSI-RS-ResourcesforChannel.

csi-SSB-ResourceSet

CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on).

nzp-CSI-RS-ResourcesForInterference

NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to the second entry, and so on ).

qcl-info

List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by nzp-CSI-RS- ResourcesforChannel. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info-forChannel corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info-forChannel corresponds to second entry in nzp-CSI-RS-Resources , and so on (see TS 38.214 [19], clause 5.2.1.5.1)

reportConfigId

The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig

resourceSet

NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (1 corresponds to the first entry, 2 to thesecond entry, and so on).

[Table 18] CSI-SemiPersistentOnPUSCH-TriggerStateList

The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214 [19], clause 5.2.

CSI-SemiPersistentOnPUSCH-TriggerStateList information element

Regarding the above-described CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig is a CSI resource setting associated with the corresponding report setting, a higher layer parameter bandwidth part identifier (bwp-id) given as CSI-ResourceConfig. It can be associated with one identified downlink (DL) bandwidth portion. As a time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, which depend on the reportConfigType parameter set from the upper layer. It can be configured from the base station to the terminal by As the semi-persistent CSI reporting method, 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)' are supported. In the case of a periodic or semi-permanent CSI reporting method, a UE may receive a PUCCH or PUSCH resource to transmit CSI from a base station through higher layer signaling. The period and slot offset of a PUCCH or PUSCH resource to transmit CSI may be given as a numerology of an uplink (UL) bandwidth portion configured to transmit CSI reports. In the case of the aperiodic CSI reporting method, the UE may receive scheduling of PUSCH resources to transmit CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

Regarding the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig may include S≥1) CSI resource sets (given by higher layer parameter csi-RS-ResourceSetList). The CSI resource set list may consist of a non-zero power (NZP) CSI-RS resource set and an SS/PBCH block set or a CSI-interference measurement (CSI-IM) resource set. can Each CSI resource setting may be located in a downlink (DL) bandwidth part identified by a higher layer parameter bwp-id, and the CSI resource setting may be linked to a CSI reporting setting of the same downlink bandwidth part. The time domain operation of the CSI-RS resource in the CSI resource setting may be set to one of 'aperiodic', 'periodic' or 'semi-permanent' from the upper layer parameter resourceType. For periodic or semi-permanent CSI resource setting, the number of CSI-RS resource sets may be limited to S = 1, and the set period and slot offset may be given as the numerology of the downlink bandwidth portion identified by bwp-id. The terminal may receive one or more CSI resource settings for channel or interference measurement from the base station through higher layer signaling, and may include, for example, the following CSI resources.

- CSI-IM resources for interference measurement

- NZP CSI-RS resource for interference measurement

- NZP CSI-RS resource for channel measurement

For CSI-RS resource sets associated with resource settings in which the upper layer parameter resourceType is set to 'non-periodic', 'periodic', or 'semi-permanent', for CSI reporting settings in which reportType is set to 'non-periodic' A trigger state and resource settings for channel or interference measurement for one or multiple component cells (CCs) may be set as an upper layer parameter CSI-AperiodicTriggerStateList.

Aperiodic CSI reporting of the UE may use PUSCH, periodic CSI reporting may use PUCCH, and semi-permanent CSI reporting may use DCI when triggered or activated by PUSCH, MAC control element, After being activated with MAC CE), it can be performed using PUCCH. As described above, CSI resource setting may also be set aperiodically, periodically, or semi-permanently. A combination of CSI reporting settings and CSI resource settings can be supported based on Table 19 below.

[Table 19

Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1 corresponding to the scheduling DCI for the PUSCH. The UE can monitor the PDCCH, obtain DCI format 0_1, and obtain scheduling information and a CSI request indicator for the PUSCH. The CSI request indicator may be set to NTS (= 0, 1, 2, 3, 4, 5, or 6) bits and may be determined by higher layer signaling (reportTriggerSize). One trigger state among one or a plurality of aperiodic CSI reporting trigger states that can be set by higher layer signaling (CSI-AperiodicTriggerStateList) can be triggered by a CSI request indicator.

- If all bits of the CSI request field are 0, this may mean that CSI reporting is not requested.

- If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, M CSI trigger states may be mapped to 2NTs-1 according to a predefined mapping relationship, and the number of 2NTs-1 One of the trigger conditions may be indicated by the CSI request field.

- If the number (M) of CSI trigger states in the configured CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states may be indicated in the CSI request field.

Table 20 below shows an example of a relationship between a CSI request indicator and a CSI trigger state that may be indicated by the corresponding indicator.

[Table 20]

The UE may perform measurement on the CSI resource in the CSI trigger state triggered by the CSI request field, and from this CSI (at least one or more of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) including) can be created. The UE may transmit the acquired CSI using the PUSCH scheduled by the corresponding DCI format 0_1. When 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 indicates "1", uplink data (UL-SCH) and acquired CSI are transmitted to PUSCH resources scheduled by DCI format 0_1 It can be transmitted by multiplexing. When 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 indicates “0”, mapping only CSI without uplink data (UL-SCH) to PUSCH resources scheduled by DCI format 0_1 can transmit

4 is a diagram illustrating an example of an aperiodic CSI reporting method.

In an example 400 of FIG. 4 , the UE may obtain DCI format 0_1 by monitoring the PDCCH 401 , and may obtain scheduling information and CSI request information for the PUSCH 405 from this. The UE may obtain resource information on the CSI-RS 402 to be measured from the received CSI request indicator. At a certain point in time based on the time when the terminal receives DCI format 0_1 and the parameter for the offset (aperiodicTriggeringOffset described above) in the CSI resource set setting (eg, NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet)) It may be determined whether measurement of the transmitted CSI-RS resource 402 should be performed. More specifically, the terminal transmits higher layer signaling from the base station to the offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration. may be set, and the set offset value X may mean an offset between a slot receiving DCI triggering aperiodic CSI reporting and a slot through which CSI-RS resources are transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship described in [Table 21] below.

[Table 21]

An example 400 of FIG. 4 shows an example in which the aforementioned offset value is set to X=0. In this case, the terminal may receive the CSI-RS 402 in the slot (corresponding to slot 0 406 in FIG. 4) in which DCI format 0_1 triggering the aperiodic CSI report is received, and the received CSI-RS The measured CSI information may be reported to the base station through the PUSCH 405. The UE may obtain scheduling information (information corresponding to each field of the aforementioned DCI format 0_1) for the PUSCH 405 for CSI reporting from DCI format 0_1. For example, the terminal may obtain information about a slot to transmit the PUSCH 405 from the above-described time domain resource allocation information for the PUSCH 405 in DCI format 0_1. In the example 400 of FIG. 4, the UE obtains a K2 value of 3 corresponding to the slot offset value for the PDCCH-to-PUSCH, and accordingly, at the time when the PUSCH 405 receives the PDCCH 401, slot 0 ( 406) can be transmitted in slot 3 (409), which is 3 slots away.

In an example 410 of FIG. 4 , the UE may obtain DCI format 0_1 by monitoring the PDCCH 411 , and may obtain scheduling information and CSI request information for the PUSCH 415 from this. The UE may obtain resource information about the CSI-RS 412 to be measured from the received CSI request indicator. An example 410 of FIG. 4 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal may receive the CSI-RS 412 in the slot (corresponding to slot 0 416 in FIG. 4) in which DCI format 0_1 triggering the aperiodic CSI report is received, and the received CSI-RS The measured CSI information may be reported to the base station through the PUSCH 415.

The aperiodic CSI report may include at least one or both of CSI part 1 and CSI part 2, and when the aperiodic CSI report is transmitted through the PUSCH, it may be multiplexed with the transport block. After the CRC is inserted into the input bits of the aperiodic CSI for multiplexing, encoding and rate matching can be performed, and then mapped to a resource element in the PUSCH in a specific pattern and transmitted. The CRC insertion may be omitted according to a coding method or the length of input bits. The number of modulation symbols calculated for rate matching when multiplexing CSI Part 1 or CSI part 2 included in the aperiodic CSI report can be calculated as shown in [Table 22].

, is determined as follows:
[수학식 3]

...
For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as

, is determined as follows:
[수학식 4]

...
For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as

, is determined as follows:
if there is CSI part 2 to be transmitted on the PUSCH,
[수학식 5]

else

...
end if
For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[수학식 6]

For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[수학식 7]

...
For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[수학식 8]

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as

, is determined as follows:
[Equation 3]

...
For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as

, is determined as follows:
[Equation 4]

...
For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as

, is determined as follows:
if there is CSI part 2 to be transmitted on the PUSCH,
[Equation 5]

else

...
end if
For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[Equation 6]

For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[Equation 7]

...
For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as

, is determined as follows:
[Equation 8]

In particular, in the case of repeated PUSCH transmission schemes A and B, the UE may multiplex and transmit the aperiodic CSI report only to the first repeated transmission among repeated PUSCH transmissions. This is because the multiplexed aperiodic CSI report information is encoded in a polar code method. At this time, to be multiplexed in multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, each actual repetition Since this can have different OFDM symbol lengths, the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition. In addition, for the repeated PUSCH transmission scheme B, the UE reports the aperiodic CSI without scheduling the transport block. When receiving a DCI that schedules or activates semi-persistent CSI reporting, the value of nominal repetition may be assumed to be 1 even if the number of repeated PUSCH transmissions set by higher layer signaling is greater than 1. In addition, when the terminal schedules or activates aperiodic or semi-permanent CSI reporting without scheduling for transport blocks based on the repeated PUSCH transmission scheme B, the terminal can expect the first nominal repetition to be the same as the first actual repetition. After semi-permanent CSI reporting is activated with DCI, for a PUSCH transmitted including semi-permanent CSI based on repeated PUSCH transmission scheme B without a schedule for DCI, if the first nominal repetition is different from the first actual repetition, the first nominal repetition Transmission for repetition may be ignored.

[PUCCH: UCI on PUSCH]

In the NR communication system, when the uplink control channel overlaps with the uplink data channel and satisfies the transmission time condition, or when transmitting the uplink control information to the uplink data channel through L1 signaling or higher signaling, the uplink control information It may be included in an uplink data channel and transmitted. At this time, a total of three uplink control information, HARQ-ACK, CSI part 1, and CSI part 2, can be transmitted on the uplink data channel, and each uplink control information can be mapped to the PUSCH according to a predetermined multiplexing rule. .

More specifically, when the number of HARQ-ACK information bits to be included in the PUSCH in the first step is 2 bits or less, the terminal reserves REs to transmit HARQ-ACK in advance. At this time, the method of determining the resource to be reserved is the same as in the second step. However, assuming that the number of HARQ-ACK bits is 2, the number and location of REs to be reserved are determined. That is, it is calculated based on Oack = 2 in Equation 9 below. In the second step, if the number of HARQ-ACK information bits to be transmitted by the UE is greater than 2 bits, the UE may map HARQ-ACK from the first OFDM symbol not including the DMRS after the first DMRS symbol. In the third step, the UE may map CSI part1 to PUSCH. In this case, CSI part1 may be mapped from the first OFDM symbol rather than the DMRS, and may not be mapped to the RE reserved in the first step and the RE to which the HARQ-ACK is mapped in the second step.

In the fourth step, the UE may map CSI part2 to PUSCH. In this case, CSI part2 may be mapped from the first OFDM symbol, not the DMRS, and may not be mapped to the RE where CSI part1 is located and the RE where HARQ-ACK mapped to the RE in the second step is located. However, it can be mapped to REs reserved in the first step. If there is a UL-SCH, the UE may map the UL-SCH to the PUSCH. In this case, the UL-SCH may be mapped from the first OFDM symbol, not the DMRS, and may not be mapped to the RE where CSI part1 is located, the RE where HARQ-ACK mapped to the RE in the second step, and the RE where CSI part2 is located. However, it can be mapped to REs reserved in the first step.

In the fifth step, if the HARQ-ACK is less than 2 bits, the UE may puncture and map the HARQ-ACK to the RE reserved in the first step. The number of REs to which the HARQ-ACK is mapped is calculated based on the actual number of HARQ-ACKs. That is, the number of REs to which HARQ-ACK is mapped may be smaller than the number of REs reserved in step 1 above. The meaning of the puncturing means that ACK is mapped instead of previously mapped CSI part2 or UL-SCH even if the RE to which HARQ-ACK is to be mapped becomes CSI part2 or UL-SCH in step 4. CSI part1 is not mapped to the reserved RE, so that puncturing by HARQ-ACK does not occur. This means that CSI part1 has a higher priority than CSI part2 and is intended to be decoded better. And, if the number of bits (or the number of modulated symbols) of uplink control information to be mapped to the PUSCH is greater than the number of bits (or RE) to which uplink control information can be mapped within the corresponding OFDM symbol to be mapped, uplink control information to be mapped The frequency axis RE interval d between modulated symbols of may be set to d = 1. If the number of bits (or the number of modulated symbols) of uplink control information to be mapped to the PUSCH by the UE is smaller than the number of bits (or RE0) capable of mapping uplink control information within the corresponding OFDM symbol to be mapped, the uplink control to be mapped The frequency axis RE interval d between modulated symbols of information may be set to d = floor (# of available bits on l-OFDM symbol / # of unmapped UCI bits at the beginning of l-OFDM symbol).

5 shows an example in which uplink control information is mapped to a PUSCH. In FIG. 5, it is assumed that the number of HARQ-ACK symbols to be mapped to the PUSCH is 5, and one resource block is configured or scheduled for the PUSCH. First, as shown in FIG. 5-(a), the UE performs HARQ-ACK of 5 symbols at an RE interval of d = floor (12/5) = 2 on the frequency axis, and the first OFDM symbol (504) that does not include the DMRS after the first DMRS. ), the HARQ-ACK may be mapped (501) from the lowest RE index (or the highest RE index). Next, the UE may map 502 CSI-part1 from the first non-DMRS OFDM symbol 505 as shown in FIG. 5-(b). Finally, as shown in FIG. 5-(c), the UE may map CSI part 2 503 to REs to which CSI-part1 and HARQ-ACK are not mapped from the first OFDM symbol not including DMRS.

Meanwhile, when HARQ-ACK is transmitted on PUSCH (or CG-PUSCH), the number of coded modulation symbols may be determined by [Equation 9].

[Equation 9]

는 각각 HARQ-ACK의 페이로드의 비트 수를 나타내고,

은 각각 CRC 비트 수를 의미한다. 보다 구체적으로는

,

그외에는

,

이다. K _r은 UL-SCH의 r 번째 코드 블록 사이즈이며,

는 기지국으로 설정 또는 스케줄링 받은 PUSCH 중 UCI 전송에 이용될 수 있는 OFDM 심볼 당 서브케리어 수를 나타낸다. 또한,

와

는 기지국으로 설정받은 값으로 상위 시그널링 또는 L1 시그널링으로 결정된다. 보다 구체적으로,

, 즉 베타 오프셋 값은 HARQ-ACK 정보가 다른 UCI 정보와 함께 multiplexing 되어 PUSCH(또는 CG-PUSCH)에 전송될 때, 리소스의 수를 결정하기 위해 정의된 값이다. 만약, fallback DCI(또는 DCI format 0_0) 또는 beta_offset 지시자 필드를 가지지 않는 non-fallback DCI(또는 DCI format 0_1)가 PUSCH 전송을 지시하고 단말이 상위 설정으로 베타 오프셋 값 설정을 'semi-static'으로 설정할 경우, 단말은 상위 설정으로 설정받은 하나의 베타 오프셋 값을 가질 수 있다. 이때, 베타 오프셋 [표 23]과 같은 테이블로 값을 가지며, 상위 설정으로 해당하는 값의 인덱스를 지시할 수 있며, HARQ-ACK 정보의 비트 수에 따라 인덱스

,

,

는 각각 HARQ-ACK 정보 비트 수가 2 이하, 2보다 크고 11이하, 11보다 큰 경우에 대한 베타 오프셋 값을 가질 수 있다. 또한, 동일한 방법으로 CSI-part1과 CSI-part2를 위한 베타 오프셋 값을 설정하는 것도 가능하다. 상기 베타 오프셋 값에 의하여 UL-SCH의 effective code rate 대비 UCI의 code rate을 조절 하는 효과가 있다. 즉 베타 오프셋 값이 2일 경우 (index=1) UCI의 code rate은 UL-SCH의 effective code rate 보다 1/2 로 더 낮은 부호율로 전송 하도록 설정 할 수 있다. here

Represents the number of bits of the payload of HARQ-ACK, respectively,

Each denotes the number of CRC bits. more specifically

,

otherwise

,

to be. K _r is the r th code block size of UL-SCH,

denotes the number of subcarriers per OFDM symbol that can be used for UCI transmission among PUSCHs configured or scheduled by the base station. also,

Wow

Is a value set by the base station and is determined by upper signaling or L1 signaling. More specifically,

, That is, the beta offset value is a value defined to determine the number of resources when HARQ-ACK information is multiplexed with other UCI information and transmitted on PUSCH (or CG-PUSCH). If a fallback DCI (or DCI format 0_0) or a non-fallback DCI (or DCI format 0_1) that does not have a beta_offset indicator field indicates PUSCH transmission, and the terminal sets the beta offset value setting to 'semi-static' as a higher setting In this case, the terminal may have one beta offset value set as a higher setting. At this time, the beta offset has a value in a table such as [Table 23], and the index of the corresponding value can be indicated by the higher setting, and the index according to the number of bits of HARQ-ACK information

,

,

may have a beta offset value for a case where the number of HARQ-ACK information bits is 2 or less, greater than 2, 11 or less, or greater than 11, respectively. Also, it is possible to set beta offset values for CSI-part1 and CSI-part2 in the same way. There is an effect of adjusting the code rate of UCI compared to the effective code rate of UL-SCH by the beta offset value. That is, when the beta offset value is 2 (index = 1), the code rate of UCI can be set to be transmitted at a code rate lower than the effective code rate of UL-SCH by 1/2.

[Table 23]

또는

또는

을 가지는 4개의 세트에 대한 베타 오프셋 값들을 구성하여 단말에게 설정할 있고, 단말은 HARQ-ACK multiplexing 때 이용할 베타 오프셋 값을 베타 오프셋 지시자 필드를 이용하여 지시할 수 있으며, 각 인덱스는 전술한 방법과 마찬가지로 HARQ-ACK 정보 비트 수에 따라 결정된다. 동일한 방법으로

,

의 세트를 지시할 수도 있다.If the base station schedules PUSCH transmission to the terminal using non-fallback DCI (or DCI format 0_1) and the non-fallback DCI has a beta offset indicator field, that is, set the beta offset value to 'dynamic' as the upper setting. In the case of HARQ-ACK, the base station as shown in [Table 24]

or

or

Beta offset values for 4 sets having . It is determined according to the number of HARQ-ACK information bits. In the same way

,

A set of may be indicated.

[Table 24]

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

, is determined as follows:

[Equation 9-A]

where

is the number of resource elements that can be used for transmission of UCI in OFDM symbol

, for

, in the PUSCH transmission assuming a nominal repetition without segmentation, and

is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS;-

is the number of resource elements that can be used for transmission of UCI in OFDM symbol

, for

, in the PUSCH transmission assuming a nominal repetition without segmentation, and

is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS;

;- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation,

;

where

is the number of subcarriers in OFDM symbol

that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation;- for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without segmentation,

where

is the number of subcarriers in OFDM symbol

that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation;

is the number of resource elements that can be used for transmission of UCI in OFDM symbol

, for

, in the 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;-

is the number of resource elements that can be used for transmission of UCI in OFDM symbol

, for

, in the 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;

;- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission;

;

where

is the number of subcarriers in OFDM symbol

that carries PTRS, in the actual repetition of the PUSCH transmission;- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission;

where

is the number of subcarriers in OFDM symbol

that carries PTRS, in the actual repetition of the PUSCH transmission;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B.

Meanwhile, when HARQ-ACK is transmitted on PUSCH (or CG-PUSCH), when UL-SCH does not exist, the number of coded modulation symbols may be determined by [Equation 9-B].

[Equation 9-B]

The R is a value set by the base station at the code rate of the PUSCH and is determined by higher level signaling or L1 signaling. Also, Qm means the order of the PUSCH modulation scheme.

을 기반으로 ACK의 부호어 비트의 개수

를 구할 수 있다. determined in Equation 9 and Equation 9-A

The number of codeword bits of ACK based on

can be obtained.

6 is a diagram illustrating a processing procedure for transmitting and receiving UCI information between a terminal and a base station through a PUSCH according to an embodiment of the present disclosure. According to the procedure of FIG. 6, the terminal generates UCI information in 600. In step 602, the terminal determines the UCI information size, and if it is 11 bits or less, the CRC is not included, and if it is greater than 12 bits, code block segmentation is additionally performed or the CRC is included according to the UCI information size. In step 604, the terminal performs channel coding of small block lengths when the size of the UCI information is less than 11 bits, and performs polar coding when the size of the UCI information is greater than 12 bits. In step 606, the terminal calculates the number of coded modulation symbols by performing rate matching according to [Equation 3] to [Equation 9] according to the type of UCI information. Code blocks are combined in 608, and UCI bit information encoded in PUSCH is multiplexed in 610. After the terminal transmits the modulated PUSCH to the base station, the base station demodulates the corresponding PUSCH in step 612 and demultiplexes the UCI bits encoded in the PUSCH. The base station divides the received information into code block units (614) and performs rate dematching (616). In step 618, decoding is performed using a coded channel coding method according to the size of UCI information. The base station combines the decoded code blocks at 620 and obtains UCI information. Through this series of procedures, UCI information is included in the PUSCH and transmitted/received. The flowchart described above in FIG. 6 is only an example, and at least one block of blocks 600 to 622 may be omitted under specific conditions. In addition, it may be sufficiently possible to add and operate blocks other than 600 to 622 included in the flowchart described above in FIG. 6 .

In the present disclosure, when a first control or first data information is mapped to a physical resource, rate matching excludes (or avoids) when a resource of the second control or second data information mapped first exists. This may refer to a method of mapping data information to a resource to which no resource has previously been mapped. In the present disclosure, when mapping a first control or first data information to a physical resource, even if a resource to which the second control or second data information is mapped exists, the corresponding second control or second data information is mapped to the physical resource. This may refer to a method of mapping first control or first data information to a resource and a resource to which no information has previously been mapped. Therefore, if the first control or first data information is actually mapped to a resource to which the second control or second data information is mapped first by puncturing later, the resource, not the second control or second data information, 1 control or first data information is transmitted and received.

Next, a procedure for multiplexing uplink data and control information is described in [Table 25].

[Table 25]

○ Step 1:

- When HARQ-ACK information to be transmitted on PUSCH is 0, 1, or 2 bits, reserved resources for potential HARQ-ACK transmission are determined. The reserved resources are determined in a frequency priority manner from the first symbol immediately after the symbol in which the first DMRS exists among the resources to which the PUSCH is allocated. The frequency priority method collectively refers to a method in which frequency resources are sequentially mapped for each symbol and then mapping is performed by moving to the next symbol. At this time, the amount of reserved resources can be calculated assuming that HARQ-ACK information is 2 bits.

- Depending on whether PUSCH hopping is performed, it is determined whether or not to divide coded bits for potential HARQ-ACK transmission by hop using reserved resources.

○ Step 2:

- When HARQ-ACK information to be transmitted on PUSCH is larger than 2 bits, rate matching is performed. That is, the coded bits of the HARQ-ACK information are mapped in a frequency priority manner from the first symbol right after the symbol in which the first DMRS exists among the resources to which the PUSCH is allocated.

○ Step 2A:

- When there is CG-UCI information to be transmitted on the PUSCH, rate matching is performed. That is, the coded bits of the CG-UCI information perform frequency priority mapping from the first symbol right after the symbol in which the first DMRS exists among the resources to which the PUSCH is allocated.

○ Step 3:

- If CSI part1 information to be transmitted in PUSCH exists, rate matching is performed. CSI part 1 performs frequency priority mapping immediately after excluding resources allocated with DMRS and HARQ-ACK reserved or HARQ-ACK or CG-UCI allocated in Step 1 or Step 2 or 2A from the first symbol from the resources allocated to PUSCH. Thereafter, CSI part 2 performs frequency priority mapping from the first symbol in the resources to which PUSCH is allocated, excluding resources to which DMRS and HARQ-ACK or CG-UCI allocated in Step 2 or 2A or CSI part 1 are allocated. CSI part2 can be allocated to the reserved RE allocated in step 1 above.

○ Step 4:

- Data information (UL-SCH) rate matching is performed. The UL-SCH performs frequency priority mapping on the resources to which the PUSCH is allocated except for the resources to which the UCI information mapped in Steps 2 and 3 are mapped. The UL-SCH can be allocated to the reserved RE allocated in step 1 above.

○ Step 5:

- When the HARQ-ACK information to be transmitted on the PUSCH is not larger than 2 bits, mapping is performed on the reserved resources in Step 1. At this time, since the amount of reserved resources is calculated assuming that HARQ-ACK is 2 bits, the actual mapped resources may be less than the number of reserved REs. If there is a UCI resource or UL-SCH previously mapped in steps 2 to 4 in the resource, the corresponding information is punctured and the HARQ-ACK information is mapped.

For the above steps, if the number of bits (or the number of modulated symbols) of uplink control information to be mapped to the PUSCH is greater than the number of bits (or RE) to which uplink control information can be mapped within the corresponding OFDM symbol to be mapped, the uplink control information to be mapped A frequency axis RE interval d between modulated symbols of link control information may be set to d=1. If the number of bits (or the number of modulated symbols) of uplink control information to be mapped to the PUSCH by the UE is smaller than the number of bits (or RE0) capable of mapping uplink control information within the corresponding OFDM symbol to be mapped, the uplink control to be mapped The frequency axis RE interval d between modulated symbols of information may be set to d = floor (# of available bits on l-OFDM symbol / # of unmapped UCI bits at the beginning of l-OFDM symbol).

[PUCCH/PUSCH: Priority level]

In the following, a transmission method of a UE according to priority information of PUCCH and PUSCH will be described.

When one terminal simultaneously supports eMBB and URLLC, it may be possible to transmit data or control information for eMBB through PUSCH or PUCCH, and transmit data or control information for URLLC through PUSCH or PUCCH. Since the requirements of the two services are different and the URLLC service generally takes precedence over the eMBB, if at least one symbol of the channel to which the eMBB is allocated overlaps with the channel to which the URLLC is allocated, the terminal selects at least one of the URLLC or eMBB channels. It may be possible to transmit by Specifically, the priority information may be indicated by a higher order signal or an L1 signal, and the priority information value may be 0 or 1. A PUCCH or PUSCH indicated by 0 may be regarded as for eMBB, and a PUCCH or PUSCH indicated as 1 may be regarded as for URLLC.

In the case of PUSCH, if there is a field that can indicate priority information in the DCI, the priority of the PUSCH is determined by a value indicated by the corresponding field. Even if a PUSCH is scheduled by DCI, if there is no field that can indicate a priority in the corresponding DCI, the UE regards the corresponding PUSCH as having a priority value of 0. The PUSCH can be applied both with or without Aperiodic CSI or Semi-persistent CSI. In the case of a configured grant PUSCH that is periodically transmitted and received without DCI, priority may be determined by an upper signal.

In the case of a PUCCH, the priority of a PUCCH for transmitting and receiving SR information and a PUCCH including HARQ-ACK information for an SPS PDSCH may be determined by a higher order signal. If there is a priority field in the corresponding DCI, the priority value indicated by the corresponding field is applied to the PUCCH including the HARQ-ACK information for the PDSCH scheduled by the DCI, and if there is no corresponding field, a priority of 0 considered to have a ranking value. In addition, a PUCCH including semi-persistent CSI or periodic CSI is always regarded as having a priority value of 0.

When the resources of the PUCCH or PUSCH indicated by an L1 signal such as a higher level signal or DCI overlap and at least some PUCCHs or PUSCHs have different priority information, the UE first selects a PUCCH or PUSCH having a priority information value of 0. Resolve nesting for . For example, a series of processes of including UCI information included in PUCCH in PUSCH may be included. Then, when the resource of the PUCCH or PUSCH finally determined through the overlapped PUCCH or PUSCH with low priority is referred to as the second PUCCH or the second PUSCH, and the PUCCH or PUSCH with the high priority is referred to as the first PUCCH or the second PUSCH , If the 2nd PUCCH or the 2nd PUSCH overlaps with the 1st PUCCH or the 1st PUSCH in terms of time resources, the UE cancels transmission of the 2nd PUCCH and the 2nd PUSCH. The UE expects that transmission of the 1st PUCCH or 1st PUSCH starts at least after the last symbol of PDCCH reception including the DCI scheduled for the transmission and after T _proc,2 +d ₁ . Otherwise, the terminal regards it as an error case. The value of T _proc,2 +d ₁ may be the value presented in [Equation 2].

According to the above description, the PUCCH including the HARQ-ACK information for the PDSCH including the eMBB data will have a value of 0 having a low priority, and the PUCCH including the HARQ-ACK information for the PDSCH including the URLLC data Priority will have a value of 1. Therefore, when the PUCCH with priority 0 and the PUCCH with priority 1 overlap in terms of time resources, the UE will drop the PUCCH with priority 0 and the PUCCH with priority 1 PUCCH will transmit. Therefore, from the point of view of the base station, since HARQ-ACK information for the PDSCH including the eMBB data has not been received, it is unknown whether the terminal properly received the corresponding eMBB data, and thus has no choice but to retransmit the eMBB data. Therefore, there is a possibility that eMBB data transmission and reception efficiency may be deteriorated.

For convenience of description, HARQ-ACK information for a PDSCH containing eMBB data is referred to as LP (Low Priority) HARQ-ACK, and HARQ-ACK information for a PDSCH containing URLLC data is referred to as HP (High Priority) HARQ-ACK. . LP (Low Priority) HARQ-ACK may refer to HARQ-ACK information having a priority value of 0, and HP (High Priority) HARQ-ACK may refer to HARQ-ACK information having a priority value of 1 there is.

A possible method for preventing the deterioration of the eMBB data transmission/reception efficiency may be a method of simultaneously multiplexing HP HARQ-ACK and LP HARQ-ACK on one PUCCH or PUSCH channel. Therefore, when HP HARQ-ACK and LP HARQ-ACK are multiplexed on PUCCH or PUSCH, there is a possibility of multiplexing together with CSI part 1 and CSI part 2. If a base station or a terminal can multiplex only up to three pieces of UCI information to PUCCH or PUSCH, a method for selecting which of the four pieces of information to drop and the rest may be needed.

또는

값이 다른 값이 적용될 수 있다. 또한, HP HARQ-ACK과 LP HARQ-ACK이 하나의 PUSCH에 다중화될 경우, HP HARQ-ACK은 [수학식 9]를 적용하는 반면에, LP HARQ-ACK이 PUSCH(또는 CG-PUSCH)에 전송될 때, 부호화된 모듈레이션 심볼의 수(

)는 다음 [수학식 10]로 결정될 수 있다.Hereafter, in an embodiment, a method of multiplexing UCI information to a PUSCH in an environment where HP HARQ-ACK and LP HARQ-ACK exist will be described. In addition, since HP HARQ-ACK and LP HARQ-ACK have different requirements even for the same HARQ-ACK information, there may be a need for HP HARQ-ACK to transmit more reliably than LP HARQ-ACK. Accordingly, Different encoding and rate matching methods can be applied. For example, when determining the number of coded modulation symbols for HP HARQ-ACK and LP HARQ-ACK in [Equation 9], at least

or

Other values may be applied. In addition, when HP HARQ-ACK and LP HARQ-ACK are multiplexed on one PUSCH, HP HARQ-ACK applies [Equation 9], while LP HARQ-ACK is transmitted on PUSCH (or CG-PUSCH) When it becomes, the number of coded modulation symbols (

) can be determined by the following [Equation 10].

[Equation 10]

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

, is determined as follows:

)는 다음 [수학식 10-B]로 결정될 수 있다.In addition, when there is no UL-SCH and there is CSI part1, the number of coded modulation symbols (

) can be determined by the following [Equation 10-B].

[Equation 10-B]

)는 다음 [수학식 10-B]로 결정될 수 있다.In addition, when there is no UL-SCH and there is CSI part1, the number of coded modulation symbols (

) can be determined by the following [Equation 10-B].

)는 다음 [수학식 10-C]로 결정될 수 있다.In addition, when there is no UL-SCH and there is CSI part1, the number of coded modulation symbols (

) can be determined by the following [Equation 10-C].

[Equation 10-C]

은 상기 수학식 9 또는 수학식 9-A 또는 수학식 9-B를 기반으로 결정된 값으로 HARQ_ACK 또는 CG-UCI 또는 HARQ_ACK/CG-UCI를 전송하기 위한 layer당 coded modulation symbols의 개수를 의미 한다. (the number of coded modulation symbols per layer)remind

is a value determined based on Equation 9 or Equation 9-A or Equation 9-B and means the number of coded modulation symbols per layer for transmitting HARQ_ACK or CG-UCI or HARQ_ACK/CG-UCI. (the number of coded modulation symbols per layer)

[PUCCH: Type 1 HARQ-ACK codebook]

The following describes a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook). 7 is a diagram illustrating a method of setting a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook) in an NR system.

In a situation where the number of HARQ-ACK PUCCHs that can be transmitted by the terminal is limited to one within one slot, when the terminal receives the upper signal configuration of the semi-static HARQ-ACK codebook, the terminal transmits the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_x. In the slot indicated by the value, HARQ-ACK information for PDSCH reception or SPS PDSCH release within the HARQ-ACK codebook is reported. The terminal reports the HARQ-ACK information bit value in the HARQ-ACK codebook as NACK in a slot not indicated by the PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_x. If the UE reports only HARQ-ACK information for one SPS PDSCH release or one PDSCH reception in MA and C cases for candidate PDSCH reception, the report is information in which the counter DACI field indicates 1 in the Pcell. When scheduled by DCI format 1_0 including , the UE determines one HARQ-ACK codebook for the corresponding SPS PDSCH release or corresponding PDSCH reception.

Others follow the HARQ-ACK codebook determination method according to the method described in detail below.

If MA,c is the set of PDSCH reception candidate cases in the serving cell c, MA,c can be obtained through the following [pseudo-code 1] steps.

[start pseudo-code 1]

-　　　　　 Step 1: Initialize j to 0 and MA,c to the empty set. Initialize k, the HARQ-ACK transmission timing index, to 0.

-　　　　　 Step 2: Set R as a set of each row in the table including slot information to which PDSCH is mapped, start symbol information, number of symbols or length information. If a PDSCH-capable mapping symbol indicated by each value of R is set as a UL symbol according to the DL and UL settings set at the top, the corresponding row is deleted from R.

-　　　　　 Step 3-1: The terminal can receive one PDSCH for unicast in one slot, and if R is not an empty set, one is added to the set MA,c.

-　　　　　 Step 3-2: If the terminal can receive more than one PDSCH for unicast in one slot, count the number of PDSCHs that can be allocated to different symbols in the calculated R and add that number to MA,c.

-　　　　　 Step 4: Increase k by 1 and start again from step 2.

[end of pseudo-code 1]

Taking the aforementioned pseudo-code 1 as an example of FIG. 7 , in order to perform HARQ-ACK PUCCH transmission in slot #k 708, PDSCH-to-HARQ-ACK timing that can indicate slot #k 708 All of these possible slot candidates are considered. In FIG. 7, slot #k 708 is performed by a PDSCH-to-HARQ-ACK timing combination that is possible only for PDSCHs scheduled in slot #n 702, slot #n + 1 704, and slot #n + 2 706. It is assumed that HARQ-ACK transmission is possible in In slots 702, 704, and 706, the maximum number of schedulable PDSCHs for each slot is derived in consideration of time domain resource configuration information of schedulable PDSCHs and information indicating whether a symbol in the slot is downlink or uplink. For example, if maximum scheduling is possible for 2 PDSCHs in slot 702, 3 PDSCHs in slot 704, and 2 PDSCHs in slot 706, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in slot 708 is the total number of PDSCHs. There are 7 of them. This is called the cardinality of the HARQ-ACK codebook.

[PUCCH: Type 2 HARQ-ACK codebook]

In the following, a dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) will be described. 8 is a diagram illustrating a method of setting a dynamic HARQ-ACK codebook (or Type-2 HARQ-ACK codebook) in an NR system.

In slot n for PDSCH reception or SPS PDSCH release, the terminal is based on the PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information and K0, which is the transmission slot position information of PDSCH scheduled in DCI format 1_x, in slot n transmits HARQ-ACK information transmitted within one PUCCH. Specifically, for the above-described HARQ-ACK information transmission, the UE transmits the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by the PDSCH-to-HARQ_feedback timing and K0 based on the DAI included in the DCI indicating the PDSCH or SPS PDSCH release. decide

The DAI is composed of Counter DAI and Total DAI. Counter DAI is information indicating the location of HARQ-ACK information corresponding to PDSCH scheduled in DCI format 1_x in the HARQ-ACK codebook. Specifically, the value of counter DAI in DCI format 1_x informs the accumulated value of PDSCH reception or SPS PDSCH release scheduled by DCI format 1_x in a specific cell c. The aforementioned cumulative value is set based on a PDCCH monitoring occasion and a serving cell in which the scheduled DCI exists.

Total DAI is a value indicating the HARQ-ACK codebook size. Specifically, the value of Total DAI means the total number of previously scheduled PDSCH or SPS PDSCH releases including the time when DCI is scheduled. In addition, Total DAI is a parameter used when HARQ-ACK information for a PDSCH scheduled in another cell including serving cell c is included in serving cell c in a CA (Carrier Aggregation) situation. In other words, there is no Total DAI parameter in a system operating with one cell.

An example of operation of the DAI is shown in FIG. 8 . In FIG. 8, when the terminal transmits the HARQ-ACK codebook selected based on DAI on the PUCCH 820 in the nth slot of carrier 0 (802) in a situation where two carriers are configured, PDCCH monitoring set for each carrier It shows the change in the value of Counter DAI (C-DAI) and Total DAI (T-DAI) indicated by DCI discovered for each occasion. First, in the DCI found at m=0 (406), C-DAI and T-DAI indicate a value of 1 (812). In the DCI found at m = 1 (408), C-DAI and T-DAI indicate a value of 2 (814). The DCI found on carrier 0 (c = 0, 802) of m = 2 (810) indicates a value (816) of C-DAI of 3. DCI found in carrier 1 (c = 1, 804) of m = 2 (810) indicates a value (418) of C-DAI of 4. At this time, when carriers 0 and 1 are scheduled on the same monitoring occasion, both T-DAIs are indicated as 4.

HARQ-ACK codebook determination in FIGS. 7 and 8 operates in a situation in which only one PUCCH containing HARQ-ACK information is transmitted in one slot. This is called 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 and transmitted in one HARQ-ACK codebook in the same slot, the PUCCH resource selected for HARQ-ACK transmission is determined as the PUCCH resource indicated by the PUCCH resource field indicated in the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated in the DCI scheduled before the DCI is ignored.

The following description defines a method and devices for determining a HARQ-ACK codebook in a situation in which two or more PUCCHs containing HARQ-ACK information can be transmitted in one slot. This is called mode 2. The terminal may operate only mode 1 (transmission of only one HARQ-ACK PUCCH in one slot) or only mode 2 (transmission of one or more HARQ-ACK PUCCHs in one slot). Alternatively, a UE supporting both Mode 1 and Mode 2 is configured so that the base station operates in only one mode by higher signaling, or Mode 1 and Mode 2 are implicitly determined by DCI format, RNTI, DCI specific field value, scrambling, etc. that could be possible For example, a PDSCH scheduled in DCI format A and related HARQ-ACK information are based on mode 1, and a PDSCH scheduled in DCI format B and related HARQ-ACK information are based on mode 2.

[PUCCH: Type 3 HARQ-ACK codebook]

In the following, a Type-3 HARQ-ACK codebook will be described.

Unlike the Type-1 and 2 HARQ-ACK codebooks, the Type-3 HARQ-ACK codebook reports all HARQ-ACK information about all serving cells configured by the UE, the number of HARQ processes, the number of TBs per HARQ process, and the number of CBGs per TB way to do it For example, if the UE has 2 serving cells, 16 HARQ processes for each serving cell, 1 TB for each HARQ process, and 2 CBGs for each TB, the UE has a total of 64 (= 2 X 16 X 1 X 2) HARQ-ACK information bits are reported. In addition, it may be possible to report the NDI value recently received by the terminal for each HARQ-ACK information and related HARQ process according to a separate setting. Through the corresponding NDI value, the base station can determine whether the PDSCH received for each HARQ process of the terminal is determined as initial transmission or retransmission. If there is no report of the corresponding NDI value, the UE already reports HARQ-ACK information for a specific HARQ process before the base station receives the DCI requesting the Type-3 HARQ-ACK codebook, the UE reports the corresponding HARQ process is mapped to NACK, and otherwise, HARQ-ACK information bits are mapped to PDSCHs received for each HARQ process. The number of serving cells, the number of HARQ processes, the number of TBs, and the number of CBGs can be set respectively. If there is no separate setting, the number of serving cells is 1, the number of HARQ processes is 8, the number of TB is 1, and the number of CBGs is As 1, each terminal can consider it. In addition, the number of HARQ processes may be different for each serving cell. In addition, the number of TBs may have a different value for each serving cell or for each BWP within the serving cell. In addition, the number of CBGs may be different for each serving cell.

One of the reasons why the Type-3 HARQ-ACK codebook is needed is when the UE cannot transmit the PUCCH or PUSCH containing the HARQ-ACK information for the PDSCH due to channel access failure or overlapping with other channels with higher priority. can happen Therefore, it is reasonable for the base station to request reporting of only the corresponding HARQ-ACK information without the need to reschedule a separate PDSCH. Accordingly, the base station may be able to schedule the Type-3 HARQ-ACK codebook and the PUCCH resource including the codebook through an upper signal or an L1 signal (eg, a specific field in DCI).

If the UE searches for a DCI format in which the value of the one-shot HARQ-ACK request field includes 1, the UE multiplexes the Type-3 HARQ-ACK codebook in a specific slot indicated by the DCI format. Determine PUCCH or PUSCH resources for And, the UE multiplexes only the Type-3 HARQ-ACK codebook within PUCCH or PUSCH for transmission in the corresponding slot. That is, if two PUCCHs overlap, one 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 UE selects a Type-3 HARQ-ACK codebook. -Multiplex only the ACK codebook to the PUCCH or PUSCH. The reason is that the Type-3 HARQ-ACK codebook includes HARQ-ACK information bits for all serving cells, all HARQ process numbers, all TBs, and all CBGs configured by the UE. It can be seen that the information of the -2 HARQ-ACK codebook is already included in the Type-3 HARQ-ACK codebook.

However, since the Type-3 HARQ-ACK codebook includes all HARQ-ACK information bits based on information configured by all terminals, even if the HARQ-ACK information bits for PDSCHs that are not actually scheduled are also mapped to NACK, the codebook It must be included, and accordingly, there is a disadvantage that the information bit size is large. Therefore, there is a possibility that the uplink transmission coverage or transmission reliability decreases as the uplink control information bit size increases. Therefore, a smaller HARQ-ACK codebook than the Type-3 HARQ-ACK codebook is required. In the present invention, this is regarded as different from the existing Type-3 HARQ codebook, and for convenience, the present invention describes it as an enhanced Type-3 HARQ-ACK codebook (or Type-4 HARQ-ACK codebook). However, it is sufficiently possible to be replaced by other names. As an example, the enhanced Type-3 HARQ-ACK codebook may be configured as follows.

- Type A: Subset of the total set of (established) serving cells

- Type B: a subset of the total set of (established) HARQ process numbers

- Type C: A subset of the total set of (established) TB indices.

- Type D: a subset of the total set of (established) CBG indices

- Type E: Combination of at least two of the above types A to D

It may have at least one feature of the types A to E of the enhanced Type-3 HARQ-ACK codebook, and may be configured as one or a plurality of sets. Among the types A to E, the entire set may be included instead of a subset. As for the meaning of a plurality of sets, it may be possible that, for example, Type A and Type B exist, or different subsets exist even in Type A. Considering the types A to E, the enhanced Type-3 HARQ-ACK codebook may be indicated by an upper signal, an L1 signal, or a combination thereof. As an example, as shown in [Table 26], a set configuration for HARQ-ACK information bits to be reported in each enhanced Type-3 HARQ-ACK codebook is indicated as an upper signal, and one value among them is indicated by the L1 signal. that could be possible As shown in [Table 26], it may be possible to individually set as an upper signal which type of enhanced Type-3 HARQ-ACK codebook is set for each index. In addition, it is also possible to use a Type-3 HARQ-ACK codebook that reports all HARQ-ACK information bits for a specific index, such as index 3. It can be determined that the Type-3 HARQ-ACK codebook is indicated by a separate upper signal or used as a default value (eg, ACK or NACK state for all HARQ process numbers) when there is no upper signal.

[Table 26]

로 결정될 수 있다. 여기서

는 상위 신호로 설정된 [표 26]의 인덱스의 총 개수를 의미한다. When the UE receives the value for requesting the one-shot HARQ-ACK feedback field and receives the value indicated by index 1 according to [Table 26], the UE receives the serving cell i, the HARQ process number (#1 to #8 ), a total of 8 bits of HARQ-ACK information bits are reported for TB 1. When the UE receives the value for requesting the one-shot HARQ-ACK feedback field and receives the value indicated by index 2 according to [Table 26], the UE receives the serving cell i, the HARQ process number (#1 to #8 ), a total of 4 bits of HARQ-ACK information bits are reported for TB 1. When the UE receives a value requesting the one-shot HARQ-ACK feedback field and receives the value indicated by index 3 according to [Table 26], the UE receives the serving cell set, the total number of HARQ processes per serving cell i, The total number of HARQ-ACK bits is calculated considering the number of TBs per HARQ process and the number of CBGs per TB. [Table 26] is only an example, the total number of indices may be more or less than this, and the range of HARQ process values indicated by each index and/or information included in the enhanced Type-3 HARQ-ACK codebook may differ. can In addition, [Table 26] may be information indicated by an upper signal, and a specific index may be notified through DCI. In addition, HARQ-ACK information indicated through a specific index value or one-shot HARQ-ACK feeback field (or other L1 signal) other than the above [Table 26] is HARQ-ACK information for a specific (or entire) HARQ process number. If specific HARQ-ACK information, other than ACK information, that the UE was scheduled to transmit in advance is dropped, it may be used for the purpose of retransmitting it. This is called a dropped HARQ-ACK retransmission. The dropped case may overlap with another PUCCH or PUSCH having a higher priority than the PUCCH or PUSCH including the HARQ-ACK information. Alternatively, in the case of the drop, it may be possible that at least one symbol of the PUCCH or PUSCH including the HARQ-ACK information was previously indicated as a downlink symbol by an upper signal. Alternatively, in the case of the drop, it may be possible that the PUCCH or PUSCH including the HARQ-ACK information overlaps at least in part with a resource indicated by DCI including Uplink Cancellation information for the purpose of canceling uplink transmission. If the terminal supports both the dropped HARQ-ACK retransmission and (enhanced) type-3 HARQ codebook-based transmission, the terminal searches for DCI CRC and scrambled RNTI information or DCI Search space type or DCI At least one of the dropped HARQ-ACK retransmission and (enhanced) type-3 HARQ codebook-based transmission is selected through priority information or at least one information of MCS, RV, NDI, HARQ process ID, etc., among fields, or a combination thereof. It may be possible to report HARQ information by doing so. Alternatively, it may be possible to set and use a specific index value in [Table 26] as a dropped HARQ-ACK retransmission. The specific index selection of Table 26 may be indicated by at least one or a combination of HARQ process number or MCS or NDI or RV or frequency resource allocation information or time resource allocation information among DCI fields. The size of the DCI bit field indicating the specific index in [Table 26] is

can be determined by here

means the total number of indices of [Table 26] set as upper signals.

The total number of HARQ-ACK bits N can be expressed as in [Equation 11].

[Equation 11]

In [Equation 11], n(c) is the total number of serving cells c, H _c is the number of HARQ processes set in serving cell c, T _b,c is the number of TBs for each HARQ process set in serving cell c and BWP b, B _c is the number of CBGs configured in the serving cell c. In addition, when the UE searches for a DCI format with a one-shot HARQ-ACK request field value of 1, the UE selects a PUCCH for multiplexing the corresponding Type-3 HARQ-ACK codebook (or enhanced Type-3 HARQ-ACK codebook) or Determine PUSCH resources. And, the UE multiplexes only the Type-3 HARQ-ACK codebook (or enhanced Type-3 HARQ-ACK codebook) on the determined PUCCH or PUSCH resource for transmission in the corresponding slot. If there is a PUCCH or PUSCH including SR information or CSI information overlapping the PUCCH or PUSCH, the UE may be able to drop the SR or CSI information without multiplexing it. That is, it may be possible to multiplex only Type-3 HARQ-ACK information and drop SR and CSI, which are other UCIs.

[PUCCH power control]

Hereinafter, PUCCH power control will be described. The following [Equation 12] is an equation for determining PUCCH transmit power.

[Equation 12]

은 기준 설정 전송 전력 설정 값으로써, 다양한 전송 타입

에 따라 다른 값을 가지며, RRC 또는 MAC CE와 같은 상위 신호에 의해 값이 변경될 수 있다. MAC CE로 값이 변경될 경우, 단말은 MAC CE를 수신한 PDSCH에 대해서 HARQ-ACK을 송신한 슬롯이 k일 경우, k + k_offset 슬롯부터 해당 값이 적용되는 것으로 판단한다. k_offset은 부반송파 간격에 따라 각기 다른 값을 가지며, 일례로 3ms를 가질 수 있다.

는 PUCCH가 할당된 주파수 자원 영역 크기이다.

는 단말의 경로 감쇄 추정 값으로써, 단말은 상위 신호 설정 여부 및 종류에 따라 다양한 CSI-RS 또는 SS/PBCH 중에 특정 기준 신호를 기반으로 계산한다. 반복 전송 PUCCH들에 대해서는 동일한

가 적용된다. 반복 전송 PUCCH들에 대해서는 동일한

가 적용된다. In [Equation 12]

is the reference setting transmission power setting value, and various transmission types

It has a different value depending on , and the value can be changed by an upper signal such as RRC or MAC CE. When the value is changed to the MAC CE, the terminal determines that the corresponding value is applied from k + k _offset slots when the slot in which the HARQ-ACK is transmitted for the PDSCH receiving the MAC CE is k. k _offset has different values depending on the subcarrier spacing, and may have 3 ms as an example.

Is the size of the frequency resource region to which the PUCCH is allocated.

is an estimated path attenuation value of the UE, which is calculated based on a specific reference signal among various CSI-RSs or SS/PBCHs depending on whether or not an upper signal is configured and the type. Same for repeated transmission PUCCHs

is applied. Same for repeated transmission PUCCHs

is applied.

의 값이 결정된다. For PUCCH formats 2, 3, and 4, if the UCI size is greater than or equal to 11, in [Equation 12] by the following [Equation 13]

The value of is determined.

[Equation 13]

은 HARQ-ACK 비트 수,

는 SR 비트 수,

는 CSI 비트 수,

는 PUCCH의 RE 수를 의미한다. In [Equation 13], K ₁ is 6,

is the number of HARQ-ACK bits,

is the number of SR bits,

is the number of CSI bits,

Means the number of REs of PUCCH.

[PDSCH:SPS]

The SPS operation will be described below. When the UE can operate two or more activated DL SPSs in one cell / one BWP, the base station can configure two or more DL SPSs for one UE. The reason for supporting two or more DL SPS settings is that when a UE supports various traffics, different MCS or time/frequency resource allocation or cycles may be different for each traffic, so it would be advantageous to configure DL SPS settings suitable for each purpose. .

The UE may receive at least some of the upper signal configuration information as shown in [Table 27] for the DL SPS.

[Table 27]

Among the upper signal configuration information, the SPS index can be used for the purpose of notifying which SPS the DCI (L1 signaling) providing activation or deactivation of the SPS indicates. Specifically, in a situation where two SPSs are configured as upper signals in one cell/one BWP, in order to know which of the two SPSs is indicated by the DCI indicating activation of the SPS, the index information indicating this is provided to the upper level information of the SPS. will be needed For example, the terminal will enable activation or deactivation through the HARQ process number field in the DCI indicating activation or deactivation of the SPS pointing to the index of a specific SPS. Specifically, as shown in [Table 28], when the DCI including the CRC scrambled with CG-RNTI includes the following information and the New Data Indicator (NDI) field of the corresponding DCI indicates 0, the UE releases a specific pre-activated SPS PDSCH (deactivation) is judged to be indicated.

[Table 28]

In [Table 28], one HARQ process number may indicate one SPS index or a plurality of SPS indices. It may be possible to indicate one or a plurality of SPS index(s) by other DCI fields (time resource field, frequency resource field, MCS, RV, PDSCH-to-HARQ timing field, etc.) in addition to the HARQ process number field. Basically, one SPS can be activated or deactivated by one DCI. The position of the type 1 HARQ-ACK codebook for HARQ-ACK information for the DCI indicating the SPS PDSCH release is the same as the position of the type 1 HARQ-ACK codebook corresponding to the reception position of the corresponding SPS PDSCH. If the position of the HARQ-ACK codebook corresponding to the candidate SPS PDSCH reception in the slot is k1, the position of the HARQ-ACK codebook for the DCI indicating the release of the corresponding SPS PDSCH is also k1. Therefore, when DCI indicating SPS PDSCH release is transmitted in slot k, the UE will not expect to be scheduled for a PDSCH corresponding to the HARQ-ACK codebook position k1 in the same slot k, and if this situation occurs, the UE regarded as an error case. Although [Table 28] took DCI formats 0_0 and 1_0 as an example, it can also be applied to DCI formats 0_1 and 1_1, and it can be sufficiently extended and applied to other DCI formats 0_x and 1_x. By the above-described operation, the terminal By receiving a DCI indicating reception of an SPS PDSCH upper signal and activation of the SPS PDSCH, one or more SPS PDSCHs can be simultaneously operated within one cell/one BWP. Thereafter, the UE periodically receives an activated SPS PDSCH within one cell/one BWP and transmits HARQ-ACK information corresponding thereto. The HARQ-ACK information corresponding to the SPS PDSCH is the exact time within the corresponding slot through the slot interval information by the PDSCH-to-HARQ-ACK timing included in the activated DCI information and the n1PUCCH-AN information included in the SPS upper configuration information. And the terminal determines through the frequency information and PUCCH format information. If there is no PDSCH-to-HARQ-ACK timing field included in the DCI information, the terminal assumes that one value previously set as an upper signal is a default value and determines that the corresponding value is applied.

Alternatively, the terminal may set the next DL SPS configuration information from the upper signal.

- Periodicity: DL SPS transmission period

- nrofHARQ-Processes: Number of HARQ processes configured for DL SPS

- n1PUCCH-AN: HARQ resource configuration information for DL SPS

- mcs-Table: MCS table setting information applied to DL SPS

In the present invention, all DL SPS configuration information can be set for each Pcell or Scell, and can also be set for each bandwidth part (BWP). In addition, it may be possible to configure one or more DL SPSs for each specific cell and each BWP.

The UE determines grant-free transmission/reception configuration information through reception of a higher-level signal for the DL SPS. The DL SPS may be able to transmit/receive data for the resource area set after receiving the DCI indicating activation, but cannot transmit/receive data for the resource area before receiving the DCI. In addition, the terminal cannot receive data for a resource region after receiving DCI indicating release.

The UE verifies the DL SPS assignment PDCCH when both of the following two conditions are satisfied for SPS scheduling activation or release.

- Condition 1: When the CRC bit of the DCI format transmitted on the PDCCH is scrambled with the CS-RNTI set as higher signaling

- Condition 2: When the New Data Indicator (NDI) field for an activated transport block is set to 0

If some of the fields constituting the DCI format transmitted through the DL SPS assignment PDCCH are the same as those presented in [Table 29] or [Table 30], the terminal indicates that the information in the DCI format is a valid activation or a valid release of the DL SPS judge As an example, when the terminal detects a DCI format that includes the information presented in [Table 29], the terminal determines that the DL SPS is activated. As another example, when the UE detects a DCI format including the information presented in [Table 30], the UE determines that the DL SPS has been released.

[Table 5] (special field configuration information for activating DL SPS) or [Table 30] (special field configuration information for releasing DL SPS) If it is not the same as suggested in, the terminal determines that the DCI format is detected as an unmatched CRC.

[Table 29]

[Table 30]

When a UE receives a PDSCH without receiving a PDCCH or receives a PDCCH indicating an SPS PDSCH release, the UE generates HARQ-ACK information bits corresponding thereto. In addition, at least in the Rel-15 NR, the UE is not expected to transmit HARQ-ACK information (s) for two or more SPS PDSCH receptions in one PUCCH resource. In other words, at least in the Rel-15 NR, the UE includes only HARQ-ACK information for one SPS PDSCH reception in one PUCCH resource.

DL SPS may also be set in P (primary) Cell and S (secondary) Cell. Parameters that can be set by DL SPS higher signaling are as follows.

- Periodicity: Transmission period of DL SPS

- nrofHARQ-processes: number of HARQ processes that can be configured for DL SPS

- n1PUCCH-AN: PUCCH HARQ resource for DL SPS, the base station sets the resource to PUCCH format 0 or 1

[Table 29] to [Table 30] described above may be possible fields in a situation where only one DL SPS can be set per cell and per BWP. A DCI field for activating (or releasing) each DL SPS resource in a situation where a plurality of DL SPSs are configured for each cell and each BWP may be different. The present disclosure provides a method to solve such a situation.

In the present disclosure, not all DCI formats described in [Table 29] and [Table 30] are used to activate or release DL SPS resources, respectively. For example, DCI format 1_0 and DCI format 1_1 used for PDSCH scheduling are used to activate DL SPS resources. For example, DCI format 1_0 used to schedule PDSCH is used to release DL SPS resources.

[Example 1]

According to the above description, since the Type-3 HARQ-ACK codebook includes HARQ-ACK information for all HARQ process numbers configured by the UE, a HARQ-ACK different from the PUCCH or PUSCH including the Type-3 HARQ-ACK codebook (eg For example, if it overlaps with PUCCH or PUSCH including Type-1 or Type-2 HARQ-ACK codebook information, since the Type-3 HARQ-ACK codebook already includes all HARQ-ACK information, each overlapping HARQ -ACK codebooks will not need to be multiplexed with each other. Therefore, it may be reasonable for the terminal to transmit only the PUCCH or PUSCH including the Type-3 HARQ-ACK codebook and drop other HARQ-ACK codebooks scheduled to overlap. However, if the enhanced Type-3 HARQ-ACK codebook including HARQ-ACK information for some HARQ process numbers other than the Type-3 HARQ-ACK codebook and the PUCCH or PUSCH containing other HARQ-ACK information overlap, this Various multiplexing methods can be considered. Figure 9 shows an example of this. 9 is a diagram showing a situation in which a plurality of different HARQ-ACK codebooks are overlapped according to an embodiment. PUCCH including Type 1 or Type 2 HARQ-ACK information is scheduled by DL DCI 1, PUCCH including enhanced Type-3 HARQ-ACK information is scheduled by DL DCI 2, and these two PUCCHs are time resources It is an overlapping situation in perspective. In this case, a PUCCH including Type 1 or Type 2 HARQ-ACK information is referred to as a first PUCCH, and a PUCCH including enhanced Type-3 HARQ-ACK information is referred to as a second PUCCH. The first PUCCH 902 includes HARQ-ACK information for HARQ process numbers 1 and 5, and the second PUCCH 904 includes HARQ-ACK information for HARQ process numbers 1, 2, 3, and 4. If only the 2nd PUCCH is transmitted and the 1st PUCCH is dropped, the UE has the HARQ-ACK information for HARQ process number 1 included in the 2nd PUCCH, but the HARQ-ACK information for HARQ process number 5 Since it is not included in the second PUCCH, the base station cannot receive HARQ-ACK information for HARQ process number 5. Therefore, the UE needs to multiplex the HARQ information included in the first PUCCH and the second PUCCH. Methods for combining different types of HARQ-ACK codebook information may be configured with at least one or a combination of the following.

* Method 1-1: This is a method of sequentially mapping each HARQ process number. In the case of the first PUCCH, since it is configured in the type 1 or type 2 HARQ-ACK codebook method, in the case of the type 1 HARQ-ACK codebook, which is not mapped by HARQ process number, the resource region to which the PDSCH is allocated or the PDSCH and the PUCCH It is determined sequentially in consideration of the slot offset and subcarrier interval, and in the case of the type 2 HARQ-ACK codebook, it is sequentially determined by the DAI value in the DCI transmitted and received on the PDCCH. Therefore, there is a need to rearrange the type 1 or type 2 HARQ-ACK codebook for each HARQ process number. On the other hand, the Type 3 HARQ-ACK codebook or the enhanced Type 3 HARQ-ACK codebook may be sorted by HARQ process number. Type 1 or type 2 HARQ-ACK codebook can determine in advance which HARQ process number each HARQ-ACK information is associated with through an upper signal or L1 signal, so the union of a plurality of different HARQ-ACK codebooks After that, it may be possible to sequentially map each HARQ process number. As an example, in FIG. 9, after the UE aggregates the HARQ-ACK codebooks included in the first PUCCH and the second PUCCH, the HARQ process numbers 1, 2, 3, 4, and 5 are sorted by HARQ process number. After sequentially mapping HARQ-ACK information (eg, O _{ack_1,} O _{ack_2,} O _{ack_3,} O _{ack_4,} O _{ack_5} ), it may be possible to report these values to the base station.

* Method 1-2: This is a method of combining each HARQ-ACK codebook regardless of the HARQ process number. Unlike method 1-1, it is a method of combining HARQ-ACK codebooks included in each PUCCH. In FIG. 9, HARQ-ACK information ( _{Oack_5, Oack_1} ) for HARQ process numbers 1 and 5 is reported on the first PUCCH, and HARQ-ACK information for HARQ process numbers 1, 2, 3, and 4 is reported on the first PUCCH When trying to report (O _{ack_1,} O _{ack_2,} O _{ack_3,} O _{ack_4} ), method 1-1 combines the HARQ-ACK information included in each PUCCH, and then maps each HARQ process number in ascending or descending order. On the other hand, method 1-2 may be able to simply combine them. Thus, {(O _{ack_5,} O _{ack_1} ), (O _{ack_1,} O _{ack_2,} O _{ack_3,} O _{ack_4} )} or {(O _{ack_1,} O _{ack_2,} O _{ack_3,} O _{ack_4} ), (O _{ack_5,} O _{ack_1} )} After combining, it may be possible for the terminal to report.

* Method 1-3: The UE may be able to assume a Type 3 HARQ-ACK codebook. Therefore, the UE transmits HARQ-ACK information for HARQ process numbers included in the first PUCCH and the second PUCCH as well as HARQ-ACK information for other HARQ-ACK process numbers. Therefore, the UE transmits all HARQ-ACK information based on the serving cell set to the upper signal described in [Equation 11], the number of HARQ processes, the number of TBs, the number of CBGs, and the like.

* Method 1-4: Similar to Method 1-2, but the combining order is determined according to the order in which PUCCH resources are allocated or scheduled. For example, as shown in FIG. 9, when the first PUCCH resource is first determined by DL DCI 1 and the second PUCCH resource is determined later by DL DCI 2, the UE receives HARQ-ACK information according to the order in which each PUCCH resource is determined. map them Therefore, according to this, the HARQ-ACK information multiplexed by the UE in FIG. 9 is {( _{Oack_5, Oack_1} ), ( _{Oack_1, Oack_2, Oack_3, Oack_4} )}. If at least one of the first PUCCH and the second PUCCH resource is a PUCCH resource that is periodically transmitted and received without DCI scheduling, it may be assumed that it is determined earlier or later than the PUCCH resource indicated by DCI.

* Method 1-5: It may be possible for the UE to drop at least one of the first PUCCH and the second PUCCH and transmit the non-dropped PUCCH.

The above methods have been described in the case where the first PUCCH and the second PUCCH are different HARQ-ACK codebooks in FIG. It could be possible. In other words, the above methods may be applied only when the first PUCCH and the second PUCCH have different HARQ-ACK codebook types.

In addition, when the first PUCCH and the second PUCCH each have priority information, it may be possible to select at least one of Methods 1-1 to 1-5 according to each priority information. The priority information may be notified by an upper signal or an L1 signal, and has a value of 0 or 1, with a value of 1 being a high priority and a value of 0 being a low priority. The UE may be able to select at least one of Methods 1-1 to 1-5 according to the priority information of the second PUCCH regardless of the priority information of the first PUCCH. For example, when the priority of the first PUCCH is high, the UE selects at least one of Methods 1-1 to 1-4, and when the priority is low, the UE selects Method 1-5. Alternatively, the UE may be able to select at least one of Methods 1-1 to 1-5 according to the priority information of the first PUCCH regardless of the priority information of the second PUCCH. For example, when the priority of the second PUCCH is low, the UE selects at least one of Methods 1-1 to 1-4, and when the priority is high, the UE selects Method 1-5. Alternatively, the UE may be able to select at least one of Methods 1-1 to 1-5 in consideration of both the priority of the first PUCCH and the priority of the second PUCCH. For example, when the priority of the first PUCCH and the priority of the second PUCCH are the same, the UE follows at least one operation of Methods 1-1 to 1-4, and the priority of the first PUCCH and the priority of the second PUCCH If priorities are different, only PUCCHs with higher priorities are selected and only HARQ codebook information included in the corresponding PUCCHs is transmitted, and other PUCCHs with lower priorities are dropped.

[Example 2]

수를 계산할 때, 중복된 HARQ-ACK 정보 비트들도 포함하거나 또는 포함하지 않는 경우가 가능할 수 있다. 상기Various methods for the case where PUCCHs containing different HARQ-ACK codebook information are overlapped have been described. Among these methods, methods 1-2 and 1-4 may generate a plurality of HARQ-ACK information for a specific HARQ process number. If such a method is considered, in [Equation 13]

When calculating the number, it may be possible to include or not include duplicate HARQ-ACK information bits as well. remind

값은 6비트가 될 것이다. 즉, HARQ 프로세스 번호 1에 대해서 2개의 비트 수를 반영한다. 반면에 상기 중복된 HARQ-ACK 정보 비트들을 포함하지 않을 경우, 도 9의 예시에 따라

값은 5비트가 될 것이다. 즉, HARQ 프로세스 번호 1에 대해서 2개의 중복된 비트 수가 각각 PUCCH로 송신되더라도 [수학식 12] 내지 [수학식 13]에 따라 PUCCH 전송 전력 결정 시에는 중복된 비트를 포함하지 않고, 순수한 정보 비트들이 포함된 것을 기준으로 한다. 상기 중복된 비트를 포함하거나 포함하지 않는 것은 단말 능력 또는 상위 신호 또는 L1 신호 또는 이들 중 적어도 일부의 조합으로 통지되는 것이 가능할 수 있다. 도 10은 일 실시 예에 따른 단말의 PUCCH 또는 PUSCH 송신 동작을 도시한 블록도이다. 단말은 기지국으로부터 제어 정보를 수신한다. 해당 제어 정보는 상위 신호 또는 L1 신호가 해당 될 수 있으며, 하나 또는 복수개 일 수 있다. 그리고 단말은 상기 제어 정보에 기초하여 PUCCH 또는 PUSCH 자원을 결정한다. 그리고, 각각의 PUCCH 또는 PUSCH에 다중화되는 HARQ-ACK 또는 그 이외 UCI 정보들을 확인한다. 그리고 2개 이상의 PUCCH 또는 PUSCH 자원이 중첩되거나 또는 적어도 하나의 슬롯 또는 서브 슬롯 내에 HARQ-ACK 정보를 포함한 PUCCH 또는 PUSCH가 2개 이상일 경우, 단말은 HARQ-ACK 다중화 여부를 상기 방법 1-1 내지 방법 1-5 중 적어도 하나를 이용하여 결정한다. 이후, 단말은 상기 방법들에 기초하여 최종적으로 HARQ-ACK 정보 또는 그 이외 UCI 정보들을 송신할 PUCCH 또는 PUSCH를 결정하고 이에 대한 전송 전력도 같이 결정한다. When including overlapping HARQ-ACK information bits, according to the example of FIG.

The value will be 6 bits. That is, two bits are reflected for HARQ process number 1. On the other hand, when the overlapping HARQ-ACK information bits are not included, according to the example of FIG. 9

The value will be 5 bits. That is, even if two overlapping bits are transmitted on the PUCCH for HARQ process number 1, the overlapping bits are not included when the PUCCH transmission power is determined according to [Equation 12] to [Equation 13], and pure information bits Based on what is included. The inclusion or non-inclusion of the overlapping bits may be notified by a terminal capability or an upper signal or an L1 signal or a combination of at least some of them. 10 is a block diagram illustrating a PUCCH or PUSCH transmission operation of a UE according to an embodiment. The terminal receives control information from the base station. Corresponding control information may correspond to a higher level signal or an L1 signal, and may be one or plural. And the terminal determines the PUCCH or PUSCH resource based on the control information. In addition, HARQ-ACK or other UCI information multiplexed on each PUCCH or PUSCH is checked. In addition, when two or more PUCCHs or PUSCH resources overlap or there are two or more PUCCHs or PUSCHs including HARQ-ACK information in at least one slot or subslot, the UE determines whether or not HARQ-ACK multiplexing is performed according to the method 1-1 to method It is determined using at least one of 1-5. Then, based on the above methods, the terminal finally determines a PUCCH or PUSCH to transmit HARQ-ACK information or other UCI information, and also determines transmission power for it.

[Example 3]

11 is a diagram showing a transmission relationship between an SPS PDSCH and HARQ-ACK information therefor according to an embodiment. The SPS PDSCH is a resource that can periodically transmit data from the base station to the terminal without a separate DCI. The period may be set to a higher signal from 1 slot to a maximum of 5160 slots. In addition, the PUCCH resource including transmission of the HARQ-ACK information for the SPS PDSCH is determined by a DCI activating the SPS PDSCH and an upper signal. 11 shows a case where K1 (subslot interval between SPS PDSCH and PUCCH) is 3 in a situation where the subslot length having a length smaller than 14 slots is set to 7. The subslot length may have a value of 2 or 6 other than 7, and may be set to different values for each subcarrier interval. As for the K1 value, when the subslot where the last symbol of the SPS PDSCH is located is n, the PUCCH resource is determined within the subslot corresponding to n+k1. In addition, in FIG. 11, the case where the transmission/reception period of the SPS PDSCH is set every 2 slots is considered. Accordingly, the HARQ-ACK transmission/reception period for the SPS PDSCH also exists every 2 slots. Since the SPS PDSCH and the PUCCH including the corresponding HARQ-ACK information are set semi-statically, in a TDD environment, if at least one symbol among the time resources for which the SPS PDSCH is set is previously indicated for uplink by a higher signal or L1 signal If the UE does not receive the SPS PDSCH and at least one symbol among the time resources for which the PUCCH is set is previously indicated as a downlink symbol by an upper signal or an L1 signal, the UE does not transmit the PUCCH. When the SPS PDSCH is not received, the UE has no effect on both the base station and the UE because the HARQ-ACK information for this is NACK, but when the SPS PDSCH is received but the HARQ-ACK information is not transmitted, the UE receives from the point of view of the base station Since the reception state of one SPS PDSCH cannot be accurately confirmed, the SPS PDSCH must be retransmitted to the terminal again, and thus radio resources may be wasted. Therefore, when the PUCCH is dropped, it may be reasonable to defer the corresponding PUCCH resource to a later slot without the need to retransmit the SPS PDSCH again. The delayed PUCCH resource may be a resource previously set as an upper signal or a resource separately indicated by an L1 signal. Alternatively, when configuring the PUCCH resource for HARQ-ACK reporting for the SPS PDSCH, the delayed PUCCH resource unit may be determined according to whether the K1 value is based on a subslot or a slot. For example, in FIG. 11, when indicated in units of subslots consisting of 7 symbols, the terminal performs deferral in units of corresponding subslots when the first PUCCH is not transmitted by a downlink symbol. In this case, the PUCCH resource information is determined as an upper signal or an L1 signal, and may include PUCCH start symbol position and length information and frequency information based on the first symbol of the subslot (or slot). Therefore, in FIG. 11, the terminal performs deferral in units of subslots, and first transmits in a subslot in which a corresponding PUCCH resource can be transmitted. At this time, the method of determining the PUCCH resource may correspond to a case in which all of the corresponding PUCCH resources are indicated as higher signals with downlink symbols or when all PUCCH resources are not indicated as higher signals with at least uplink symbols. The unit for delaying the PUCCH may be indicated by a separate upper signal or an L1 signal regardless of the K1 unit. For example, the unit of K1 is determined in units of slots, but the unit for delaying the PUCCH may be determined in units of subslots consisting of 7 symbols, which may be indicated by a separate upper signal or L1 signal. The sub-slot unit can also have a symbol length other than 2, 6, and 7 symbols. However, when the delayed PUCCH crosses the slot boundary, it is determined that the corresponding PUCCH resource is not valid, and it may be possible to perform the delay in units of the subslot until a situation occurs when the corresponding PUCCH resource does not cross the slot boundary. there is. Alternatively, when the PUCCH resource spans a slot boundary, it may be possible to segment (divide) the PUCCH resource based on the slot boundary. For example, when a 4-symbol PUCCH resource spans a slot boundary by 2 symbols each, the UE may be able to transmit 2-symbol PUCCH in each slot.

12A is a diagram illustrating transmission and reception operations of an SPS PDSCH and a HARQ-ACK PUCCH of a UE according to an embodiment. The terminal receives configuration information for the SPS PDSCH through the upper signal and the L1 signal. At this time, the main configuration information may correspond to an SPS PDSCH transmission resource area, transmission period, transmission format, transmission length, etc., and PUCCH resource information including HARQ-ACK information for the SPS PDSCH also exists. Specifically, the terminal receives some information through an upper signal, and then the SPS PDSCH is activated through an L1 signal (eg, DCI format). Thereafter, the terminal receives the SPS PDSCH based on the configuration information. Then, PUCCH resources for reporting HARQ-ACK information on SPS PDSCH are checked. Then, it is determined whether the corresponding PUCCH resource is actually a resource region in which the UE can transmit. If at least one symbol of a PUCCH resource is indicated as a downlink symbol by a different upper signal, the UE determines a PUCCH resource capable of transmitting the HARQ-ACK information after the corresponding PUCCH resource. The corresponding determination method searches while deferring PUCCH resources in units of slots (or sub-slots). The unit of the subslot may have a value of 1 to 13 symbols. The terminal transmits the HARQ-ACK information in the determined PUCCH resource thereafter. In addition to the PUCCH including the corresponding HARQ-ACK information, if a PUCCH or PUSCH containing other HARQ-ACK or UCI information overlaps or exists in the same sub-slot or slot, the UE multiplexes them and reports them to the base station.

[Example 4]

Hereinafter, in Example 4, a semi-static cell selection method for PUCCH transmission will be described. In Embodiment 3, when at least one symbol among resources to transmit PUCCH for SPS PDSCH overlaps with a downlink symbol, retransmission of the corresponding PUCCH in a different frequency or time resource within the same carrier (or cell) has been described. . Unlike this, in Example 4, transmission of the corresponding PUCCH on a carrier other than the same carrier is described. Embodiment 4 can be applied when a terminal has two or more carriers configured. Therefore, Example 3 may be applied to a single carrier and Example 4 to multiple carriers. In addition, in Example 4, in addition to transmitting the PUCCH including HARQ-ACK information for the SPS PDSCH through another carrier, PUCCH including UCI information such as SR or CSI or HARQ-scheduled by a PDSCH other than the SPS PDSCH It may also be applicable to PUCCH including ACK information. 12B is a diagram illustrating resource configuration in which a PUCCH can be transmitted and received semi-statically according to an embodiment. The P1 period is set according to the upper signal configuration, and (B1, B2, ... Bn) in the P1 period informs which carrier is configured for PUCCH transmission in each detailed period in a bitmap format. For example, when the unit of B1, B2, ..., Bn is 1 bit, it may be possible to indicate one of CC#1 or CC#2 as a carrier selected for PUCCH transmission with a value of 0 or 1. If the value of 0 is CC#1 and the value of 1 is CC#2, it may be indicated in the form of (0, 1, ..., 0, 1) according to FIG. 12B. 12b is limited to the case where there are only two carriers, but can be applied even when there are more carriers. In this case, the number of bits of B1 can be two or more bits instead of one, and the value of the number of bits is ceiling(log ₂ (N _carrier )). Here, the meaning of N _carrier is the maximum number of carriers capable of PUCCH transmission, which may exist as a separate upper signal or follow the value of carrier number configuration information set for PUSCH transmission. In FIG. 12B, the unit of P1 and (B1, B2, ..., Bn) may be a slot unit based on 15 kHz or a unit of ms, and the corresponding value may be determined by another upper signal or indicated as a fixed value. there is. Alternatively, the corresponding unit may be set based on a slot having the smallest subcarrier interval between CC#1 and CC#2. In addition, even if a resource for transmitting a PUCCH is configured by the upper layer signal, if a PUCCH transmission resource scheduled according to another TDD higher layer signal overlaps a downlink symbol, the UE can cancel the corresponding PUCCH transmission. Therefore, it can be seen that the higher signal indicating the PUCCH carrier has a lower priority than the higher signal indicating the TDD configuration. In addition, the indication unit of B1 must include all slots indicated according to the subcarrier spacing set for a specific carrier. That is, it does not allow the instruction unit of B1 to end or start in the middle of a specific slot. For example, if the unit of (B1, B2, ..., Bn) is based on the subcarrier interval of CC#2, in the case of CC#1, there is a possibility that the carrier for PUCCH transmission is changed in the middle of a specific slot. . Therefore, in order to prevent this situation, at least, in FIG. 12B, the minimum unit of (B1, B2, ..., Bn) is 15 kHz based on the subcarrier of CC#1 and the smallest of the slot length or the subcarrier spacing supported by NR It may be determined as a slot length of or 1 ms. In addition, as for the PUCCH transmission power, the TPC value applied in carrier A can be applied only within the corresponding carrier. That is, the TPC value of the PUCCH received on carrier A is not applied to the PUCCH on carrier B. This is because each carrier may have a different frequency band and different channel environment, so it may not be possible to adjust transmission power in different carriers. However, depending on circumstances, the TPC value of the PUCCH received on carrier A may be applied to the PUCCH on carrier B, which may be set by a separate upper signal. Alternatively, in addition to indicating which carrier among specific carriers is used for PUCCH transmission, the bitmap value of B1 determines whether each carrier is used for PUCCH transmission as a separate upper signal (offset, sub-period) during the P1 period. It may be possible to inform with an upper signal. Therefore, a plurality of upper signal information exists for each carrier, and slots or slot periods in which PUCCH can be transmitted can be informed with each piece of information. In this way, a situation may occur in which one or more PUCCHs may be transmitted in a specific slot or period, and in this case, the UE transmits the PUCCH to the carrier having the smallest value or the largest value according to the carrier index. judge that you can 12b may apply to at least one of intra-band CA and inter-band CA for a plurality of carriers. Intra-band CA means a case where each carrier is concatenated in terms of frequency, and inter-band CA means a case where each carrier is separated from each other in terms of frequency. 12c is a diagram illustrating a UE operation for PUCCH transmission carrier switching according to an embodiment. The terminal receives carrier switching information for PUCCH transmission from the base station. As described above with reference to FIG. 12B, the carrier switching information includes information indicating which carrier PUCCH is used for transmission within a specific period according to one or more upper signal configuration information. Thereafter, the terminal selects a carrier that has performed PUCCH transmission in a specific slot based on the upper signal information. Information for determining the transmission power may be determined based on control information received from a corresponding carrier or control information received from another carrier. The semi-static cell selection method may be limited to PUCCH or SR including HARQ information for SPS PDSCH or PUCCH including periodically transmitted/received CSI information. Alternatively, it may not correspond to a PUCCH including UCI information scheduled by DCI, but may correspond only to a PUCCH including UCI information set by an upper signal. While the semi-static cell selection method is a method in which a cell to transmit a PUCCH is determined in advance by a higher order signal, the dynamic cell selection method refers to a method in which a PUCCH scheduled by DCI can be transmitted and received through a specific cell. In this method, a cell to transmit PUCCH can be selected through a specific field in DCI, and configuration information and bit size of the specific field can be set in advance by a higher order signal.

[Example 5]

Hereinafter, in Example 5, a method for setting an enhanced Type-3 HARQ-ACK codebook in a situation in which priority indicator information exists in a terminal will be described. The priority information may be included in an upper signal or an L1 signal and transmitted, and the priority of the PUSCH or PUCCH transmitted by the UE may be higher or lower according to the corresponding information. URLLC data may be an example of information having a high priority, and eMBB data may be an example of information having a low priority. The following [Table 31] is an example of higher order signal information related to priority information.

- PDSCH-CodeBlockGroupTransmissionList-r16 ::= SEQUENCE (SIZE (1..2)) OF PDSCH-CodeBlockGroupTransmission --> Parameter indicating whether to set CBG (codeblock group) transmission by priority

- PDSCH-HARQ-ACK-CodebookList-r16 ::= SEQUENCE (SIZE (1..2)) OF ENUMERATED {semiStatic, dynamic} --> Indicates whether HARQ-ACK codebook settings are semi-static or dynamic by priority parameter

- multi-CSI-PUCCH-ResourceList ::= SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId --> Parameter indicating PUCCH transmission resource configuration information including CSI information for each priority

- PUCCH-ConfigurationList-r16 ::= SEQUENCE (SIZE (1..2)) OF PUCCH-Config --> Parameter indicating PUCCH transmission resource configuration information by priority

- UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16 --> PUSCH scheduled in DCI format 0_2 by priority Parameter that informs setting information related to UCI information included in

- UCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH --> Settings related to UCI information included in PUSCH scheduled in DCI format 0_1 by priority parameters that give information

Scheduled CBG, PUCCH, or HARQ-ACK codebook configuration information may be different according to the priority information based on the upper signal configuration information of [Table 31]. The priority information may be a value composed of 1 bit or other bit information, and in the case of 1 bit, if 0, the priority is low, and if 1, the priority is high. In addition, in the case of a DCI format in which priority-related setting information is set as a higher-order signal but has no priority information in the DCI field, it may be possible to always regard the priority as low. For example, the number of CBGs set according to the priority information according to [Table 31] may be different, and when the priority is low, the number of CBGs may be 8, and when the priority is high, the number of CBGs may be 1. Therefore, when priority setting information and CBG setting information exist in the DCI format, the DCI format is configured with the largest bit of CBG setting information set according to each priority information. Therefore, when the priority information is low, the CBG composed of 8 bits informs whether each is scheduled, and when the priority information is high, the 8-bit value is regarded as inactive (or a value not used by the terminal).

The enhanced Type-3 HARQ-ACK codebook may be indicated by DCI, and in this case, the priority information value may be included in the corresponding DCI information. Therefore, at this time, the priority information may be able to inform the priority information of the PUCCH or PUSCH including the enhanced Type-3 HARQ-ACK codebook, and the information of the enhanced Type-3 HARQ-ACK codebook itself is the priority information It may or may not change depending on Changing according to the priority information means that the priority information field additionally provides enhanced Type-3 HARQ-ACK codebook information configuration information in addition to the field indicating the enhanced Type-3 HARQ-ACK codebook information configuration itself. What does not change according to the priority information is that even if there is a priority information field, the enhanced Type-3 HARQ-ACK codebook information is set only by the field indicating the configuration of the enhanced Type-3 HARQ-ACK codebook information itself, regardless of the priority information. means to be

The case of changing according to the priority information is, for example, when the priority is low as in the example above, the number of CBGs is 8, and when the priority is high, the number of CBGs is 1, the enhanced Type-3 HARQ-ACK codebook When the field indicating is activated and at the same time a low priority information is indicated, the terminal assumes that the information of the enhanced Type-3 HARQ-ACK codebook is in the form that each TB consists of 8 CBGs On the other hand, when a high value of priority information is indicated, the terminal may be able to assume the information of the enhanced Type-3 HARQ-ACK codebook in the form of each TB. If it does not change according to the priority information, the number of CBGs may be changed according to the priority setting information as shown in [Table 31], and as described above, the number of CBGs among the elements constituting the enhanced Type-3 HARQ-ACK codebook information Since it considers, methods for configuring a constant enhanced Type-3 HARQ-ACK codebook may be needed regardless of the information indicated by the priority value. As an example for solving this problem, it may be possible to force the UE to always set the same number of CBG values regardless of priority information. If a different number is set, the terminal may consider this as an error case or assume that the enhanced Type-3 HARQ-ACK codebook is configured with the largest or smallest value among CBGs of different values set for each priority. Alternatively, it may be possible to assume a CBG setting value related to the lowest priority or to assume a CBG setting value related to the highest priority.

If the enhanced Type-3 HARQ-ACK codebook is configured with a large value, a case may occur when the corresponding CBG is not actually scheduled for each HARQ process, and in this case, the terminal transmits the corresponding CBG value with NACK Mapping may be possible. Specifically, for example, in a situation where 8 CBGs are configured for each TB, the UE can map HARQ-ACK information of each CBG with up to 8 bits for each HARQ process. If, in a specific HARQ process, only 2 CBGs are actually When scheduled, the terminal may be able to map only the first two bits of information to ACK or NACK information for the corresponding CBG, and map the other six bits of information to NACK.

If the enhanced Type-3 HARQ-ACK codebook is configured with a small value, it may happen that more CBGs are actually scheduled for each HARQ process, and in this case, the terminal is HARQ bundling or dropping It may be possible to do For example, the UE configures the enhanced Type-3 HARQ-ACK codebook by considering only one CBG (or TB) for each HARQ process, but when 4 CBGs are actually scheduled for a specific HARQ process, the UE configures the corresponding CBGs ACK or NACK information is bundled and reported as one value. Here, bundling ACK or NACK means that if at least one value of NACK is information, the corresponding bundled HARQ-ACK information is NACK. As another example, for example, the UE configures an enhanced Type-3 HARQ-ACK codebook by considering only two CBGs (or TBs) for each HARQ process, but in fact four CBGs are scheduled for a specific HARQ process. , it may be possible that the former two CBGs are bundled and mapped to the first bit, and the latter two CBGs are bundled and mapped to the second bit. If the CBG field is set but the actual CBG is not scheduled, the terminal considers it an ACK when bundling HARQ-ACK including the CBG or does not use HARQ-ACK information for the unscheduled CBG in bundling operation that could be possible

If the enhanced Type-3 HARQ-ACK codebook is configured with the number of CBGs related to low-priority information or the number of CBGs related to high-priority information, the number of CBGs related to other priority information may be generated, As described above, when the number of CBGs considered for setting the enhanced Type-3 HARQ-ACK codebook is greater than the number of CBGs indicated for the actual specific HARQ process, NACK information is mapped for CBGs that are not actually scheduled, and the actual specific HARQ process If the number of CBGs considered for setting the enhanced Type-3 HARQ-ACK codebook is less than the number of CBGs indicated for , it is possible to bundle and map all or part of the HARQ-ACK information of a plurality of actually scheduled CBGs. For example, when the priority value is 0 and the number of CBGs is set to 4, when the enhanced Type-3 HARQ-ACK codebook is generated based on the low priority information value (when 0), HARQ Bits for 4 CBGs are required per process and per TB. At this time, if the number of CBGs when the priority value is 1 is 1, only 1 bit of MSB or LBS is used for mapping among 4 bits, and if the number of CBGs is 2, only 2 bits of MSB or LBS are used. When the number of CBGs is 4, all 4 previously set bits are used for mapping, and when the number of CBGs is 8, bundling 2 for each CBG is generated as 1 bit, and then mapping to 4 bits. that could be possible Mapping to a specific bit means putting a value of 0 or 1 in a bit position associated with HARQ-ACK information generated for each specific TB and each CBG.

Alternatively, apart from CBG size information set according to the priority information described in [Table 31], indicator information indicating how many CBGs per TB can be set for each HARQ process for configuring the enhanced Type-3 HARQ-ACK codebook is upper signal can be included. Alternatively, based on the CBG size information set according to the priority information described in [Table 31], certain CBG information bits are selected through the CBG indicator field included in the DCI format indicating transmission of the enhanced Type-3 HARQ-ACK codebook information. It may be possible to indicate an indication as an operation included in . For example, when the corresponding DCI format is composed of 4 CBG indicator fields and indicates 1100, when the UE transmits enhanced Type-3 HARQ-ACK codebook information, HARQ-ACK codebook information transmitted for each HARQ process and for each TB It may be possible to include information of only two CBGs in .

The above description has been mainly limited to the case where the number of CBGs set for each priority is different, but in addition to this, it can be sufficiently applied even when the number of codewords set for each priority is different, the number of set HARQ processes, or the number of set serving cells is different. can

As described above, it may be possible to report NDI information in addition to HARQ-ACK information for each serving cell and each HARQ process in not only the Type-3 HARQ-ACK codebook but also the enhanced Type-3 HARQ-ACK codebook information. The presence or absence of NDI information included in the Enhanced Type-3 HARQ-ACK codebook information configuration may be set per serving cell or per priority. When configured per serving cell, it is possible for the terminal to map or not map the most recently received NDI information from the base station for each HARQ process in addition to the HARQ-ACK information according to the presence or absence of NDI information per serving cell regardless of the presence or absence of priority information. can

If, in addition to the serving cell, if the presence or absence of NDI information differs according to the priority value even within the same serving cell, the UE should always include NDI information when transmitting enhanced Type-3 HARQ-ACK codebook information in the serving cell. You need to decide what to include or not to include. For example, in a specific serving cell, when the priority value is 0, the NDI is not included, and when the priority value is 1, the NDI value is set to be included. Since it has been set to include, it may be possible to transmit the enhanced Type-3 HARQ-ACK codebook including the NDI value. Alternatively, since the terminal has received a setting not to include the NDI value in at least one priority value, it may be possible to transmit the enhanced Type-3 HARQ-ACK codebook without including the NDI value. Alternatively, the UE may be able to transmit the enhanced Type-3 HARQ-ACK codebook without including the NDI value in consideration of only NDI configuration information having a low priority value. Alternatively, the UE may be able to transmit the enhanced Type-3 HARQ-ACK codebook including the NDI value in consideration of only NDI configuration information having a high priority value. Alternatively, an enhanced Type-3 HARQ-ACK codebook including an NDI value is transmitted based on the higher signal configuration information according to the priority information value included in the DCI format indicating the enhanced Type-3 HARQ-ACK codebook, or NDI It may be possible to transmit an enhanced Type-3 HARQ-ACK codebook that does not include a value. Alternatively, the base station may be forced to always provide the same NDI configuration for each serving cell regardless of priority information. That is, the terminal does not expect to receive different NDI settings for each of the above-described different priorities, and when such settings are received from the base station, the terminal may regard it as an error case.

When the terminal reports the ability to report the enhanced Type-3 HARQ-ACK codebook to the base station, the above-described embodiments may be operated by setting the base station. Alternatively, the terminal may be able to report the ability to report the enhanced Type-3 HARQ-ACK codebook to the base station under the condition that the terminal has the ability to report the Type-3 HARQ-ACK codebook. Alternatively, it may be possible to report the ability to report the enhanced Type-3 HARQ-ACK codebook separately from the ability to report the Type-3 HARQ-ACK codebook.

The base station may set the enhanced Type-3 HARQ-ACK codebook setting to a combination of at least one or some of the above-described embodiments, and the enhanced Type-3 HARQ-ACK codebook and the Type-3 HARQ-ACK codebook for each serving cell It may be possible to set them separately. The maximum number of HARQ-ACK codebooks that can be indicated in the enhanced Type-3 HARQ-ACK codebook may be limited to a maximum of 2 or a maximum of N for each serving cell, and the value of N may be reported for each terminal capability. there is. The value of N can be considered as the number of rows in [Table 26]. That is, it means the number of types of enhanced Type-3 HARQ-ACK codebooks that can be indicated in a specific field of the DCI format indicating the enhanced Type-3 HARQ-ACK codebook. For example, when a specific terminal reports an enhanced Type-3 HARQ-ACK codebook and the base station reports that the value of N is 2, the base station sets up to two enhanced Type-3 HARQ-ACK codebooks in [Table 26]. Information composed of rows may be provided to the terminal. Therefore, when the terminal receives DCI indicating the enhanced Type-3 HARQ-ACK codebook, it may be possible to transmit enhanced Type-3 HARQ-ACK codebook information for at least one of up to two on PUCCH or PUSCH. In addition, the terminal may be able to report information on which embodiment among the above embodiments is supported and the terminal capability. In addition, the terminal may be able to report information on whether different NDI configuration information or different numbers of CBGs are supported according to priority information.

The terminal may transmit HARQ-ACK information corresponding to the codebook after N symbols after the last symbol of the PDCCH including the DCI indicating the request for reporting the Type-3 HARQ-ACK codebook. The value of N may vary depending on the subcarrier interval and the processing time setting of the UE. For example, when the UE is configured to process fast processing in a specific serving cell, N = 5 for 15 kHz, N = 5.5 for 30 kHz, and N = 11 for 60 kHz, and when there is no corresponding setting, N = 10 for 15 kHz, N =12 for 30kHz, N=22 for 60kHz, N=25 for 120kHz. If the subcarrier spacing of the PDCCH including the DCI indicating the request for reporting the Type-3 HARQ-ACK codebook is different from the subcarrier spacing of the PUCCH or PUSCH transmitting HARQ-ACK information, the smallest subcarrier is assumed. Processing time calculation for the Enhanced Type-3 HARQ-ACK codebook may be the same as that described in the Type-3 HARQ-ACK codebook. Alternatively, since the Enhanced Type-3 HARQ-ACK codebook report can report one or more different HARQ-ACK information unlike the Type-3 HARQ-ACK codebook report, more processing time is required to reduce the implementation burden of the UE. can As an example, the UE may transmit HARQ-ACK information corresponding to the codebook after (N + A) symbols after the last symbol of the PDCCH including the DCI indicating the request for reporting the Enhanced Type-3 HARQ-ACK codebook. can The A value may exist when two or more Enhanced Type-3 HARQ-ACK codebooks are configured. When the number of HARQ-ACK information that can be reported in the Enhanced Type-3 HARQ-ACK codebook is 1, A = 0, and when the number of HARQ-ACK information that can be reported in the Enhanced Type-3 HARQ-ACK codebook is 2, A = 1. Alternatively, the A value may have a different value according to the number of HARQ-ACK information that can be reported in the Enhanced Type-3 HARQ-ACK codebook. Alternatively, the A value may have different values according to UE capability reports.

13 is a diagram illustrating a structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 13 , a terminal may include a terminal receiving unit 1300 and a transceiver that refers to a terminal transmitting unit 1310, a memory (not shown), and a terminal processing unit 1305 (or a terminal control unit or processor). According to the communication method of the terminal described above, the transmission/reception units 1300 and 1310 of the terminal, the memory and the terminal processing unit 1305 may operate. However, the components of the terminal are not limited to the above-described examples. For example, a terminal may include more or fewer components than the aforementioned components. In addition, the transceiver, memory, and processor may be implemented in a single chip form.

The transmitting/receiving unit may transmit/receive signals with the base station. Here, the signal may include control information and data. To this end, the transceiver unit may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting the frequency. However, this is only one embodiment of the transceiver, and components of the transceiver are not limited to the RF transmitter and the RF receiver.

Also, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit the signal output from the processor through the wireless channel.

The memory may store programs and data required for operation of the terminal. In addition, the memory may store control information or data included in signals transmitted and received by the terminal. The memory may 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. Also, there may be a plurality of memories.

In addition, the processor may control a series of processes so that the terminal can operate according to the above-described embodiment. For example, the processor may control components of the terminal to simultaneously receive a plurality of PDSCHs by receiving DCI composed of two layers. There may be a plurality of processors, and the processors may perform component control operations of the terminal by executing a program stored in a memory.

14 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 14 , a base station may include a base station receiving unit 1400 and a transmitting/receiving unit that refers to a base station transmitting unit 1410, a memory (not shown), and a base station processing unit 1405 (or a base station control unit or processor). According to the communication method of the base station described above, the transmission/reception units 1400 and 1410 of the base station, the memory and the base station processing unit 1405 can operate. However, components of the base station are not limited to the above-described examples. For example, a base station may include more or fewer components than those described above. In addition, the transceiver, memory, and processor may be implemented in a single chip form.

The transmission/reception unit may transmit/receive signals with the terminal. Here, the signal may include control information and data. To this end, the transceiver unit may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying a received signal and down-converting the frequency. However, this is only one embodiment of the transceiver, and components of the transceiver are not limited to the RF transmitter and the RF receiver.

Also, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit the signal output from the processor through the wireless channel.

The memory may store programs and data necessary for the operation of the base station. In addition, the memory may store control information or data included in signals transmitted and received by the base station. The memory may 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. Also, there may be a plurality of memories.

The processor may control a series of processes so that the base station operates according to the above-described embodiment of the present disclosure. For example, the processor may configure and transmit two layers of DCIs including allocation information for a plurality of PDSCHs and may control each element of the base station. There may be a plurality of processors, and the processors may perform a component control operation of the base station by executing a program stored in a memory.

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

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

Such programs (software modules, software) may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of It can be stored on optical storage devices, magnetic cassettes. Alternatively, it may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

In addition, the program accesses through a communication network such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), or a Storage Area Network (SAN), or a communication network composed of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the invention are expressed in singular or plural numbers according to the specific embodiments presented. However, the singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

On the other hand, the embodiments of the present disclosure disclosed in the present specification and drawings are only presented as specific examples to easily explain the technical content of the present disclosure and help understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other modifications based on the technical idea of the present disclosure are possible. In addition, each of the above embodiments can be operated in combination with each other as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure and another embodiment. For example, a base station and a terminal may be operated by combining parts of the first embodiment and the second embodiment of the present disclosure. In addition, although the above embodiments have been presented based on the FDD LTE system, other modifications based on the technical idea of the above embodiment may be implemented in other systems such as a TDD LTE system, 5G or NR system.

Meanwhile, the order of explanation in the drawings for explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

Alternatively, drawings describing the method of the present invention may omit some of the elements and include only some of the elements within the scope of not impairing the essence of the present invention.

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

Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those of ordinary skill in the art to which the present disclosure belongs will be able to understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present disclosure. The scope of the present disclosure is indicated by the following claims rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included in the scope of the present disclosure. do.

Claims (1)

A control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images