KR20220151928A - Method and apparatus for spatial relation activation of physical uplink control channel for network cooperative communication system - Google Patents

Abstract

The present disclosure relates to a communication technique for converging a 5G communication system with IoT technology to support a higher data transfer rate beyond a 4G system, and a system thereof. The present disclosure can be applied to intelligent services (for example, smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security- and safety-related services, or the like) based on 5G communication technology and IoT-related technology. The present disclosure relates to a method and apparatus for performing spatial relation activation of an uplink control signal considering multiple transmission/reception points in a wireless communication system.

Description

METHOD AND APPARATUS FOR SPATIAL RELATION ACTIVATION OF PHYSICAL UPLINK CONTROL CHANNEL FOR NETWORK COOPERATIVE 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 and apparatus for performing spatial relationship activation of an uplink control signal considering multiple transmission/reception points in a wireless communication system.

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.

The disclosed embodiments provide an apparatus and method capable of effectively providing 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 setting a bandwidth portion in a wireless communication system according to an embodiment of the present disclosure.
4 is a diagram illustrating an example of setting a control resource set of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.
5 is a diagram illustrating a structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.
6 is a diagram illustrating an example of base station beam allocation according to TCI state setting in a wireless communication system according to an embodiment of the present disclosure.
7 is a diagram illustrating an example of a TCI state allocation method for a PDCCH in a wireless communication system according to an embodiment of the present disclosure.
6 is a diagram illustrating a TCI indication MAC CE signaling structure for PDCCH DMRS in a wireless communication system according to an embodiment of the present disclosure.
9 is a diagram illustrating an example of beam configuration of a control resource set and a search space in a wireless communication system according to an embodiment of the present disclosure.
10A and 10B are diagrams for explaining a method for selecting a receivable control resource set in consideration of priority when a terminal receives a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.
11 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.
12 is a diagram illustrating an example of MAC CE for PUCCH resource group based spatial relationship activation in a wireless communication system according to an embodiment of the present disclosure.
13 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.
14 is a diagram illustrating a radio protocol structure of a base station and a terminal in single cell, carrier aggregation, and dual connectivity situations in a wireless communication system according to an embodiment of the present disclosure.
15 is a diagram illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment of the present disclosure.
16 is a diagram illustrating a configuration example of downlink control information (DCI) for cooperative communication in a wireless communication system according to an embodiment of the present disclosure.
17a and 17b show spatial relationship information for a PUCCH resource group indicated as first in a corresponding MAC CE among PUCCH resource groups including a PUCCH resource having a minimum ID according to an embodiment of the present disclosure. It is a diagram showing an example of activating spatial relationship information of a PUCCH resource having an ID.
18 illustrates an operation of a UE for activating spatial relationship information of a PUCCH resource having a minimum ID according to an embodiment of the present disclosure.
19 illustrates an operation of a base station for activating spatial relationship information of PUCCH resources according to an embodiment of the present disclosure.
20 illustrates an example of MAC CE for activating PUCCH resource group-based spatial relationship information when configuring a PUCCH resource group for repeated PUCCH transmission considering multiple TRPs according to an embodiment of the present disclosure.
21 is a diagram illustrating a structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.
22 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, gNB, eNode B, eNB, Node B, BS (Base Station), a radio access unit, a base station controller, or a node on a network. . In addition, the base station includes an Integrated Access and Backhaul-donor (IAB-donor), which is a gNB that provides network access to the terminal (s) through a network of backhaul and access links in the NR system, and the terminal (s) ) and an IAB-node, which is a radio access network (RAN) node supporting NR backhaul links to the IAB-donor or other IAB-nodes. . The terminal is wirelessly connected through the IAB-node and can transmit and receive data with an IAB-donor connected to at least one IAB-node through a backhaul link. 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 wireless communication technology (5G, new radio, NR) developed after LTE-A may be included in this, and the following 5G may be a concept including existing LTE, LTE-A and other similar services have. 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.

For convenience of description below, some terms and names defined in the 3GPP standards (5G, NR, LTE, or similar system standards) may be used. However, the present disclosure is not limited by terms and names, and may be equally applied to systems conforming to other standards. Also used in the following description are terms for identifying access nodes, terms for network entities (network entities), terms for messages, terms for interfaces between network entities, and various types of identification information. Terms and the like referring to are illustrated for convenience of description. Therefore, it is not limited to the terms used in this disclosure, and other terms that refer to objects having equivalent technical meanings may be used.

[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에서

는 부반송파 간격 설정(μ)을 위한 서브프레임(110) 당 OFDM 심볼 수이고, 5G 시스템에서 자원 구조에 대한 보다 구체적인 설명은 TS 38.211 section 4 규격을 참조할 수 있다.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). in Figure 1

is the number of OFDM symbols per subframe 110 for setting the subcarrier interval (μ), and a more detailed description of the resource structure in the 5G system may refer to TS 38.211 section 4 standard.

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)으로 구성될 수 있다. 즉 부반송파 간격(subcarrier spacing)에 대한 설정 값 μ에 따라 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 spacing (

) 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.

0 14 10 One One 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16 5 14 320 32

[Bandwidth Part (BWP)]

Next, the bandwidth part (BWP) setting in the 5G communication system will be described in detail with reference to the drawings.

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

3 shows an example in which the UE bandwidth 300 is set to two bandwidth parts, that is, bandwidth part # 1 (BWP # 1) 301 and bandwidth part # 2 (BWP # 2) 302. show The base station may set one or a plurality of bandwidth parts to the terminal, and may set the following information for each bandwidth part.

BWP ::= SEQUENCE {
bwp-Id BWP-Id,
(Bandwidth Part Identifier)
locationAndBandwidth INTEGER (1..65536),
(Bandwidth part position)
subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},
(subcarrier spacing)
cyclicPrefix ENUMERATED { extended }
(cyclic prefix)
}

In [Table 2], "locationAndBandwidth" represents the location and bandwidth in the frequency domain of the bandwidth part, "subcarrierSpacing" represents the subcarrier spacing to be used in the bandwidth part, and "cyclicPrefix" represents the extended CP (cyclic prefix) is used.

Of course, it is not limited to the above example, and various parameters related to the bandwidth part may be set in the terminal in addition to the setting information. The information may be transmitted from the base station to the terminal through higher layer signaling, for example, radio resource control (RRC) signaling. At least one bandwidth part among one or a plurality of set bandwidth parts may be activated. Whether or not the set bandwidth portion is activated may be semi-statically transmitted from the base station to the terminal through RRC signaling or dynamically transmitted through downlink control information (DCI).

According to some embodiments, a terminal before RRC (Radio Resource Control) connection may receive an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, in the initial access step, the terminal receives system information (remaining system information; RMSI or System Information Block 1; may correspond to SIB1) necessary for initial access through the MIB. PDCCH for receiving can be transmitted Setting information on a control resource set (CORESET) and a search space may be received. The control resource set and search space set by MIB can be regarded as identity (ID) 0, respectively. The control resource set and search space established through the MIB may be referred to as a common control resource set and common search space, respectively. The base station may notify the terminal of setting information such as frequency allocation information, time allocation information, and numerology for the control region #0 through the MIB. In addition, the base station may notify the terminal of configuration information about the monitoring period and occasion for control region #0, that is, configuration information about search space #0, through the MIB. The terminal may regard the frequency domain set as the control resource set #0 acquired from the MIB as an initial bandwidth part for initial access. At this time, the identifier (ID) of the initial bandwidth part may be regarded as 0. The control resource set may be referred to as a control region, a control resource region, and the like.

The setting for the portion of the bandwidth supported by 5G can be used for various purposes.

According to some embodiments, when the bandwidth supported by the terminal is smaller than the system bandwidth, it can be supported through the bandwidth portion setting. For example, the base station can transmit and receive data at a specific frequency position within the system bandwidth by setting the frequency position of the bandwidth part to the terminal.

Also, according to some embodiments, the base station may set a plurality of bandwidth parts to the terminal for the purpose of supporting different numerologies. For example, in order to support both data transmission and reception using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz to a terminal, two bandwidth parts may be set to subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth parts may be frequency division multiplexed, and when data is to be transmitted/received at a specific subcarrier interval, a bandwidth portion set at a corresponding subcarrier interval may be activated.

Also, according to some embodiments, for the purpose of reducing the power consumption of the terminal, the base station may set bandwidth parts having different sizes of bandwidth to the terminal. For example, when a terminal supports a very large bandwidth, for example, a bandwidth of 100 MHz and always transmits and receives data with the corresponding bandwidth, very large power consumption may occur. In particular, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz in a non-traffic situation may be very inefficient in terms of power consumption. For the purpose of reducing power consumption of the terminal, the base station may set a bandwidth part of a relatively small bandwidth, for example, a bandwidth part of 20 MHz for the terminal. In a situation where there is no traffic, the terminal can perform a monitoring operation in the 20 MHz bandwidth part, and when data is generated, it can transmit and receive data in the 100 MHz bandwidth part according to the instructions of the base station.

In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information on the initial bandwidth part (Initial Bandwidth Part) through a Master Information Block (MIB) in an initial access step. More specifically, the terminal is a control resource set for a downlink control channel in which DCI (Downlink Control Information) scheduling SIB (System Information Block) from MIB of PBCH (Physical Broadcast Channel) can be transmitted , CORESET) can be set. The bandwidth of the control resource set set as the MIB may be regarded as an initial bandwidth portion, and the terminal may receive a physical downlink shared channel (PDSCH) through which the SIB is transmitted through the set initial bandwidth portion. The initial bandwidth portion may be used for other system information (Other System Information, OSI), paging, and random access in addition to the purpose of receiving the SIB.

[Change bandwidth part (BWP)]

When one or more bandwidth parts are configured for the terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using a bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently active bandwidth part of the terminal is bandwidth part #1 301, the base station may instruct the terminal with the bandwidth part #2 302 as a bandwidth part indicator in the DCI, and the terminal receives The bandwidth part change can be performed with the bandwidth part #2 302 indicated by the bandwidth part indicator in the DCI.

As described above, since the DCI-based bandwidth part change can be indicated by the DCI that schedules the PDSCH or PUSCH, when the UE receives the bandwidth part change request, the PDSCH or PUSCH scheduled by the corresponding DCI is grouped in the changed bandwidth part. It must be possible to receive or transmit without To this end, the standard stipulates a requirement for a delay time (T _BWP ) required when changing a bandwidth part, and may be defined, for example, as follows.

NR Slot length (ms) BWP switch delay T _BWP (slots) Type 1 ^{Note 1} Type 2 ^{Note 1} 0 One One 3 One 0.5 2 5 2 0.25 3 9 3 0.125 6 18 Note 1: Depends on UE capability.
Note 2: If the BWP switch involves changing of SCS, the BWP switch delay is determined by the larger one between the SCS before BWP switch and the SCS after BWP switch.

The requirement for the bandwidth part change delay time supports type 1 or type 2 according to the capability of the terminal. The terminal may report the supportable bandwidth partial delay time type to the base station.

According to the above-mentioned requirement for the bandwidth portion change delay time, when the terminal receives the DCI including the bandwidth portion change indicator in slot n, the terminal changes to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+ It can be completed at a time no later than T _BWP , and transmission and reception for a data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth part. When the base station wants to schedule the data channel with a new bandwidth part, it can determine the time domain resource allocation for the data channel in consideration of the bandwidth part change delay time (T _BWP ) of the terminal. That is, when scheduling a data channel with a new bandwidth part, in the method of determining time domain resource allocation for the data channel, the base station may schedule the corresponding data channel after the bandwidth part change delay time. Accordingly, the terminal may not expect that the DCI indicating the bandwidth portion change indicates a slot offset value (K0 or K2) smaller than the bandwidth portion change delay time (T _BWP ).

If the terminal receives a DCI (for example, DCI format 1_1 or 0_1) indicating a change in bandwidth portion, the terminal receives the PDCCH including the DCI from the third symbol of the received slot, the time domain resource allocation indicator field in the corresponding DCI No transmission or reception may be performed during a time period corresponding to the start point of the slot indicated by the slot offset value (K0 or K2) indicated by . For example, if the terminal receives a DCI indicating a bandwidth portion change in slot n, and the slot offset value indicated by the corresponding DCI is K, the terminal moves from the third symbol of slot n to the previous symbol of slot n+K (i.e., the slot No transmission or reception may be performed until the last symbol of n+K-1).

[SS/PBCH block]

Next, a Synchronization Signal (SS)/PBCH block in 5G will be described.

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

- PSS: This is a signal that is a standard for downlink time/frequency synchronization and provides some information of cell ID.

- SSS: serves as a standard for downlink time/frequency synchronization, and provides remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for demodulation of PBCH.

- PBCH: Provides essential system information necessary for transmitting and receiving the data channel and control channel of the terminal. Essential system information may include search space-related control information indicating radio resource mapping information of a control channel, scheduling control information for a separate data channel through which system information is transmitted, and the like.

- SS/PBCH block: The SS/PBCH block consists of a combination of PSS, SSS, and PBCH. One or a plurality of SS/PBCH blocks may be transmitted within 5 ms, and each SS/PBCH block to be transmitted may be distinguished by an index.

The UE can detect the PSS and SSS in the initial access stage and decode the PBCH. A MIB can be obtained from the PBCH, and a control resource set (CORESET) #0 (which may correspond to a control resource set having a control resource set index of 0) can be set therefrom. The UE may perform monitoring for the control resource set #0 assuming that the selected SS/PBCH block and demodulation reference signal (DMRS) transmitted in the control resource set #0 are quasi co-located (QCL). The terminal may receive system information through downlink control information transmitted from control resource set #0. The terminal may obtain RACH (Random Access Channel) related setting information required for initial access from the received system information. The terminal may transmit a physical RACH (PRACH) to the base station in consideration of the selected SS/PBCH index, and the base station receiving the PRACH may obtain information on the SS/PBCH block index selected by the terminal. The base station can know that the terminal has selected a certain block from among each SS/PBCH block and monitors the control resource set #0 related thereto.

[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 DCI format for non-preparation 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 terminal. 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.

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.

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.

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.

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

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

4 is a diagram illustrating an example of a control resource set (CORESET) through which a downlink control channel is transmitted in a 5G wireless communication system. 4 shows a UE bandwidth part (410) on the frequency axis and two control resource sets (control resource set # 1 (401) and control resource set # 2 (402) within 1 slot 420 on the time axis. ) is set. The control resource sets 401 and 402 may be set to a specific frequency resource 403 within the entire terminal bandwidth portion 410 on the frequency axis. In FIG. 4, a specific frequency resource 403 shows an example of a frequency resource set in the control resource set #1 401. The control resource set may be configured with one or a plurality of OFDM symbols on the time axis and may be defined as a control resource set duration (404). Referring to the example shown in FIG. 4, control resource set #1 (401) is set to a control resource set length of 2 symbols, and control resource set #2 (402) is set to a control resource set length of 1 symbol. have.

The above-described control resource set in 5G may be set by the base station to the terminal through higher layer signaling (eg, system information, master information block (MIB), radio resource control (RRC) signaling). Setting the control resource set to the terminal means providing information such as a control resource set identity, a frequency location of the control resource set, and a symbol length of the control resource set. For example, the setting information for the control resource set may include the following information.

ControlResourceSet ::= SEQUENCE {
-- Corresponds to L1 parameter 'CORESET-ID'

controlResourceSetId ControlResourceSetId,
(Control resource set identifier (Identity))
frequencyDomainResources BIT STRING (SIZE (45)),
(frequency axis resource allocation information)
duration INTEGER (1..maxCoReSetDuration),
(time axis resource allocation information)
cce-REG-MappingType CHOICE {
(CCE-to-REG mapping method)
interleaved SEQUENCE {

reg-BundleSize ENUMERATED {n2, n3, n6},
(REG bundle size)

precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},

interleaverSize ENUMERATED {n2, n3, n6}
(interleaver size)

shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL
(Interleaver Shift)
},
nonInterleaved NULL
},
tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,
(QCL setting information)
tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S
}

In Table 8, the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) setting information includes one or a plurality of SSs (Synchronization signal)/PBCH (Physical Broadcast Channel) block index or CSI-RS (Channel State Information Reference Signal) index information.

5 is a diagram showing an example of basic units of time and frequency resources constituting a downlink control channel that can be used in 5G. According to FIG. 5, the basic unit of time and frequency resources constituting the control channel can be referred to as a REG (Resource Element Group, 503), and the REG 503 is 1 OFDM symbol 501 on the time axis and 1 PRB on the frequency axis. (Physical Resource Block, 502), that is, it can be defined as 12 subcarriers. The base station may configure a downlink control channel allocation unit by concatenating the REGs 503.

As shown in FIG. 5, when a basic unit to which a downlink control channel is allocated in 5G is a Control Channel Element (CCE) 504, one CCE 504 may be composed of a plurality of REGs 503. Taking the REG 503 shown in FIG. 5 as an example, the REG 503 may consist of 12 REs, and if 1 CCE 504 consists of 6 REGs 503, 1 CCE 504 may consist of 72 REs. When a downlink control resource set is set, a corresponding area may be composed of a plurality of CCEs 504, and a specific downlink control channel is one or a plurality of CCEs 504 according to an aggregation level (AL) in the control resource set. ) and can be transmitted. The CCEs 504 in the control resource set are identified by numbers, and at this time, the numbers of the CCEs 504 may be assigned according to a logical mapping method.

The basic unit of the downlink control channel shown in FIG. 5, that is, the REG 503, may include both REs to which DCI is mapped and a region to which the DMRS 505, which is a reference signal for decoding them, is mapped. As shown in FIG. 5, three DMRSs 505 may be transmitted within one REG 503. The number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16 according to the aggregation level (AL), and the different numbers of CCEs can be used for link adaptation of the downlink control channel. can be used to implement For example, when AL=L, one downlink control channel can be transmitted through L CCEs. A UE needs to detect a signal without knowing information about a downlink control channel. A search space representing a set of CCEs is defined for blind decoding. The search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode on a given aggregation level, and various aggregations that make one group with 1, 2, 4, 8, and 16 CCEs Since there are levels, the terminal can have a plurality of search spaces. A search space set may be defined as a set of search spaces at all set aggregation levels.

The search space can be classified into a common search space and a UE-specific search space. A certain group of terminals or all terminals can search the common search space of the PDCCH in order to receive cell-common control information such as dynamic scheduling for system information or a paging message. For example, PDSCH scheduling allocation information for SIB transmission including cell operator information may be received by examining the common search space of the PDCCH. In the case of a common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a set of pre-promised CCEs. Scheduling assignment information for the UE-specific PDSCH or PUSCH may be received by examining the UE-specific search space of the PDCCH. The UE-specific search space may be defined UE-specifically as a function of the identity of the UE and various system parameters.

In 5G, a parameter for a search space for a PDCCH may be configured from a base station to a terminal using higher layer signaling (eg, SIB, MIB, RRC signaling). For example, the base station includes the number of PDCCH candidate groups at each aggregation level L, a monitoring period for the search space, a monitoring occasion in symbol units within a slot for the search space, a search space type (common search space or UE-specific search space), A combination of a DCI format and an RNTI to be monitored in the search space, a control resource set index to be monitored in the search space, and the like may be set to the terminal. For example, configuration information for a search space for a PDCCH may include the following information.

SearchSpace ::= SEQUENCE {
-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.
searchSpaceId SearchSpaceId,
(search space identifier)
controlResourceSetId ControlResourceSetId,
(control resource set identifier)
monitoringSlotPeriodicityAndOffset CHOICE {
(monitoring slot level period)
sl1 NULL,
sl2 INTEGER (0..1),
sl4 INTEGER (0..3),
sl5 INTEGER (0..4),
sl8 INTEGER (0..7),
sl10 INTEGER (0..9),
sl16 INTEGER (0..15),
sl20 INTEGER (0..19)
} OPTIONAL,
duration (monitoring length) INTEGER (2..2559)
monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,
(monitoring symbol in slot)
nrofCandidates SEQUENCE {
(number of PDCCH candidates by aggregation level)
aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}
},

searchSpaceType CHOICE {
(search space type)
-- Configures this search space as common search space (CSS) and DCI formats to monitor.
common SEQUENCE {
(common search space)
}
ue-Specific SEQUENCE {
(terminal-specific search space)
-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.
formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},
...
}

According to the setting information, the base station may set one or a plurality of search space sets for the terminal. According to some embodiments, the base station may set search space set 1 and search space set 2 to the terminal, set DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and search DCI format B scrambled with Y-RNTI in space set 2 can be configured to be monitored in a UE-specific search space. In the X-RNTI and Y-RNTI, "X" and "Y" may correspond to one of various RNTIs to be described later.

According to the setting information, one or a plurality of search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be set as common search spaces, and search space set #3 and search space set #4 may be set as terminal-specific search spaces.

In the common search space, a combination of the following DCI format and RNTI can be monitored. Of course, it is not limited to the following examples.

- DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

- DCI format 2_0 with CRC scrambled by SFI-RNTI

- DCI format 2_1 with CRC scrambled by INT-RNTI

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

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

In the UE-specific search space, a combination of the following DCI format and RNTI may be monitored. Of course, it is not limited to the following examples.

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

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

The specified RNTIs may follow the following definitions and uses.

C-RNTI (Cell RNTI): Use of UE-specific PDSCH scheduling

TC-RNTI (Temporary Cell RNTI): Use for UE-specific PDSCH scheduling

CS-RNTI (Configured Scheduling RNTI): Use of semi-statically configured UE-specific PDSCH scheduling

RA-RNTI (Random Access RNTI): PDSCH scheduling in random access phase

P-RNTI (Paging RNTI): PDSCH scheduling purpose through which paging is transmitted

SI-RNTI (System Information RNTI): PDSCH scheduling purpose for transmitting system information

INT-RNTI (Interruption RNTI): used to inform whether pucturing for PDSCH

TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control command for PUSCH

TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Use to indicate power control command for PUCCH

TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control command for SRS

The aforementioned specified DCI formats may follow the definition below.

DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1 Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1 Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slot format 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a group of TPC commands for SRS transmissions by one or more UEs

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

- L: aggregation level

: 캐리어(Carrier) 인덱스-

: Carrier index

: 제어자원세트 p 내에 존재하는 총 CCE 개수-

: Total number of CCEs present in the control resource set p

: 슬롯 인덱스-

: slot index

: 집성 레벨 L의 PDCCH 후보군 수-

: Number of PDCCH candidates at aggregation level L

= 0, ...,

-1: 집성 레벨 L의 PDCCH 후보군 인덱스-

= 0, ...,

-1: PDCCH candidate group index of aggregation level L

- i = 0, ..., L-1

,

,

,

,

,

-

,

,

,

,

,

: 단말 식별자-

: terminal identifier

값은 공통 탐색공간의 경우 0에 해당할 수 있다.

The value may correspond to 0 in the case of a common search space.

값은 단말-특정 탐색공간의 경우, 단말의 신원(C-RNTI 또는 기지국이 단말에게 설정해준 ID)과 시간 인덱스에 따라 변하는 값에 해당할 수 있다.

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

In 5G, as a plurality of search space sets can be set with different parameters (eg, parameters in Table 9), the set of search space sets monitored by the terminal at each point in time may be different. For example, if search space set #1 is set to an X-slot period and search space set #2 is set to a Y-slot period and X and Y are different, the terminal searches search space set #1 and search space set #1 in a specific slot. All space set #2 can be monitored, and one of search space set #1 and search space set #2 can be monitored in a specific slot.

[QCL, TCI state]

In a wireless communication system, one or more different antenna ports (or one or more channels, signals, and combinations thereof may be replaced, but in the future description of the present disclosure, for convenience, different antenna ports will be collectively referred to) They can be associated with each other by setting Quasi co-location (QCL) as shown in [Table 10] below. The TCI state is for notifying/indicating the QCL relationship between a PDCCH (or PDCCH DMRS) and another RS or channel, a certain reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) is mutually QCLed (QCLed) means that the terminal is permitted to apply some or all of the large-scale channel parameters estimated from the antenna port A to channel measurement from the antenna port B. QCL is 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) RRM (radio resource management) affected by average gain, 4) spatial parameter It may be necessary to associate different parameters depending on circumstances such as affected beam management (BM). Accordingly, NR supports four types of QCL relationships as shown in Table 11 below.

QCL type Large-scale characteristics A Doppler shift, Doppler spread, average delay, delay spread B Doppler shift, Doppler spread C Doppler shift, average delay D Spatial Rx parameter

The spatial RX parameter includes various parameters such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit/receive channel correlation, transmit/receive beamforming, and spatial channel correlation. Some or all of them may be generically named.

The QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 12 below. Referring to Table 12 below, the base station sets one or more TCI states to the UE and informs the UE of up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS referring to the TCI state ID, that is, the target RS. have. At this time, each QCL information (QCL-Info) included in each of the TCI states includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 11 above. do.

TCI-State ::= SEQUENCE {
tci-StateId TCI-StateId,
(ID of the TCI state)
qcl-Type1 QCL-Info;
(QCL information of the first reference RS of RS (target RS) referring to the corresponding TCI state ID)
qcl-Type2 QCL-Info OPTIONAL, -- Need R
(QCL information of the second reference RS of RS (target RS) referring to the corresponding TCI state ID)
...
}

QCL-Info ::= SEQUENCE {
cell ServCellIndex OPTIONAL, -- Need R
(The serving cell index of the reference RS indicated by the corresponding QCL information)
bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated
(BWP index of the reference RS indicated by the corresponding QCL information)
referenceSignal CHOICE {
csi-rs NZP-CSI-RS-ResourceId,
ssb SSB-Index
(either CSI-RS ID or SSB ID indicated by the corresponding QCL information)
},
qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},
...
}

6 is a diagram illustrating an example of base station beam allocation according to TCI state setting. Referring to FIG. 6, the base station may deliver information on different N beams to the terminal through different N TCI states. For example, as shown in FIG. 6, when N = 3, the base station determines that the qcl-Type2 parameters included in the three TCI states (600, 605, and 610) are related to CSI-RS or SSB corresponding to different beams, and the QCL type By setting it to D, it is possible to notify/indicate that antenna ports referring to the different TCI states 600, 605, or 610 are associated with different spatial Rx parameters, that is, different beams.

Tables 13 to 17 below show valid TCI state settings according to the type of target antenna port.

Table 13 below shows valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). The TRS means a NZP (Non-Zero-Power) CSI-RS in which the repetition parameter is not set among CSI-RSs and trs-Info is set to true in the configuration information exemplified in [Table 18] and [Table 19] below. . In the case of setting No. 3 in Table 13, it can be used for aperiodic TRS.

Table 14 below shows valid TCI state settings when the target antenna port is CSI-RS for CSI. The CSI-RS for CSI refers to an NZP CSI-RS in which a parameter indicating repetition (eg, a repetition parameter) is not set among CSI-RSs and the trs-Info is not set to true.

Table 15 below shows valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, CSI-RS for L1 Reference Signal Received Power (RSRP) reporting). The CSI-RS for BM means an NZP CSI-RS in which the repetition parameter is set among CSI-RSs and has a value of On or Off, and the trs-Info is not set to true.

Table 16 below shows valid TCI state settings when the target antenna port is PDCCH DMRS.

Table 17 below shows valid TCI state settings when the target antenna port is PDSCH DMRS.

In the representative QCL setting method according to Tables 13 to 17, the target antenna port and reference antenna port for each step are "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS" is set and operated. Through this, it is possible to help the reception operation of the terminal by linking the statistical characteristics measurable from the SSB and TRS to each antenna port.

For configuration information of trs-Info related to the NZP CSI-RS, refer to [Table 18] and [Table 1-9] below.

[PDCCH: related to TCI state]

Specifically, TCI state combinations applicable to PDCCH DMRS antenna ports are shown in Table 20 below. In Table 20, the fourth row is a combination assumed by the UE before RRC configuration, and it is impossible to configure after RRC configuration.

Valid TCI
state Configuration DL RS 1 qcl-Type1 DL RS 2
(if configured) qcl-Type2
(if configured) One TRS QCL-TypeA TRS QCL-TypeD 2 TRS QCL-TypeA CSI-RS (BM) QCL-TypeD 3 CSI-RS (CSI) QCL-TypeA 4 SS/PBCH Block QCL-TypeA SS/PBCH Block QCL-TypeD

In NR, a hierarchical signaling method as shown in FIG. 8 is supported for dynamic allocation of PDCCH beams.

7 is a diagram illustrating an example of a TCI state allocation method for a PDCCH in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 7, the base station can set N TCI states (705, 710, ..., 720) to the terminal through RRC signaling 700, and some of them can be set as TCI states for CORESET. (725). Thereafter, the base station may instruct the terminal of one of the TCI states (730, 735, 740) for CORESET through MAC CE (MAC Control Element) signaling (745). Thereafter, the UE receives the PDCCH based on beam information included in the TCI state indicated by the MAC CE signaling.

8 is a diagram illustrating a TCI indication MAC CE signaling structure for PDCCH DMRS in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 8, the TCI indication MAC CE signaling for the PDCCH DMRS is composed of, for example, 2 bytes (16 bits) (Oct1 800, Oct2 805), 5-bit serving cell ID (815), 4-bit CORESET ID 820 and a 7-bit TCI state ID 825.

9 is a diagram illustrating an example of beam configuration of a control resource set (CORESET) and a search space (search space) in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 9, the base station may instruct the terminal one of the TCI state lists included in the CORESET 900 configuration through MAC CE signaling (905). Thereafter, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal connects to the CORESET, for example, one or more search spaces #1, #2, and #3 (910, 915, 920) It is considered that the same QCL information (beam #1, 905) is applied to all. In the PDCCH beam allocation method described above, it is difficult to indicate a beam change faster than the MAC CE signaling delay, and since the same beam is collectively applied to each CORESET regardless of search space characteristics, flexible PDCCH beam operation can be difficult.

Hereinafter, embodiments of the present disclosure provide a more flexible PDCCH beam configuration and operation method. Hereinafter, in describing the embodiments of the present disclosure, several distinct examples are provided for convenience of explanation, but the illustrated embodiments are not mutually exclusive, and two or more embodiments may be appropriately combined and applied according to circumstances.

The base station may set one or a plurality of TCI states for a specific control resource set to the terminal, and may activate one of the set TCI states through a MAC CE activation command. For example, {TCI state#0, TCI state#1, TCI state#2} are set as TCI states in control resource set #1, and the base station sets TCI state for control resource set #1 through MAC CE. A command enabling to assume TCI state#0 may be transmitted to the terminal. The UE can correctly receive the DMRS of the corresponding control resource set based on the QCL information in the activated TCI state based on the activation command for the TCI state received through the MAC CE.

Regarding the control resource set (control resource set #0) whose index is set to 0, if the terminal does not receive the MAC CE activation command for the TCI state of the control resource set #0, the terminal transmits from the control resource set #0 It can be assumed that the SS/PBCH block (SSB) and QCL identified during the initial access process or the non-contention based random access process that is not triggered by the PDCCH command for the DMRS to be QCL.

Regarding the control resource set (control resource set #X) whose index is set to a value other than 0, if the terminal has not received the TCI state for the control resource set #X, or has set one or more TCI states, but one of them If the MAC CE activation command for activating is not received, the terminal may assume that the SS/PBCH block identified in the initial access process is QCL with respect to the DMRS transmitted in the control resource set #X.

[PDCCH: related to QCL prioritization rule]

In the following, the QCL priority determination operation for the PDCCH will be described in detail.

The UE operates with carrier aggregation within a single cell or band, and a plurality of control resource sets existing within an activated bandwidth portion within a single cell or multiple cells have the same or different QCL-TypeD characteristics in a specific PDCCH monitoring interval, and In case of overlapping, the terminal may select a specific control resource set according to the QCL priority determination operation and monitor control resource sets having the same QCL-TypeD characteristics as the corresponding control resource set. That is, when a plurality of control resource sets overlap in time, only one QCL-TypeD characteristic can be received. In this case, the criteria for determining the QCL priority may be as follows.

- Criterion 1. A control resource set connected to the common search section of the lowest index within a cell corresponding to the lowest index among cells including a common search section.

- Criterion 2. A control resource set associated with a UE-specific search interval having the lowest index within a cell corresponding to the lowest index among cells including a UE-specific search interval.

As described above, each of the above criteria applies the next criterion when the criterion is not satisfied. For example, when control resource sets overlap in time in a specific PDCCH monitoring period, if all control resource sets are not connected to a common search period but connected to a terminal-specific search period, that is, if criterion 1 is not satisfied, the terminal may omit the application of criterion 1 and apply criterion 2.

When selecting a control resource set based on the above criteria, the terminal may additionally consider the following two items for QCL information set in the control resource set. First, if control resource set 1 has CSI-RS 1 as a reference signal having a QCL-TypeD relationship, and this CSI-RS 1 has SSB 1 as a reference signal having a QCL-TypeD relationship, another If the reference signal with which control resource set 2 has a QCL-TypeD relationship is SSB 1, the UE may consider these two control resource sets 1 and 2 to have different QCL-TypeD characteristics. Second, if control resource set 1 has CSI-RS 1 set in cell 1 as a reference signal having a QCL-TypeD relationship, and this CSI-RS 1 has a QCL-TypeD relationship, the reference signal is SSB 1, control resource set 2 has CSI-RS 2 configured in cell 2 as a reference signal having a QCL-TypeD relationship, and this CSI-RS 2 has the same reference signal having a QCL-TypeD relationship. In the case of SSB 1, the UE may consider the two control resource sets to have the same QCL-TypeD characteristics.

10A and 10B are diagrams for explaining a method of selecting a receivable control resource set in consideration of priority when a terminal receives a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

For example, a UE may be configured to receive a plurality of control resource sets overlapping in time in a specific PDCCH monitoring period 1010, and these plurality of control resource sets are a common search space or a UE-specific search space for a plurality of cells. may be connected with Within the corresponding PDCCH monitoring period, the first control resource set 1015 connected to the first common search period may exist within the first bandwidth portion 1000 of the first cell, and the first bandwidth portion of the second cell (1005 ), the first control resource set 1020 connected to the first common search period and the second control resource set 1025 connected to the second terminal-specific search period may exist. The control resource sets 1015 and 1020 have a relationship of CSI-RS resource No. 1 and QCL-TypeD set within the bandwidth part No. 1 of cell No. 1, and the control resource set 1025 is the bandwidth No. 1 of cell No. 2 It may have a relationship between CSI-RS resource No. 1 set in the part and QCL-TypeD. Therefore, if criterion 1 is applied to the corresponding PDCCH monitoring period 1010, all other control resource sets having QCL-TypeD reference signals such as the first control resource set 1015 can be received. Therefore, the UE can receive the control resource sets 1015 and 1020 in the corresponding PDCCH monitoring period 1010.

As another example, a UE may be set to receive a plurality of control resource sets overlapping in time in a specific PDCCH monitoring period 1040, and the plurality of control resource sets may be configured to receive a common search space for a plurality of cells or to be specific to a UE. It may be related to the search space. Within the corresponding PDCCH monitoring interval, within the first bandwidth part 1030 of cell #1, the first control resource set 1045 connected to the UE 1 specific search interval and the second control resource set connected to the UE 2 specific search interval 1050 may exist, and within the bandwidth part 1 1035 of cell 2, the first control resource set 1055 connected to the UE 1 specific search interval and the second control resource connected to the UE 3 specific search interval A set 1060 may exist. Control resource sets 1045 and 1050 have a relationship of CSI-RS resource No. 1 and QCL-TypeD set in the bandwidth part No. 1 of cell No. 1, and control resource set 1055 is bandwidth No. 1 of cell No. 2 It has a QCL-TypeD relationship with the first CSI-RS resource set in the second cell, and the control resource set 1060 may have a QCL-TypeD relationship with the second CSI-RS resource set in the first bandwidth portion of the second cell. have. However, when criterion 1 is applied to the corresponding PDCCH monitoring period 1040, since there is no common search period, criterion 2, which is the next criterion, can be applied. If criterion 2 is applied to the corresponding PDCCH monitoring period 1040, all other control resource sets having the same QCL-TypeD reference signal as the control resource set 1045 can be received. Accordingly, the UE can receive control resource sets 1045 and 1050 in the corresponding PDCCH monitoring period 1040.

11 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 11, resource allocation (RA) type 0 (1100), RA type 1 (1105), and dynamic switch of resource allocation (RA type 0, RA type 1) that can be set through higher layer signaling The three frequency axis resource allocation methods of 1110 are illustrated. If the terminal is set to use only RA type 0 (1100) through higher layer signaling, some downlink control information (DCI) for allocating the PDSCH to the corresponding terminal is a bitmap consisting of N _RBG bits (1115 ). In this case, the N _RBG means the number of resource block groups (RBGs) determined as shown in [Table 21] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and the bitmap Data is transmitted to the RBG indicated by 1 by

개의 비트들로 구성되는 주파수 축 자원 할당 정보를 포함한다. 상기 N^DL,BWP _RB는 하향링크 대역폭부분(BWP)의 RB 수이다. 기지국은 이를 통하여 starting VRB(1120)와 이로부터 연속적으로 할당되는 주파수 축 자원의 길이(1125)를 설정할 수 있다.If the terminal is configured to use only RA type 1 1105 through higher layer signaling, some DCIs allocating the PDSCH to the terminal

and frequency-axis resource allocation information consisting of N bits. The N ^DL,BWP _RB is the number of RBs in the downlink bandwidth part (BWP). Through this, the base station can set the starting VRB 1120 and the length 1125 of frequency axis resources continuously allocated therefrom.

If the terminal is configured to use both RA type 0 and RA type 1 through higher layer signaling (1110), some DCIs that allocate a PDSCH to the corresponding terminal use a payload for configuring RA type 0 and RA type 1 It includes frequency axis resource allocation information consisting of bits of a large value (1135) among payloads to be set. At this time, one bit 1130 may be added to the first part (MSB) of the frequency axis resource allocation information in the DCI to indicate the use of RA type 0 or RA type 1. For example, if the corresponding bit 1130 has a value of '0', it may indicate that RA type 0 is used, and if it has a value of '1', it may indicate that RA type 1 is used.

[PUCCH: transmission related]

In the NR system, a UE may transmit uplink control information (UCI) to a base station through a physical uplink control channel (PUCCH). Control information includes HARQ-ACK indicating successful demodulation/decoding of the TB (transport block) received by the UE through PDSCH, and SR (scheduling request) requesting resource allocation from the PUSCH base station for uplink data transmission by the UE. At least one of channel state information (CSI), which is information for reporting the channel state of the terminal, may be included.

PUCCH resources can be largely divided into long PUCCH and short PUCCH according to the length of the allocated symbol. In the NR system, the long PUCCH has a length of 4 symbols or more in a slot, and the short PUCCH has a length of 2 symbols or less in a slot.

More specifically, the long PUCCH can be used for the purpose of improving uplink cell coverage, and therefore can be transmitted in a single carrier DFT-S-OFDM scheme rather than OFDM transmission. Long PUCCH supports transport formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4 depending on the number of supportable control information bits and whether or not UE multiplexing through Pre-DFT OCC support is supported at the front end of IFFT.

First, PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format capable of supporting control information of up to 2 bits, and uses frequency resources as much as 1 RB. Control information may consist of a combination of HARQ-ACK and SR or each of them. PUCCH format 1 is composed of an OFDM symbol including a demodulation reference signal (DMRS), which is a demodulation reference signal (or reference signal), and an OFDM symbol including UCI.

)를 이용하여 확산되고, IFFT 수행 후 전송될 수 있다. For example, if the number of transmission symbols of PUCCH format 1 is 8 symbols, it consists of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol in order from the first start symbol of 8 symbols. It can be. A DMRS symbol is an orthogonal code (or orthogonal sequence or spreading code,

), and can be transmitted after performing IFFT.

))을 이용하여 확산시키고 IFFT 수행 후 전송될 수 있다. For the UCI symbol, the terminal generates d(0) by modulating 1-bit control information with BPSK and 2-bit control information with QPSK, and scrambling by multiplying the generated d(0) by a sequence corresponding to a length of 1 RB in the frequency axis, , orthogonal code (or orthogonal sequence or spreading code,

)) and can be transmitted after performing IFFT.

The terminal generates a sequence based on the group hopping or sequence hopping set by higher layer signaling from the base station and the set ID, and cyclic shifts the generated sequence with the initial CS (cyclic shift) value set as the upper signal to obtain a length of 1 RB. Create the corresponding sequence.

은 스프레딩 부호의 길이(N_SF)가 주어지면

와 같이 결정되며, 구체적으로 다음 [표 22]과 같이 주어진다. i는 스프레딩 부호 그 자체의 인덱스를 의미하며, m은 스프레딩 부호의 element들의 인덱스를 의미한다. 여기서 [표 22] 내에 [ ]안의 숫자들은 을 의미하며, 가령 스프레딩 부호의 길이가 2이고, 설정된 스프레딩 부호의 인덱스 i=0인 경우, 스프레딩 부호

은

,

이 되어서

=[1 1]이 된다.

Given the length of the spreading code (N _SF )

It is determined as follows, and is specifically given as in the following [Table 22]. i means the index of the spreading code itself, and m means the index of elements of the spreading code. Here, the numbers in [ ] in [Table 22] mean . For example, if the length of the spreading code is 2 and the index i of the set spreading code is 0, the spreading code

silver

,

become

=[1 1].

Next, PUCCH format 3 is a DFT-S-OFDM-based long PUCCH format capable of supporting control information of more than 2 bits, and the number of RBs used can be set through a higher layer. Control information may be composed of a combination or each of HARQ-ACK, SR, and CSI. In PUCCH format 3, the DMRS symbol position is presented in the following [Table 23] according to whether frequency hopping is performed within a slot and whether an additional DMRS symbol is configured.

For example, when the number of transmission symbols of PUCCH format 3 is 8 symbols, the first start symbol of the 8 symbols starts with 0, and the DMRS is transmitted on the 1st symbol and the 5th symbol. [Table 17] is also applied to the DMRS symbol position of PUCCH format 4 in the same way.

Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM that can support control information of more than 2 bits, and uses frequency resources as much as 1 RB. Control information may be composed of a combination or each of HARQ-ACK, SR, and CSI. PUCCH format 4 is different from PUCCH format 3 in that PUCCH format 4 can multiplex PUCCH format 4 of several UEs within one RB. It is possible to multiplex PUCCH format 4 of multiple terminals by applying Pre-DFT Orthogonal Cover Code (OCC) to control information in the front end of the IFFT. However, the number of transmittable control information symbols of one terminal is reduced according to the number of multiplexed terminals. The number of multiplexable terminals, that is, the number of different OCCs available may be 2 or 4, and the number of OCCs and the OCC index to be applied may be configured through a higher layer.

Next, short PUCCH will be described. Short PUCCH can be transmitted in both a downlink centric slot and an uplink centric slot, and is generally the last symbol of a slot or an OFDM symbol at the end (e.g., the last OFDM symbol or It can be transmitted in the second-to-last OFDM symbol or the last 2 OFDM symbols). Of course, it is also possible to transmit a short PUCCH at an arbitrary position within a slot. And, Short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. Short PUCCH can be used to reduce delay time compared to long PUCCH in a situation where uplink cell coverage is good and can be transmitted in CP-OFDM.

Short PUCCH may support transmission formats such as PUCCH format 0 and PUCCH format 2 according to the number of supportable control information bits. First, PUCCH format 0 is a short PUCCH format capable of supporting control information of up to 2 bits, and uses frequency resources as much as 1 RB. Control information may consist of a combination of HARQ-ACK and SR or each of them. PUCCH format 0 has a structure in which DMRS is not transmitted and only sequences mapped to 12 subcarriers in a frequency axis are transmitted within one OFDM symbol. The terminal generates a sequence based on the group hopping or sequence hopping set as the upper signal from the base station and the set ID, and adds another CS value according to whether it is ACK or NACK to the indicated initial CS (cyclic shift) value. Final CS value The generated sequence may be cyclically shifted, mapped to 12 subcarriers, and transmitted.

For example, when the HARQ-ACK is 1 bit, the terminal generates the final CS by adding 6 to the initial CS value if it is ACK, and adds 0 to the initial CS if it is NACK to generate the final CS, as shown in Table 24 below. have. A CS value of 0 for NACK and a CS value of 6 for ACK are defined in the standard, and the UE can generate PUCCH format 0 according to the value defined in the standard and transmit 1-bit HARQ-ACK.

For example, when HARQ-ACK is 2 bits, the UE adds 0 to the initial CS value if it is (NACK, NACK), adds 3 to the initial CS value if it is (NACK, ACK), and (ACK , ACK), 6 is added to the initial CS value, and if (ACK, NACK), 9 is added to the initial CS value. A CS value of 0 for (NACK, NACK), a CS value of 3 for (NACK, ACK), a CS value of 6 for (ACK, ACK), and a CS value of 9 for (ACK, NACK) are defined in the standard. can generate PUCCH format 0 according to the value defined in the standard and transmit 2-bit HARQ-ACK. When the final CS value exceeds 12 due to the CS value added according to the ACK or NACK to the initial CS value, since the length of the sequence is 12, modulo 12 can be applied to the final CS value.

Next, PUCCH format 2 is a short PUCCH format supporting control information of more than 2 bits, and the number of RBs used can be set through a higher layer. Control information may be composed of a combination or each of HARQ-ACK, SR, and CSI. When the index of the first subcarrier is #0, in PUCCH format 2, the position of the subcarriers on which the DMRS is transmitted within one OFDM symbol corresponds to the subcarriers with indexes #1, #4, #7, and #10. can be fixed The control information may be mapped to subcarriers other than the subcarrier where the DMRS is located through a modulation process after channel coding.

In summary, values and ranges that can be set for each PUCCH format described above can be summarized as shown in [Table 26] below. In [Table 26] below, if a value does not need to be set, it is marked with N.A.

Meanwhile, to improve uplink coverage, multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be set for each PUCCH format. The UE may perform repetitive transmission on PUCCH including UCI as many times as the number of slots set through nrofSlots, which is higher layer signaling. For repetitive PUCCH transmission, PUCCH transmission in each slot is performed using the same number of consecutive symbols, and the corresponding number of consecutive symbols is determined through nrofSymbols in PUCCH-format1, PUCCH-format3, or PUCCH-format4, which is higher layer signaling. can be set. For repetitive PUCCH transmission, PUCCH transmission in each slot is performed using the same start symbol, and the corresponding start symbol is set through startingSymbolIndex in PUCCH-format 1, PUCCH-format 3, or PUCCH-format 4, which is higher layer signaling. can For repeated PUCCH transmission, a single PUCCH-spatialRelationInfo may be configured for a single PUCCH resource. Regarding repeated PUCCH transmission, if the terminal is set to perform frequency hopping in PUCCH transmission in different slots, the terminal may perform frequency hopping in units of slots. In addition, if the terminal is set to perform frequency hopping in PUCCH transmission in different slots, the terminal starts PUCCH transmission from the first PRB index set through startingPRB, which is upper layer signaling, in the even slot, and In the second slot, PUCCH transmission can be started from the second PRB index set through secondHopPRB, which is higher layer signaling. Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmission in different slots, the index of the slot in which the first PUCCH transmission is instructed to the terminal is 0, and for the total number of repeated PUCCH transmissions configured, each slot In , the value of the number of repeated PUCCH transmissions may be increased regardless of PUCCH transmission performance. If the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE does not expect frequency hopping within the slot to be configured during PUCCH transmission. If the terminal is not configured to perform frequency hopping in PUCCH transmission in different slots and is configured to perform frequency hopping within a slot, the first and second PRB indexes may be equally applied within the slot. If the number of uplink symbols capable of transmitting PUCCH is smaller than nrofSymbols configured in higher layer signaling, the UE may not transmit PUCCH. Even if the UE fails to transmit the PUCCH for some reason in a certain slot during repeated PUCCH transmission, the UE can increase the number of repeated PUCCH transmissions.

[PUCCH: PUCCH resource setting]

Next, the PUCCH resource configuration of the base station or terminal will be described. The base station may be able to configure PUCCH resources for each BWP through a higher layer for a specific terminal. PUCCH resource configuration may be as shown in [Table 27].

PUCCH-Config ::= SEQUENCE {
resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N
resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N
resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N
resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N
format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig
OPTIONAL, -- Need N
schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId
OPTIONAL, -- Need N
multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M
dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M
spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo
OPTIONAL, -- Need N
spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId
OPTIONAL, -- Need N
pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M
...,
[[
resourceToAddModListExt-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-r16 OPTIONAL, -- Need N
dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, -- Need M
ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16 } OPTIONAL, -- Need M
subslotLengthForPUCCH-r16 CHOICE {
normalCP-r16 ENUMERATED {n2,n7},
extendedCP-r16 ENUMERATED {n2,n6}
} OPTIONAL, -- Need R
dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need M
numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R
dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK
spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo
OPTIONAL, -- Need N
spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId
OPTIONAL, -- Need N
spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16
OPTIONAL, -- Need N
spatialRelationInfoToReleaseListExt-v1610 SEQUENCE(SIZE(1..maxNrofSpatialRelationInfos-r16)) OF
PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N
resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16
OPTIONAL, -- Need N
resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16
OPTIONAL, -- Need N
sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M
schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610
OPTIONAL -- Need N
]]
}

According to [Table 27], one or multiple PUCCH resource sets may be set in the PUCCH resource configuration for a specific BWP, and a maximum payload value for UCI transmission may be set in some of the PUCCH resource sets. One or multiple PUCCH resources may belong to each PUCCH resource set, and each PUCCH resource may belong to one of the aforementioned PUCCH formats.

Regarding the PUCCH resource set, the maximum payload value of the first PUCCH resource set may be fixed to 2 bits. Accordingly, the corresponding value may not be separately set through an upper layer or the like. When the remaining PUCCH resource sets are configured, the index of the corresponding PUCCH resource set may be set in ascending order according to the maximum payload value, and the maximum payload value may not be set in the last PUCCH resource set. Higher layer configuration for PUCCH resource set may be as shown in [Table 28].

PUCCH-ResourceSet ::= SEQUENCE {
pucch-ResourceSetId PUCCH-ResourceSetId,
resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,
maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R
}

The resourceList parameter of [Table 28] may include IDs of PUCCH resources belonging to the PUCCH resource set.

If the PUCCH resource set is not set during initial access or if the PUCCH resource set is not set, a PUCCH resource set configured with a plurality of cell-specific PUCCH resources as shown in [Table 29] may be used in the initial BWP. A PUCCH resource to be used for initial access within this PUCCH resource set may be indicated through SIB1.

The maximum payload of each PUCCH resource included in the PUCCH resource set may be 2 bits in the case of PUCCH format 0 or 1, and may be determined by the symbol length, the number of PRBs, and the maximum code rate in the case of the remaining formats. The symbol length and the number of PRBs may be set for each PUCCH resource, and the maximum code rate may be set for each PUCCH format.

Next, PUCCH resource selection for UCI transmission will be described. In the case of SR transmission, the PUCCH resource for the SR corresponding to the schedulingRequestID can be configured through higher layers as shown in [Table 30] below. A PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.

SchedulingRequestResourceConfig ::= SEQUENCE {
schedulingRequestResourceId SchedulingRequestResourceId,
schedulingRequestID SchedulingRequestId,
periodicityAndOffset CHOICE {
sym2 NULL,
sym6or7 NULL,
sl1 NULL, -- Recurs in every slot
sl2 INTEGER (0..1),
sl4 INTEGER (0..3),
sl5 INTEGER (0..4),
sl8 INTEGER (0..7),
sl10 INTEGER (0..9),
sl16 INTEGER (0..15),
sl20 INTEGER (0..19),
sl40 INTEGER (0..39),
sl80 INTEGER (0..79),
sl160 INTEGER (0..159),
sl320 INTEGER (0..319),
sl640 INTEGER (0..639)
} OPTIONAL, -- Need M
resource PUCCH-ResourceId OPTIONAL -- Need M
}

The set PUCCH resource may have a transmission period and offset set through the periodicityAndOffset parameter of [Table 24]. If there is uplink data to be transmitted by the terminal at the time corresponding to the set period and offset, the corresponding PUCCH resource is transmitted, and otherwise, the corresponding PUCCH resource may not be transmitted.

In the case of CSI transmission, a PUCCH resource to transmit a periodic or semi-persistent CSI report through PUCCH may be set in the pucch-CSI-ResourceList parameter as shown in Table 31 below. The pucch-CSI-ResourceList parameter may include a list of PUCCH resources for each BWP for a cell or CC to transmit a corresponding CSI report. The PUCCH resource may be a resource belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. The transmission period and offset of the PUCCH resource may be set through reportSlotConfig of [Table 31].

CSI-ReportConfig ::= SEQUENCE {
reportConfigId CSI-ReportConfigId,
carrier ServCellIndex OPTIONAL, -- Need S
...
reportConfigType CHOICE {
periodic SEQUENCE {
reportSlotConfig CSI-ReportPeriodicityAndOffset,
pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
},
semiPersistentOnPUCCH SEQUENCE {
reportSlotConfig CSI-ReportPeriodicityAndOffset,
pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
},
semiPersistentOnPUSCH SEQUENCE {
reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},
reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),
p0alpha P0-PUSCH-AlphaSetId
},
aperiodic SEQUENCE {
reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)
}
},
...
}

In the case of HARQ-ACK transmission, a resource set of PUCCH resources to be transmitted may be selected first according to the payload of UCI including the corresponding HARQ-ACK. That is, a PUCCH resource set having a minimum payload not smaller than the UCI payload may be selected. Next, the PUCCH resource in the PUCCH resource set can be selected through the PUCCH resource indicator (PRI) in the DCI that scheduled the TB corresponding to the HARQ-ACK, and the PRI is the PUCCH resource specified in [Table 6] or [Table 7] may be an indicator. The relationship between the PRI and the PUCCH resource selected from the PUCCH resource set may be as shown in [Table 32].

If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resource may be selected by the following equation.

는 PUCCH resource set 내 선택된 PUCCH resource의 인덱스,

는 PUCCH resource set에 속한 PUCCH resource의 개수,

는 PRI 값,

는 수신 DCI가 속한 CORESET p의 총 CCE 수,

는 수신 DCI에 대한 첫번째 CCE 인덱스를 나타낸다.In [Equation 2]

Is the index of the selected PUCCH resource in the PUCCH resource set,

Is the number of PUCCH resources belonging to the PUCCH resource set,

is the PRI value,

is the total number of CCEs of CORESET p to which the receiving DCI belongs,

represents the first CCE index for the received DCI.

슬롯 이후이다.

값의 후보는 상위 레이어로 설정되며, 보다 구체적으로 [표 27]에 명시된 PUCCH-Config 내 dl-DataToUL-ACK 파라미터에 설정될 수 있다. 이들 후보 중 하나의

값이 TB를 스케줄하는 DCI 내 PDSCH-to-HARQ feedback timing indicator에 의해 선택될 수 있으며 이 값은 [표 5] 또는 [표 6]에 명시된 값일 수 있다. 한편,

값의 단위는 슬롯 단위이거나 서브슬롯 단위일 수 있다. 여기서 서브슬롯이란 슬롯보다 작은 길이의 단위로서 하나 또는 복수개의 심볼이 하나의 서브슬롯을 구성할 수 있다.The point at which the corresponding PUCCH resource is transmitted is from TB transmission corresponding to the corresponding HARQ-ACK.

after the slot

Value candidates are set in higher layers, and more specifically, they can be set in the dl-DataToUL-ACK parameter in PUCCH-Config specified in [Table 27]. one of these candidates

A value may be selected by a PDSCH-to-HARQ feedback timing indicator in DCI scheduling TB, and this value may be a value specified in [Table 5] or [Table 6]. Meanwhile,

The value unit may be a slot unit or a subslot unit. Here, a subslot is a unit of length smaller than a slot, and one or a plurality of symbols may constitute one subslot.

Next, a case in which two or more PUCCH resources are located in one slot will be described. When a UE can transmit UCI through one or two PUCCH resources in one slot or subslot, and UCI is transmitted through two PUCCH resources in one slot/subslot, i) each PUCCH resource does not overlap on a symbol basis, ii) At least one PUCCH resource may be a short PUCCH. Meanwhile, the UE may not expect to transmit a plurality of PUCCH resources for HARQ-ACK transmission within one slot.

[PUCCH: related to transmit beam]

슬롯 이후 처음 등장하는 슬롯부터 MAC CE를 통한 pucch-spatialRelationInfoID 활성화를 적용할 수 있다. μ는 PUCCH 전송에 적용되는 뉴머롤로지이고,

는 주어진 뉴머롤로지에서 서브프레임 당 슬롯의 개수를 의미한다. pucch-spatialRelationInfo에 대한 상위 레이어 구성은 다음의 [표 33]와 같을 수 있다.Next, configuration of an uplink transmission beam to be used for PUCCH transmission will be described. If the UE does not have a dedicated PUCCH resource configuration for PUCCH resource configuration, the PUCCH resource set is provided through higher layer signaling, pucch-ResourceCommon, and in this case, beam configuration for PUCCH transmission is Random Access It follows the beam configuration used in PUSCH transmission scheduled through the Response (RAR) UL grant. If the UE has a dedicated PUCCH resource configuration for PUCCH resource configuration, beam configuration for PUCCH transmission may be provided through upper signaling pucch-spatialRelationInfoId included in [Table 27]. If the UE is configured with one pucch-spatialRelationInfoId, beam configuration for PUCCH transmission of the UE may be provided through one pucch-spatialRelationInfoId. If the terminal is configured with a plurality of pucch-spatialRelationInfoIDs, the terminal may be instructed to activate one of the plurality of pucch-spatialRelationInfoIDs through a MAC control element (CE). The terminal may receive a maximum of 8 pucch-spatialRelationInfoIDs through higher signaling, and may be instructed to activate only one pucch-spatialRelationInfoID among them. When the terminal is instructed to activate a certain pucch-spatialRelationInfoID through the MAC CE, the terminal receives an HARQ-ACK transmission for the PDSCH through which the MAC CE containing the activation information for the pucch-spatialRelationInfoID is transmitted.

Activation of pucch-spatialRelationInfoID through MAC CE can be applied from the first slot after the slot. μ is a numerology applied to PUCCH transmission,

Means the number of slots per subframe in a given numerology. The upper layer configuration for pucch-spatialRelationInfo can be as shown in [Table 33].

PUCCH-SpatialRelationInfo ::= SEQUENCE {
pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId,
servingCellId ServCellIndex OPTIONAL, -- Need S
referenceSignal CHOICE {
ssb-Index SSB-Index,
csi-RS-Index NZP-CSI-RS-ResourceId,
srs PUCCH-SRS
},
pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,
p0-PUCCH-Id P0-PUCCH-Id,
closedLoopIndex ENUMERATED { i0, i1 }
}

PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos)

According to [Table 33], one referenceSignal setting may exist within a specific pucch-spatialRelationInfo setting, and the corresponding referenceSignal is an ssb-Index indicating a specific SS/PBCH, or a csi-RS-Index indicating a specific CSI-RS, Alternatively, it may be srs indicating a specific SRS. If referenceSignal is set to ssb-Index, the UE sets the beam used when receiving SS/PBCH corresponding to ssb-Index among SS/PBCHs in the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided A beam used when receiving SS/PBCH corresponding to ssb-Index among SS/PBCHs in a cell indicated by servingCellId can be set as a beam for pucch transmission. If referenceSignal is set to csi-RS-Index, the UE sets the beam used when receiving the CSI-RS corresponding to the csi-RS-Index among CSI-RSs in the same serving cell as the beam for PUCCH transmission, If servingCellId is provided, a beam used when receiving a CSI-RS corresponding to csi-RS-Index among CSI-RSs in a cell indicated by servingCellId can be set as a beam for pucch transmission. If referenceSignal is set to srs, the UE sets the transmission beam used when transmitting the SRS corresponding to the resource index provided as a higher signaling resource within the same serving cell and/or within the activated uplink BWP to the beam for PUCCH transmission Alternatively, if the servingCellID and/or uplinkBWP are provided, the transmission beam used when transmitting the SRS corresponding to the resource index provided through the higher signaling resource in the cell and/or uplink BWP indicated by the servingCellID and/or uplinkBWP is PUCCH transmission It can be set as a beam for One pucch-PathlossReferenceRS-Id setting may exist within a specific pucch-spatialRelationInfo setting. The PUCCH-PathlossReferenceRS in [Table 34] can be mapped with the pucch-PathlossReferenceRS-Id in [Table 33], and up to 4 can be set through pathlossReferenceRSs in the upper signaling PUCCH-PowerControl in [Table 34]. PUCCH-PathlossReferenceRS can be configured with ssb-Index if connected to SS/PBCH through higher signaling referenceSignal, and can be configured with csi-RS-Index if connected with CSI-RS.

PUCCH-PowerControl ::= SEQUENCE {
deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, -- Need R
deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, -- Need R
deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, -- Need R
deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, -- Need R
deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, -- Need R
p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, -- Need M
pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS
OPTIONAL, -- Need M
twoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, -- Need S
...,
[[
pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610 } OPTIONAL -- Need M
]]
}

P0-PUCCH ::= SEQUENCE {
p0-PUCCH-Id P0-PUCCH-Id,
p0-PUCCH-Value INTEGER (-16..15)
}

P0-PUCCH-Id ::= INTEGER (1..8)

PathlossReferenceRSs-v1610 ::= SEQUENCE(SIZE(1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16

PUCCH-PathlossReferenceRS ::= SEQUENCE {
pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,
referenceSignal CHOICE {
ssb-Index SSB-Index,
csi-RS-Index NZP-CSI-RS-ResourceId
}
}

PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE {
pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610;
referenceSignal-r16 CHOICE {
ssb-Index-r16 SSB-Index,
csi-RS-Index-r16 NZP-CSI-RS-ResourceId
}
}

[PUCCH: Activate group-based spatial relationships]

In Rel-15, if a plurality of pucch-spatialRelationInfoIDs are configured, the UE may determine the spatial relationship of the corresponding PUCCH resource by receiving a MAC CE for activating the spatial relationship for each PUCCH resource. However, this method has a disadvantage in that it requires a lot of signaling overhead to activate the spatial relationship of a plurality of PUCCH resources. Therefore, Rel-16 introduces a new MAC CE for adding PUCCH resource groups and activating spatial relationships in units of PUCCH resource groups. A PUCCH resource group can set up to four PUCCH resource groups through resourceGroupToAddModList in [Table 27], and each PUCCH resource group can set a plurality of PUCCH resource IDs in one PUCCH resource group as a list as shown in [Table 35]. have.

PUCCH-ResourceGroup-r16 ::= SEQUENCE {
pucch-ResourceGroupId-r16 PUCCH-ResourceGroupId-r16,
resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId
}

PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16)

In Rel-16, the base station sets each PUCCH resource group to the terminal through the resourceGroupToAddModList in [Table 27] and the upper layer configuration in [Table 35], and the spatial relationship of all PUCCH resources in one PUCCH resource group is simultaneously You can configure the MAC CE to activate.

12 is a diagram illustrating an example of MAC CE for PUCCH resource group based spatial relationship activation in a wireless communication system according to an embodiment of the present disclosure.

Referring to the example of FIG. 12 , a supported cell ID 1210 and a bandwidth part ID 1220 to which a PUCCH resource to which a corresponding MAC CE is to be applied are set as Oct 1 1200 . PUCCH Resource IDs (1231, 1241) indicate IDs of PUCCH resources, and if the indicated PUCCH resources are included in a PUCCH resource group according to resourceGroupToAddModList, other PUCCH resource IDs within the same PUCCH resource group are not indicated in the same MAC CE and the same All PUCCH resources in the PUCCH resource group are activated with the same Spatial Relation Info ID (1236, 1246). At this time, Spatial Relation Info IDs (1236, 1246) include a value corresponding to PUCCH-SpatialRelationInfoId - 1 to be applied to the PUCCH resource group of [Table 27].

[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 semi-statically set through reception of configuredGrantConfig including rrc-ConfiguredUplinkGrant in [Table 36] through higher layer signaling without reception of the 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 in [Table 36] through upper signaling. When PUSCH transmission is operated by a configured grant, parameters applied to PUSCH transmission are dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided as push-Config in [Table 36] below, which are higher layer signaling. is applied through configuredGrantConfig, which is higher layer signaling in [Table 36]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is higher layer signaling in [Table 36], the terminal applies tp-pi2BPSK in push-Config in [Table 36] 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 can follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pushch-Config in [Table 37], which is higher layer 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 37] below, 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.

In this case, SRI may be given through a field SRS resource indicator in DCI or set through srs-ResourceIndicator, which is higher layer signaling. When transmitting codebook-based PUSCH, the terminal receives at least one SRS resource, and can receive 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 fields precoding information and number of layers in DCI, or may be set through precodingAndNumberOfLayers, which is higher layer 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 layer signaling. In codebook-based PUSCH transmission, a UE determines a codebook subset based on TPMI and codebookSubset in push-Config, which is higher layer signaling. CodebookSubset in push-Config, which is higher layer 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 higher layer 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 layer signaling, indicates two SRS antenna ports, the UE does not expect that the value of codebookSubset, which is higher layer signaling, is set to 'partialAndNonCoherent'.

The terminal may receive one SRS resource set in which the value of usage in the SRS-ResourceSet, which is higher layer signaling, is set to 'codebook', and one SRS resource in the corresponding SRS resource set may be indicated through SRI. If several SRS resources are set in an SRS resource set in which the usage value in the higher-level signaling SRS-ResourceSet is set to 'codebook', the UE determines that the value of nrofSRS-Ports in the higher-layer signaling SRS-Resource is the same for all SRS resources. Expect a value to be set.

The terminal transmits one or a plurality of 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 layer signaling, and the base station selects one of the SRS resources transmitted by the terminal and corresponds to the corresponding Instructs the UE to perform PUSCH transmission using the transmission beam information of the SRS 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 layer signaling, is set to 'nonCodebook', the UE uses one connected NZP (Non-Zero-Power) CSI-RS resource (non-zero power CSI-RS ) can be set. 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 layer 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 the associatedCSI-RS in the SRS-ResourceSet, which is higher layer signaling. For non-codebook based transmission, the UE does not expect spatialRelationInfo, which is higher layer signaling for SRS resource, and associatedCSI-RS in SRS-ResourceSet, which is higher layer signaling, to be configured 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 SRS-ResourceSet, which is higher layer 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 3] below.

[Equation 3]

2^-μ T_c + T_ext + T_switch, d_2,2 )T _proc,2 = max(( N ₂ + d _2,1 + d ₂ )( 2048 + 144 )

2 ^-μ T _c + T _ext + T _switch , d _2,2 )

Each variable in T _proc,2 of Equation 3 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 capability report of the UE, it has the value of [Table 38] below, and if it is reported as UE processing capability 2 and it is set through higher layer signaling that UE processing capability 2 can be used, the following [Table 38] 39].

-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-

:64

또는

중, T_proc,2이 더 크게 되는 값을 따른다.

은 PUSCH를 스케줄링 하는 DCI가 포함된 PDCCH가 전송되는 하향링크의 뉴머롤로지를 뜻하고,

은 PUSCH가 전송되는 상향링크의 뉴머롤로지를 뜻한다.- μ:

or

Of which, T _proc,2 follows the larger value.

denotes the numerology of the downlink through which the PDCCH including the DCI scheduling the PUSCH is transmitted,

denotes the numerology of the uplink through which the 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 repeated 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 position of the start symbol are determined by the time domain resource allocation method within one slot, and the base station determines the number of repeated transmissions through higher layer signaling (eg RRC signaling) or L1 signaling (For example, DCI) may notify the terminal.

- The terminal can repeatedly transmit an uplink data channel having the same start symbol as the length of the uplink data channel configured based on the number of repeated transmissions received from the base station in consecutive slots. 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 number of repetitions through higher layer signaling (eg, RRC signaling) or L1 signaling (eg, RRC signaling). For example, the UE may be notified through DCI).

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

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

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

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

는 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, and L represents the symbol length of the configured uplink data channel.

Represents a slot in which PUSCH transmission starts

Indicates 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.

13 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.

Referring to the example of FIG. 13, the terminal may set the start symbol S of the uplink data channel to 0, the length L of the uplink data channel to 14, and the number of repeated transmissions to 16. In this case, nominal repetition is indicated in 16 consecutive slots (1301). After that, the terminal may determine a symbol set as a downlink symbol in each nominal repetition 1301 as an invalid symbol. In addition, the terminal determines symbols set to 1 in invalid symbol pattern 1302 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 (1303).

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.

[Regarding device capability reporting]

In the LTE and NR systems, the terminal may perform a procedure for reporting the capability supported by the terminal to the corresponding base station while connected to the serving base station. In the description below, this is referred to as a UE capability report.

The base station may transmit a UE capability inquiry message requesting a capability report to a UE in a connected state. The message may include a UE capability request for each radio access technology (RAT) type of the base station. The request for each RAT type may include supported frequency band combination information. In addition, in the case of the terminal capability inquiry message, UE capabilities for each RAT type may be requested through one RRC message container transmitted by the base station, or the base station sends a terminal capability inquiry message including a terminal capability request for each RAT type. It can be included multiple times and delivered to the terminal. That is, in one message, the UE capability inquiry is repeated multiple times, and the UE can construct and report a corresponding UE capability information message multiple times. In the next-generation mobile communication system, a UE capability request for MR-DC (Multi-RAT dual connectivity) including NR, LTE, and EN-DC (E-UTRA-NR dual connectivity) can be requested. In addition, although the terminal capability inquiry message is generally initially transmitted after the terminal connects to the base station, the base station may request it under any condition when necessary.

As described above, the terminal receiving the UE capability report request from the base station configures the terminal capability according to the RAT type and band information requested from the base station. Examples of how the UE configures UE capabilities in the NR system are summarized below.

One. If the terminal receives a list of LTE and/or NR bands from the base station as a UE capability request, the terminal configures a band combination (BC) for EN-DC and NR stand alone (SA). That is, BC candidate lists for EN-DC and NR SA are configured based on the bands requested to the base station through FreqBandList. In addition, bands have priorities in the order described in FreqBandList.

2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag in the UE capability inquiry message, the UE selects NR SA BC from the candidate list of BCs configured above. about them is completely removed. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

3. Thereafter, the terminal removes fallback BCs from the configured BC candidate list. Here, the fallback BC means a BC that can be obtained by removing a band corresponding to at least one SCell from any BC, and since the BC before removing the band corresponding to at least one SCell can already cover the fallback BC, can be omitted. This step also applies to MR-DC, ie LTE bands as well. The remaining BCs after this step are the final "candidate BC list".

4. The terminal selects BCs to be reported by selecting BCs suitable for the requested RAT type from the final "candidate BC list". In this step, the terminal configures the supportedBandCombinationList in a predetermined order. That is, the terminal configures the BC and UE capabilities to be reported according to the order of the preset rat-Type. (nr -> eutra-nr -> eutra). In addition, featureSetCombination is configured for the configured supportedBandCombinationList, and a list of "candidate feature set combination" is configured in the candidate BC list from which the list for fallback BC (including capabilities of the same or lower level) is removed. The above "candidate feature set combination" includes both feature set combinations for NR and EUTRA-NR BC, and can be obtained from the feature set combination of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

5. In addition, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations is included in both containers of UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of NR includes only UE-NR-Capabilities.

After the terminal capabilities are configured, the terminal transmits a terminal capability information message including the terminal capabilities to the base station. Based on the terminal capabilities received from the terminal, the base station then performs appropriate scheduling and transmission/reception management for the corresponding terminal.

[CA/DC related]

14 is a diagram illustrating a radio protocol structure of a base station and a terminal in single cell 1410, carrier aggregation 1420, and dual connectivity 1430 situations according to an embodiment of the present disclosure.

Referring to FIG. 14, the wireless protocols of the next-generation wireless communication system are NR SDAP (Service Data Adaptation Protocol 1425 and 1470), NR PDCP (Packet Data Convergence Protocol 1430 and 1465), NR RLC (Radio Link Control) in the terminal and NR base station, respectively 1435 and 1460) and NR MAC (Medium Access Control 1440 and 1455) layers. In the following description, each layer device may be understood as a functional block in charge of the corresponding layer.

The main functions of the NR SDAPs 1425 and 1470 may include some of the following functions.

- Transfer of user plane data

- A mapping function between a QoS flow and a data bearer for uplink and downlink (mapping between a QoS flow and a DRB for both DL and UL)

- Marking function of QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

- Function to map reflective QoS flow to data bearer for UL SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

Regarding the SDAP layer device, the terminal may receive a RRC message to set whether to use the header of the SDAP layer device or the function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel, and SDAP header is set, the 1-bit NAS QoS reflection setting indicator (NAS reflective QoS) and the 1-bit AS QoS reflection setting indicator (AS reflective QoS) of the SDAP header allow the UE to send uplink and downlink QoS flows and data bearer mapping information can be instructed to update or reset. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority and scheduling information to support smooth service.

Main functions of the NR PDCPs 1430 and 1465 may include some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- PDCP PDU reordering for reception

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Ciphering and deciphering

- Timer-based SDU discard in uplink.

The NR PDCP reordering function refers to a function of rearranging PDCP PDUs received from a lower layer in order based on a PDCP SN (sequence number), and a function of transmitting data to the upper layer in the rearranged order. can do. Alternatively, the reordering of the NR PDCP may include a function of immediately forwarding without considering the order, and may include a function of reordering and recording lost PDCP PDUs, and the lost PDCP A function of reporting the status of PDUs to the transmitter may be included, and a function of requesting retransmission of lost PDCP PDUs may be included.

Main functions of the NR RLCs 1435 and 1460 may include some of the following functions.

- Transfer of upper layer PDUs

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection

- Error detection function (Protocol error detection)

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment

The NR RLC in-sequence delivery refers to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. In-sequence delivery of the NR RLC may include a function of reassembling and delivering the received RLC SDU when one RLC SDU is divided into several RLC SDUs. It may include a function of reordering based on RLC sequence number (SN) or PDCP sequence number (SN), and may include a function of reordering and recording lost RLC PDUs. A function of reporting the status to the transmitter may be included, and a function of requesting retransmission of lost RLC PDUs may be included. The in-sequence delivery function of the NR RLC may include, when there is a lost RLC SDU, a function of delivering only RLC SDUs prior to the lost RLC SDU to the upper layer in order, or Even if there are RLC SDUs, if a predetermined timer expires, a function of sequentially delivering all received RLC SDUs to an upper layer before the timer starts may be included. Alternatively, the in-sequence delivery function of the NR RLC device may include a function of sequentially delivering all RLC SDUs received up to now to a higher layer if a predetermined timer expires even if there is a lost RLC SDU. In addition, RLC PDUs may be processed in the order in which they are received (regardless of the order of serial numbers and sequence numbers, in the order of arrival) and delivered to the PDCP device regardless of order (out-of sequence delivery). In , segments stored in a buffer or to be received later may be received, reconstructed into one complete RLC PDU, processed, and transmitted to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

The out-of-sequence delivery function of the NR RLC refers to a function of immediately delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and originally one RLC SDU is divided into several RLC SDUs When received divided into , it may include a function of reassembling and forwarding them, and may include a function of storing RLC SNs or PDCP SNs of received RLC PDUs and arranging them in order to record lost RLC PDUs. .

The NR MACs 1440 and 1455 may be connected to several NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

- Mapping between logical channels and transport channels

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function (Padding)

The NR PHY layer (1445, 1450) channel-codes and modulates higher-layer data, converts it into OFDM symbols and transmits it through a radio channel, or demodulates and channel-decodes an OFDM symbol received through a radio channel and transmits it to a higher layer can be performed.

The detailed structure of the radio protocol structure may be variously changed according to a carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure for each layer, as shown by reference number 1410 in FIG. 14 . On the other hand, when the base station transmits data to the terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal have a single structure up to RLC as shown in reference number 1420, but multiplexing the PHY layer through the MAC layer. A protocol structure is used. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal have a single structure up to RLC as shown in reference number 1430, but PHY through the MAC layer A protocol structure that multiplexes layers is used.

Referring to the descriptions related to the PDCCH and beam configuration described above, it is difficult to achieve the required reliability in scenarios requiring high reliability such as URLLC because repetitive PDCCH transmission is not currently supported in Rel-15 and Rel-16 NRs. The present disclosure provides a method for repeatedly transmitting a PDCCH through multiple transmission points (TRPs) to improve PDCCH reception reliability of a UE. Specific methods are specifically described in the following examples.

The contents of this disclosure are applicable to at least one of FDD and TDD systems. Hereinafter, higher signaling (or higher layer signaling) in the present disclosure is a method of transmitting a signal from a base station to a terminal using a downlink data channel of a physical layer, or from a terminal to a base station using an uplink data channel of the physical layer, It may also be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (MAC CE).

Hereinafter, in the present disclosure, in determining whether cooperative communication is applied, a PDCCH (s) allocated to a PDSCH to which cooperative communication is applied has a specific format, or a PDCCH (s) allocated to a PDSCH to which cooperative communication is applied is cooperative. Include a specific indicator indicating whether communication is applied, or PDCCH(s) allocating a PDSCH to which cooperative communication is applied are scrambled with a specific RNTI, or cooperative communication is assumed in a specific interval indicated by a higher layer, etc. It is possible to use various methods. For convenience of description, a case in which a UE receives a PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as a non-coherent joint transmission (NC-JT) case.

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.

[NC-JT related]

According to an embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a UE to receive a PDSCH from multiple transmission and reception points (TRPs).

The 5G wireless communication system can support not only services requiring high transmission rates, but also services with very short transmission delays and services requiring high connection density, unlike conventional ones. In a wireless communication network including multiple cells, transmission and reception points (TRPs), or beams, coordinated transmission between each cell, TRP or/and beam increases the strength of a signal received by a terminal or each cell , TRP or/and inter-beam interference control can be efficiently performed to satisfy various service requirements.

Joint Transmission (JT) is a typical transmission technology for the above-described cooperative communication, and transmits a signal to one UE through a plurality of different cells, TRPs, or/and beams, thereby transmitting the strength or throughput of the signal received by the UE. is a technique that increases At this time, the characteristics of the channel between each cell, TRP or / and beam and the terminal may be significantly different, and in particular, a channel supporting non-coherent precoding between each cell, TRP or / and beam In the case of non-coherent joint transmission (NC-JT), individual precoding, MCS, resource allocation, TCI indication, etc. may be required according to channel characteristics for each cell, TRP or/and link between a beam and a UE.

The aforementioned NC-JT transmission may be applied to at least one of a downlink data channel (PDSCH), a downlink control channel (PDCCH), an uplink data channel (PUSCH), and an uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, TCI (Transmission Configuration 　 Indication) is indicated as DL DCI, and for NC-JT transmission, the transmission information must be independently indicated for each cell, TRP or / and beam do. This is a major factor in increasing a payload required for DL DCI transmission, which may adversely affect reception performance of a PDCCH transmitting DCI. Therefore, it is necessary to carefully design the tradeoff between DCI information amount and control information reception performance for JT support of PDSCH.

15 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting a PDSCH using cooperative communication in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 15, examples for PDSCH transmission are described for each technique of joint transmission (JT), and examples for allocating radio resources for each TRP are shown.

Referring to FIG. 15 , an example 1510 of coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP or/and beam is shown.

In the case of the C-JT, TRP A (1511) and TRP B (1513) transmit single data (PDSCH) to the terminal 1515, and joint precoding may be performed in multiple TRPs. . This may mean that DMRS is transmitted through the same DMRS ports so that TRP A 1511 and TRP B 1513 transmit the same PDSCH. For example, each of TRP A 1511 and TRP B 1513 may transmit DRMS to the UE through DMRS port A and DMRS port B. In this case, the terminal may receive one DCI information for receiving one PDSCH demodulated based on DMRS transmitted through DMRS port A and DMRS port B.

15 also shows an example 1520 of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP or/and beam for PDSCH transmission. This may mean that DMRS is transmitted through different DMRS ports in order for TRP A 1521 and TRP B 1523 to transmit different PDSCHs. For example, TRP A 1521 can transmit DRMS to the UE through DMRS port A, and TRP B 1523 can transmit DRMS to UE 1525 through DMRS port B. The terminal may receive DCI information for receiving each PDSCH demodulated based on the DMRS transmitted through the DMRS port A and the DMRS port B, respectively.

In the case of NC-JT, a PDSCH is transmitted to the terminal 1525 for each cell, TRP or/and beam, and individual precoding may be applied to each PDSCH. Each cell, TRP or/and beam may transmit different PDSCHs or different PDSCH layers to the UE to improve throughput compared to transmission of a single cell, TRP or/and beam. In addition, each cell, TRP or / and beam repeatedly transmits the same PDSCH to the UE, thereby improving reliability compared to single cell, TRP or / and beam transmission. For convenience of description, a cell, a TRP, or/and a beam are collectively referred to as TRP below.

In addition, in the example of FIG. 15, if the frequency and time resources used by multiple TRPs are the same for PDSCH transmission (1530), if the frequency and time resources used by multiple TRPs do not overlap at all (1540), multiple Various radio resource allocations may be considered, such as when some of the frequency and time resources used by the TRPs of the overlap (1550).

To support NC-JT, DCIs of various forms, structures, and relationships may be considered in order to simultaneously allocate a plurality of PDSCHs to one UE.

16 illustrates an example of a configuration of downlink control information (DCI) for NC-JT in which each TRP transmits a different PDSCH or a different PDSCH layer to a terminal in a wireless communication system according to an embodiment of the present disclosure. It is a drawing to

Referring to FIG. 16, in case #1 (1610), in addition to the serving TRP (TRP#0) used during single PDSCH transmission, (N-1) additional TRPs (TRP#1 to TRP#(N-1)) In a situation where different (N-1) PDSCHs are transmitted, this is an example in which control information on PDSCHs transmitted in (N-1) additional TRPs is transmitted independently of control information about PDSCHs transmitted in serving TRPs. . That is, the terminal transmits control information on PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). can be obtained The formats of the independent DCIs may be the same or different, and the payloads of the DCIs may also be the same or different. In case #1 1610 described above, each PDSCH control or allocation degree of freedom can be completely guaranteed, but when each DCI is transmitted in different TRPs, a coverage difference occurs for each DCI, and reception performance may deteriorate. .

In case #2 (1620), in addition to the serving TRP (TRP#0) used during single PDSCH transmission, (N-1) additional TRPs (TRP#1 to TRP#(N-1)) ) PDSCHs are transmitted, control information (DCI) for the PDSCHs of (N-1) additional TRPs is transmitted, and each of these DCIs (sDCI#0 to sDCI#(N-2)) serves TRP An example dependent on the control information (DCI#0) for the PDSCH transmitted from

For example, in the case of DCI#0, which is control information for the PDSCH transmitted from the serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but the cooperative TRP DCI format 1_0, It may include only some of the information elements of DCI format 1_1 and DCI format 1_2. Therefore, in the case of sDCI that transmits control information for PDSCHs transmitted from cooperative TRPs, compared to nDCI because the payload is smaller than normal DCI (nDCI) that transmits PDSCH-related control information transmitted from serving TRPs. Thus, it is possible to include reserved bits.

In case #2 (1620) described above, each PDSCH control or allocation degree of freedom may be limited according to the content of information elements included in sDCI, but the reception performance of sDCI is superior to that of nDCI, so DCI coverage The probability of a difference may be reduced.

In FIG. 16, case #3 1630 shows different (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used during single PDSCH transmission. In a situation where N-1) PDSCHs are transmitted, one control information (sDCI) for the PDSCHs of (N-1) additional TRPs is transmitted, and this DCI is transmitted as control information (DCI) for the PDSCHs transmitted from the serving TRP. ) shows an example dependent on.

For example, in the case of DCI#0, which is control information for the PDSCH transmitted from the serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and the cooperative TRP In the case of control information for PDSCHs transmitted from TRP#1 to TRP#(N-1), only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 are used as one 'secondary' DCI ( sDCI) and can be transmitted. For example, the sDCI may include at least one of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs. In addition, information not included in sDCI, such as a bandwidth part (BWP) indicator or carrier indicator, may follow the DCI (DCI#0, normal DCI, nDCI) of the serving TRP.

In FIG. 16, in case #3 1630, each PDSCH control or allocation degree of freedom may be limited according to the content of information elements included in sDCI, but reception performance of sDCI can be adjusted, and case # 1 1610 or Compared to case #2 1620, complexity of DCI blind decoding of the UE may be reduced.

In FIG. 16, case #4 (1640) shows different (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used during single PDSCH transmission In a situation where N-1) PDSCHs are transmitted, control information for PDSCHs transmitted from (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as control information for PDSCHs transmitted from serving TRPs. This is an example. That is, the terminal can obtain control information on PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case # 4 (1640), the complexity of DCI blind decoding of the terminal may not increase, but the degree of freedom in PDSCH control or allocation may be low, such as the number of cooperative TRPs being limited according to the long DCI payload limit.

In the following description and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI format 1_0 to 1_1 described above) including PDSCH control information transmitted from cooperative TRP, and has special restrictions. If not specified, the description is similarly applicable to the various auxiliary DCIs.

In the following descriptions and embodiments, cases of case #1 (1610), case #2 (1620), and case #3 (1630) in which one or more DCIs (PDCCH) are used to support NC-JT are multiple PDCCHs. It is divided into base NC-JT, and the case of the above-described case # 4 (1640) in which a single DCI (PDCCH) is used to support NC-JT can be divided into single PDCCH-based NC-JT. In multiple PDCCH-based PDSCH transmission, a CORESET in which DCI of serving TRP (TRP#0) is scheduled and a CORESET in which DCI of cooperative TRPs (TRP#1 to TRP#(N-1)) are scheduled can be distinguished. As a method for distinguishing CORESETs, there may be a method of distinguishing through an upper layer indicator for each CORESET, a method of distinguishing through beam setting for each CORESET, and the like. In addition, in the single PDCCH-based NC-JT, a single DCI schedules a single PDSCH having a plurality of layers instead of scheduling a plurality of PDSCHs, and the above-described plurality of layers can be transmitted from a plurality of TRPs. At this time, the connection relationship between the layer and the TRP transmitting the layer may be indicated through a TCI (Transmission Configuration Indicator) indication for the layer.

In the embodiments of the present disclosure, "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam" in actual application.

In the embodiments of the present disclosure, "when NC-JT is applied" means "when the terminal simultaneously receives one or more PDSCHs in one BWP", "when the terminal simultaneously receives two or more TCI indications in one BWP" It is possible to interpret variously according to the situation, such as "when the PDSCH is received based on the base", "when the PDSCH received by the terminal is associated with one or more DMRS port groups", etc., but for convenience of description, one expression was used as

In the present disclosure, the radio protocol structure for NC-JT may be used in various ways according to TRP deployment scenarios. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) similar to reference number 1420 of FIG. 14 is possible. On the other hand, when the backhaul delay between cooperative TRPs is too large to be ignored (for example, when information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs requires a time of 2 ms or more), reference number 1430 of FIG. 14 Similar to , a method (DC-like method) for securing characteristics robust against delay using an independent structure for each TRP from the RLC layer is possible.

The UE supporting C-JT/NC-JT may receive parameters or setting values related to C-JT/NC-JT from higher layer settings, and may set RRC parameters of the UE based on this. For higher layer configuration, the UE may utilize a UE capability parameter, for example, tci-StatePDSCH. Here, the UE capability parameter, for example, tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission, and the number of TCI states is 4, 8, 16, 32, 64, 128 in FR1 (frequency range 1), In FR2, it can be set to 64 or 128, and among the set numbers, up to 8 states that can be indicated by TCI field 3 bits of DCI through MAC CE message can be set. The maximum value of 128 means a value indicated by maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in capability signaling of the UE. As such, a series of configuration processes from higher layer configuration to MAC CE configuration may be applied to a beamforming instruction or a beamforming change command for at least one PDSCH in one TRP.

[Multi-DCI based Multi-TRP]

According to an embodiment of the present disclosure, a downlink control channel for NC-JT transmission may be configured based on Multi-PDCCH.

In NC-JT based on multiple PDCCHs, when DCI is transmitted for the PDSCH schedule of each TRP, it is possible to have a CORESET or search space classified for each TRP. CORESET or search space for each TRP can be set in at least one of the following cases.

- Upper layer index setting for each CORESET: The CORESET setting information set through the upper layer may include an index value, and the TRP transmitting the PDCCH in the corresponding CORESET can be distinguished by the index value for each set CORESET. That is, in a set of CORESETs having the same index value set through a higher layer, it may be considered that the PDCCH is transmitted by the same TRP or a PDCCH scheduling the PDSCH of the same TRP is transmitted. The index for each CORESET described above may be named as CORESETPoolIndex, and it may be considered that the PDCCH is transmitted from the same TRP for CORESETs for which the same CORESETPoolIndex value is set. In the case of a CORESET in which the CORESETPoolIndex value is not set, it can be considered that the default value of CORESETPoolIndex is set, and the above-described default value may be 0.

-Multiple PDCCH-Config settings: Multiple PDCCH-Configs are configured in one BWP, and each PDCCH-Config may include PDCCH settings for each TRP. That is, a list of CORESETs for each TRP and/or a list of search spaces for each TRP can be configured in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config are considered to correspond to a specific TRP. can do.

- CORESET beam/beam group configuration: TRPs corresponding to the CORESETs can be distinguished through beams or beam groups set for each CORESET. For example, when the same TCI state is set in a plurality of CORESETs, it can be considered that the corresponding CORESETs are transmitted through the same TRP or a PDCCH scheduling the PDSCH of the same TRP is transmitted in the corresponding CORESET.

- Configuration of search space beams/beam groups: A beam or beam group is configured for each search space, and through this, TRPs for each search space can be distinguished. For example, when the same beam/beam group or TCI state is set in multiple search spaces, it can be considered that the same TRP transmits the PDCCH in the search space, or the PDCCH scheduling the PDSCH of the same TRP is transmitted in the search space. have.

As described above, by classifying the CORESET or search space for each TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, and through this, independent HARQ-ACK codebook generation and independent PUCCH resource use for each TRP are possible.

The above setting may be independent for each cell or each BWP. For example, while two different CORESETPoolIndex values are set for PCell, no CORESETPoolIndex value may be set for a specific SCell. In this case, it can be considered that NC-JT transmission is configured in the PCell, whereas NC-JT transmission is not configured in the SCell for which the CORESETPoolIndex value is not set.

[Single-DCI-based Multi-TRP]

According to another embodiment of the present disclosure, a downlink beam for NC-JT transmission may be configured based on a single-PDCCH.

In single PDCCH-based NC-JT, PDSCHs transmitted by multiple TRPs can be scheduled with one DCI. At this time, the number of TCI states may be used as a method of indicating the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is two, it can be regarded as single PDCCH-based NC-JT transmission, and if the number of TCI states is one, it can be regarded as single-TRP transmission. The TCI states indicated by the above DCI can correspond to one or two TCI states among the TCI states activated by MAC-CE. If the TCI states of DCI correspond to the two TCI states activated by MAC-CE, the correspondence between the TCI codepoint indicated by DCI and the TCI states activated by MAC-CE is established, and the MAC corresponding to the TCI codepoint -This may be the case when there are two TCI states activated by CE.

The above setting may be independent for each cell or each BWP. For example, a PCell may have up to two activated TCI states corresponding to one TCI codepoint, whereas a specific SCell may have up to one activated TCI states corresponding to one TCI codepoint. In this case, while NC-JT transmission is configured in the PCell, it can be considered that NC-JT transmission is not configured in the aforementioned SCell.

Referring to the above PUCCH/PUSCH descriptions, in the current Rel-15/16 NR, a single cell or/and a single TRP or/and a single panel or/and a single beam or/and a single transmission direction for repeated PUCCH/PUSCH transmissions It is focused. However, if there is a deterioration factor having a high correlation in time and space, such as blockage, in the channel between the UE and a specific TRP, repeated transmission of PUCCH/PUSCH to a single TRP may not satisfy the expected performance. this is big Therefore, in order to overcome such degradation, Rel-17 or later releases may support repeated PUCCH/PUSCH transmission considering a plurality of TRPs. This may be a method of maximizing a diversity gain by considering a channel between a plurality of TRPs having different spatial characteristics and a UE. To support this, the UE must support configuration for repeated PUCCH/PUSCH transmission to multiple TRPs. For example, it is necessary to configure or indicate methods for multiple transmission beams to be used, power control, etc. when repeatedly transmitting PUCCH/PUSCH considering multiple TRPs. In addition, higher layer signaling or dynamic indication is required to distinguish between repeated transmission schemes considering a single TRP defined in Rel-15/16 and repeated PUCCH/PUSCH transmissions considering multiple TRPs to be newly defined in Rel-17. . In this case, in order to support repeated PUCCH transmission considering Rel-17 multiple TRPs, MAC CE for activating one or more spatial relationships for power control and transmission beams for each TRP may be considered.

In the present disclosure, when PUCCH spatial relation is activated in consideration of multiple TRPs, a method for determining spatial relation of a PUCCH resource corresponding to a minimum ID referenced to transmit a PUSCH scheduled in DCI format 0_0 may be provided. . Specific methods are specifically described in the following examples.

For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, or transmission points that can be distinguished through higher layer/L1 parameters such as TCI state or spatial relation information or indicators such as cell ID, TRP ID, or panel ID / and the transmission direction are unified and described as a transmission reception point (TRP). Therefore, in actual application, TRP can be appropriately replaced with one of the above terms.

Hereinafter, in the present disclosure, in determining whether cooperative communication is applied, a PDCCH (s) allocated to a PDSCH to which cooperative communication is applied has a specific format, or a PDCCH (s) allocated to a PDSCH to which cooperative communication is applied is cooperative. Cooperative communication is assumed in a specific interval indicating whether communication is applied or not, or PDCCH (s) allocating a PDSCH to which cooperative communication is applied is scrambled with a specific RNTI, or indicated through higher layer signaling. It is possible to use various methods such as For convenience of explanation, the terminal receiving the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as an NC-JT case.

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.

<First Embodiment: Method for Determining Spatial Relationship Information of PUCCH Resources with Minimum ID Included in Multiple PUCCH Resource Groups>

The first embodiment of the present disclosure is a PUCCH resource having the lowest ID according to a method of activating a plurality of spatial relation information based on a PUCCH resource group for repeated PUCCH transmission considering multiple TRPs. A method for determining synoptic relationship information is described.

In Rel-16, one PUCCH resource can be activated with one piece of spatial relationship information, and efficient signaling can be supported by setting the PUCCH resources to be simultaneously activated through a PUCCH resource group. However, since this method can activate only one spatial relation information for a PUCCH resource, it is not suitable for performing repeated PUCCH transmission considering multiple TRPs. Accordingly, in Rel-17, one PUCCH resource may be configured to be included in a plurality of PUCCH resource groups in order to activate a PUCCH resource for performing repetitive transmission considering multiple TRPs with a plurality of spatial relation information. That is, each PUCCH resource group can be used to manage spatial relationship information for each TRP, and is included in multiple PUCCH resource groups so that one PUCCH resource can be activated with spatial relationship information for multiple TRPs. can be set

For example, if PUCCH resources #1, #2 and #3 are set to PUCCH resource group #1 and PUCCH resources #3, #5 and #7 are set to PUCCH resource group #2, PUCCH resource #3 is set to PUCCH resource group Spatial relationship information #1 activated as #1 and spatial relationship information #2 activated as PUCCH resource group #2 can be activated as two pieces of spatial relationship information. Accordingly, when the UE transmits the PUCCH through PUCCH resource #3, it is possible to perform repeated PUCCH transmission considering multiple TRPs using the two activated spatial relationship information. Additionally, PUCCH resources #1 and #2 are activated only with spatial relationship information #1 according to PUCCH resource group #1, and PUCCH resources #5 and #7 are activated only with spatial relationship information #2 according to PUCCH resource group #2. At this time, if the UE transmits PUCCH through one of PUCCH resources #1, #2, #5, and #7, repeated PUCCH transmission considering a single TRP is performed according to the spatial relationship information for the corresponding PUCCH resource. That is, according to the number of PUCCH resource groups including PUCCH resources, the UE can distinguish a PUCCH resource supporting repeated transmission considering multiple TRPs and a PUCCH resource supporting only repeated transmission considering a single TRP.

If PUCCH resource #n is included in two PUCCH resource groups, PUCCH resource #n can be activated up to two pieces of spatial relationship information. Here, Spatial Relation Info ID (1235 or 1245) indicated by the MAC CE as shown in [FIG. 12] indicates which of the two spatial relationship information of PUCCH resource #n is activated, in the reserved area (1237 or 1247 ) can be used. For example, Spatial Relation Info ID 1236 in Oct 3 1235 and Spatial Relation Info ID 1246 in Oct 2N-1 1245 both represent spatial relationships of PUCCH resources within a PUCCH resource group to which PUCCH resource #n belongs. information can be activated. In addition, one or a plurality of bits of the reserved area 1237 for Oct 3 (1235) may indicate 0, and one or a plurality of bits of the reserved area 1247 for Oct 2N-1 (1245) may indicate 1. In this case, Spatial Relation Info ID 1236 for Oct 3 1235 activates the first spatial relation information of PUCCH resource #n, and Spatial Relation Info ID 1246 for Oct 2N-1 1245 is PUCCH resource The second spatial relationship information of #n can be activated. If a PUCCH resource is included in only one PUCCH resource group, spatial relationship information can be activated regardless of a reserved area.

Since the PUSCH scheduled in DCI format 0_0 does not have a separate SRS resource indicator (SRI) field indicated by DCI, the corresponding PUSCH is transmitted according to the spatial relationship information of the PUCCH having the minimum ID. If the PUCCH resource with the minimum ID is activated with a plurality of pieces of spatial relationship information, the UE can determine whether to transmit the PUSCH scheduled in DCI format 0_0 by referring to which piece of spatial relationship information of the PUCCH resource with the minimum ID. There may be issues with not having it. Therefore, a constraint condition that a PUCCH resource having a minimum ID should be activated with only one piece of spatial relationship information may occur. However, the fact that the PUCCH resource with the minimum ID can be activated with only one spatial relationship information does not mean that the PUCCH resource with the minimum ID is supported with only one TRP. That is, it may be activated as spatial relationship information for transmitting the PUCCH resource having the minimum ID to TRP1 according to the channel condition between each TRP and the UE, or may be activated as spatial relationship information for transmitting to TRP2 or TRP N. Therefore, a PUCCH resource having a minimum ID may also be included in a plurality of PUCCH resource groups for flexible management. Method 1-1, 1 of the present disclosure for including a PUCCH resource having a minimum ID in a plurality of PUCCH resource groups so that it can be managed flexibly as described above, but not being activated by a plurality of spatial relationship information at the same time -2 will be described in the embodiment.

<Embodiment 1-1: A method for a UE to activate a PUCCH resource with a minimum ID as one spatial relationship information when receiving a MAC CE activating two or more pieces of spatial relationship information for a PUCCH resource with a minimum ID >

As an embodiment of the present disclosure, in the 1-1 embodiment, when a MAC CE for activating two or more pieces of spatial relationship information for a PUCCH resource with a minimum ID is received, the UE assigns the PUCCH resource with the minimum ID to one space. A method of activating with relational information will be described.

As described above, in order to efficiently manage the PUCCH resource having the minimum ID according to the channel state between the terminal and the TRP and to transmit the PUSCH scheduled in DCI format 0_0 accordingly, the base station allocates the PUCCH resource with the minimum ID to multiple PUCCHs. It can be set to be included in a resource group.

If a PUCCH resource other than the PUCCH resource with the minimum ID is included in two PUCCH resource groups and the UE receives a MAC CE activating the spatial relationship information for the two corresponding PUCCH resource groups, the UE receives the corresponding PUCCH resource for the corresponding PUCCH resource. Activate both spatial relation information. However, for a PUCCH resource having a minimum ID, an additional rule is required so that only one piece of spatial relationship information can be activated even when the same signaling is received from the base station. Accordingly, the UE may determine the spatial relationship information of the PUCCH resource having the minimum ID by defining one of the following additional rules in advance between the BS and the UE.

[Additional rule 1]

If the UE receives a MAC CE for activating spatial relationship information for two or more PUCCH resource groups including the PUCCH resource with the minimum ID, the UE receives the corresponding MAC among the PUCCH resource groups including the PUCCH resource with the minimum ID. Spatial relationship information of a PUCCH resource having a minimum ID as spatial relationship information for a PUCCH resource group indicated as the first in the CE is activated.

[Additional rule 2]

If the UE receives a MAC CE for activating spatial relationship information for two or more PUCCH resource groups including the PUCCH resource with the minimum ID, the UE receives the corresponding MAC among the PUCCH resource groups including the PUCCH resource with the minimum ID. Spatial relationship information of a PUCCH resource having a minimum ID as spatial relationship information for a PUCCH resource group indicated as the last in CE is activated.

17a and 17b show spatial relationship information for a PUCCH resource group indicated as first in a corresponding MAC CE among PUCCH resource groups including a PUCCH resource having a minimum ID according to an embodiment of the present disclosure. It is a diagram showing an example of activating spatial relationship information of a PUCCH resource having an ID.

Referring to FIG. 17A, if the UE receives a MAC CE 1710 for activating PUCCH resource group-based spatial relationship information as in Case 1, the UE receives a first entry (consisting of 1711, 1712, and 1713) for activating spatial relationship information. ), spatial relation information of PUCCH resource group #1 is activated with Spatial Relation Info ID #X. At this time, in order to indicate which spatial relationship information among a plurality of spatial relationship information for PUCCH resources belonging to two or more PUCCH resource groups, such as PUCCH resources #0 and #3, is activated as a corresponding entry, the reserved area 1713 One bit or multiple bits can be used. Similarly, the UE activates spatial relationship information of PUCCH resource group #2 with Spatial Relation Info ID #Y according to the last spatial relationship information activation entry (consisting of 1721, 1722, and 1723). At this time, since PUCCH resource #0, which is the PUCCH resource with the minimum ID, belongs to PUCCH resource group #1 and PUCCH resource group #2, it is among the PUCCH resource groups including the PUCCH resource with the minimum ID according to the above-described additional rule 1. Spatial relationship information for the PUCCH resource group (ie, PUCCH resource group #1) indicated as the first in the corresponding MAC CE, spatial relationship information of the PUCCH resource having the minimum ID, that is, Spatial Relation Info ID #X activate Here, PUCCH resource #3, which is not the minimum ID belonging to both PUCCH resource group #1 and PUCCH resource group #2, has two spatial relationship information, that is, Spatial Relation Info ID #X and Spatial Relation Info for repeated PUCCH transmission considering multiple TRPs. The base station may instruct the terminal to activate with ID #Y to activate two spatial relationships for one PUCCH resource. Since PUCCH resource #2 belongs only to PUCCH resource group #1, it is activated only with single spatial relationship information, that is, Spatial Relation Info ID #X, and similarly, PUCCH resource #7 is also activated only with single spatial relationship information, that is, Spatial Relation Info ID #Y. do.

Referring to FIG. 17B, if the UE receives a MAC CE 1730 for activating PUCCH resource group-based spatial relationship information as in Case 2, the UE receives a first entry for spatial relationship information activation (consisting of 1731, 1732, and 1733). ), spatial relation information of PUCCH resource group #2 is activated with Spatial Relation Info ID #Y. At this time, in order to indicate which spatial relationship information among a plurality of spatial relationship information for PUCCH resources belonging to two or more PUCCH resource groups, such as PUCCH resources #0 and #3, is activated as a corresponding entry, the reserved area 1733 One bit or multiple bits can be used. Similarly, the UE activates spatial relationship information of PUCCH resource group #1 with Spatial Relation Info ID #X according to the last spatial relationship information activation entry (consisting of 1741, 1742, and 1743). At this time, since PUCCH resource #0, which is the PUCCH resource with the minimum ID, belongs to PUCCH resource group #1 and PUCCH resource group #2, it is among the PUCCH resource groups including the PUCCH resource with the minimum ID according to the above-described additional rule 1. Spatial relationship information for the PUCCH resource group (ie, PUCCH resource group #2) indicated as the first in the corresponding MAC CE. Spatial relationship information of the PUCCH resource having the minimum ID, that is, Spatial Relation Info ID #Y activate

If the MAC CE received by the UE activates the spatial relationship information for one of the PUCCH resource groups including the PUCCH resource with the minimum ID, the UE activates the spatial relationship information for the PUCCH resource with the minimum ID according to the corresponding MAC CE. Spatial relational information can be activated without additional rules.

18 illustrates an operation of a UE for activating spatial relationship information of a PUCCH resource having a minimum ID according to an embodiment of the present disclosure.

Referring to FIG. 18, the terminal reports UE capabilities to the base station (1810). At this time, the UE includes UE capability for reporting whether PUCCH transmission considering multiple TRPs is possible. Thereafter, the terminal may receive higher layer parameter settings for uplink transmission considering multiple TRPs from the base station (1811). If the terminal receives only higher layer parameter settings for uplink transmission considering a single TRP, it operates according to the Rel-16 procedure (1812). The UE receives a MAC CE for activating PUCCH resource group-based spatial relationship information from the base station (1813). The UE determines a MAC CE application method according to whether a PUCCH resource having a minimum ID is included in one or more PUCCH resource groups (1814). If the PUCCH resource with the minimum ID is included in only one PUCCH resource group, the UE performs spatial relationship information activation of PUCCH resource groups based on the PUCCH resource group according to the MAC CE command without additional rule 1 or additional rule 2 described above ( 1816). If the PUCCH resource with the minimum ID is included in one or more PUCCH resource groups, the UE checks whether the received MAC CE indicates activation of spatial relationship information for a plurality of PUCCH resource groups including the PUCCH resource with the minimum ID ( 1815). If the MAC CE activates only the spatial relationship information for one PUCCH resource group among the PUCCH resource groups including the PUCCH resource with the minimum ID, the UE does not have additional rule 1 or additional rule 2 according to the MAC CE command based on the PUCCH resource group. Activation of spatial relationship information of PUCCH resources is performed (1816). If the MAC CE activates the spatial relationship information for a plurality of PUCCH resource groups among the PUCCH resource groups including the PUCCH resource with the minimum ID, the UE accesses the PUCCH resource with the minimum ID according to additional rule 1 or additional rule 2. Spatial relationship information to be activated for is determined (1817).

19 illustrates an operation of a base station for activating spatial relationship information of PUCCH resources according to an embodiment of the present disclosure.

Referring to FIG. 19, the base station receives UE capability from the terminal (1910). At this time, the base station receives UE capability including whether or not PUCCH transmission considering multiple TRPs is possible. The base station may set higher layer parameters for repeated PUCCH transmission considering multiple TRPs in the terminal based on the UE capability reported by the terminal (1911). Higher layer parameters configured at this time may include PUCCH-Config including PUCCH resource group configuration, transmission power control parameters for determining PUCCH transmission power, and one or more PUCCH-SpatialRelationInfo. The base station may transmit a MAC CE for activating spatial relationship information based on a PUCCH resource group to the terminal in order to activate spatial relationship information on PUCCH resources (1913).

<Embodiment 1-2: Spatial Relationship Information Activation Constraint Method for Multiple PUCCH Resource Groups Including PUCCH Resources with Minimum ID>

As an embodiment of the present disclosure, a method for restricting activation of spatial relationship information for a plurality of PUCCH resource groups including a PUCCH resource having a minimum ID will be described in the first and second embodiments.

If the PUCCH resource with the minimum ID is included in a plurality of PUCCH resource groups to support flexible TRP change, the base station adds the following condition to the PUCCH resource group activated by the MAC CE, so that the PUCCH resource with the minimum ID It can be supported to be activated with this one spatial relationship information.

[MAC CE Configuration Additional Conditions]

If the PUCCH resource with the minimum ID is included in a plurality of PUCCH resource groups, the base station does not transmit MAC CE indicating activation of spatial relationship information for the PUCCH resource group including the PUCCH resource with two or more minimum IDs to the terminal. don't That is, only spatial relationship information for one PUCCH resource group including a PUCCH resource having a minimum ID can be activated through one MAC CE. In addition, an activation command of spatial relationship information for a PUCCH resource group that does not include a PUCCH resource having a minimum ID may be transmitted together through a corresponding MAC CE.

Through the above MAC CE configuration additional condition, it is possible to prevent the case where the PUCCH resource having the minimum ID is activated with two pieces of spatial relationship information, and the UE can activate the spatial relationship information of the PUCCH resources according to the MAC CE received from the base station. can

<Embodiment 2: Method of configuring a PUCCH group for a PUCCH resource having a minimum ID when configuring a separate PUCCH resource group for a PUCCH resource considering multiple TRPs>

As an embodiment of the present disclosure, the second embodiment describes a method of configuring a PUCCH group for a PUCCH resource having a minimum ID when configuring a separate PUCCH resource group for a PUCCH resource considering multiple TRPs.

Spatial relationship information of PUCCH resources may be activated through a method other than the MAC CE enhancement method for activating spatial relationship information based on PUCCH resource groups for repeated PUCCH transmission considering multiple TRPs described in the first embodiment. In the first embodiment, if a single PUCCH resource can be included in a plurality of PUCCH resource groups, another method can support by including some PUCCH resources for repeated PUCCH transmission considering multiple TRPs in a separate PUCCH resource group. For example, if PUCCH resource IDs #3, #10, and #23 are set as PUCCH resources for transmission to multiple TRPs, the corresponding PUCCH resources are set to be the fourth PUCCH resource group among the maximum configurable 4 PUCCH resource groups. can Alternatively, the number of maximum configurable PUCCH resource groups may be increased from 4 to a larger number, and the increased PUCCH resource groups may be used as a group of PUCCH resources for PUCCH transmission considering multiple TRPs. At this time, the PUCCH resource(s) included in the PUCCH resource group for repeated PUCCH transmission considering multiple TRPs are activated with a plurality of spatial relationship information, and a new MAC CE may be required to support this. At this time, the new MAC CE may be similar to the MAC CE for activation of spatial relation information based on PUCCH resource group of Rel-16, but the PUCCH resource group for repeated PUCCH transmission considering multiple TRPs consists of one Spatial Relation Info ID field A plurality of Spatial Relation Info ID fields that are not allowed may be included. PUCCH resource IDs #3, #10, and #23 included in the corresponding PUCCH resource group are activated with spatial relation information indicated through a plurality of Spatial Relation Info ID fields.

20 illustrates an example of MAC CE for activating PUCCH resource group-based spatial relationship information when configuring a PUCCH resource group for repeated PUCCH transmission considering multiple TRPs according to an embodiment of the present disclosure.

Referring to FIG. 20, the base station issues spatial relationship information activation commands for a PUCCH resource group including PUCCH resource(s) for PUCCH (repetitive) transmission considering a single TRP in Oct 2 (2010) and Oct 3 (2011). It can be configured as such, and the spatial relationship information activation command for the PUCCH resource group including the PUCCH resource (s) for repeated PUCCH transmission considering multiple TRPs is Oct 2N-2 (2020), Oct 2N-1 (2021), and It can be configured like Oct 2N (2022). At this time, one reserved bit can be set and used as C to indicate whether the transmitted MAC CE includes an activation command for spatial relationship information of a PUCCH resource group for repeated PUCCH transmission considering multiple TRPs. (2031 or 2032). If the C field 2031 is set to 0, it means that the corresponding Oct 2 (2010) and Oct 3 (2011) are activated as one Spatial Relation Info. If the C field 2032 is set to 1, it means that the corresponding Oct 2N-2, Oct 2N-1, and Oct 2N are activated as two Spatial Relation Info.

In this way, if repeated PUCCH transmission considering multiple TRPs is supported using a separate PUCCH resource group, the base station prevents the PUCCH resource having the minimum ID from being activated with two or more spatial relation information, so that the PUCCH resource group for repeated multiple TRP PUCCH transmissions (For example, as described above, the PUCCH resource having the minimum ID is not included in the last or newly added PUCCH resource group among the four PUCCH resource groups.) In addition, the UE recognizes that the PUCCH resource with the minimum ID is included in the PUCCH resource group for repeated multi-TRP PUCCH transmission (eg, the last or newly added PUCCH resource group among the 4 PUCCH resource groups as described above). don't expect

21 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. 21 , a terminal may include a transceiver that refers to a receiver 2101 and a transmitter 2103, a memory (not shown), and a processor 2105. The processor 2105 may be at least one processor and may be referred to as a controller or a control unit. The processor 2105 may control overall devices of the terminal so that the terminal operates according to each of the above-described embodiments of the present disclosure as well as a combination of at least one embodiment. 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 the form of at least one chip.

The transceiver may transmit and receive signals to and from the base station. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts its 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 2105, and transmit the signal output from the processor 2105 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 2105 can control a series of processes so that the terminal can operate according to the above-described embodiment. For example, the processor 2105 may control a series of processes of repeatedly transmitting a PUCCH or a PUSCH in consideration of multiple TRPs based on configuration information received from a base station. In addition, the processor 2105 may control components of the terminal to simultaneously receive a plurality of PDSCHs by receiving DCI composed of two layers. The number of processors 2105 may be plural, and the processors may perform control operations on component(s) of the terminal by executing a program stored in a memory.

22 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. 22 , a base station may include a transceiver that refers to a receiver 2201 and a transmitter 2203), a memory (not shown), and a processor 2205. The base station may include a communication interface (not shown) for wired or wireless communication with another base station through a backhaul link. The processor 2205 may be at least one processor and may be referred to as a controller or a control unit. The processor 2205 may control overall devices of the base station so that the base station operates according to each of the above-described embodiments of the present disclosure as well as a combination of at least one embodiment. 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 the form of at least one chip.

The transceiver may transmit and receive signals to and from the terminal. Here, the signal may include control information and data. To this end, the transceiver 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.

In addition, the transceiver may receive a signal through a wireless channel, output the signal to the processor 2205, and transmit the signal output from the processor 2205 through a 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 2205 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 2205 may control a series of processes of scheduling and receiving repeated PUCCH or PUSCH transmissions in consideration of multiple TRPs. The processor 2205 may configure and transmit DCIs of two layers including allocation information for a plurality of PDSCHs and may control each element of the base station. The processor 2205 may be plural, and the processor 2205 may perform a control operation on the component(s) 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 description in the drawings for explaining the method of the present disclosure 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 disclosure may omit some components and include only some components within a range that does not impair the essence of the present disclosure.

In addition, the method of the present disclosure 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 present 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 construed 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