KR20240016863A - Method and apparatus for transmitting uplink control information with multi panels in wireless communication system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. Specifically, the present disclosure provides a method and apparatus for an uplink transmission process considering simultaneous transmission of multiple panels.

Description

Method and device for transmitting uplink control information through multiple panels in a wireless communication system {METHOD AND APPARATUS FOR TRANSMITTING UPLINK CONTROL INFORMATION WITH MULTI PANELS IN WIRELESS COMMUNICATION SYSTEM}

This disclosure relates to the operation of a terminal and a base station in a wireless communication system (or mobile communication system). Specifically, the present disclosure relates to a method for performing simultaneous uplink transmission using a plurality of panels in a wireless communication system, a method for transmitting uplink control information accordingly, and a device capable of performing the same.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes not only the sub-6GHz frequency band ('Sub 6GHz') such as 3.5 gigahertz (3.5GHz), but also millimeter wave ('Sub 6GHz') bands such as 28GHz and 39GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called ㎜Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, in order to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth of that. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early stages of 5G mobile communication technology, services for ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable & low-latency communications (URLLC), and massive machine-type communications (mMTC) were provided. With the goal of meeting support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio wave propagation distance, is implemented. Numerology (multiple subcarrier spacing operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), and large-capacity data transmission. Provides new channel coding methods such as LDPC (Low Density Parity Check) codes and Polar Code for highly reliable transmission of control information, L2 pre-processing, and a dedicated network specialized for specific services. Standardization for network slicing, etc. has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X to help autonomous vehicles make driving decisions and increase user convenience, NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands, and NR terminal low-power consumption technology (UE Power Saving), physical layer standardization for technologies such as Non Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and positioning. Is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and 5G baseline architecture (e.g. , Service based Architecture, Service based Interface), and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, are also in progress in the system architecture/service field.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, 5G performance is improved and complexity is reduced using extended reality (XR), artificial intelligence (AI), and machine learning (ML) to efficiently support augmented reality and virtual reality. , new research on AI service support, metaverse service support, drone communication, etc. will be conducted.

In addition, the development of these 5G mobile communication systems includes new waveforms, Full Dimensional MIMO (FD-MIMO), and Array Antenna to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, full duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

Meanwhile, with the development of communication systems, research is being conducted on the uplink transmission and reception process using a plurality of panels, and in particular, the demand for improving the uplink control information transmission process using a plurality of panels is increasing.

Various embodiments of the present disclosure seek to provide devices and methods that can effectively provide services in a mobile communication system. Various embodiments of the present disclosure are intended to provide a method for simultaneously transmitting a plurality of uplink channels using a plurality of panels in a wireless communication system and a device for performing the same.

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

According to various embodiments of the present disclosure, devices and methods that can effectively provide services in a mobile communication system can be provided.

According to various embodiments of the present disclosure, a method for simultaneously transmitting a plurality of uplink channels using a plurality of panels in a wireless communication system and a device for performing the same can be provided.

1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure.
FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to an embodiment of the present disclosure.
FIG. 3 is a diagram illustrating an example of bandwidth portion setting in a wireless communication system according to an embodiment of the present disclosure.
FIG. 4 is a diagram illustrating an example of base station beam allocation according to TCI (transmission configuration indicator) state settings in a wireless communication system according to an embodiment of the present disclosure.
FIG. 5 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure.
FIG. 6 is a diagram illustrating an example of PDSCH time axis resource allocation in a wireless communication system according to an embodiment of the present disclosure.
Figure 7 shows the process for beam setting and activation of PDSCH.
FIG. 8 is a diagram illustrating an example of a medium access control (MAC) control element (CE) for activating a spatial relationship based on a physical uplink control channel (PUCCH) resource group in a wireless communication system according to an embodiment of the present disclosure.
FIG. 9 is a diagram illustrating an example of PUSCH (physical uplink shared channel) repetitive transmission type B in a wireless communication system according to an embodiment of the present disclosure.
FIG. 10 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to an embodiment of the present disclosure.
FIG. 11 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.
FIG. 12 is a diagram illustrating an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment of the present disclosure.
Figure 13 is a diagram showing the Enhanced PDSCH TCI state activation/deactivation MAC-CE structure.
FIG. 14 is a diagram illustrating a radio link monitoring (RLM) reference signal (RS) selection process according to an embodiment of the present disclosure.
FIG. 15 is a diagram showing a MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.
FIG. 16 is a diagram illustrating another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.
FIG. 17 is a diagram illustrating another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.
FIG. 18 is a diagram illustrating a MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.
FIG. 19 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.
FIG. 20 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.
FIG. 21 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.
FIG. 22 is a diagram showing a MAC-CE structure for activating and indicating joint and separate TCI states in a wireless communication system according to an embodiment of the present disclosure.
FIG. 23 is a diagram illustrating another MAC-CE structure for activating and indicating joint and separate TCI states in a wireless communication system according to an embodiment of the present disclosure.
Figure 24 is a diagram of the beam application time that can be considered when using the integrated TCI method in a wireless communication system according to an embodiment of the present disclosure.
FIG. 25 is a diagram illustrating a MAC-CE structure for activating and indicating a plurality of joint TCI states in a wireless communication system according to an embodiment of the present disclosure.
FIG. 26 is a diagram illustrating a MAC-CE structure for activating and indicating a plurality of separate TCI states in a wireless communication system according to an embodiment of the present disclosure.
FIG. 27 is a diagram illustrating another MAC-CE structure for activating and indicating a plurality of separate TCI states in a wireless communication system according to an embodiment of the present disclosure.
Figure 28 shows a panel for allocating and transmitting resources for uplink transmission in FDM (frequency division multiplexing), SDM (spatial division multiplexing), and SFN (single frequency network) methods to support STxMP (simultaneous transmission with multi panels). It is a drawing.
Figure 29 shows an example of mulxiplexing UCI (uplink control information) in an STxMP transmission situation based on FDM and SDM.
FIG. 30 is a diagram illustrating an example of a PUSCH simultaneously transmitted through multiple panels scheduled as mDCI (multi DCI) or sDCI (single DCI) and an example of a PUCCH that overlaps the scheduled PUSCH in the time domain.
FIG. 31 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.
FIG. 32 is a diagram illustrating the 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 attached drawings.

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

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically shown. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification. Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted 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 process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram 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). Additionally, it should be noted that in some alternative execution examples, it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to 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. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' 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. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.

As a representative example of the broadband wireless communication system, the LTE system adopts Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL), and Single Carrier Frequency Division Multiplexing (SC-FDMA) in the uplink (UL). Access) method is adopted. Uplink refers to a wireless 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 wireless link in which the base station transmits data or control signals to the base station (eNode B, or base station (BS)). It refers to a wireless link that transmits data or control signals. The above multiple access method usually distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. You can.

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is.

eMBB aims to provide more improved data transmission speeds than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink from the perspective of one base station. In addition, the 5G communication system must provide the maximum transmission rate and at the same time provide increased user perceived data rate. In order to meet these requirements, improvements in various transmission and reception technologies are required, including more advanced multi-antenna (Multi Input Multi Output, MIMO) transmission technology. In addition, while LTE transmits signals using a maximum of 20MHz transmission bandwidth in the 2GHz band, the 5G communication system uses a frequency bandwidth wider than 20MHz in the 3~6GHz or above 6GHz frequency band to transmit the 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 the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC requires support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km^2) within a cell. Additionally, due to the nature of the service, terminals that support mMTC are likely to be located in shadow areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system. Terminals that support mMTC must be composed of low-cost terminals, and since it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

Lastly, URLLC is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency situations. Services used for emergency alerts, etc. can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy a wireless access latency (Air interface latency) of less than 0.5 milliseconds and at the same time have a packet error rate requirement of 10 ^-5 or less. Therefore, for services supporting URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, a design that requires allocating wide resources in the frequency band to ensure the reliability of the communication link. Specifications may be required.

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

Hereinafter, the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network. A terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel type. For example, this may include the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A, and the term 5G hereinafter may also include the existing LTE, LTE-A, and other similar services. there is. In addition, this disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge.

[NR time-frequency resource]

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

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

(일례로 12)개의 연속된 RE들은 하나의 자원 블록(Resource Block, RB, 104)을 구성할 수 있다. 시간축에서 하나의 서브프레임(110)은 복수의 OFDM symbol (102)를 포함할 수 있다. 예를 들어, 1 서브프레임의 길이는 1 ms 일 수 있다.The horizontal axis in Figure 1 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 can be defined as 1 OFDM symbol 102 on the time axis and 1 subcarrier 103 on the frequency axis. in the frequency domain

(For example, 12) consecutive REs may constitute one resource block (Resource Block, RB, 104). One subframe 110 on the time axis may include a plurality of OFDM symbols 102. For example, the length of 1 subframe may be 1 ms.

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

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

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

)가 달라질 수 있다. 각 부반송파 간격 설정 μ에 따른 및 는 하기의 표 1로 정의될 수 있다.FIG. 2 shows an example of a frame 200, subframe 201, and slot 202 structure. 1 frame (200) can be defined as 10ms. 1 subframe 201 may be defined as 1 ms, and therefore 1 frame 200 may consist of a total of 10 subframes 201. 1 slot (202, 203) can be defined with 14 OFDM symbols (i.e., number of symbols per slot (

=14)).1 subframe 201 may be composed of one or a plurality of slots 202, 203, and the number of slots 202, 203 per 1 subframe 201 is the setting value for the subcarrier spacing. It may vary depending on μ(204, 205). In an example of FIG. 2, a case where μ=0 (204) and a case where μ=1 (205) are shown as the subcarrier spacing 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. It can be composed of . That is, the number of slots per subframe (depending on 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 as Table 1 below.

[Table 1]

[Bandwidth Part (BWP)]

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

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

Figure 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. It shows. The base station can set one or more bandwidth parts to the terminal, and can set the following information for each bandwidth part.

[Table 2]

Of course, it is not limited to the above example, and in addition to the setting information, various parameters related to the bandwidth can be set to the terminal. The above information can be delivered from the base station to the terminal through higher layer signaling, for example, Radio Resource Control (RRC) signaling. Among the one or multiple bandwidth portions set, at least one bandwidth portion may be activated. Whether to activate the set bandwidth portion can be semi-statically transmitted from the base station to the terminal through RRC signaling or dynamically transmitted through DCI.

According to some embodiments, the terminal before connection (RRC) may receive the initial bandwidth portion (Initial BWP) for initial connection from the base station through MIB (Master Information Block). To be more specific, the terminal may perform the initial connection stage. A control resource area (Control Resource Set, CORESET) where PDCCH can be transmitted to receive system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial connection through MIB. ) and configuration information about the search space can be received. The control area and search space set by MIB can each be regarded as identifier (ID) 0. The base station provides control to the terminal through the MIB. Setting information such as frequency allocation information, time allocation information, numerology, etc. for area #0 can be notified. In addition, the base station provides the terminal with the monitoring period and monitoring purpose for control area #0 through the MIB. setting information for (occasion), that is, setting information for search space #0. The terminal may regard the frequency area set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be regarded as 0.

Setting 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, this can be supported through the bandwidth portion setting. For example, the base station sets the frequency location (setting information 2) of the bandwidth portion to the terminal, allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

Additionally, according to some embodiments, the base station may set a plurality of bandwidth portions 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 15kHz and a subcarrier spacing of 30kHz for a certain terminal, the two bandwidth portions can be set to subcarrier spacings of 15kHz and 30kHz, respectively. Different bandwidth portions can be frequency division multiplexed (FDM), and when data is to be transmitted and received at a specific subcarrier interval, the bandwidth portion set at the corresponding subcarrier interval can be activated.

Additionally, according to some embodiments, for the purpose of reducing power consumption of the terminal, the base station may set bandwidth portions with different sizes of bandwidth to the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and always transmits and receives data through that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a situation where there is no traffic can be very inefficient in terms of power consumption. For the purpose of reducing power consumption of the terminal, the base station may set a relatively small bandwidth portion of the terminal, for example, a bandwidth portion of 20 MHz. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, data can be transmitted and received in the 100 MHz bandwidth portion according to the instructions of the base station.

In the method of configuring the bandwidth portion, terminals before RRC connection can receive configuration information about the initial bandwidth portion (Initial BWP) through MIB in the initial connection stage. To be more specific, the terminal can receive a control area (i.e. CORESET) for the downlink control channel through which a DCI scheduling SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). . The bandwidth of the control area set as MIB can be considered as the initial bandwidth part, and through the set initial bandwidth part, the terminal can receive the PDSCH (Physical Downlink Shared Channel) through which the SIB is transmitted. In addition to receiving SIB, the initial bandwidth portion can also be used for other system information (OSI), paging, and random access.

[Bandwidth part (BWP) change]

If one or more bandwidth parts are configured for the terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth portion using the Bandwidth Part Indicator field in the DCI. As an example, in Figure 3, if the currently activated bandwidth portion of the terminal is bandwidth portion #1 (301), the base station may indicate bandwidth portion #2 (302) to the terminal as a bandwidth portion indicator in the DCI, and the terminal may indicate the received bandwidth portion #2 (302). Bandwidth part change can be performed using bandwidth part #2 (302) indicated by the bandwidth part indicator in DCI.

As described above, since the DCI-based bandwidth portion change can be indicated by the DCI scheduling the PDSCH or PUSCH, when the UE receives a bandwidth portion change request, the PDSCH or PUSCH scheduled by the corresponding DCI may be unreasonable in the changed bandwidth portion. It must be possible to perform reception or transmission without it. For this purpose, the standard stipulates requirements for the delay time (T _BWP ) required when changing the bandwidth portion, and can be defined, for example, as follows.

[Table 3]

Requirements for bandwidth change delay time support type 1 or type 2 depending on the terminal's capability. The terminal can report the supportable bandwidth portion delay time type to the base station.

According to the requirements for the bandwidth portion change delay described above, when the terminal receives a DCI including a 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 no later than T _BWP , and transmission and reception on the data channel scheduled by the relevant DCI can be performed in the new changed bandwidth portion. When the base station wants to schedule a data channel with a new bandwidth portion, it can determine time domain resource allocation for the data channel by considering the bandwidth portion change delay time (T _BWP ) of the terminal. That is, when scheduling a data channel with a new bandwidth portion, the base station can schedule the data channel after the bandwidth portion change delay time in determining time domain resource allocation for the data channel. Accordingly, the terminal may not expect that the DCI indicating a bandwidth portion change indicates a slot offset (K0 or K2) value that is smaller than the bandwidth portion change delay time (T _BWP ).

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

[PDCCH: DCI-related]

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

In the 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel, PUSCH) or downlink data (or Physical Downlink Shared Channel, PDSCH) is transmitted through DCI. It is transmitted from the base station to the terminal. The terminal can monitor the DCI format for fallback and the DCI format for non-fallback for PUSCH or PDSCH. The countermeasure DCI format may consist of fixed fields predefined between the base station and the terminal, and the non-contrast DCI format may include configurable fields.

DCI can be transmitted through PDCCH (Physical Downlink Control Channel), a physical downlink control channel, through channel coding and modulation processes. A CRC (Cyclic Redundancy Check) is attached to the DCI message payload, and the CRC can be scrambled with an RNTI (Radio Network Temporary Identifier) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, for example, UE-specific data transmission, power control command, or random access response. In other words, the RNTI is not transmitted explicitly but is transmitted included in the CRC calculation process. When receiving a DCI message transmitted on the PDCCH, the terminal checks the CRC using the allocated RNTI, and if the CRC check result is correct, the terminal can know that the message was sent to the terminal.

For example, DCI scheduling PDSCH for system information (SI) may be scrambled with SI-RNTI. The DCI that schedules the PDSCH for a Random Access Response (RAR) message can be scrambled with RA-RNTI. DCI scheduling PDSCH for paging messages can be scrambled with P-RNTI. DCI notifying SFI (Slot Format Indicator) can be scrambled with SFI-RNTI. DCI notifying TPC (Transmit Power Control) can be scrambled with TPC-RNTI. The DCI scheduling the 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 at this time, CRC can be scrambled with C-RNTI. DCI format 0_0, in which the CRC is scrambled with C-RNTI, may include, for example, the following information.

[Table 4]

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

[Table 5]

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

[Table 6]

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

[Table 7]

[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, they will be collectively referred to as different antenna ports for convenience). They can be associated with each other by QCL (Quasi co-location) settings as shown in [Table 8] below. The TCI state is to announce the QCL relationship between PDCCH (or PDCCH DMRS) and other RS or channels, and the QCL relationship between a certain reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) is mutually exclusive. QCLed means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at antenna port A to channel measurement from antenna port B. QCL is based on 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, and 4) spatial parameter. Depending on the situation, such as the affected BM (beam management), it may be necessary to associate different parameters. Accordingly, NR supports four types of QCL relationships as shown in Table 8 below.

[Table 8]

The spatial RX parameter is 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, spatial channel correlation, etc. Some or all of them can be collectively referred to.

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

[Table 9]

FIG. 4 is a diagram illustrating an example of base station beam allocation according to TCI state settings.

Referring to FIG. 4, the base station can transmit information about N different beams to the terminal through N different TCI states. For example, when N = 3 as shown in FIG. 4, the base station is associated with CSI-RS or SSB corresponding to beams with different qcl-Type2 parameters included in the three TCI states (400, 405, 410), and QCL type D By setting it to , it can be announced that antenna ports referring to the different TCI states 400, 405, or 410 are associated with different spatial Rx parameters, that is, different beams.

Tables 10 to 14 below show valid TCI state settings according to target antenna port type.

Table 10 shows valid TCI state settings when the target antenna port is CSI-RS for tracking (i.e. TRS). The TRS refers to an NZP CSI-RS in which the repetition parameter among CSI-RSs is not set and trs-Info is set to true. Setting number 3 in Table 10 can be used for aperiodic TRS.

[Table 10] Valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS)

Table 11 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 (e.g., repetition parameter) among CSI-RSs is not set and trs-Info is also not set to true.

[Table 11] Valid TCI state settings when the target antenna port is CSI-RS for CSI

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

[Table 12] Valid TCI state settings when the target antenna port is CSI-RS for BM (for L1 RSRP reporting)

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

[Table 13] Valid TCI state settings when the target antenna port is PDCCH DMRS

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

[Table 14] Valid TCI state settings when the target antenna port is PDSCH DMRS

A representative QCL setting method according to Tables 10 to 14 above is to change the target antenna port and reference antenna port for each step from "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH. It is set and operated as “DMRS, or PDSCH DMRS”. Through this, it is possible to assist the terminal's reception operation by linking the statistical characteristics that can be measured from SSB and TRS to each antenna port.

[PDSCH: Frequency resource allocation related]

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

Figure 5 shows three frequency axis resource allocation methods: type 0 (5-00), type 1 (5-05), and dynamic switch (5-10) that can be set through the upper layer in the NR wireless communication system. This is a drawing showing them.

Referring to FIG. 5, if the terminal is set to use only resource type 0 through higher layer signaling (5-00), some downlink control information (DCI) that allocates the PDSCH to the corresponding terminal is a bit consisting of N_RBG bits. Includes a map. The conditions for this will be explained later. At this time, N_RBG means the number of RBG (resource block group) determined as shown in [Table 15] according to the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and is determined by the bitmap. Data is transmitted to the RBG indicated as 1.

[Table 15]

개의 비트들로 구성되는 주파수 축 자원 할당 정보를 포함한다. 이를 위한 조건은 차후 다시 설명된다. 기지국은 이를 통하여 starting VRB(5-20)와 이로부터 연속적으로 할당되는 주파수 축 자원의 길이(5-25)를 설정할 수 있다.If the terminal is set to use only resource type 1 through upper layer signaling (5-05), some DCIs that allocate PDSCH to the terminal are

Contains frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (5-20) and the length (5-25) of the frequency axis resources continuously allocated from it.

If the terminal is set to use both resource type 0 and resource type 1 through upper layer signaling (5-10), some DCIs that allocate PDSCH to the terminal may require payload (5-15) to set resource type 0. and payload (5-20, 5-25) for setting resource type 1, and includes frequency axis resource allocation information consisting of bits of the larger value (5-35). The conditions for this will be explained later. At this time, one bit (5-30) may be added to the first part (MSB) of the frequency axis resource allocation information in the DCI, and if the corresponding bit (5-30) has the value of '0', resource type 0 is used. Indicated, and if the value is '1', it may be indicated that resource type 1 is used.

[PDSCH/PUSCH: Time resource allocation related]

Below, a time domain resource allocation method for data channels in a next-generation mobile communication system (5G or NR system) is described.

The base station may set a table for time domain resource allocation information for the downlink data channel (PDSCH) and uplink data channel (PUSCH) to the terminal using higher layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of up to maxNrofDL-Allocations=16 entries can be set, and for PUSCH, a table consisting of up to maxNrofUL-Allocations=16 entries can be set up. In one embodiment, the time domain resource allocation information includes the PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0) ), PDCCH-to-PUSCH slot timing (corresponds to the time interval in slot units between the time when PDCCH is received and the time when PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), PDSCH or PUSCH within the slot Information on the location and length of the scheduled start symbol, mapping type of PDSCH or PUSCH, etc. may be included. For example, information such as [Table 16] or [Table 17] below may be transmitted from the base station to the terminal.

[Table 16]

[Table 17]

The base station may notify the terminal of one of the entries in the table for the above-described time domain resource allocation information through L1 signaling (e.g. DCI) (e.g. indicated by the 'time domain resource allocation' field in DCI). possible). The terminal can obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

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

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

[PDSCH: TCI state activation MAC-CE]

Figure 7 shows the process for beam setting and activation of PDSCH. The list of TCI states for PDSCH can be indicated through a higher layer list such as RRC (7-00). The list of TCI states may be indicated, for example, as tci-StatesToAddModList and/or tci-StatesToReleaseList in the PDSCH-Config IE for each BWP. Next, some of the list of TCI states can be activated through MAC-CE (7-20). Among the TCI states activated through the MAC-CE, the TCI state for PDSCH may be indicated through DCI (7-40). The maximum number of activated TCI states can be determined depending on the capabilities reported by the terminal. (7-50) shows an example of the MAC-CE structure for PDSCH TCI state activation/deactivation.

The meaning of each field in the MAC CE and the values that can be set for each field are shown in Table 18 below.

[Table 18]

[PUCCH: Transmission related]

In the NR system, the terminal can transmit control information (UCI) to the base station through PUCCH. Control information includes HARQ-ACK indicating success in demodulating/decoding the TB (transport block) received by the terminal through PDSCH, and SR (scheduling request) in which the terminal requests resource allocation from the PUSCH base station for uplink data transmission. , 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 broadly divided into long PUCCH and short PUCCH depending on the length of the allocated symbol. In the NR system, long PUCCH has a length of 4 symbols or more within a slot, and short PUCCH has a length of 2 symbols or less within a slot.

To describe Long PUCCH in more detail, long PUCCH can be used for the purpose of improving uplink cell coverage, and therefore can be transmitted using DFT-S-OFDM, a single carrier transmission, rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4 depending on the number of control information bits that can be supported and whether UE multiplexing is supported through Pre-DFT OCC support in front of IFFT.

First, PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format that can support up to 2 bits of control information, and uses as much frequency resources as 1 RB. Control information may consist of a combination of HARQ-ACK and SR or each separately. PUCCH format 1 is repeatedly 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.

For example, if the number of transmission symbols in PUCCH format 1 is 8 symbols, starting from the first starting symbol of the 8 symbols, it consists of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol in order. It can be. A DMRS symbol is a sequence corresponding to the length of 1RB on the frequency axis within one OFDM symbol and an orthogonal code (or orthogonal sequence or spreading code, ) and can be transmitted after performing 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 scrambles the generated d(0) by multiplying it by a sequence corresponding to the length of 1 RB on the frequency axis. , an orthogonal code (or orthogonal sequence or spreading code, It can be spread using )) and transmitted after performing IFFT.

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

와 같이 결정되며, 구체적으로 다음 [표 19]와 같이 주어진다. i는 스프레딩 부호 그 자체의 인덱스를 의미하며, m은 스프레딩 부호의 element들의 인덱스를 의미한다. 여기서 [표 19] 내에 [ ]안의 숫자들은

을 의미하며, 가령 스프레딩 부호의 길이가 2이고, 설정된 스프레딩 부호의 인덱스 i=0인 경우, 스프레딩 부호 w_i(m)은

,

이 되어서 w_i(m)=[1 1]이 된다. w _i (m) is given the length of the spreading sign (NSF)

It is determined as follows, and is specifically given as in [Table 19]. i means the index of the spreading sign itself, and m means the index of the elements of the spreading sign. Here, the numbers in [ ] in [Table 19] are

This means that, for example, if the length of the spreading sign is 2 and the index i = 0 of the set spreading sign, the spreading sign w _i (m) is

,

This becomes w _i (m)=[1 1].

[Table 19]

Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support more than 2 bits of control information, and the number of RBs used can be set through the upper layer. Control information may consist 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 20] depending on whether intra-slot frequency hopping and whether additional DMRS symbols are set.

[Table 20]

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

Next, PUCCH format 4 is a DFT-S-OFDM-based long PUCCH format that can support more than 2 bits of control information, and uses 1RB of frequency resources. Control information may consist of a combination or each of HARQ-ACK, SR, and CSI. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 can multiplex PUCCH format 4 of multiple terminals within one RB. It is possible to multiplex PUCCH format 4 of multiple terminals by applying Pre-DFT OCC (Orthogonal Cover Code) to control information in the IFFT front end. However, the number of control information symbols that can be transmitted by one terminal decreases depending on the number of terminals being multiplexed. The number of terminals capable of multiplexing, that is, the number of different OCCs available, can be 2 or 4, and the number of OCCs and the OCC index to be applied can be set through the upper layer.

Next, short PUCCH will be explained. Short PUCCH can be transmitted in both the downlink centric slot and the uplink centric slot, and is generally transmitted in the last symbol of the slot, or in the latter OFDM symbol (e.g., the last OFDM symbol or It can be transmitted in the penultimate OFDM symbol, or the last two OFDM symbols). Of course, it is also possible for Short PUCCH to be transmitted at any location within the 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 situations where uplink cell coverage is good and can be transmitted using CP-OFDM.

Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 depending on the number of control information bits that can be supported. First, PUCCH format 0 is a short PUCCH format that can support up to 2 bits of control information, and uses 1RB of frequency resources. Control information may consist of a combination of HARQ-ACK and SR or each separately. PUCCH format 0 does not transmit DMRS and has a structure that transmits only sequences mapped to 12 subcarriers on the frequency axis within one OFDM symbol. The terminal generates a sequence based on the group hopping or sequence hopping settings received as a higher signal from the base station and the set ID, and the final CS value obtained by adding a different CS value depending on whether it is ACK or NACK to the indicated initial CS (cyclic shift) value. The sequence generated can be cyclically shifted and mapped to 12 subcarriers for transmission.

For example, when HARQ-ACK is 1 bit, the terminal can generate the final CS by adding 6 to the initial CS value if it is ACK, and add 0 to the initial CS if it is NACK, as shown in [Table 21] below. there is. The CS value of 0 for NACK and the CS value of 6 for ACK are defined in the standard, and the terminal can transmit 1-bit HARQ-ACK by generating PUCCH format 0 according to the value defined in the standard.

[Table 21]

For example, when HARQ-ACK is 2 bits, the terminal adds 0 to the initial CS value if (NACK, NACK), adds 3 to the initial CS value if (NACK, ACK), and (ACK) as shown in [Table 22] below. , ACK), 6 is added to the initial CS value, and if (ACK, NACK), 9 is added to the initial CS value. The CS value 0 for (NACK, NACK), the CS value 3 for (NACK, ACK), the CS value 6 for (ACK, ACK), and the CS value 9 for (ACK, NACK) are defined in the standard, and the terminal Can transmit 2-bit HARQ-ACK by generating PUCCH format 0 according to the value defined in the standard. If the final CS value exceeds 12 due to the CS value added to the initial CS value according to ACK or NACK, modulo 12 can be applied to the final CS value because the length of the sequence is 12.

[Table 22]

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

In summary, the configurable values and ranges for each PUCCH format described above can be summarized as shown in [Table 23] below. In [Table 23] below, cases where the value does not need to be set are indicated as N.A.

[Table 23]

Meanwhile, to improve uplink coverage, multi-slot repetition can be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition can be set for each PUCCH format. The terminal can perform repeated transmission on PUCCH including UCI as many slots as set through nrofSlots, which is upper layer signaling. For PUCCH repetitive transmission, the 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 the upper layer signaling, PUCCH-format1 or PUCCH-format3 or PUCCH-format4. You can get it set. For PUCCH repetitive transmission, PUCCH transmission in each slot is performed using the same starting symbol, and the corresponding starting symbol is set through startingSymbolIndex in upper layer signaling, PUCCH-format 1 or PUCCH-format 3 or PUCCH-format 4. You can. For PUCCH repetitive transmission, a single PUCCH-spatialRelationInfo can be set for a single PUCCH resource. For repetitive PUCCH transmission, if the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE can perform frequency hopping on a slot-by-slot basis. Additionally, if the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE starts PUCCH transmission from the first PRB index set through startingPRB, which is upper layer signaling, in the even-numbered slots and starts PUCCH transmission in odd-numbered slots. In the second slot, PUCCH transmission can start from the second PRB index set through secondHopPRB, which is upper layer signaling. Additionally, if the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the index of the slot in which the UE is instructed to transmit the first PUCCH is 0, and for the entire set number of PUCCH repetition transmissions, each slot The PUCCH repetition transmission count value 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 to be configured within the slot when transmitting the PUCCH. If the UE is not configured to perform frequency hopping in PUCCH transmission in different slots, but is configured to perform frequency hopping within the slot, the first and second PRB indexes can be applied equally within the slot. If the number of uplink symbols capable of transmitting PUCCH is smaller than nrofSymbols set for higher layer signaling, the terminal may not transmit PUCCH. Even if the terminal fails to transmit PUCCH for some reason in a slot during repeated PUCCH transmission, the terminal can increase the number of repeated PUCCH transmissions.

[PUCCH: PUCCH resource settings]

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

[Table 24]

According to [Table 24], one or multiple PUCCH resource sets may be set in the PUCCH resource settings for a specific BWP, and a maximum payload value for UCI transmission may be set in some of the PUCCH resource sets. Each PUCCH resource set may include one or multiple PUCCH resources, and each PUCCH resource may belong to one of the above-described PUCCH formats.

For 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 set separately through an upper layer, etc. If 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. The upper layer configuration for the PUCCH resource set may be as shown in [Table 25] below.

[Table 25]

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

If initial connection or the PUCCH resource set is not set, a PUCCH resource set as shown in [Table 26] below, which consists of a number of cell-specific PUCCH resources in the initial BWP, can be used. Within this PUCCH resource set, the PUCCH resource to be used for initial access can be indicated through SIB1.

[Table 26]

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

Next, PUCCH resource selection for UCI transmission is described. In the case of SR transmission, the PUCCH resource for SR corresponding to schedulingRequestID can be set through the upper layer, as shown in [Table 27] below. The PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.

[Table 27]

For the configured PUCCH resource, the transmission period and offset can be set through the periodicityAndOffset parameter in [Table 27]. 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. Otherwise, the corresponding PUCCH resource may not be transmitted.

In the case of CSI transmission, PUCCH resources for transmitting periodic or semi-persistent CSI reports through PUCCH can be set in the pucch-CSI-ResourceList parameter as shown in [Table 28] below. The pucch-CSI-ResourceList parameter may include a list of PUCCH resources for each BWP for the cell or CC that will transmit the 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 can be set through reportSlotConfig in [Table 28].

[Table 28]

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 containing the corresponding HARQ-ACK. That is, a PUCCH resource set with a minimum payload that is no smaller than the UCI payload can be selected. Next, the PUCCH resource within the PUCCH resource set can be selected through the PUCCH resource indicator (PRI) within the DCI that schedules the TB corresponding to the HARQ-ACK, and the PRI is the PUCCH resource specified in [Table 6] or [Table 7]. It can be an indicator. The relationship between PRI and PUCCH resources selected from the PUCCH resource set may be as shown in [Table 29] below.

[Table 29]

If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resource can be selected according to Equation 1 below.

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

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

는 PRI 값,

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

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

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 in 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 the TB transmission corresponding to the HARQ-ACK.

This is after the slot. The candidate value is set to the upper layer, and more specifically, can be set to the dl-DataToUL-ACK parameter in PUCCH-Config specified in [Table 27]. one of these candidates The value may be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI that schedules the TB, and this value may be the value specified in [Table 5] or [Table 6]. Meanwhile, The unit of value may be a slot unit or a subslot unit. Here, a subslot is a unit of length smaller than a slot, and one or multiple symbols can constitute one subslot.

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

[PUCCH: Transmission beam related]

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

는 주어진 뉴머롤로지에서 서브프레임 당 슬롯의 개수를 의미한다. pucch-spatialRelationInfo에 대한 상위 레이어 구성은 다음의 [표 30]과 같을 수 있다.Next, the uplink transmission beam settings to be used for PUCCH transmission will be described. If the UE does not have a UE-specific PUCCH resource configuration (dedicated PUCCH resource configuration), the PUCCH resource set is provided through pucch-ResourceCommon, which is upper layer signaling. At this time, the beam configuration for PUCCH transmission is Random Access. Response (RAR) Follows the beam settings used in PUSCH transmission scheduled through the UL grant. If the UE has a UE-specific PUCCH resource configuration (dedicated PUCCH resource configuration), the beam configuration for PUCCH transmission can be provided through pucch-spatialRelationInfoId, a higher-order signaling included in [Table 24]. If the terminal has been configured with one pucch-spatialRelationInfoId, beam configuration for PUCCH transmission of the terminal can be provided through one pucch-spatialRelationInfoId. If the terminal has been configured with multiple pucch-spatialRelationInfoIDs, the terminal can be instructed to activate one of the multiple pucch-spatialRelationInfoIDs through the MAC CE (control element). The terminal can receive up to eight pucch-spatialRelationInfoIDs through higher-level signaling, and can be instructed that only one pucch-spatialRelationInfoID among them is activated. When the terminal is instructed to activate a random pucch-spatialRelationInfoID through MAC CE, the terminal starts from a slot that transmits HARQ-ACK for the PDSCH on which the MAC CE containing activation information for pucch-spatialRelationInfoID is transmitted.

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

means the number of slots per subframe in a given numerology. The upper layer configuration for pucch-spatialRelationInfo may be as shown in [Table 30] below.

[Table 30]

According to [Table 30], one referenceSignal setting may exist within a specific pucch-spatialRelationInfo setting, and the referenceSignal may be an ssb-Index indicating a specific SS/PBCH, a csi-RS-Index indicating a specific CSI-RS, or Or it may be srs, which represents a specific SRS. If referenceSignal is set to ssb-Index, the terminal sets the beam used to receive the SS/PBCH corresponding to ssb-Index among SS/PBCHs within the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided, The beam used when receiving the SS/PBCH corresponding to ssb-Index among the SS/PBCHs in the cell indicated by servingCellId can be set as the beam for pucch transmission. If referenceSignal is set to csi-RS-Index, the UE sets the beam used to receive the CSI-RS corresponding to the csi-RS-Index among CSI-RSs within the same serving cell as the beam for PUCCH transmission, or If servingCellId is provided, the beam used when receiving the CSI-RS corresponding to the csi-RS-Index among the CSI-RSs in the cell indicated by servingCellId can be set as the beam for pucch transmission. If referenceSignal is set to srs, the terminal 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 as the beam for PUCCH transmission. Alternatively, if servingCellID and/or uplinkBWP are provided, the transmission beam used when transmitting the SRS corresponding to the resource index provided through the upper signaling resource in the cell indicated by servingCellID and/or uplinkBWP and/or in the uplink BWP is used for PUCCH transmission. It can be set as a beam for There may be one pucch-PathlossReferenceRS-Id setting within a specific pucch-spatialRelationInfo setting. PUCCH-PathlossReferenceRS in [Table 31] can be mapped to pucch-PathlossReferenceRS-Id in [Table 30], and up to 4 can be set through pathlossReferenceRSs in the upper signaling PUCCH-PowerControl in [Table 31]. PUCCH-PathlossReferenceRS can receive ssb-Index if connected to SS/PBCH through upper signaling referenceSignal, and csi-RS-Index if connected to CSI-RS.

[Table 31]

[PUCCH: Enable group-based spatial relationships]

In Rel-15, if the terminal has been configured with a plurality of pucch-spatialRelationInfoIDs, the spatial relationship of the corresponding PUCCH resource can be determined by receiving a MAC CE for activating the spatial relationship for each PUCCH resource. However, this method has the disadvantage of requiring a lot of signaling overhead to activate the spatial relationship of multiple PUCCH resources. Therefore, in Rel-16, a PUCCH resource group was added and a new MAC CE was introduced to activate spatial relationships on a PUCCH resource group basis. A PUCCH resource group can set up to 4 PUCCH resource groups through resourceGroupToAddModList in [Table 24], and each PUCCH resource group can set multiple PUCCH resource Ids in one PUCCH resource group as a list as shown in [Table 32]. there is.

[Table 32]

In Rel-16, the base station sets each PUCCH resource group to the terminal through resourceGroupToAddModList in [Table 24] and upper layer settings in [Table 32], and simultaneously (simultaneously) sets the spatial relationship of all PUCCH resources in one PUCCH resource group. You can configure MAC CE to enable it.

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

Referring to the example in FIG. 8, the support cell ID 810 and bandwidth part ID 820 in which the PUCCH resource to which the corresponding MAC CE is applied are set are indicated as Oct 1 (800). PUCCH Resource ID (831, 841) indicates the ID of the PUCCH resource, and if the indicated PUCCH resource is included in the PUCCH resource group according to resourceGroupToAddModList, other PUCCH resource IDs within the same PUCCH resource group are not indicated to the same MAC CE and are Activate all PUCCH resources within the PUCCH resource group with the same Spatial Relation Info ID (836, 846). At this time, Spatial Relation Info ID (836, 846) includes a value corresponding to PUCCH-SpatialRelationInfoId - 1 to be applied to the PUCCH resource group in [Table 30].

[SRS-related]

Next, an uplink channel estimation method using the terminal's Sounding Reference Signal (SRS) transmission is described. The base station can set at least one SRS configuration for each uplink BWP to deliver configuration information for SRS transmission to the terminal, and can also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal can exchange high-level signaling information as follows to deliver information about the SRS resource set.

- srs-ResourceSetId: SRS resource set index

- srs-ResourceIdList: A set of SRS resource indexes referenced in the SRS resource set.

- resourceType: Time axis transmission setting of the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the use of the SRS resource set. If set to 'aperiodic', aperiodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the use of the SRS resource set.

- usage: Setting for the usage of the SRS resource referenced in the SRS resource set, can be set to one of 'beamManagement', 'codebook', 'nonCodebook', and 'antennaSwitching'.

- alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for transmitting power adjustment of the SRS resource referenced in the SRS resource set.

The terminal can understand that the SRS resource included in the set of SRS resource indexes referenced in the SRS resource set follows the information set in the SRS resource set.

Additionally, the base station and the terminal can transmit and receive upper layer signaling information to deliver individual configuration information for SRS resources. For example, individual setting information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information about frequency hopping within or between slots of the SRS resource. . Additionally, individual setting information for the SRS resource may include time axis transmission settings for the SRS resource and may be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. This may be limited to having the same time axis transmission settings as the SRS resource set containing the SRS resource. If the time axis transmission settings of the SRS resource are set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (for example, periodicityAndOffset) may be additionally included in the time axis transmission settings.

The base station may activate, deactivate, or trigger SRS transmission to the UE through higher layer signaling including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, the base station can activate or deactivate periodic SRS transmission through upper layer signaling to the terminal. The base station can instruct to activate an SRS resource set whose resourceType is set to periodic through higher layer signaling, and the terminal can transmit the SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping including the transmission period and slot offset follows periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to the associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit SRS resources within the activated uplink BWP for periodic SRS resources activated through higher layer signaling.

For example, the base station can activate or deactivate semi-persistent SRS transmission through upper layer signaling to the terminal. The base station can instruct to activate the SRS resource set through MAC CE signaling, and the terminal can transmit the SRS resource referenced in the activated SRS resource set. The SRS resource set activated through MAC CE signaling may be limited to an SRS resource set whose resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitting SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping including the transmission period and slot offset follows periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to the associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is set in the SRS resource, the spatial domain transmission filter can be determined by referring to the setting information for spatial relation info delivered through MAC CE signaling that activates semi-persistent SRS transmission without following this. The terminal can transmit an SRS resource within an activated uplink BWP for a semi-persistent SRS resource activated through higher layer signaling.

For example, the base station can trigger aperiodic SRS transmission to the terminal through DCI. The base station may indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of DCI. The terminal may understand that, among the configuration information of the SRS resource set, the SRS resource set including the aperiodic SRS resource trigger indicated through DCI in the aperiodic SRS resource trigger list has been triggered. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource can be determined through the slot offset between the PDCCH including DCI and the SRS resource, which can refer to the value(s) included in the slot offset set set in the SRS resource set. Specifically, the slot offset between the PDCCH including the DCI and the SRS resource may apply the value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set set in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to the associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit an SRS resource within the activated uplink BWP for aperiodic SRS resource triggered through DCI.

When the base station triggers aperiodic SRS transmission to the terminal through DCI, in order for the terminal to transmit SRS by applying configuration information for the SRS resource, the minimum distance between the PDCCH containing the DCI that triggers aperiodic SRS transmission and the transmitted SRS A minimum time interval may be required. The time interval for the UE's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggers aperiodic SRS transmission and the first symbol to which the earliest transmitted SRS resource is mapped among the transmitted SRS resource(s). You can. The minimum time interval can be determined by referring to the PUSCH preparation procedure time required for the UE to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values depending on the use of the SRS resource set including the transmitted SRS resource. For example, the minimum time interval may be set to the N2 symbol defined by considering the terminal processing capability according to the terminal's capabilities with reference to the terminal's PUSCH preparation procedure time. In addition, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval is set to N2 symbol, and the usage of the SRS resource set is 'nonCodebook' Alternatively, if set to 'beamManagement', the minimum time interval can be set to N2+14 symbols. The UE transmits aperiodic SRS when the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, and ignores the DCI triggering aperiodic SRS when the time interval for aperiodic SRS transmission is less than the minimum time interval. You can.

[Table 33]

The spatialRelationInfo setting information in [Table 33] refers to one reference signal and applies the beam information of the reference signal to the beam used for SRS transmission. For example, the setting of spatialRelationInfo may include information as shown in [Table 34] below.

[Table 34]

Referring to the spatialRelationInfo setting, in order to use the beam information of a specific reference signal, the index of the reference signal to be referenced, that is, the SS/PBCH block index, CSI-RS index, or SRS index, can be set. The upper signaling referenceSignal is setting information indicating which reference signal's beam information to refer to for the corresponding SRS transmission, ssb-Index is the index of the SS/PBCH block, csi-RS-Index is the index of CSI-RS, and srs is the index of SRS. Each refers to an index. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the reception beam used when receiving the SS/PBCH block corresponding to ssb-Index as the transmission beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the reception beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmission beam for the corresponding SRS transmission. . If the value of the upper signaling referenceSignal is set to 'srs', the UE can apply the transmission beam used when transmitting the SRS corresponding to srs as the transmission beam for the corresponding SRS transmission.

[PUSCH: Transmission method related]

Next, the scheduling method of PUSCH transmission will be described. PUSCH transmission can be dynamically scheduled by the UL grant in DCI or operated by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

Configured grant Type 1 PUSCH transmission can be set semi-statically through reception of configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 35] through higher-order signaling without receiving the UL grant in DCI. Configured grant Type 2 PUSCH transmission can be scheduled semi-persistently by the UL grant in DCI after receiving configuredGrantConfig that does not include rrc-ConfiguredUplinkGrant of [Table 35] through higher-level signaling. When PUSCH transmission operates by a configured grant, the parameters applied to PUSCH transmission are [ It is applied through configuredGrantConfig, the higher level signaling in Table 38]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the higher-order signaling in [Table 35], the terminal applies tp-pi2BPSK in pusch-Config in [Table 36] to PUSCH transmission operated by the configured grant.

[Table 35]

Next, the PUSCH transmission method will be described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of [Table 36], which is the upper signaling, is 'codebook' or 'nonCodebook'.

As described above, PUSCH transmission can be scheduled dynamically through DCI format 0_0 or 0_1, and can be set semi-statically by a configured grant. If the UE is instructed to schedule PUSCH transmission through DCI format 0_0, the UE transmits PUSCH using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell. Beam setup for transmission is performed, and at this time, PUSCH transmission is based on a single antenna port. The terminal does not expect scheduling for PUSCH transmission through DCI format 0_0 within a BWP in which a PUCCH resource including pucch-spatialRelationInfo is not set. If the terminal has not set txConfig in pusch-Config in [Table 36], the terminal does not expect to be scheduled in DCI format 0_1.

[Table 36]

Next, codebook-based PUSCH transmission is explained. Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1 and can operate semi-statically by configured grant. When the codebook-based PUSCH is scheduled dynamically by DCI format 0_1 or set semi-statically by a configured grant, the terminal uses SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (of the PUSCH transmission layer). Based on the number, the precoder for PUSCH transmission is determined.

At this time, SRI can be given through a field SRS resource indicator in DCI or set through srs-ResourceIndicator, which is higher-level signaling. The terminal receives at least one SRS resource when transmitting a codebook-based PUSCH, and can receive up to two settings. When a terminal receives an SRI through DCI, the SRS resource indicated by the SRI refers to an SRS resource corresponding to the SRI among SRS resources transmitted before the PDCCH containing the SRI. Additionally, TPMI and transmission rank can be given through the field precoding information and number of layers in DCI, or can be set through precodingAndNumberOfLayers, which is higher-level signaling. TPMI is used to indicate the precoder applied to PUSCH transmission. If the terminal receives one SRS resource configured, TPMI is used to indicate the precoder to be applied in one configured SRS resource. If the terminal receives multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

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

The terminal can receive one SRS resource set whose usage value in the upper-level signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within the corresponding SRS resource set can be indicated through SRI. If multiple SRS resources are set in an SRS resource set where the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal sets the value of nrofSRS-Ports in the higher signaling SRS-Resource to the same value for all SRS resources. I look forward to seeing this set up.

The terminal transmits one or more SRS resources included in the SRS resource set with the usage value set to 'codebook' to the base station according to higher-level signaling, and the base station selects one of the SRS resources transmitted by the terminal and sends the corresponding SRS Instructs the terminal to perform PUSCH transmission using the transmission beam information of the resource. At this time, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and is included in DCI. Additionally, the base station includes information indicating the TPMI and rank that the terminal will use for PUSCH transmission in the DCI. The terminal uses the SRS resource indicated by the SRI and performs PUSCH transmission by applying the rank indicated based on the transmission beam of the SRS resource and the precoder indicated by TPMI.

Next, non-codebook-based PUSCH transmission is explained. Non-codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1 and can operate semi-statically by configured grant. If at least one SRS resource is set in the SRS resource set where the usage value in the higher-level signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive non-codebook-based PUSCH transmission scheduled through DCI format 0_1.

For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal can perform calculations on the precoder for SRS transmission through measurement of the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission from the terminal is less than 42 symbols, the terminal updates information about the precoder for SRS transmission. don't expect it to happen

If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by SRS request, 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, a connected NZP CSI-RS exists if the value of the field SRS request in DCI format 0_1 or 1_1 is not '00'. It indicates that At this time, the relevant DCI must not indicate cross carrier or cross BWP scheduling. Additionally, if the value of the SRS request indicates the existence of NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field was transmitted. At this time, the TCI states set in the scheduled subcarrier are not set to QCL-TypeD.

If a periodic or semi-persistent SRS resource set is set, the connected NZP CSI-RS can be indicated through the associatedCSI-RS in the upper signaling SRS-ResourceSet. For non-codebook-based transmission, the terminal does not expect that spatialRelationInfo, the upper-level signaling for the SRS resource, and associatedCSI-RS in the upper-level signaling SRS-ResourceSet are set together.

When a terminal receives a plurality of SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, SRI can be indicated through a field SRS resource indicator in DCI or set through srs-ResourceIndicator, which is higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the terminal receives an SRI through DCI, the SRS resource indicated by the SRI is an SRS resource corresponding to the SRI among the SRS resourcs transmitted before the PDCCH containing the SRI. it means. The terminal can use one or multiple 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 terminal to the base station. It is decided. At this time, SRS resources simultaneously transmitted by the terminal occupy the same RB. The terminal sets one SRS port for each SRS resource. Only one SRS resource set with the usage value in the upper-level signaling SRS-ResourceSet 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 connected to 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 results measured 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 whose usage is set to 'nonCodebook' to the base station, and the base station transmits one or more SRS resources among the one or more SRS resources received. Select SRS resource. At this time, in non-codebook-based PUSCH transmission, SRI represents an index that can express a combination of one or multiple 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 can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[PUSCH: Preparation Course Time]

Next, the PUSCH preparation procedure time will be explained. When the base station schedules the terminal to transmit PUSCH using DCI format 0_0, 0_1, or 0_2, the terminal uses the transmission method indicated through DCI (transmission precoding method of SRS resource, number of transmission layers, spatial domain transmission filter) PUSCH preparation process time may be required to transmit PUSCH by applying . NR took this into consideration and defined the PUSCH preparation process time. The PUSCH preparation process time of the terminal can follow [Equation 2] below.

[Equation 2]

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

- N ₂ : Number of symbols determined according to UE processing capability 1 or 2 and numerology μ according to the capability of the terminal. If the terminal processing capability is reported as 1 according to the terminal's capability report, it has the value in [Table 37], and if it is reported as terminal processing capability 2 and it is set through upper layer signaling that terminal processing capability 2 can be used [Table 38] It can have a value of .

[Table 37]

[Table 38]

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

:64-

:64

또는

중, T_proc,2이 더 크게 되는 값을 따른다. 은 PUSCH를 스케줄링 하는 DCI가 포함된 PDCCH가 전송되는 하향링크의 뉴머롤로지를 뜻하고, 은 PUSCH가 전송되는 상향링크의 뉴머롤로지를 뜻한다.-μ:

or

Among them, T _proc,2 follows the larger value. refers to the numerology of the downlink where PDCCH including DCI for scheduling PUSCH is transmitted, refers to the numerology of the uplink where PUSCH is transmitted.

를 가진다. _-Tc :

has

- d _2,2 : If the DCI scheduling PUSCH indicates BWP switching, the BWP switching time is followed; otherwise, it has 0.

- d ₂ : When PUCCH and the OFDM symbols of the PUSCH with a high priority index and the 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 terminal uses the shared spectrum channel access method, the terminal can calculate T _ext and apply it to the PUSCH preparation process time. Otherwise, T _ext is assumed to be 0.

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

Considering the time axis resource mapping information of the PUSCH scheduled through DCI and the influence of timing advance between uplink and downlink, the base station and the terminal start from the last symbol of the PDCCH including the DCI scheduling the PUSCH after T _proc,2. If the first symbol of the PUSCH starts before the first uplink symbol started by the CP, 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 transmits the PUSCH only when the PUSCH preparation time is sufficient, and if the PUSCH preparation time is not sufficient, the UE may ignore the DCI scheduling the PUSCH.

[PUSCH: Related to repetitive transmission]

In the following, repetitive transmission of the uplink data channel in the 5G system will be described in detail. The 5G system supports two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. The terminal can receive either PUSCH repetitive transmission type A or B through upper layer signaling.

1. 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 repetitive transmissions through higher layer signaling (e.g. RRC signaling) or L1 signaling. The terminal can be notified through (for example, DCI).

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

2. 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 determines the number of repetitive transmissions through upper signaling (e.g. RRC signaling) or L1 signaling (e.g. For example, the terminal can be notified through DCI).

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

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

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

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

는 PUSCH 전송이 시작하는 슬롯을 나타내고

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

The symbol given by and starting from that slot is

is given by The slot where the nth nominal repetition ends is

The symbol given by and ending in that slot is

is given by Here, n=0, ..., numberofprepetitions-1, S represents the start symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel.

indicates the slot where PUSCH transmission starts

represents the number of symbols per slot.

- The terminal determines an invalid symbol for PUSCH repetitive transmission type B. The symbol set for downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is determined as an invalid symbol for PUSCH repetitive 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 or two slots so that invalid symbols can be set. In the bitmap, 1 represents an invalid symbol. Additionally, the period and pattern of the bitmap can be set through upper layer parameters (e.g. periodicityAndPattern). If the upper layer parameter (e.g. InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies an invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If the upper layer parameter (for example, InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies an invalid symbol pattern.

After an invalid symbol is determined, for each nominal repetition, the terminal can 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 contain one or more actual repetitions. Here, each actual repetition contains a continuous set of valid symbols that can be used for PUSCH repetitive transmission type B within one slot.

FIG. 9 is a diagram illustrating an example of PUSCH repetitive transmission type B in a wireless communication system according to an embodiment of the present disclosure.

The terminal can have the start symbol S of the uplink data channel set to 0, the length L of the uplink data channel set to 14, and the number of repeated transmissions set to 16. In this case, nominal repetition appears in 16 consecutive slots (901). Afterwards, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (901) is an invalid symbol. Additionally, the terminal determines symbols set to 1 in the invalid symbol pattern (902) as invalid symbols. In each nominal repetition, if valid symbols other than invalid symbols consist of one or more consecutive symbols in one slot, they are set to actual repetition and transmitted (903).

Additionally, for repetitive PUSCH transmission, NR Release 16 can 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 PUSCH repetitive transmissions are scheduled within one slot or across the boundaries of consecutive slots. Additionally, for method 1, the time domain resource allocation information in the DCI indicates the resource of the first repeated transmission. Additionally, time domain resource information for the first repeated transmission and time domain resource information for the remaining repeated transmissions can be determined according to the 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 PUSCH repeated transmissions are scheduled in consecutive slots through one UL grant. At this time, one transmission is designated for each slot, and each transmission may have a different starting point or different repetition length. Additionally, in method 2, time domain resource allocation information in DCI indicates the starting point and repetition length of all repeated transmissions. Additionally, when performing repetitive transmission within a single slot through method 2, if there are multiple bundles of consecutive uplink symbols within the slot, each repeated transmission is performed for each uplink symbol bundle. If there is a unique set of consecutive uplink symbols in the slot, one PUSCH repetition transmission is performed according to the method of NR Release 15.

- Method 3: Two or more PUSCH repeated transmissions are scheduled in consecutive slots through two or more UL grants. At this time, one transmission is designated for each slot, and the nth UL grant can be received before the PUSCH transmission scheduled for the n-1th 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 boundaries 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 refers to the resources 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 the resource information of at least the first repeated transmission and the uplink or downlink direction of the symbols. If the time domain resource information of the 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. At this time, one repetitive transmission may be included for each uplink period within one slot.

[PUSCH: Frequency hopping process]

Below, frequency hopping of the uplink data channel (PUSCH) in the 5G system will be described in detail.

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

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

[Equation 3]

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

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

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

으로 나타낼 수 있다.

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

represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method.

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

It can be expressed as, and the number of symbols in the second hop is

It can be expressed as

is the length of PUSCH transmission within one slot, expressed as the number of OFDM symbols.

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

The starting RB during a slot can be expressed through Equation 4.

[Equation 4]

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

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

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

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

represents the starting RB within the UL BWP and is calculated from the frequency resource allocation method.

represents the frequency offset between two hops through upper layer parameters.

Next, the inter-repetition frequency hopping method supported by PUSCH repetition transmission type B is to transmit resources allocated in the frequency domain for one or multiple actual repetitions within each nominal repetition by moving them by a set frequency offset. RB _start (n), which is the index of the start RB on the frequency domain for one or multiple actual repetitions in the nth nominal repetition, may follow Equation 5 below.

[Equation 5]

In Equation 5, n is the index of nominal repetition, represents the RB offset between two hops through upper layer parameters.

[Rate matching for UCI multipexed to PUSCH]

In the following, rate matching for uplink control information (UCI) in the 5G system will be described in detail. First, before explaining rate matching for UCI, the case where UCI is multiplexed to PUSCH will be explained. The terminal transmits overlapping PUCCH(s) and PUSCH(s) or multiple overlapping PUCCH(s) for one slot, and the terminal is set to multiplex different UCI types on one PUCCH, and multiple overlapping If at least one of the PUCCH(s) or PUSCH(s) is a signal transmitted according to the UE receiving the DCI format, the timeline condition (timeline condition) as specifically described in Section 9.2.5 of the following 3GPP standard TS 38.213 ) The terminal can multiplex all applicable UCI types that satisfy. As an example of a timeline condition for UCI multiplexing, if either PUCCH transmission or PUSCH transmission is scheduled through DCI, the terminal must transmit the earliest PUCCH or PUSCH among the PUCCH and PUSCH overlapping in the slot. ) UCI multiplexing can be performed only when the symbol S ₀ satisfies the following conditions:

이후에 시작하는 CP를 포함하는 심볼보다 이전에 전송되는 심볼이 아니다. 여기서 는 중첩되는 PUCCH와 PUSCH 그룹 내에 PUCCH로 전송되는 HARQ-ACK과 연관되는 i 번째 PDSCH에 대해

중 최대 값이 된다.

는 i 번째 PDSCH에 대한 처리 과정 시간 (processing procedure time)으로

로 정의된다. 여기서

는 3GPP 규격 TS 38.214 cluase 5.3를 참조하여 i 번째 PDSCH에 대해 결정되는 값이며 N₁은 PDSCH 처리 능력 (processing capability)에 따른 PDSCH 처리 시간 (processing time) 값이다. 그리고 μ는 i 번째 PDSCH를 스케줄링하는 PDCCH, i 번째 PDSCH, i 번째 PDSCH에 대한 HARQ-ACK을 포함하는 PUCCH, 중첩되는 PUCCH와 PUSCH 그룹 중 모든 PUSCH들 중 가장 작은 부반송파 설정 값이 된다. T_C는

이며

는 64이다.- S ₀ starts after the last symbol of the corresponding PDSCH

It is not a symbol transmitted before a symbol containing a CP starting later. here For the ith PDSCH associated with the HARQ-ACK transmitted to the PUCCH within the overlapping PUCCH and PUSCH group

becomes the maximum value.

is the processing procedure time for the ith PDSCH.

It is defined as here

is a value determined for the ith PDSCH with reference to 3GPP standard TS 38.214 clause 5.3, and N ₁ is a PDSCH processing time value according to PDSCH processing capability. And μ is the smallest subcarrier setting value among all PUSCHs among the PDCCH scheduling the i-th PDSCH, the i-th PDSCH, the PUCCH containing HARQ-ACK for the i-th PDSCH, and the overlapping PUCCH and PUSCH groups. T _C is

and

is 64.

This is part of the timeline condition for UCI multiplexing, and when the timeline condition is satisfied by referring to clause 9.2.5 of TS 38.213 of the 3GPP standard, the UE can perform UCI multiplexing on PUSCH. When PUCCH and PUSCH overlap and the timeline conditions for UCI multiplexing specifically described in Section 9.2.5 of 3GPP standard specification TS 38.213, including the above-described example, are satisfied, the terminal accesses PUCCH according to the UCI information included in PUSCH. The included HARQ-ACK and/or CSI information may be multiplexed to PUSCH and PUCCH may not be transmitted.

Afterwards, if the PUCCH and PUSCH overlap and the timeline conditions for UCI multiplexing are satisfied, and the UE decides to multiplex the UCI included in the PUCCH into the PUSCH, the UE performs UCI rate matching for multiplexing the UCI. UCI multiplexing is performed in the following order: HARQ-ACK, CG-UCI (configurd grant uplink control information), CSI part 1, and CSI part 2. The terminal performs rate matching considering the UCI multiplexing order. Therefore, the terminal calculates the coded modulation symbol per layer for HARQ-ACK and CG-UCI and considers this to calculate the coded modulation symbol per layer of CSI part 1. Afterwards, the terminal calculates the coded modulation symbol per layer of CSI part 2 by considering the coded modulation symbol per layer for HARQ-ACK, CG-UCI, and CSI part 1.

When performing rate matching according to each UCI type, a method for calculating the number of coded modulation symbols per layer depending on the repetitive transmission type of the PUSCH on which the UCI is multiplexed and whether uplink data (uplink shared channel, hereinafter referred to as UL-SCH) is included. This is different. For example, when performing rate matching for HARQ-ACK, the coded modulation symbol calculation formula per layer according to PUSCH in which UCI is multiplexed is as follows.

[Equation 6]

[Equation 7]

[Equation 8]

[Equation 6] is the coded modulation symbol calculation formula per layer for HARQ-ACK multiplexed on the PUSCH when the PUSCH including the UL-SCH is not repetitive transmission type B, and [Equation 7] is the formula for calculating the coded modulation symbol per layer for the PUSCH including the UL-SCH. This is the coded modulation symbol calculation formula per layer for HARQ-ACK multiplexed in repetitive transmission type B. [Equation 8] is the coded modulation symbol calculation formula per layer for HARQ-ACK multiplexed to PUSCH that does not include UL-SCH.

는 HARQ-ACK 비트 수이다.

는 HARQ-ACK에 대한 CRC 비트의 수이다.

는 HARQ-ACK에 대한 beta offset으로

와 같다.

는 PUSCH 전송에 대한 UL-SCH의 코드 블록의 수이며,

은 r 번째 코드 블록의 코드 블록 사이즈이다.

는

심볼에 UCI 전송을 위해 이용될 수 있는 resource element의 수를 의미하여

심볼의 DMRS와 PTRS 유무에 따라서 수가 결정된다. 만약

심볼에 DMRS가 포함된다면

이다. DMRS가 포함되지 않는 심볼

에 대해서는

과 같다.

은 PUSCH 전송이 스케줄된 대역폭에 대한 부반송파의 수이며,

는

심볼 내 PTRS를 포함하는 부반송파의 수이다.

는 PUSCH의 전체 심볼 수를 나타낸다.

는 상위 계층 파라미터 scaling이며 이는 전체 PUSCH 전송을 위한 자원 중, UCI가 multiplexing될 수 있는 자원의 비율을 의미한다.

는 첫 번째 DMRS 이후의 DMRS를 포함하지 않는 첫 번째 심볼의 인덱스를 나타낸다. In [Equation 6]

is the number of HARQ-ACK bits.

is the number of CRC bits for HARQ-ACK.

is the beta offset for HARQ-ACK

It's the same.

is the number of code blocks of UL-SCH for PUSCH transmission,

is the code block size of the rth code block.

Is

This refers to the number of resource elements that can be used for UCI transmission in a symbol.

The number is determined depending on the presence or absence of DMRS and PTRS of the symbol. if

If the symbol includes DMRS

am. Symbols that do not contain DMRS

About

Same as

is the number of subcarriers for the bandwidth for which PUSCH transmission is scheduled,

Is

This is the number of subcarriers containing PTRS within the symbol.

represents the total number of symbols of PUSCH.

is upper layer parameter scaling, which means the ratio of resources on which UCI can be multiplexed among all resources for PUSCH transmission.

represents the index of the first symbol that does not include the DMRS after the first DMRS.

은 nominal 반복에 대한 UCI 전송에 이용될 수 있는 resource element의 수를 나타내며 DMRS가 포함된 심볼에 대해서는 0이며 DMRS가 포함되지 않은 심볼에 대해서는

과 같으며

는 nominal 반복을 가정한 PUSCH에 대한

심볼 내 PTRS를 포함하는 부반송파의 수이다.

은 PUSCH의 nominal 반복에 대한 전체 심볼 수를 의미한다.

은 actual 반복에 대한 UCI 전송에 이용될 수 있는 resource element의 수를 나타내며 DMRS가 포함된 심볼에 대해서는 0이며 DMRS가 포함되지 않은 심볼에 대해서는

과 같으며

는 PUSCH의 actual 반복에 대한

심볼 내 PTRS를 포함하는 부반송파의 수이다.

은 PUSCH의 actual 반복에 대한 전체 심볼 수를 의미한다. In [Equation 7]

represents the number of resource elements that can be used for UCI transmission for the nominal repetition, and is 0 for symbols that include DMRS, and is 0 for symbols that do not include DMRS.

It is the same as

is for PUSCH assuming nominal repetition.

This is the number of subcarriers containing PTRS within the symbol.

means the total number of symbols for the nominal repetition of PUSCH.

represents the number of resource elements that can be used for UCI transmission for the actual repetition, and is 0 for symbols that include DMRS and is 0 for symbols that do not include DMRS.

It is the same as

For the actual repetition of PUSCH

This is the number of subcarriers containing PTRS within the symbol.

means the total number of symbols for the actual repetition of PUSCH.

은 PUSCH의 modulation order이다. In [Equation 8], R is the code rate of PUSCH and

is the modulation order of PUSCH.

The number of coded modulation symbols per layer that performed rate matching of CSI part 1 can be calculated similarly to HARQ-ACK, but the maximum number of allocable resources among all resources is excluding the number of coded modulation symbols for HARQ-ACK/CG-UCI. value decreases. The calculation formula for the coded modulation symbol per layer of CSI part 1 is as follows [Equation 9], [Equation 10], [Equation 11] and [Equation 12] depending on the repetitive transmission type of PUSCH and whether or not UL-SCH is included. .

[Equation 9]

[Equation 10]

[Equation 11]

[Equation 12]

와

은 각각 CSI part 1에 대한 비트 수와 CSI part 1에 대한 CRC 비트 수를 의미한다.

는 CSI part 1에 대한 beta offset으로

와 같다.

은 HARQ-ACK 그리고/또는 CG-UCI에 대해 계산된 레이어 당 coded modulation symbol 수이다. 이외 파라미터는 앞서 HARQ-ACK에 대한 레이어 당 coded modulation symbol 수를 계산하는데 필요한 파라미터와 동일하다. [Equation 9] is the coded modulation symbol calculation formula per layer for CSI part 1 multiplexed to the PUSCH in the case of non-PUSCH repetitive transmission type B including UL-SCH, and [Equation 10] is the formula for calculating the coded modulation symbol per layer for PUSCH including UL-SCH. This is the coded modulation symbol calculation formula per layer for CSI part 1 multiplexed in repetitive transmission type B. [Equation 11] is the coded modulation symbol calculation formula per layer for the multiplexed CSI part 1 when CSI part 1 and CSI part 2 are multiplexed in the PUSCH that does not include the UL-SCH. [Equation 12] is the coded modulation symbol calculation formula per layer for CSI part 1 that is multiplexed when CSI part 2 is not multiplexed in PUSCH that does not include UL-SCH. In [Equation 9]

and

means the number of bits for CSI part 1 and the number of CRC bits for CSI part 1, respectively.

is the beta offset for CSI part 1

It's the same.

is the number of coded modulation symbols per layer calculated for HARQ-ACK and/or CG-UCI. Other parameters are the same as those required to calculate the number of coded modulation symbols per layer for HARQ-ACK.

The number of coded modulation symbols per layer performing rate matching of CSI part 2 can be calculated similarly to CSI part 1, but the maximum number of allocable resources among all resources is the number of coded modulation symbols for HARQ-ACK/CG-UCI and CSI. It is reduced to a value excluding the number of coded modulation symbols for part 2. The calculation formula for the coded modulation symbol per layer of CSI part 1 is as follows [Equation 13], [Equation 14], and [Equation 15] depending on the repetitive transmission type of PUSCH and whether UL-SCH is included.

[Equation 13]

[Equation 14]

[Equation 15]

와

은 각각 CSI part 2에 대한 비트 수와 CSI part 2에 대한 CRC 비트 수를 의미한다.

는 CSI part 2에 대한 beta offset으로

와 같다. 이외 파라미터는 앞서 HARQ-ACK 및 CSI part 1에 대한 레이어 당 coded modulation symbol 수를 계산하는데 필요한 파라미터와 동일하다.[Equation 13] is the coded modulation symbol calculation formula per layer for CSI part 2 multiplexed to the PUSCH when the PUSCH including UL-SCH is not repetitive transmission type B, and [Equation 14] is the formula for calculating the coded modulation symbol per layer for the PUSCH including the UL-SCH. This is the coded modulation symbol calculation formula per layer for CSI part 2 multiplexed in repetitive transmission type B. [Equation 15] is the coded modulation symbol calculation formula per layer for CSI part 2 multiplexed to PUSCH that does not include UL-SCH. In [Equation 13]

and

means the number of bits for CSI part 2 and the number of CRC bits for CSI part 2, respectively.

is the beta offset for CSI part 2

It's the same. Other parameters are the same as those required to calculate the number of coded modulation symbols per layer for HARQ-ACK and CSI part 1.

The number of coded modulation symbols per layer that performed rate matching of CG-UCI can also be calculated similarly to HARQ-ACK. The calculation formula for the coded modulation symbol per layer of CG-UCI multiplexed to the PUSCH including the UL-SCH is as in [Equation 16].

[Equation 16]

와

는 각각 CG-UCI의 비트 수와 CG-UCI에 대한 CRC 비트 수를 의미한다.

는 CG-UCI에 대한 beta offset으로

와 같다. 이외 파라미터는 앞서 HARQ-ACK에 대한 레이어 당 coded modulation symbol 수를 계산하는데 필요한 파라미터와 동일하다.In [Equation 16]

and

means the number of bits of CG-UCI and the number of CRC bits for CG-UCI, respectively.

is the beta offset for CG-UCI.

It's the same. Other parameters are the same as those required to calculate the number of coded modulation symbols per layer for HARQ-ACK.

When HARQ-ACK and CG-UCI are multiplexed in a PUSCH including UL-SCH, the number of coded modulation symbols per layer performing rate matching of HARQ-ACK and CG-UCI can be calculated as in [Equation 17]. there is.

[Equation 17]

는 HARQ-ACK에 대한 beta offset으로

과 같으며 이외 파라미터는 앞서 HARQ-ACK에 대한 레이어 당 coded modulation symbol 수를 계산하는데 필요한 파라미터와 동일하다.In [Equation 17]

is the beta offset for HARQ-ACK

The other parameters are the same as those required to calculate the number of coded modulation symbols per layer for HARQ-ACK.

는

으로 계산될 수 있으며 여기서,

은 PUSCH의 전송 레이어의 수,

은 modulation order 그리고

는 UCI 타입에 따른 레이어 당 coded modulation symbol의 수로

또는

또는

또는

일 수 있다. After calculating the number of coded modulation symbols per layer for each UCI type as above, the number of bits for the entire UCI

Is

It can be calculated as, where:

is the number of transport layers of PUSCH,

is the modulation order and

is the number of coded modulation symbols per layer according to UCI type.

or

or

or

It can be.

[Related to reporting terminal capabilities]

In LTE and NR, the terminal can perform a procedure to report the capabilities 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 (UE capability inquiry) message requesting a capability report to the terminal in the connected state. The message may include a terminal capability request for each radio access technology (RAT) type of the base station. The request for each RAT type may include information on combinations of supported frequency bands, etc. Additionally, in the case of the UE 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 may send a UE capability inquiry message including a UE capability request for each RAT type. It can be included multiple times and delivered to the terminal. That is, the UE capability inquiry is repeated multiple times within one message, and the UE can construct a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, terminal capability requests can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). In addition, the terminal capability inquiry message is generally transmitted initially after the terminal is connected to the base station, but the base station can request it under any conditions when necessary.

In the above step, the terminal that has received a 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. Below is a summary of how the terminal configures UE capabilities in the NR system.

One. If the terminal receives a list of LTE and/or NR bands through a UE capability request from the base station, the terminal configures a band combination (BC) for EN-DC and NR stand alone (SA). In other words, a BC candidate list for EN-DC and NR SA is constructed based on the bands requested from the base station through FreqBandList. Additionally, the bands are prioritized in the order listed in FreqBandList.

2. If the base station requests UE capability reporting by setting the “eutra-nr-only” flag or “eutra” flag, the UE completely removes NR SA BCs from the candidate list of configured BCs. This operation can only occur if the LTE base station (eNB) requests “eutra” capability.

3. Afterwards, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, fallback BC means BC that can be obtained by removing the band corresponding to at least one SCell from any BC, because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. It can be omitted. This step also applies to MR-DC, i.e. LTE bands as well. The BCs remaining after this step are the final “candidate BC list”.

4. The terminal selects BCs to report by selecting BCs that fit the requested RAT type from the final “candidate BC list” above. In this step, the terminal configures the supportedBandCombinationList in a given order. In other words, the terminal configures the BC and UE capabilities to be reported in accordance with the order of the preset rat-Type. (nr -> eutra-nr -> eutra). Additionally, a featureSetCombination is constructed for the configured supportedBandCombinationList, and a list of "candidate feature set combinations" is constructed from the candidate BC list from which the list of fallback BCs (containing 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. Additionally, if the requested rat Type is eutra-nr and it affects, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, NR's feature set includes only UE-NR-Capabilities.

After the terminal capability is configured, the terminal transmits a terminal capability information message containing the terminal capability to the base station. The base station then performs appropriate scheduling and transmission/reception management for the terminal based on the terminal capabilities received from the terminal.

[CA/DC related]

FIG. 10 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to an embodiment of the present disclosure.

Referring to Figure 10, the wireless protocols of the next-generation mobile communication system are NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), and NR RLC (Radio Link Control) at the terminal and NR base station, respectively. S35, S60) and NR MAC (Medium Access Control S40, S55).

The main functions of NR SDAP (S25, S70) may include some of the following functions:

- Transfer of user plane data

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

- Marking QoS flow ID in both DL and UL packets for uplink and downlink

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

For the SDAP layer device, the terminal can receive an RRC message to configure whether to use the header of the SDAP layer device or to use the function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel, and the SDAP header When set, the terminal sends uplink and downlink QoS flows and mapping information to the data bearer to the NAS QoS reflection setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflection setting 1-bit indicator (AS reflective QoS) in the SDAP header. You can instruct to update or reset. The SDAP header may include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

The main functions of NR PDCP (S30, S65) 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

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

In the above, the reordering function of the NR PDCP device refers to the function of rearranging the PDCP PDUs received from the lower layer in order based on the PDCP SN (sequence number), and delivering data to the upper layer in the reordered order. may include. Alternatively, the reordering function of the NR PDCP device may include a function of directly forwarding without considering the order, may include a function of reordering the lost PDCP PDUs, and may include a function of recording the lost PDCP PDUs. It may include a function to report the status of PDUs to the transmitting side, and may include a function to request retransmission of lost PDCP PDUs.

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

- Data transfer function (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 function

- Protocol error detection

- RLC SDU deletion function (RLC SDU discard)

- RLC re-establishment function

In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in order. The in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering when one RLC SDU is originally received by being divided into several RLC SDUs, and the received RLC PDUs It may include a function for reordering based on RLC SN (sequence number) or PDCP SN (sequence number), and may include a function for reordering and recording lost RLC PDUs. It may include a function to report status to the transmitting side, and may include a function to request retransmission of lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function of delivering only the RLC SDUs up to the lost RLC SDU in order when there is a lost RLC SDU, or the lost RLC SDU may be transmitted to the upper layer in order. Even if there are RLC SDUs, if a predetermined timer has expired, a function may be included to deliver all RLC SDUs received before the timer starts to the upper layer in order. Alternatively, the in-sequence delivery function of the NR RLC device may include a function of delivering all RLC SDUs received to date to the upper layer in order if a predetermined timer expires even if there are lost RLC SDUs. In addition, the RLC PDUs described above can be processed in the order they are received (in the order of arrival, regardless of the order of the serial number or sequence number) and delivered to the PDCP device out of sequence (out-of sequence delivery). In the case of a segment, It is possible to receive segments stored in a buffer or to be received later, reconstruct them into one complete RLC PDU, process them, and transmit them 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 the multiplexing function of the NR MAC layer.

In the above, the out-of-sequence delivery function of the NR RLC device refers to the function of directly delivering RLC SDUs received from a lower layer to the upper layer regardless of the order, and originally, one RLC SDU is transmitted to multiple RLCs. If it is received divided into SDUs, it may include a function to reassemble and transmit them, and it may include a function to store the RLC SN or PDCP SN of the received RLC PDUs, sort the order, and record lost RLC PDUs. You can.

NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC may include some of the following functions.

- Mapping function (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 function

- Padding function

The NR PHY layer (S45, S50) performs the operation of channel coding and modulating upper layer data, converting it into an OFDM symbol and transmitting it over a wireless channel, or demodulating and channel decoding the OFDM symbol received through a wireless channel and transmitting it to the upper layer. It can be done.

The detailed structure of the wireless protocol structure may vary depending on the carrier (or cell) operation method. For example, when the base station transmits data to the terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure with a single structure for each layer, such as S00. 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 like S10, but a protocol that multiplexes the PHY layer through the MAC layer. structure is used. As another example, when the base station transmits data to the 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 like S20, but transmit data to the PHY layer through the MAC layer. A multiplexing protocol structure is used.

[NC-JT related]

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

Unlike existing systems, the 5G wireless communication system can support not only services that require high transmission speeds, but also services that require very short transmission delays and services that require high connection density. 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 the signal received by the terminal or increases the strength of the signal received by each cell. , TRP or/and inter-beam interference control can be efficiently performed to satisfy various service requirements.

Joint Transmission (JT) is a representative transmission technology for the above-described cooperative communication, and transmits signals to one terminal through multiple different cells, TRPs, or/and beams, thereby measuring the strength or throughput of the signal received by the terminal. It is a technology that increases. At this time, the characteristics of the channel between each cell, TRP or/and beam and the terminal may be significantly different, especially those that support 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. are required depending on the channel characteristics of each cell, TRP or/and link between beam and terminal. You can.

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

FIG. 11 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. 11, examples for PDSCH transmission are explained for each Joint Transmission (JT) technique, and examples for allocating radio resources for each TRP are shown.

Referring to FIG. 11, an example 1100 of Coherent Joint Transmission (C-JT) supporting coherent precoding between each cell, TRP or/and beam is shown.

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

Figure 11 is an example of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP or/and beam for PDSCH transmission (Non-Coherent Joint Transmission) 1120).

In the case of NC-JT, a PDSCH is transmitted to the UE 1135 for each cell, TRP, or/and beam, and individual precoding may be applied to each PDSCH. Each cell, TRP or/and beam can transmit different PDSCHs or different PDSCH layers to the terminal, thereby improving throughput compared to single cell, TRP or/and beam transmission. Additionally, each cell, TRP or/and beam can repeatedly transmit the same PDSCH to the UE, thereby improving reliability compared to single cell, TRP or/and beam transmission. For convenience of explanation, cells, TRPs or/and beams are hereinafter collectively referred to as TRPs.

At this time, if the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1140), and if the frequency and time resources used by multiple TRPs do not overlap at all (1145), Various radio resource allocations may be considered, such as when some of the used frequency and time resources overlap (1150).

To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to one UE.

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

Referring to FIG. 12, case #1 (1200) receives information from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH. In a situation where other (N-1) PDSCHs are transmitted, this is an example in which control information for PDSCHs transmitted in (N-1) additional TRPs is transmitted independently from control information for PDSCHs transmitted in the serving TRP. . That is, the terminal provides control information on PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). It can be obtained. The formats between the independent DCIs may be the same or different, and the payloads between the DCIs may also be the same or different. In case #1 described above, the degree of control or allocation freedom for each PDSCH can be completely guaranteed, but if each DCI is transmitted in different TRPs, there may be a difference in coverage for each DCI, resulting in deterioration of reception performance.

Case #2 (1205) is a different (N-1) from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH. ) In a situation where PDSCHs are transmitted, control information (DCI) for the PDSCHs of (N-1) additional TRPs is transmitted, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP. see.

For example, in the case of DCI#0, which is the 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 In the case of shortened DCI (hereinafter, sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCHs transmitted from TRP#1 to TRP#(N-1), DCI format 1_0, It may contain only some of the information elements of DCI format 1_1 and DCI format 1_2. Therefore, in the case of sDCI, which transmits control information for PDSCHs transmitted from cooperative TRPs, the payload is smaller than normal DCI (nDCI), which transmits control information related to PDSCHs transmitted from serving TRPs, so it is compared with nDCI. Thus, it is possible to include reserved bits.

In the aforementioned case #2, the degree of control or allocation freedom for each PDSCH may be limited depending on the content of the information element included in sDCI, but since the reception performance of sDCI is superior to nDCI, differences in coverage for each DCI may occur. The probability may be lowered.

Case #3 (1210) is a different (N-1) from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH. ) In a situation where PDSCHs are transmitted, one control information for the PDSCHs of (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCHs transmitted from the serving TRP.

For example, in the case of DCI#0, which is the 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 ( It is possible to collect and transmit via sDCI). 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, for information not included in sDCI, such as BWP (bandwidth part) indicator or carrier indicator, the DCI (DCI#0, normal DCI, nDCI) of the serving TRP can be followed.

In case #3 (1210), the control or allocation freedom of each PDSCH may be limited depending on the content of the information element included in sDCI, but the reception performance of sDCI can be adjusted and case #1 (1200) or case #2 Compared to (1205), the complexity of DCI blind decoding of the terminal may be reduced.

Case #4 (1215) is a different (N-1) from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH. ) In a situation where PDSCHs are transmitted, this is an example of transmitting control information for PDSCHs transmitted from (N-1) additional TRPs on the same DCI (Long DCI) as control information for PDSCHs transmitted from serving TRPs. That is, the terminal can obtain control information about PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4 (1215), the complexity of DCI blind decoding of the terminal may not increase, but the number of cooperative TRPs may be limited due to long DCI payload limitations, and the degree of freedom in PDSCH control or allocation may be low.

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

In the following description and embodiments, the cases of case #1 (1200), case #2 (1205), and case #3 (1210), in which more than one DCI (PDCCH) is used to support NC-JT, are used as multiple PDCCH. The case #4 (1215) described above, in which a single DCI (PDCCH) is used to support NC-JT, can be classified as a single PDCCH-based NC-JT. In PDSCH transmission based on Multiple PDCCH, CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and CORESET in which the DCI of the cooperative TRPs (TRP#1 to TRP#(N-1)) are scheduled can be distinguished. Methods for distinguishing CORESETs include a method of distinguishing through upper layer indicators for each CORESET and a method of distinguishing through beam settings for each CORESET. Additionally, in single PDCCH-based NC-JT, a single DCI schedules a single PDSCH with multiple layers instead of scheduling multiple PDSCHs, and the multiple layers described above can be transmitted from multiple TRPs. At this time, the connection relationship between a layer and a TRP transmitting the layer may be indicated through a Transmission Configuration Indicator (TCI) indication for the layer.

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

In embodiments of the present disclosure, “when NC-JT is applied” means “when the terminal receives one or more PDSCHs simultaneously from one BWP” and “when the terminal receives two or more TCIs (Transmission It is possible to interpret it in various ways depending on the situation, such as "when PDSCH is received based on the Configuration Indicator indication" or "when the PDSCH received by the terminal is associated with one or more DMRS port groups." For convenience, one expression was used.

In the present invention, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method (CA-like method) using a structure based on MAC layer multiplexing is possible, similar to S10 of FIG. 10. On the other hand, when the backhaul delay between cooperative TRPs is too large to be ignored (for example, when more than 2 ms is required to exchange information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), similar to S20 in Figure 10 It is possible to secure robust characteristics against delay by using an independent structure for each TRP starting from the RLC layer (DC-like method).

A terminal that supports C-JT / NC-JT can receive C-JT / NC-JT related parameters or setting values from the upper layer settings and set the RRC parameters of the terminal based on this. For upper layer configuration, the UE can utilize UE capability parameters, 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, and 128 in FR1 and 64 and 128 in FR2. It can be set, and among the set number, up to 8 states can be set that can be indicated by 3 bits of the TCI field of DCI through a MAC CE message. The maximum value of 128 means the value indicated by maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in the terminal's capability signaling. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to a beamforming instruction or beamforming change instruction for at least one PDSCH in one TRP.

[Multi-DCI based Multi-TRP]

As an embodiment of the present disclosure, a multi-DCI based multi-TRP transmission method will be described. The multi-DCI based multi-TRP transmission method can set a downlink control channel for NC-JT transmission based on Multi-PDCCH.

In NC-JT based on Multiple PDCCH, when transmitting DCI for the PDSCH schedule of each TRP, there can be a separate CORESET or search space for each TRP. CORESET or search space for each TRP can be set as at least one of the following cases.

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

** In the present disclosure, if the type of CORESETPoolIndex of each of a plurality of CORESETs included in the PDCCH-Config, which is upper layer signaling, exceeds one, that is, if each CORESET has a different CORESETPoolIndex, the terminal is It can be considered that the multi-DCI based multi-TRP transmission method can be used.

** In contrast, in the present disclosure, if each of a plurality of CORESETs included in the PDCCH-Config, which is upper layer signaling, has one type of CORESETPoolIndex, that is, if all CORESETs have the same CORESETPoolIndex of 0 or 1, the terminal It can be considered that the base station transmits using single-TRP rather than using the multi-DCI-based multi-TRP transmission method.

* Multiple PDCCH-Config settings: Multiple PDCCH-Configs are set within one BWP, and each PDCCH-Config may include PDCCH settings for each TRP. In other words, a list of CORESETs for each TRP and/or a list of search spaces for each TRP may 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 CORESET can be distinguished through the beam or beam group set for each CORESET. For example, if the same TCI state is set in multiple CORESETs, the CORESETs may be considered to be transmitted through the same TRP, or the PDCCH scheduling the PDSCH of the same TRP may be considered to be transmitted in the CORESETs.

* Search space beam/beam group configuration: A beam or beam group is configured for each search space, and through this, the TRP for each search space can be distinguished. For example, if the same beam/beam group or TCI state is set in multiple search spaces, the same TRP may be considered to transmit the PDCCH in the search space, or the PDCCH scheduling the PDSCH of the same TRP may be considered to be transmitted in the search space. there is.

By dividing the CORESET or search space by TRP as above, it is possible to classify PDSCH and HARQ-ACK information for each TRP, and through this, it is possible to create an independent HARQ-ACK codebook for each TRP and use an independent PUCCH resource.

The above settings may be independent per cell or per BWP. For example, two different CORESETPoolIndex values may be set for a PCell, while no CORESETPoolIndex value may be set for a specific SCell. 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 SCell for which the CORESETPoolIndex value is not set.

The PDSCH TCI state activation/deactivation MAC-CE applicable to the multi-DCI-based multi-TRP transmission method can follow FIG. 7 above. If the terminal has not set CORESETPoolIndex for each of all CORESETs in the upper layer signaling PDCCH-Config, the terminal can ignore the CORESET Pool ID field (7-55) in the corresponding MAC-CE (7-50). If the terminal can support the multi-DCI-based multi-TRP transmission method, that is, if each CORESET in the terminal's upper layer signaling PDCCH-Config has a different CORESETPoolIndex, the terminal can The TCI state in the DCI included in the PDCCH transmitted in CORESETs with a CORESETPoolIndex value equal to the value of the CORESET Pool ID field (7-55) can be activated. For example, if the value of the CORESET Pool ID field (7-55) in the corresponding MAC-CE (7-50) is 0, the TCI state in the DCI included in the PDCCH transmitted from CORESETs with CORESETPoolIndex of 0 is that of the corresponding MAC-CE. You can follow the activation information.

When the terminal is configured to use the multi-DCI-based multi-TRP transmission method from the base station, that is, when the type of CORESETPoolIndex for each of the plurality of CORESETs included in PDCCH-Config, which is upper layer signaling, exceeds one, or When each CORESET has a different CORESETPoolIndex, the UE can know that the following restrictions exist for PDSCHs scheduled from PDCCHs in each CORESET with two different CORESETPoolIndex.

1) If the PDSCH indicated from the PDCCH in each CORESET having two different CORESETPoolIndex completely or partially overlaps, the UE can apply the TCI states indicated from each PDCCH to different CDM groups. In other words, two or more TCI states may not be applied to one CDM group.

2) If the PDSCH indicated from the PDCCH in each CORESET having two different CORESETPoolIndex completely or partially overlaps, the UE determines the actual number of front loaded DMRS symbols of each PDSCH, the actual number of additional DMRS symbols, the location of the actual DMRS symbol, and the DMRS You can expect the types to not be different from each other.

3) The terminal can expect that the bandwidth indicated from the PDCCH in each CORESET with two different CORESETPoolIndex is the same and the subcarrier spacing is also the same.

4) The terminal can expect that each PDCCH completely contains information about the scheduled PDSCH from the PDCCH in each CORESET with two different CORESETPoolIndex.

[Single-DCI-based Multi-TRP]

As an embodiment of the present disclosure, a single-DCI based multi-TRP transmission method is described. The single-DCI based multi-TRP transmission method can set up a downlink control channel for NC-JT transmission based on single-PDCCH.

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

As another example, if at least one codepoint among all codepoints in the TCI state field in the DCI indicates two TCI states, the terminal may consider that the base station can transmit based on the single-DCI based multi-TRP method. You can. At this time, at least one codepoint indicating two TCI states within the TCI state field can be activated through Enhanced PDSCH TCI state activation/deactivation MAC-CE.

Figure 13 is a diagram showing the Enhanced PDSCH TCI state activation/deactivation MAC-CE structure. The meaning of each field in the MAC CE and the values that can be set for each field are shown in Table 39 below.

[Table 39]

In Figure 13, if the value of the C ₀ field (13-05) is 1, the corresponding MAC-CE includes the TCI state ID _0,2 field (13-15) in addition to the TCI state ID _0,1 field (13-10). It can be included. This means that TCI state ID _0,1 and TCI state ID _0,2 are activated for the 0th codepoint of the TCI state field included in the DCI. If the base station indicates the corresponding codepoint to the terminal, the terminal has two TCI states. You can receive instructions. If the value of the C ₀ field (13-05) is 0, the corresponding MAC-CE cannot include the TCI state ID _0,2 field (13-15), which is the 0th codepoint of the TCI state field included in the DCI. This means that one TCI state corresponding to TCI state ID _0,1 is activated.

The above settings may be independent per cell or per BWP. For example, a PCell may have a maximum of two activated TCI states corresponding to one TCI codepoint, while a specific SCell may have a maximum of one activated TCI state corresponding to one TCI codepoint. In this case, it can be considered that NC-JT transmission is configured in the PCell, while NC-JT transmission is not configured in the SCell described above.

[How to distinguish between Single-DCI based Multi-TRP PDSCH repetitive transmission techniques (TDM/FDM/SDM)]

Next, we describe how to distinguish between single-DCI-based multi-TRP PDSCH repetitive transmission techniques. The UE may receive instructions from the base station for different single-DCI-based multi-TRP PDSCH repetitive transmission techniques (e.g., TDM, FDM, SDM) depending on the value indicated in the DCI field and higher layer signaling settings. Table 40 below shows a method of distinguishing between single or multiple TRP-based techniques indicated to the UE according to the value of a specific DCI field and upper layer signaling settings.

[Table 40]

In Table 40 above, each column can be explained as follows.

- Number of TCI states (column 2): This refers to the number of TCI states indicated by the TCI state field in the DCI, and can be 1 or 2.

- Number of CDM groups (column 3): This refers to the number of different CDM groups of DMRS ports indicated by the Antenna port field in DCI. It can be 1, 2 or 3.

- RepetitionNumber setting and indication conditions (column 4): Three conditions are set depending on whether repetitionNumber is set for all TDRA entries that can be indicated by the Time Domain Resource Allocation field in DCI and whether the actually indicated TDRA entry has a repetitionNumber setting. You can have it.

* Condition 1: At least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field includes a setting for repetitionNumber, and the TDRA entry indicated by the Time Domain Resource Allocation field in the DCI contains a setting for repetitionNumber greater than 1. If it contains

* Condition 2: At least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field includes a setting for repetitionNumber, and the TDRA entry indicated by the Time Domain Resource Allocation field in the DCI does not contain a setting for repetitionNumber. case

* Condition 3: When all TDRA entries that can be indicated by the Time Domain Resource Allocation field do not include a setting for repetitionNumber.

- RepetitionScheme setting related (column 5): Indicates whether repetitionScheme, which is upper layer signaling, is set. RepetitionScheme, which is upper layer signaling, can be set to one of 'tdmSchemeA', 'fdmSchemeA', and 'fdmSchemeB'.

- Transmission technique indicated to the terminal (column 6): Refers to single or multiple TRP techniques indicated according to each combination (column 1) represented in Table 42 above.

* Single-TRP: Refers to single TRP-based PDSCH transmission. If the terminal has been configured with pdsch-AggegationFactor in the upper layer signaling PDSCH-config, the terminal can receive a single TRP-based repetitive PDSCH transmission scheduled for the number of times configured. Otherwise, the UE can schedule a single PDSCH transmission based on a single TRP.

* Single-TRP TDM scheme B: refers to PDSCH repetitive transmission based on time resource division between slots based on a single TRP. According to Condition 1 related to repetitionNumber described above, the terminal repeatedly transmits the PDSCH on the time dimension as many slots as the repetitionNumber number greater than 1 set in the TDRA entry indicated by the Time Domain Resource Allocation field. At this time, the same start symbol and symbol length of the PDSCH indicated by the TDRA entry are applied to each slot as many repetitionNumber times, and the same TCI state is applied to each PDSCH repetition transmission. This technique is similar to the slot aggregation method in that it performs repetitive PDSCH transmission between slots on time resources, but differs from slot aggregation in that it can dynamically determine whether to direct repeated transmission based on the Time Domain Resource Allocation field in DCI. there is.

* Multi-TRP SDM: refers to a multi-TRP based spatial resource division PDSCH transmission method. This is a method of receiving layers separately from each TRP. Although it is not a repetitive transmission method, it can increase the reliability of PDSCH transmission in that it can be transmitted by lowering the coding rate by increasing the number of layers. The UE can receive the PDSCH by applying the two TCI states indicated through the TCI state field in the DCI to each of the two CDM groups indicated by the base station.

* Multi-TRP FDM scheme A: This refers to a multi-TRP based frequency resource division PDSCH transmission method. It has one PDSCH transmission location (occasion), so it is not a repetitive transmission like multi-TRP SDM, but it increases the amount of frequency resources and lowers the coding rate. This is a technique that can transmit with high reliability. Multi-TRP FDM scheme A can apply two TCI states indicated through the TCI state field in DCI to frequency resources that do not overlap each other. If the PRB bundling size is determined to be wideband, the UE applies the first TCI state to the first ceil (N/2) RBs when the number of RBs indicated in the Frequency Domain Resource Allocation field is N, and the remaining floor (N/ 2) RBs receive by applying the second TCI state. Here, ceil(.) and floor(.) are operators that mean rounding up and rounding down to the first decimal place. If the PRB bundling size is set to 2 or 4, even-numbered PRGs receive the first TCI state, and odd-numbered PRGs receive the second TCI state.

* Multi-TRP FDM scheme B: refers to a multi-TRP based frequency resource division PDSCH repetitive transmission method. It has two PDSCH transmission positions (occasions), so the PDSCH can be transmitted repeatedly to each position. Multi-TRP FDM scheme B, like A, can apply two TCI states indicated through the TCI state field in DCI to frequency resources that do not overlap each other. If the PRB bundling size is determined to be wideband, the UE applies the first TCI state to the first ceil (N/2) RBs when the number of RBs indicated in the Frequency Domain Resource Allocation field is N, and the remaining floor (N/ 2) RBs receive by applying the second TCI state. Here, ceil(.) and floor(.) are operators that mean rounding up and rounding down to the first decimal place. If the PRB bundling size is set to 2 or 4, even-numbered PRGs receive the first TCI state, and odd-numbered PRGs receive the second TCI state.

* Multi-TRP TDM scheme A: Refers to a PDSCH repetitive transmission scheme within a multi-TRP-based time resource division slot. The terminal has two PDSCH transmission positions (occasions) within one slot, and the first reception position can be determined based on the start symbol and symbol length of the PDSCH indicated through the Time Domain Resource Allocation field in the DCI. The starting symbol of the second reception position of the PDSCH can be a position where a symbol offset is applied from the last symbol of the first transmission position by StartingSymbolOffsetK, which is upper layer signaling, and the transmission position can be determined by the symbol length indicated from this. If StartingSymbolOffsetK, which is upper layer signaling, is not set, the symbol offset can be considered 0.

* Multi-TRP TDM scheme B: Refers to a PDSCH repetitive transmission scheme between multiple TRP-based time resource division slots. The terminal has one PDSCH transmission location (occasion) within one slot, and receives repeated transmissions based on the start symbol and symbol length of the same PDSCH during slots equal to the repetitionNumber number indicated through the Time Domain Resource Allocation field in the DCI. can do. If repetitionNumber is 2, the UE can receive PDSCH repetition transmissions in the first and second slots by applying the first and second TCI states, respectively. If repetitionNumber is greater than 2, the terminal can use different TCI state application methods depending on which tciMapping, which is upper layer signaling, is set. If tciMapping is set to cyclicMapping, the first and second TCI states are applied to the first and second PDSCH transmission positions, respectively, and this TCI state application method is equally applied to the remaining PDSCH transmission positions. If tciMapping is set to sequentialMapping, the first TCI state is applied to the first and second PDSCH transmission locations, the second TCI state is applied to the third and fourth PDSCH transmission locations, and this TCI state application method is used for the remaining The same applies to the PDSCH transmission location.

[Related to RLM RS]

Next, we describe how to select or determine RLM RS (Radio Link Monitoring Reference Signal) when it is set or not set. The terminal can receive a set of RLM RSs from the base station through RadioLinkMonitoringRS in RadioLinkMonitoringConfig, which is upper layer signaling, for each downlink bandwidth part of SpCell, and the specific upper layer signaling structure can follow Table 41 below.

[Table 41]

Table 42 below shows the number of RLM RSs that can be set or selected for each specific application depending on the maximum number of SSBs per half frame (L _max ). As shown in Table 44 below, depending on the L _max value, N _LR-RLM RSs can be used for link recovery or radio link monitoring purposes, and among the N _LR-RLM RSs, N _RLM RSs can be used for radio link monitoring purposes.

[Table 42]

If the terminal has not been configured with RadioLinkMonitoringRS, which is upper layer signaling, and the TCI state for receiving PDCCH has been set in the control resource set and at least one CSI-RS is included in the TCI state, the following RLM RS selection method You can choose RLM RS according to your needs.

- RLM RS selection method 1) If the activated TCI state to be used for PDCCH reception has one reference RS (i.e., if one activated TCI state has only one of QCL-TypeA, B, or C), The UE can select the reference RS of the activated TCI state to be used for PDCCH reception as the RLM RS.

- RLM RS selection method 2) If the activated TCI state to be used for PDCCH reception has two reference RSs (i.e., one activated TCI state has one of QCL-TypeA, B, or C and QCL-Type (when additionally having TypeD), the UE can select the reference RS of QCL-TypeD as RLM-RS. The terminal does not expect two QCL-TypeDs to be set in one activated TCI state.)

- RLM RS selection method 3) The terminal does not expect an aperiodic or semi-persistent RS to be selected as the RLM RS.

- RLM RS selection method 4) If L _max = 4, the terminal can select N _RLM (since L _max is 4, 2 can be selected) RS. The selection of the RLM RS is performed among the reference RSs of the TCI state set in the control resource set for PDCCH reception, based on the RLM RS selection methods 1 to 3, and the short period of the search space to which the control resource set is connected is selected as high. Judging by priority, RLM RS selection is performed starting from the reference RS of the TCI state set in the control resource set connected to the search space of the shortest period. If there are multiple control resource sets connected to multiple search spaces with the same period, RLM RS selection is performed starting from the reference RS of the TCI state set at the high control resource set index.

Figure 14 is a diagram illustrating the RLM RS selection process according to an embodiment of the present disclosure. This figure shows control resource set #1 to control resource set #3 (14-04) connected to search space #1 to search space #4 (14-01 to 14-04) having different cycles within the activated downlink bandwidth part. 05 to 14-07) and the reference RS of the TCI state set in each control resource set. Based on the RLM RS selection method 4 above, RLM RS selection uses the TCI state set in the control resource set connected to the search space of the shortest period, but search space #1 (14-01) and search space #3 (14- Since the period of 03) is the same, the reference of the TCI state set in control resource set #2 with the higher index among control resource set #1 (14-05) and control resource set #2 (14-06) connected to each search space. RS can be used as the highest priority in RLM RS selection. In addition, the TCI state set in control resource set #2 has only QCL-TypeA, and the reference RS is a periodic RS, so P CSI-RS #2 (14-10) by the RLM RS selection methods 1 and 3 can be selected as the RLM RS first. Next, among the reference RSs of the TCI state set in the control resource set #1 with priority, the reference RS of QCL-TypeD can be a selection candidate by the RLM RS selection method 2, but the RS is semi-persistent. Since it is an RS (14-09), it is not selected as an RLM RS by the RLM RS selection method 3 above. Therefore, the reference RSs of the TCI state set in control resource set #3 can be considered as the next priority, and by the RLM RS selection method 2, the reference RS of QCL-TypeD can be a selection candidate, and the reference RS can be selected periodically. Since it is a (periodic) RS, P CSI-RS#4 (14-12) can be selected as the second RLM RS by RLM RS selection method 3 above. Therefore, the final selected RLM RS can be P CSI-RS#2 and P CSI-RS#4 (14-13).

For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, or /and transmission direction can be unified and described as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.

Hereinafter, in this disclosure, when determining whether to apply cooperative communication, the terminal determines whether the PDCCH(s) allocating the PDSCH to which cooperative communication is applied has a specific format, or the PDCCH(s) allocating the PDSCH to which cooperative communication is applied is cooperative. It contains a specific indicator indicating whether communication is applied, or the PDCCH(s) allocating the PDSCH to which cooperative communication is applied is scrambled with a specific RNTI, or assumes application of cooperative communication in a specific section indicated by the upper layer, etc. It is possible to use a variety of methods. For convenience of explanation, the case where the UE receives a PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.

Hereinafter, embodiments of the present disclosure will be described in detail with the accompanying drawings. Hereinafter, the base station is an entity that performs resource allocation for the terminal and may be at least one of gNode B, gNB, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network. A terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Hereinafter, embodiments of the present disclosure will be described using the 5G system as an example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel types. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Accordingly, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person skilled in the art. The content in this disclosure is applicable to FDD and TDD systems. Hereinafter, in the present disclosure, higher signaling (or higher layer signaling) is a signal transmission method in which a signal is transmitted from a base station to a terminal using a downlink data channel of the 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 medium access control (MAC) control element (CE).

Additionally, when describing the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

In describing the present disclosure below, upper 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

- RRC (Radio Resource Control)

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

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

- PDCCH (Physical Downlink Control Channel)

- DCI (Downlink Control Information)

- UE-specific DCI

- Group common DCI

- Common DCI

- Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

- Non-scheduled DCI (e.g. DCI not intended for scheduling 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 the one with the higher priority and performing the corresponding operation according to a predetermined priority rule, or selecting the one with the lower priority. It can be mentioned in various ways, such as omit or drop the action.

Hereinafter, the term slot used in the present disclosure is a general term that can refer to a specific time unit corresponding to TTI (Transmit Time Interval). Specifically, it may refer to a slot used in a 5G NR system, or a 4G LTE system. It may also mean a slot or subframe used in.

Hereinafter, in the present disclosure, the above examples are described through a number of embodiments, but these are not independent examples, and it is possible for one or more embodiments to be applied simultaneously or in combination.

<First embodiment: Single TCI state activation and indication method based on integrated TCI method>

As an example of an embodiment of the present disclosure, a method for indicating and activating a single TCI state based on the integrated TCI method is described. The integrated TCI method is a method of managing the transmission and reception beam management methods, which were differentiated into the TCI state method used in downlink reception of the terminal in the existing Rel-15 and 16 and the spatial relation info method used in uplink transmission, into the TCI state. It can mean. Therefore, when the terminal receives a TCI state indication from the base station based on the integrated TCI method, it can perform beam management using the TCI state even for uplink transmission. If the terminal has been configured with a TCI-State, which is higher layer signaling, and has tci-stateId-r17, which is higher layer signaling, from the base station, the terminal can use the corresponding TCI-State to perform operations based on the integrated TCI method. TCI-State can exist in two forms: joint TCI state or separate TCI state.

The first type is the joint TCI state, and the terminal can receive instructions from the base station of both the TCI state to be applied to uplink transmission and downlink reception through one TCI-State. If the UE is instructed to use a TCI-State based on the joint TCI state, the UE uses the RS corresponding to qcl-Type1 in the TCI-State based on the joint TCI state to determine parameters to be used for downlink channel estimation and qcl-Type2. Parameters to be used as a downlink reception beam or reception filter can be indicated using the corresponding RS. If the UE is instructed to use a TCI-State based on the joint TCI state, the UE uses the RS corresponding to qcl-Type2 in the TCI-State based on the joint DL/UL TCI state to set parameters to be used as an uplink transmission beam or transmission filter. You can receive instructions. At this time, if the terminal is instructed to TCI-State based on the joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

The second type is a separate TCI state, and the terminal can be individually instructed by the base station of the UL TCI state to be applied to uplink transmission and the DL TCI state to be applied to downlink reception. If the UE is instructed to use the UL TCI state, the UE can be instructed to use the reference RS or source RS set in the UL TCI state for parameters to be used as an uplink transmission beam or transmission filter. If the UE is instructed to use a DL TCI state, the UE sets parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 set in the DL TCI state, and downlink using the RS corresponding to qcl-Type2. Parameters to be used as a reception beam or reception filter can be instructed.

If the UE is instructed to use the DL TCI state and the UL TCI state together, the UE can be instructed on the parameters to be used as an uplink transmission beam or transmission filter using the reference RS or source RS set in the UL TCI state, and the DL Parameters to be used for downlink channel estimation can be indicated using the RS corresponding to qcl-Type1 set in the TCI state, and parameters to be used as a downlink reception beam or reception filter can be indicated using the RS corresponding to qcl-Type2. At this time, if the DL TCI state indicated by the UE and the reference RS or source RS set in the UL TCI state are different, the UE applies an uplink transmission beam based on the indicated UL TCI state and based on the DL TCI state. A downlink reception beam can be applied.

The terminal can receive up to 128 joint TCI states from the base station as upper layer signaling for each specific bandwidth part (BWP) within a specific cell, and among the separate TCI states, the DL TCI state is based on the UE capability report. Up to 64 or 128 upper layer signaling can be set for each specific bandwidth part within a specific cell, and among separate TCI states, the DL TCI state and joint TCI state can use the same upper layer signaling structure. For example, if 128 joint TCI states are set and 64 DL TCI states are set among the separate TCI states, the 64 DL TCI states can be included in 128 joint TCI states.

Among separate TCI states, UL TCI state can be set to upper layer signaling up to 32 or 64 for each specific bandwidth part within a specific cell based on UE capability report, and the relationship between DL TCI state and joint TCI state among separate TCI states. Likewise, the UL TCI state and the joint TCI state among separate TCIs may also use the same upper layer signaling structure, and the UL TCI state among separate TCIs may use a different upper layer signaling structure from the DL TCI state among the joint TCI state and separate TCI states. It may be possible. In this way, using different or the same upper layer signaling structures may be defined in the standard, or another method set by the base station based on the terminal capability report containing information on whether or not the terminal can support one of the two usage methods. They may also be distinguished through upper layer signaling.

The terminal can receive transmission/reception beam-related instructions in the integrated TCI method using either the joint TCI state or the separate TCI state set by the base station. The terminal can be configured through upper layer signaling from the base station as to whether to use one of the joint TCI state and the separate TCI state.

The UE receives instructions related to transmission and reception beams using one of the joint TCI state and separate TCI state through upper layer signaling. At this time, the transmission and reception beam instruction methods from the base station are MAC-CE-based instruction method and MAC-CE-based instruction method. There can be two methods: activation and DCI-based indication.

If the terminal is set to receive instructions related to transmission and reception beams using the joint TCI state method through upper layer signaling, the terminal can perform transmission and reception beam application operations by receiving a MAC-CE indicating the joint TCI state from the base station. , the base station can schedule the terminal to receive a PDSCH including the corresponding MAC-CE through the PDCCH. If the MAC-CE includes one joint TCI state, the terminal transmits a PUCCH including HARQ-ACK information indicating successful reception of the PDSCH including the MAC-CE to the base station, and the PUCCH Starting 3 ms after transmission, the indicated joint TCI state can be used to determine the uplink transmission beam or transmission filter and the downlink reception beam or reception filter. If there are two or more joint TCI states included in the MAC-CE, the terminal transmits a PUCCH including HARQ-ACK information indicating successful reception of the PDSCH including the MAC-CE to the base station, and the PUCCH Starting 3 ms after transmission, a plurality of joint TCI states indicated by MAC-CE are confirmed to correspond to each code point in the TCI state field of DCI format 1_1 or 1_2, and the joint TCI state indicated by MAC-CE can be activated. . Afterwards, the terminal can receive DCI format 1_1 or 1_2 and apply one joint TCI state indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beam. At this time, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include (without DL assignment).

If the terminal is set to receive instructions related to transmission and reception beams using the separate TCI state method through upper layer signaling, the terminal can receive a MAC-CE indicating separate TCI state from the base station and perform transmission and reception beam application operations. And the base station can schedule a PDSCH including the corresponding MAC-CE to the terminal through the PDCCH. If the set of separate TCI states included in the MAC-CE is 1, the terminal transmits a PUCCH including HARQ-ACK information indicating successful reception of the PDSCH to the base station, starting 3 ms after transmission of the PUCCH. The uplink transmission beam or transmission filter and the downlink reception beam or reception filter can be determined using the separate TCI states included in the indicated separate TCI state set. At this time, the separate TCI state set may mean single or multiple separate TCI states that one codepoint of the TCI state field in DCI format 1_1 or 1_2 can have, and one separate TCI state set is one DL TCI state. It may include, may include one UL TCI state, or may include one DL TCI state and one UL TCI state. If the set of separate TCI states included in the MAC-CE is two or more, the terminal transmits a PUCCH including HARQ-ACK information indicating successful reception of the PDSCH to the base station, and 3 ms after transmission of the PUCCH It is possible to confirm that a plurality of separate TCI state sets indicated by MAC-CE correspond to each code point of the TCI state field of DCI format 1_1 or 1_2 and activate the indicated separate TCI state set. At this time, each code point in the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. . The terminal can receive DCI format 1_1 or 1_2 and apply a separate TCI state set indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beam. At this time, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (i.e., with DL assignment) or may not include (i.e., without DL assignment).

The MAC-CE used to activate or indicate the single joint TCI state and separate TCI state described above may exist for each joint and separate TCI state method, and one MAC-CE can be used to select one of the joint or separate TCI state methods. Based on this, the TCI state can be activated or indicated. Through the drawings described later, various MAC-CE structures for joint or separate TCI state activation and indication can be considered.

FIG. 15 is a diagram showing a MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 15, the S field (15-00) may indicate the number of joint TCI state information included in MAC-CE. If S If the value of field (15-00) is 1, the corresponding MAC-CE can indicate one joint TCI state and can have a length of up to the 2nd Octet. If the value of the S field (15-00) is 0, the corresponding MAC-CE may include two or more joint TCI state information, and each joint TCI at each code point of the TCI state field of DCI format 1_1 or 1_2. A state can be activated, and up to 8 joint TCI states can be activated. Setting the 0, 1 value of the S field (15-00) is not limited to the above setting method. When the value is 0, it indicates including one joint TCI state, and when the value is 1, it indicates including information on two or more joint TCI states. You can also indicate what to include. This analysis of the S field can also be applied to other embodiments of the present invention. The TCI states indicated through the TCI state ID ₀ field (15-15) to the TCI state ID _N-1 field (15-25) are the 0th to N-1th codepoints of the TCI state field of DCI format 1_1 or 1_2, respectively. can correspond to . The Serving Cell ID field (15-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (15-10) may indicate the bandwidth part ID. The R field may be a 1-bit reserve field that does not contain indicating information.

FIG. 16 is a diagram illustrating another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 16, the Serving Cell ID field (16-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (16-10) may indicate the bandwidth part ID. The R field (16-00) may be a 1-bit reserve field that does not contain indicating information. Each field in the 2nd to Nth Octet is a bitmap that represents the joint TCI state set to upper layer signaling. For example, T ₇ (16-15) may be a field indicating whether the 8th joint TCI state set as upper layer signaling is indicated. If the T _N value is 1, the corresponding joint TCI state can be interpreted as indicated or activated, and if the value is 0, the corresponding joint TCI state can be interpreted as not indicated or activated. Setting the values of 0 and 1 is not limited to the above setting method. If there is one joint TCI state transmitted through the MAC-CE structure of FIG. 16, the terminal can apply the joint TCI state indicated by MAC-CE to the uplink transmission and downlink reception beam. If there are two or more joint TCI states transmitted through the MAC-CE structure, the terminal confirms that each joint TCI state indicated by MAC-CE corresponds to each codepoint in the TCI state field of DCI format 1_1 or 1_2 and The joint TCI state can be activated, and can be activated in order from the joint TCI state with the lowest index among the indicated joint TCI states, corresponding to the codepoints of the low index of the TCI state field of DCI format 1_1 or 1_2. there is.

FIG. 17 is a diagram illustrating another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 17, the Serving Cell ID field (17-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (17-10) may indicate the bandwidth part ID.

The S field (17-00) may indicate the number of joint TCI state information included in MAC-CE. For example, if S If the value of the field (17-00) is 1, the corresponding MAC-CE can indicate one joint TCI state, can include only up to the 2nd octet, and can be accessed by the terminal through the TCI state ID ₀ field (17-20). The joint TCI state may be indicated to. For example, if the value of the S field (17-00) is 0, the corresponding MAC-CE may include two or more joint TCI state information, and each code point in the TCI state field of DCI format 1_1 or 1_2 is each The joint TCI state can be activated, up to 8 joint TCI states can be activated, the 2nd Octet does not exist, and the N+1th Octet from the 1st and 3rd Octet in the MAC-CE structure of FIG. 17 This can exist. Each field present in the 3rd to N+1th Octet is a bitmap that represents the joint TCI state set by upper layer signaling. For example, T ₁₅ (17-25) may be a field indicating whether the 16th joint TCI state set as upper layer signaling is indicated. The R field (17-15) may be a 1-bit reserve field that does not contain indicating information.

If there is one joint TCI state transmitted through the MAC-CE structure of FIG. 17, the terminal can apply the joint TCI state indicated by MAC-CE to the uplink transmission and downlink reception beam. If there are two or more joint TCI states transmitted through the MAC-CE structure of FIG. 17, the terminal corresponds to each joint TCI state indicated by MAC-CE to each code point in the TCI state field of DCI format 1_1 or 1_2. You can check and activate each joint TCI state, and among the joint TCI states indicated, the joint TCI state with the lowest index corresponds to the low-index code point of the TCI state field of DCI format 1_1 or 1_2 in order. It can be activated.

FIG. 18 is a diagram illustrating a MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 18, the Serving Cell ID field (18-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (18-10) may indicate the bandwidth part ID.

The S field (18-00) may indicate the number of separate TCI state set information included in MAC-CE. For example, if S If the value of field (18-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set and can include only up to the 3rd Octet. For example, if the value of the S field (18-00) is 0, the corresponding MAC-CE may include two or more separate TCI state set information, and each code point in the TCI state field of DCI format 1_1 or 1_2 is respectively A set of separate TCI states can be activated, and up to 8 separate TCI state sets can be activated. The C ₀ field (18-15) may be a field indicating which separate TCI states the indicated separate TCI state set includes. For example, if the value of the C ₀ field is “00”, reserve, if “01”, 1 DL TCI state, if “10”, 1 UL TCI state, and if “11”, 1 DL TCI state and 1 UL TCI state are indicated. However, this is only an example of the interpretation of the C ₀ field (18-15), and the interpretation of the C ₀ field (18-15) is not limited to this. The TCI state ID _D,0 field (18-20) and the TCI state ID _U,0 field (18-25) mean the DL TCI state and UL TCI state that can be indicated and included in the 0th separate TCI state set, respectively. You can. If the value of the C ₀ field is “01”, the TCI state ID _D,0 field (18-20) can indicate the DL TCI state, and the TCI state ID _U,0 field (18-25) can be ignored. . If the value of the C ₀ field is “10”, the TCI state ID _D,0 field (18-20) can be ignored, and the TCI state ID _U,0 field (18-25) can indicate the UL TCI state. If the value of the C ₀ field is “11”, the TCI state ID _D,0 field (18-20) can indicate the DL TCI state, and the TCI state ID _U,0 field (18-25) can indicate the UL TCI state. there is.

FIG. 18 may illustrate an example of MAC-CE when the UL TCI state among the separate TCI states uses a higher layer signaling structure such as the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the length of the TCI state ID _D,0 field (18-20) and the TCI state ID _U,0 field (18-25) can be 7 bits to represent up to 128 TCI states. Therefore, in order to use 7 bits as the TCI state ID _D,0 field (18-20), 6 bits (18-20) can be allocated to the 2nd Octet and 1 bit (18-21) can be allocated to the 3rd Octet. Additionally, FIG. 18 may indicate a case where the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the UL TCI state requires 6 bits that can express up to 64, so the first bit of the TCI state ID _U,0 field (18-25) can be fixed to 0 or 1, and the actual UL TCI state The bits to be expressed can only be a total of 6 bits from the 2nd to the 7th bit.

FIG. 19 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 19, the Serving Cell ID field (19-05) may indicate a serving cell ID, and the BWP ID field (19-10) may indicate a bandwidth part ID. The S field (19-00) may indicate the number of separate TCI state set information included in MAC-CE. For example, if S If the value of field (19-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set and can include only up to the 3rd Octet. If, for example, the value of the S field (19-00) is 0, the corresponding MAC-CE may include two or more separate TCI state set information, and each codepoint in the TCI state field of DCI format 1_1 or 1_2 is each Each separate TCI state set can be activated in response to a separate TCI state set, and up to 8 separate TCI state sets can be activated. The C _D,0 field (19-15) may be a field indicating whether the indicated separate TCI state set includes the DL TCI state. If the value of the C _D,0 field (19-15) is 1, the DL TCI state and can indicate the DL TCI state through the TCI state ID _D,0 field (19-25). If the value of the C _D,0 field (19-15) is 0, it does not include the DL TCI state and can indicate the TCI state. ID _D,0 fields (19-25) can be ignored. Similarly, the C _U,0 field (19-20) may be a field indicating whether the indicated separate TCI state set includes the UL TCI state, and the value of the C _U,0 field (19-20) is If it is 1, it includes the UL TCI state and the UL TCI state can be indicated through the TCI state ID _U,0 field (19-30). If the value of the C _U,0 field (19-20) is 0, it includes the UL TCI state. Otherwise, the TCI state ID _U,0 field (19-30) can be ignored.

FIG. 19 may illustrate an example of MAC CE when the UL TCI state among the separate TCI states uses a higher layer signaling structure such as the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the length of the TCI state ID _D,0 field (19-25) and the TCI state ID _U,0 field (19-30) can be 7 bits to express up to 128 TCI states. Additionally, FIG. 19 may illustrate an example of MAC CE when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the UL TCI state requires 6 bits to represent up to 64, so the first bit of the TCI state ID _U,0 field (19-25) can be fixed to 0 or 1, and the actual UL TCI state The bits to be expressed can only be a total of 6 bits from the 2nd to the 7th bit.

FIG. 20 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 20, the Serving Cell ID field (20-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (20-10) may indicate the bandwidth part ID. The S field (20-00) may indicate the number of separate TCI state set information included in MAC-CE. For example, if S If the value of field (20-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set and can include only up to the 3rd Octet. The MAC-CE structure of FIG. 20 can indicate one separate TCI state set using two octets, and if the separate TCI state set includes the DL TCI state, the first octet of the two octets is the DL TCI state. Indicates , and the second Octet can indicate the UL TCI state. Alternatively, this order may be changed.

For example, if the value of the S field (20-00) is 0, the corresponding MAC-CE may include two or more separate TCI state set information, and each codepoint in the TCI state field of DCI format 1_1 or 1_2 is each A separate TCI state set can be activated, and up to 8 separate TCI state sets can be activated. The C _0,0 field (20-15) may have the meaning of distinguishing whether the TCI state indicated by the TCI state ID _0,0 field (20-25) is a DL TCI state or a UL TCI state. If the value of the C _0,0 field (20-15) is 1, it means the DL TCI state, the DL TCI state can be indicated through the TCI state ID _0,0 field (20-25), and a 3rd octet may exist. . At this time, if the value of the C _1,0 field (20-20) is 1, the UL TCI state can be indicated through the TCI state ID _1,0 field (20-30), and the C _1,0 field (20-20) If the value of is 0, the TCI state ID _1,0 fields (20-30) can be ignored. If the value of the C _0,0 field (20-15) is 0, the UL TCI state may be indicated through the TCI state ID _0,0 field (20-25), and the 3rd Octet may not exist. This interpretation of the C _0,0 field (20-15) field and the C _1,0 field (20-20) is only an example, and the 0, 1 values of the C _0,0 field (20-15) field are reversed. It is not excluded to interpret or reversely interpret the DL TCI state and UL TCI state values.

Figure 20 may illustrate an example of MAC CE when the UL TCI state among the separate TCI states uses higher layer signaling structures such as the DL TCI state and the joint TCI state among the separate TCI states as described above, and accordingly, the TCI The length of the state ID _0,0 field (20-25) and the TCI state ID _1,0 field (20-30) can be 7 bits to represent up to 120 TCI states. Additionally, FIG. 20 may illustrate an example of MAC CE when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the TCI state ID _0,0 field (20-25) has 7 bits that can express both 6 bits that can express up to 64 UL TCI states and 7 bits that can represent up to 120 DL TCI states. It can be. If the value of the C _1,0 field (20-15) is 1 and the TCI state ID _0,0 field (20-25) indicates the UL TCI state, the first value of the TCI state ID _0,0 field (20-25) The second bit can be fixed to 0 or 1, and only a total of 6 bits from the 2nd to the 7th bit can represent the actual UL TCI state.

FIG. 21 is a diagram illustrating another MAC-CE structure for activating and indicating separate TCI state in a wireless communication system according to an embodiment of the present disclosure.

In Figure 21, the Serving Cell ID field (21-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (21-10) may indicate the serving cell ID and bandwidth part ID, respectively. The S field (21-00) may indicate the number of separate TCI state set information included in MAC-CE. For example, if S If the value of field (21-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set and can include only up to the 3rd Octet.

For example, if the value of the S field (21-00) is 0, the corresponding MAC-CE may include two or more separate TCI state set information, and each codepoint in the TCI state field of DCI format 1_1 or 1_2 is each A separate TCI state set can be activated, and up to 8 separate TCI state sets can be activated. The C ₀ field (21-15) may be a field indicating which separate TCI states the indicated separate TCI state set includes. If the value of the C ₀ field (21-15) is “00”, reserve, “01 ” may indicate one DL TCI state, “10” may indicate one UL TCI state, and “11” may mean one DL TCI state and one UL TCI state, but this is interpreted as the C ₀ field (21-15). This is only an example, and the interpretation of the C ₀ field (26-15) is not limited to this. The TCI state ID _U,0 field (21-20) and the TCI state ID _D,0 field (21-25) mean the UL TCI state and DL TCI state that can be indicated and included within the 0th separate TCI state set, respectively. You can. If the value of the C ₀ field (21-15) is “01”, the TCI state ID _D,0 field (21-25) can indicate the DL TCI state, and the TCI state ID _U,0 field (21-20) can be ignored. If the value of the C ₀ field (21-15) is “10”, the 3rd Octet can be ignored, and the TCI state ID _U,0 field (21-20) can indicate the UL TCI state. If the value of the C ₀ field (21-15) is “11”, the TCI state ID _D,0 field (21-25) indicates the DL TCI state, and the TCI state ID _U,0 field (21-20) indicates the UL TCI. The state can be indicated. The R field (21-21) may be a 1-bit reserve field that does not contain indicating information.

FIG. 21 may illustrate an example of MAC CE used when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the length of the TCI state ID _D,0 field (21-25) can use 7 bits to express up to 128 TCI states, and the length of the TCI state ID _U,0 field (21-20) can be up to 64 bits. 6 bits can be used to express 2 TCI states.

FIG. 22 is a diagram showing a MAC-CE structure for activating and indicating joint and separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 22, the Serving Cell ID field (22-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (22-10) may indicate the bandwidth part ID. The J field (22-00) may indicate whether the TCI state indicated through MAC CE is a joint TCI state or a separate TCI state set. For example, J If the value of field (22-00) is 1, the corresponding MAC-CE can indicate a joint TCI state, and if it is 0, it can indicate a separate TCI state set. J The above interpretation of Field (22-00) is only an example, and does not exclude an opposite interpretation.

- If the MAC-CE indicates a joint TCI state, all odd octets (3rd, 5th, ...) except the first octet can be ignored. The C _0,0 field (22-15) indicates whether the MAC-CE indicates one joint TCI state or contains information on two or more TCI states, and each code point in the TCI state field of DCI format 1_1 or 1_2 is This may mean whether each TCI state is activated. If the value of the C _0,0 field (22-15) is 1, the corresponding MAC-CE can indicate one joint TCI state and may not exist from the 3rd Octet. If the value of the C _0,0 field (22-15) is 0, two or more joint TCI states indicated by the corresponding MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 and can be activated. TCI state ID _0,0 may mean the indicated 1st joint TCI state.

- If the corresponding MAC-CE indicates a separate TCI state set, for example, the C _0,0 field (22-15) is the TCI state indicated by the TCI state ID _0,0 field (22-25) is the DL TCI state It can have the meaning of distinguishing whether it is a UL TCI state, and if the value is 1, it means DL TCI state, and the DL TCI state can be indicated through the TCI state ID _D,0 field (22-25), and the 3rd Octet This can exist. At this time, if the value of the C _1,0 field (22-20) is 1, the UL TCI state can be indicated through the TCI state ID _1,0 field (22-30), and the C _1,0 field (22-20) If the value of is 0, the TCI state ID _1,0 fields (22-30) can be ignored. If the value of the C _0,0 field (22-15) is 0, the UL TCI state may be indicated through the TCI state ID _0,0 field (22-25), and the 3rd Octet may not exist. FIG. 22 may illustrate an example of the MAC CE used when the UL TCI state among the separate TCI states uses a higher layer signaling structure such as the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the length of the TCI state ID _0,0 field (22-25) and the TCI state ID _1,0 field (22-30) can be 7 bits to express up to 128 TCI states. In addition, FIG. 22 may illustrate an example of a MAC CE used when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. there is. Accordingly, the TCI state ID _0,0 field (22-25) contains 7 bits that can express both 6 bits that can express up to 64 possible UL TCI states and 7 bits that can express up to 128 possible DL TCI states. You can use it. If the value of the C _0,0 field (22-15) is 1 and the TCI state ID _0,0 field (22-25) means the UL TCI state, the first value of the TCI state ID _0,0 field (22-25) The second bit can be fixed to 0 or 1, and only a total of 6 bits from the 2nd to the 7th bit can represent the actual UL TCI state.

FIG. 23 is a diagram illustrating another MAC-CE structure for activating and indicating joint and separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

In Figure 23, the Serving Cell ID field (23-05) and the BWP ID field (23-10) may indicate the serving cell ID and bandwidth part ID, respectively. The J field (23-00) may indicate whether the TCI state indicated through MAC CE is a joint TCI state or a separate TCI state set. For example, J If the value of field (23-00) is 1, the corresponding MAC-CE can indicate a joint TCI state, and if it is 0, it can indicate a separate TCI state set. J The above interpretation of Field (23-00) is only an example, and does not exclude an opposite interpretation.

- If the MAC-CE indicates a joint TCI state, all even octets (2nd, 4th, ...) except the first octet can be ignored. The S ₀ field (23-21) indicates whether the corresponding MAC-CE indicates one joint TCI state, or whether two or more TCI states correspond to and are activated for each code point in the TCI state field of DCI format 1_1 or 1_2. can do. If the value of the S ₀ field (23-21) is 1, the corresponding MAC-CE can indicate one joint TCI state and may not exist from the 3rd Octet onwards. If the value of the S ₀ field (23-21) is 0, the corresponding MAC-CE may include two or more joint TCI state information, and each code point in the TCI state field of DCI format 1_1 or 1_2 represents each joint TCI state. It can be activated. TCI state ID _D,0 may mean the indicated 1st joint TCI state.

- If the corresponding MAC-CE indicates a separate TCI state set, the C ₀ field (23-15) may be a field indicating which separate TCI states the indicated separate TCI state set includes. If the value of the C ₀ field (23-15) is “00”, reserve, if “01”, 1 DL TCI state, if “10”, 1 UL TCI state, if “11”, 1 DL TCI state and 1 UL TCI state It can mean that the dog is being directed. These values are only examples and the present invention is not limited by these examples. The TCI state ID _U,0 field (23-20) and the TCI state ID _D,0 field (23-25) mean the UL TCI state and DL TCI state that can be indicated and included in the 0th separate TCI state set, respectively. You can. If the value of the C ₀ field (23-15) is “01”, the TCI state ID _D,0 field (23-25) can indicate the DL TCI state, and the TCI state ID _U,0 field (23-20) can be ignored, and if the value of the C ₀ field (23-15) is “10”, the TCI state ID _U,0 field (23-20) can indicate the UL TCI state, and the C ₀ field (23-15) can indicate the UL TCI state. ) is “11”, the TCI state ID _D,0 field (23-25) may indicate the DL TCI state, and the TCI state ID _U,0 field (23-20) may indicate the UL TCI state. If the value of the S ₀ field (23-21) is 1, the corresponding MAC-CE indicates one separate TCI state set, and may not exist from the 4th Octet. If the value of the S ₀ field (23-21) is 0, the corresponding MAC-CE may include two or more separate TCI state set information, and each code point in the TCI state field of DCI format 1_1 or 1_2 is each separate TCI. A set of states can be activated, and up to eight separate TCI state sets can be activated. For example, if the value of the S ₀ field (23-21) is 0, if the value of the C ₁ ,..., C _N-1 fields is “10”, it means that only the UL TCI state is indicated, so the 5th , 7th, ..., Mth Octet can be ignored. Alternatively, the S _n field may indicate whether an Octet for the next separate TCI state set exists. For example, if the value of the S _n field is 1, the next Octet may not exist, and if the value of the S _n field is 0, the next Octet containing C _n+1 and TCI state ID _U,n+1 may exist. This value of the Sn field is only an example, and the present invention is not limited by this example.

- FIG. 23 may disclose an example of MAC CE when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the length of the TCI state ID _D,0 field (23-25) can be 7 bits to express up to 128 TCI states, and the length of the TCI state ID _U,0 field (23-20) can be up to 64 bits. It can be 6 bits to represent the TCI state.

If the UE receives instructions related to transmission and reception beams using the joint TCI state method or the separate TCI state method through upper layer signaling, the UE receives a PDSCH including a MAC-CE indicating the joint TCI state or separate TCI state from the base station. It is possible to receive and apply the transmission/reception beam. If there are two or more sets of joint TCI states or separate TCI states included in the MAC-CE, as described above, the terminal starts 3 ms after transmission of the PUCCH including HARQ-ACK information indicating successful reception of the corresponding PDSCH. It is possible to confirm that a plurality of joint TCI states or separate TCI state sets indicated by MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 and activate the indicated joint TCI state or separate TCI state sets. . Afterwards, the terminal can receive DCI format 1_1 or 1_2 and apply one joint TCI state or a separate TCI state set indicated by the TCI state field in the corresponding DCI to the uplink transmission and downlink reception beams. At this time, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include (without DL assignment).

Figure 24 is a diagram of the beam application time that can be considered when using the integrated TCI method in a wireless communication system according to an embodiment of the present disclosure.

As described above, the terminal receives DCI format 1_1 or 1_2 including (with DL assignment) or without (without DL assignment) downlink data channel scheduling information from the base station and configures one DCI format indicated by the TCI state field in the DCI. A joint TCI state or a separate TCI state set can be applied to the uplink transmission and downlink reception beams.

- DCI format 1_1 or 1_2 with DL assignment (24-00): If the terminal receives DCI format 1_1 or 1_2 including downlink data channel scheduling information from the base station (24-01), one joint TCI based on the integrated TCI method When indicating a state or a separate TCI state set, the terminal receives a PDSCH scheduled based on the received DCI (24-05) and sends a PUCCH including HARQ-ACK, which indicates successful reception of the DCI and PDSCH. Can be transmitted to the base station (24-10). At this time, HARQ-ACK may include both the meaning of successful reception of DCI and PDSCH, and if at least one of DCI and PDSCH is not received, the terminal may transmit NACK, and if reception of both is successful, the terminal can transmit ACK.

- DCI format 1_1 or 1_2 without DL assignment (24-50): If the terminal receives DCI format 1_1 or 1_2 that does not include downlink data channel scheduling information from the base station (24-55), one based on the integrated TCI method is assigned. When indicating a joint TCI state or separate TCI state set, the terminal can assume the following for the corresponding DCI.

* Includes CRC scrambled using CS-RNTI.

* The value of all bits assigned to all fields used as RV (Redundancy Version) fields is 1.

* The value of all bits assigned to all fields used as MCS (Modulation and Coding Scheme) fields is 1.

* The value of all bits assigned to all fields used as NDI (New Data Indication) fields is 0.

* For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits allocated to the FDRA field is 0, and for FDRA Type 1, the value of all bits allocated to the FDRA field is 1, and if the FDRA method is dynamicSwitch, FDRA The value of all bits assigned to the field is 0.

The terminal may transmit a PUCCH including HARQ-ACK, which indicates successful reception of DCI format 1_1 or 1_2 assuming the above-mentioned details, to the base station (24-60).

- For both DCI format 1_1 or 1_2 with DL assignment (24-00) and without DL assignment (24-50), if the new TCI state indicated through DCI (24-01, 24-55) has already been indicated If the TCI state applied to the uplink transmission and downlink reception beam is the same, the terminal can maintain the previously applied TCI state. If the new TCI state is different from the previously indicated TCI state, the terminal determines the application time of the joint TCI state or separate TCI state set that can be indicated from the TCI state field included in the DCI at BAT (beam application time, It can be determined to be applied from the start of the first slot (24-20, 24-70) after a period of time (24-15, 24-65) (section 24-30, 24-80), and the slot's The previously indicated TCI-state can be used up to the starting point (24-20, 24-70) and the previous section (24-25, 24-75).

- For both DCI format 1_1 or 1_2 with DL assignment (24-00) and without DL assignment (24-50), BAT is a certain number of OFDM symbols and can be set to upper layer signaling based on UE capability reporting information. . The numerology for BAT and the first slot after BAT can be determined based on the smallest numerology among all cells to which the joint TCI state or separate TCI state set indicated through DCI is applied.

The UE receives one joint TCI state indicated through MAC-CE or DCI for control resource sets connected to all UE-specific search spaces, receives PDSCH scheduled as PDCCH transmitted from the corresponding control resource set, and receives PUSCH. It can be applied to transmission for, and transmission of all PUCCH resources.

If one separate TCI state set indicated through MAC-CE or DCI includes one DL TCI state, the terminal receives one separate TCI state set for control resource sets connected to all terminal-specific search spaces, It can be applied to reception of PDSCH scheduled as PDCCH transmitted from the corresponding control resource set, and can be applied to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

If one separate TCI state set indicated through MAC-CE or DCI includes one UL TCI state, the UE can apply it to all PUSCH and PUCCH resources and all TCI states based on the previously indicated DL TCI state. It can be applied to reception of control resource sets connected to a terminal-specific search space and reception of PDSCH scheduled as a PDCCH transmitted from the corresponding control resource set.

If one separate TCI state set indicated through MAC-CE or DCI includes one DL TCI state and one UL TCI state, the UE uses the DL TCI state for control resource sets connected to the UE-specific search space. It can be applied to reception of the PDSCH scheduled as the PDCCH transmitted from the corresponding control resource set, and the UL TCI state can be applied to all PUSCH and PUCCH resources.

In the example of the MAC CE of FIGS. 15 to 23 described above, it is possible for at least one of its components to be combined with each other.

<Second embodiment: Multiple TCI state indication and activation method based on integrated TCI method>

As an example of the present disclosure, a method for indicating and activating multiple TCI states based on an integrated TCI method is described. The multiple TCI state indication and activation method is used when the number of joint TCI states indicated is expanded to two or more, and each of the DL TCI state and UL TCI state included in one separate TCI state set is expanded to a maximum of two or more. It may mean a case. If one separate TCI state set can include up to two DL TCI states and UL TCI states, a total of eight combinations of the DL TCI state and UL TCI state that one separate TCI state set can have are possible. can ({DL,UL} = {0,1}, {0,2}, {1,0}, {1,1}, {1,2}, {2,0}, {2,1} , {2,2}, the number indicates the number of TCI states.)

If the terminal receives multiple TCI states from the base station based on MAC-CE, the terminal can receive a set of two or more joint TCI states or one separate TCI state from the base station through the corresponding MAC-CE. The base station can schedule the terminal to receive a PDSCH including the corresponding MAC-CE through the PDCCH, and the terminal can schedule the PUCCH including HARQ-ACK information indicating whether reception of the PDSCH including the corresponding MAC-CE is successful. Starting 3 ms after transmission, the uplink transmission beam or transmission filter and the downlink reception beam or reception filter can be determined based on a set of two or more joint TCI states or one separate TCI state.

If the terminal receives multiple TCI states based on DCI format 1_1 or 1_2 from the base station, each code point of one TCI state field in the DCI format 1_1 or 1_2 corresponds to two or more joint TCI states or two or more separate TCIs. A set of states can be indicated. At this time, the terminal can receive MAC-CE from the base station and activate a set of two or more joint TCI states or two or more separate TCI states corresponding to each code point of one TCI state field in the corresponding DCI format 1_1 or 1_2. there is. The base station can schedule the terminal to receive a PDSCH including the corresponding MAC-CE through the PDCCH, and the terminal can schedule the PUCCH including HARQ-ACK information indicating whether reception of the PDSCH including the corresponding MAC-CE is successful. The TCI state information included in MAC-CE can be activated starting 3 ms after transmission.

If the terminal receives multiple TCI states from the base station based on DCI format 1_1 or 1_2, there may be two or more TCI state fields in the DCI format 1_1 or 1_2, and two or more joints can be created based on each TCI state field. One of a TCI state or a set of two or more separate TCI states may be indicated. At this time, the terminal can receive the MAC-CE from the base station and activate a joint TCI state or separate TCI state set corresponding to each code point of two or more TCI state fields in the corresponding DCI format 1_1 or 1_2. The base station can schedule the terminal to receive a PDSCH including the corresponding MAC-CE through the PDCCH. The terminal can activate the TCI state information included in the MAC-CE from 3 ms after transmitting the PUCCH including HARQ-ACK information indicating successful reception of the PDSCH including the corresponding MAC-CE. The terminal can be configured for the presence or absence of one or more additional TCI state fields through upper layer signaling, and the bit length of the additional TCI state field may be the same as the existing TCI state field, and the length may be determined based on upper layer signaling. may be adjusted.

The terminal can receive transmission/reception beam-related instructions in the integrated TCI method using either the joint TCI state or the separate TCI state set by the base station. The terminal can be configured to use either the joint TCI state or the separate TCI state through upper layer signaling from the base station. For the Separate TCI state indication, the terminal can be set so that the bit length of the TCI state field in DCI format 1_1 or 1_2 is up to 4 through upper layer signaling.

The MAC-CE used to activate or indicate the plurality of joint TCI states and separate TCI states described above may exist for each joint and separate TCI state method, and one MAC-CE may be used to select one of the joint or separate TCI state methods. The TCI state can be activated or indicated based on one, and the MAC-CE used in the MAC-CE-based indication method and the MAC-CE-based activation method may share one MAC-CE structure, or individual MAC-CE You can also use structures. Through the drawings described later, various MAC-CE structures for activating and indicating multiple joints or separate TCI states can be considered. In the drawings to be described later, for convenience of explanation, the case where two TCI states are activated or indicated is considered, but can be similarly applied to cases where three or more TCI states are activated or indicated.

FIG. 25 is a diagram illustrating a MAC-CE structure for activating and indicating a plurality of joint TCI states in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 25, the Serving Cell ID field (25-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (25-10) may indicate the bandwidth part ID. The R field may be a 1-bit reserve field that does not contain indicating information. The S field (25-00) may indicate the number of joint TCI state set information included in MAC-CE. For example, if S If the value of field (25-00) is 1, the corresponding MAC-CE can indicate one or two joint TCI states and can have a length of up to the 3rd Octet. At this time, if the value of the C ₀ field (25-15) is 0, the 3rd octet does not exist, and one joint TCI state can be indicated through the TCI state ID _0,0 field (25-20). If the value of the C ₀ field (25-15) is 1, the 3rd Octet exists, and 2 octets are entered through the TCI state ID _0,0 field (25-20) and the TCI state ID _1,0 field (25-25). The joint TCI state can be indicated respectively.

For example, if the value of the S field (25-00) is 0, the MAC-CE activates one or two joint TCI states corresponding to each codepoint in the TCI state field of DCI format 1_1 or 1_2, or One joint TCI state corresponding to each code point in the two TCI state fields of DCI format 1_1 or 1_2 can be activated, and joint TCI states for up to 8 code points can be activated. If 1 or 2 joint TCI states are activated for 1 code point of 1 TCI state field, the TCI state ID _0,Y field and TCI state ID _1,Y field are respectively the Yth of the TCI state field. This may refer to the first and second joint TCI states among the two joint TCI states activated in the code point. If one joint TCI state is activated for one code point of two TCI state fields, the TCI state ID _0,Y field and TCI state ID _1,Y field are the 1st and 2nd TCI state fields, respectively. This may refer to each joint TCI state activated at the Yth code point.

FIG. 26 is a diagram illustrating a MAC-CE structure for activating and indicating a plurality of separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 26, the Serving Cell ID field (26-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (26-10) may indicate the bandwidth part ID. The R field may be a 1-bit reserve field that does not contain indicating information. The S field (26-00) may indicate the number of separate TCI state set information included in MAC-CE. If S If the value of field (26-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set, and only up to the 5th Octet can be included. If the value of the S field (26-00) is 0, the MAC-CE may include information about a plurality of separate TCI state sets, and the MAC-CE may contain information about each TCI state field in DCI format 1_1 or 1_2. You can activate one separate TCI state set corresponding to a codepoint, or you can activate one separate TCI state set corresponding to each codepoint of two TCI state fields in DCI format 1_1 or 1_2, and as described above, the parent Separate TCI states for up to 8 or 16 code points can be activated by layer signaling.

In the MAC-CE structure of FIG. 26, each 4 octets starting from the 2nd octet may correspond to one separate TCI state set. For example, the C ₀ field (26-15) can have a total of 8 values from “000” to “111”, and as described above, each corresponds to the number of 8 cases that one separate TCI state set can have. You can.

- If the C ₀ field has a value of “000”, one separate TCI state set means that it includes one UL TCI state, and the TCI state ID _D,0,0 field (26-20, 26-21 ) can be ignored, and the TCI state ID _U,0,0 field (26-25) can contain one UL TCI state information. Additionally, the 4th and 5th octets can be ignored.

- If the C ₀ field has a value of “001”, one separate TCI state set includes two UL TCI states, and the TCI state ID _D,0,0 field (26-20, 26-21 ) can be ignored, and the TCI state ID _U,0,0 field (26-25) may include the first UL TCI state information of the two UL TCI states. Additionally, the 4th Octet can be ignored, and the TCI state ID _U,1,0 field (26-35) may contain information about the second UL TCI state of the two UL TCI states.

- If the C ₀ field has a value of “010”, one separate TCI state set includes one DL TCI state, and the TCI state ID _D,0,0 field (26-20, 26-21 ) can contain one DL TCI state information, and the TCI state ID _U,0,0 field (26-25) and the 4th and 5th Octet can be ignored.

- If the C ₀ field has a value of “011”, one separate TCI state set includes one DL TCI state and one UL TCI state, and the TCI state ID _D,0,0 field (26- 20, 26-21) may contain one DL TCI state information, and the TCI state ID _U,0,0 field (26-25) may contain one UL TCI state information. The 4th and 5th octets can be ignored.

- If the C ₀ field has a value of “100”, one separate TCI state set includes one DL TCI state and two UL TCI states, and the TCI state ID _D,0,0 field (26- 20, 26-21) may contain one DL TCI state information, and the TCI state ID _U,0,0 field (26-25) may contain the first UL TCI state information of two UL TCI states. there is. Additionally, the 4th Octet can be ignored, and the TCI state ID _U,1,0 field (26-35) may contain information about the second UL TCI state of the two UL TCI states.

- If the C ₀ field has a value of “101”, it means that one separate TCI state set includes two DL TCI states, and the TCI state ID _D,0,0 field (26-20, 26-21 ) may include information on the first DL TCI state of the two DL TCI states, and the TCI state ID _U,0,0 field (26-25) and the 5th Octet may be ignored. The TCI state ID _D,1,0 field (26-30) may include information about the second DL TCI state among the two DL TCI states.

- If the C ₀ field has a value of “110”, it means that one separate TCI state set includes two DL TCI states and one UL TCI state, and the TCI state ID _D,0,0 field (26- 20, 26-21) may contain information on the first DL TCI state of two DL TCI states, and the TCI state ID _U,0,0 field (26-25) may contain information on one UL TCI state. In addition, the TCI state ID _D,1,0 field (26-30) may contain information on the second DL TCI state of the two DL TCI states, and the 5th Octet may be ignored.

- If the C ₀ field has a value of “111”, it means that one separate TCI state set includes two DL TCI states and two UL TCI states, and the TCI state ID _D,0,0 field (26- 20, 26-21) may contain information on the first DL TCI state of two DL TCI states, and the TCI state ID _U,0,0 field (26-25) may contain information on the first UL TCI of two UL TCI states. May contain state information, and the TCI state ID _D,1,0 field (26-30) may contain the second DL TCI state information of the two DL TCI states, and the TCI state ID _U,1,0 field (26-35) may include information on the second UL TCI state of the two UL TCI states.

FIG. 26 may illustrate an example of MAC CE used when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the UL TCI state requires 6 bits to express up to 64, so the TCI state ID _D,0,0 to TCI state ID _D,1,N fields expressing the DL TCI state can be expressed with 7 bits. In contrast, the TCI state ID _U,0,0 to TCI state ID _U,1,N fields representing the UL TCI state can be expressed in 6 bits.

FIG. 27 is a diagram illustrating another MAC-CE structure for activating and indicating a plurality of separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

In FIG. 27, the Serving Cell ID field (27-05) may indicate the identifier (serving cell ID) of the serving cell, and the BWP ID field (27-10) may indicate the bandwidth part ID. The R field may be a 1-bit reserve field that does not contain indicating information. The S field (27-00) may indicate the number of separate TCI state set information included in MAC-CE. For example, if S If the value of field (27-00) is 1, the corresponding MAC-CE can indicate one separate TCI state set and can have a length of up to the 5th Octet.

For example, if the value of the S field (27-00) is 0, the MAC-CE may include information about a plurality of separate TCI state sets, and the MAC-CE may include the TCI state field in DCI format 1_1 or 1_2. You can activate one separate TCI state set corresponding to each code point, or you can activate one separate TCI state set corresponding to each code point of the two TCI state fields of DCI format 1_1 or 1_2, as described above. As such, a separate TCI state set corresponding to up to 8 or 16 code points can be activated by upper layer signaling.

In the MAC-CE structure of FIG. 27, each 4 octets starting from the 2nd octet may correspond to one separate TCI state set. The C _U,0 field (27-15) and C _D,0 field (27-21) mean the number of UL TCI states and DL TCI states included in one separate TCI state set, respectively, as follows. Each code point can have a different meaning.

- If the C _U,0 field has a value of “00”, it means that it does not contain the UL TCI state, so TCI state ID _U,0,0 (27-20) and TCI state ID _U,1,0 ( 27-25) can be ignored.

- If the C _U,0 field has a value of “01”, it means that it contains one UL TCI state, so TCI state ID _U,0,0 (27-20) contains one UL TCI state information. can be done, and TCI state ID _U,1,0 (27-25) can be ignored.

- If the C _U,0 field has a value of “10”, it means that it contains two UL TCI states, so TCI state ID _U,0,0 (27-20) is the first of the two UL TCI states. It may contain UL TCI state information, and TCI state ID _U,1,0 (27-25) may contain the second UL TCI state information of the two UL TCI states.

- If the C _D,0 field has a value of “00”, it means that it does not include the DL TCI state, so the 4th and 5th Octet can be ignored.

- If the C _D,0 field has a value of “01”, it means that it contains one DL TCI state, so TCI state ID _D,0,0 (27-30) contains one DL TCI state information. It can be done, and the 5th Octet can be ignored.

- If the C _D,0 field has a value of “10”, it means that it contains two DL TCI states, so TCI state ID _D,0,0 (27-30) is the first of the two DL TCI states. It may contain DL TCI state information, and TCI state ID _D,1,0 (27-35) may contain the second DL TCI state information of the two DL TCI states.

FIG. 27 may illustrate an example of a MAC CE used when the UL TCI state among the separate TCI states uses a different upper layer signaling structure from the DL TCI state and the joint TCI state among the separate TCI states, as described above. Accordingly, the UL TCI state requires 6 bits to express up to 64, so the TCI state ID _D,0,0 to TCI state ID _D,1,N fields expressing the DL TCI state can be expressed with 7 bits. In contrast, the TCI state ID _U,0,0 to TCI state ID _U,1,N fields representing the UL TCI state can be expressed in 6 bits.

In the example of the MAC CE of FIGS. 25 to 27 described above, it is possible for at least one of its components to be combined with each other.

<Third embodiment: When supporting simultaneous uplink transmission using multiple panels, method for transmitting uplink control information included in uplink channels with the same priority>

Hereinafter, according to an embodiment of the present disclosure, when an uplink channel is simultaneously transmitted using a plurality of panels, a method of multiplexing uplink control information (UCI) to the simultaneously transmitted uplink channel will be described. do. At this time, in the third embodiment, it is assumed that the multixpled UCI is information included (or multiplexed) in PUCCH or PUSCH with the same priority.

Until NR release 17, the method of transmitting multiple uplink channels (for example, PUSCH, PUCCH, or SRS, etc. may be included in the uplink channel) on the same time resource for one serving cell was not supported. To support this operation, multiple panels capable of transmitting different uplink channels may be required. The panel here can be interpreted in various ways. For example, the panel may include one or more TXRUs (transmission and reception units or transceiver units) capable of receiving or transmitting signals using one downlink reception beam or an uplink transmission beam, and an antenna element associated with the TXRUs. A set of elements can be defined as one panel. Alternatively, a plurality of antenna elements may be configured into one panel regardless of the number of supportable reception beams or transmission beams. Alternatively, depending on the capabilities of the terminal or base station, a certain number of TXRUs may be configured as one panel, and one TXRU may be connected to one or more antenna elements. In addition, various panel implementation methods can be considered. In the present invention, as an example of the first panel configuration, it is assumed that a panel is a TXRU and a set of antenna elements associated with it that can receive or transmit a signal using one downlink reception beam or uplink transmission beam.

In NR release 18 phase, transmission techniques using multiple panels are discussed to support simultaneous transmission in time resources, and specific techniques and operations can be introduced into the standard. In NR release 17, major improvements were made for integrated beam management of downlink and uplink. As a separate technique improvement, NR release 17 introduced a PUCCH and PUSCH transmission method considering multiple TRPs (hereinafter mTRP (multi TRP)). At this time, PUCCH or PUSCH can be repeatedly transmitted through mTRP using a segmented multiplexing scheme (TDM) in the time domain. Since the PUCCH or PUSCH transmitted for each TRP is transmitted in different time domains, the terminal supports time-division repetitive transmission rather than simultaneous transmission. However, in NR release 18, considering FDM, SDM, or SFN (single frequency network) rather than TDM, different uplink beams (or the same uplink beam) are transmitted with different TRPs (or the same TRP). By using two or more panels, simultaneous uplink transmission using multiple panels (UL simultaneous transmission with multi-panel, UL STxMP, hereinafter referred to as STxMP) that transmits the corresponding uplink channel in the same time domain can be supported.

Figure 28 is a diagram showing resource allocation and transmission panels for FDM, SDM, and SFN uplink transmission to support STxMP. For convenience of explanation, PUSCH is described as an example, but this is only one example, and the contents proposed below can be similarly applied to PUCCH, SRS, or other uplink channels.

FDM schemeA (28-00) is a method that sets all of one scheduled PUSCH resource as one TB and encodes information bits based on this. Afterwards, according to the FDM method, resources can be divided in half in the frequency domain and simultaneously transmitted at the same time using each panel. For example, the terminal transmits the first part of the entire PUSCH resource (part containing the low index RB) through the first panel (28-01), and the second part of the entire PUSCH resource (part other than the first part) can be transmitted (28-02) through the second panel. This is just one example, and each part may be mapped to the panel and transmitted in a different order than the example (e.g., the first part of the entire PUSCH resource is transmitted through the second panel, and the second part of the entire PUSCH resource is transmitted through the second panel). part may be transferred through the first panel). At this time, if one TB is divided in half and transmitted through each panel and transmitted to different TRPs using each panel, a portion of one TB is received as one TRP. Afterwards, the base station can receive the signal transmitted by the terminal by collecting it into one and jointly decoding it or separately decoding it, depending on the base station implementation. In FDM scheme A (28-00), DMRS can be transmitted over the entire PUSCH resource (28-05). Alternatively, each DMRS may be transmitted in each PUSCH portion transmitted through different TRPs, and in this case, the DMRS transmitted through different TRPs may configure different DMRS ports or different DMRS sequences may be used.

FDM schemeB (28-10) first divides one scheduled PUSCH resource into half in the frequency domain according to the FDM method, then sets each divided PUSCH resource transmitted to each panel to one TB and sends information bits. This is the encoding method. Afterwards, the terminal transmits the same TB through each panel. At this time, the TB transmitted to each panel may be the same RV (redundancy version) sequence or a different RV sequence. Since it is the result of rate matching according to each RV sequence in a buffer of one encoded bit encoded through one TB, the FDM scheme (28-10) can be referred to as repetitive transmission. For example, the terminal may transmit the first repetitively transmitted portion through the first panel (28-11), and transmit the second repetitively transmitted portion through the second panel (28-12). At this time, if the repeatedly transmitted TB is transmitted through each panel and transmitted to different TRPs using each panel, the repeatedly transmitted TB is received as one TRP. Afterwards, the base station can receive the signal transmitted by the terminal by collecting it into one and jointly decoding it or separately decoding it, depending on the base station implementation. In FDM scheme B (28-10), DMRS can be transmitted over the entire PUSCH resource (28-15). Alternatively, each DMRS may be transmitted in each PUSCH portion transmitted through different TRPs, and in this case, the DMRS transmitted through different TRPs may configure different DMRS ports or different DMRS sequences may be used.

The SDM scheme (28-20) is a method that sets the entire scheduled PUSCH resource into one TB considering the total number of layers and encodes information bits based on this. Afterwards, according to the SDM method, the terminal can divide resources in half in the spatial domain and transmit simultaneously at the same time using each panel. In other words, the terminal divides different layers into each panel and transmits them. For example, the terminal transmits the first part (part containing the low-index layer) through the first panel (28-21), and transmits the second part (part other than the first part) through the second panel. (28-22) It can be done. This is just one example, and each part may be mapped to the panel and transmitted in a different order than the example (for example, the first part may be transmitted through the second panel, and the second part may be transmitted through the first panel). (maybe). The DMRS (28-25) of the PUSCH transmitted to each panel consists of different DMRS ports, and different DMRS ports may be included in different CDM groups. Alternatively, only the DMRS ports may be different from each other and may be included in the same CDM group. At this time, if one TB is divided in half and transmitted through each panel and transmitted to different TRPs using each panel, a portion of one TB is received as one TRP. Afterwards, the base station can receive the signal transmitted by the terminal by collecting it into one and jointly decoding it or separately decoding it, depending on the base station implementation.

The SFM scheme (28-30) is a method of configuring and transmitting the exact same TB and the same DMRS on the same frequency and same time resources. PUSCH transmitted to each panel may include the same data and the same DMRS. That is, the terminal can transmit the first part through the first panel (28-31) and the second part through the second panel (28-32). This is just one example, and each part may be mapped to the panel and transmitted in a different order than the example (for example, the first part may be transmitted through the second panel, and the second part may be transmitted through the first panel). (maybe). At this time, if the same TB is transmitted through each panel and different TRPs using each panel, the same TB is received as one TRP. Afterwards, the base station can receive the signal transmitted by the terminal by collecting it into one and jointly decoding it or separately decoding it, depending on the base station implementation. In the SFN scheme (28-30), DMRS transmitted to each panel may be configured with the same DMRS port (28-35).

In addition to the transmission method described above in FIG. 28, repeated transmission of transmitting the same TB based on the SDM scheme may be supported. In other words, any technique that can transmit simultaneously in the time domain using different panels can follow the UCI multiplexing method according to this embodiment.

When considering various transmission methods to support STxMP, two major transmission channel configuration methods can be considered. As a first method of configuring a transmission channel, the terminal can repeatedly transmit the same information using each panel. As a second transmission channel configuration method, the terminal can transmit different information through different panels through spatial multiplexing (SM). According to the second transmission channel configuration method, the terminal may configure the same TB (transport block) and transmit by mapping resources to different frequency regions or different layers, and the terminal may configure different TBs for each panel to transmit at different frequencies. It can also be transmitted by mapping to areas or different layers. Until NR Release 17, uplink support supported transmission using only one TB (or can be expressed as a CW (codeword)), so if you want to support a TB larger than one, upper layer settings and downlink control information ( DCI) may require new DCI field configuration.

The UE can multiplex UCIs by considering whether UCIs included in PUCCH or PUSCH have the same priority index (index) or different priority indexes. In the third embodiment, UCIs with the same priority index are assumed, and the method for the terminal to multiplex UCIs accordingly may be as follows.

Example 1) If the terminal:

- UCI must be multiplexed for PUCCH transmission that overlaps with PUSCH transmission,

- Conditions for multiplexing UCI as described above in the section where the PUSCH and PUCCH described UCI rate matching multiplexed to PUSCH (timeline conditions (timeline conditions specifically described in Section 9.2.5 of 3GPP standard specification TS 38.213) If condition)) is satisfied,

The terminal is:

- If the UE multiplexes an aperiodic or semi-persistent CSI report on the PUSCH, it multiplexes only the HARQ-ACK information from UCI to the corresponding PUSCH transmission and does not transmit the PUCCH.

- If the UE does not multiplex an aperiodic or semi-persistent CSI report on the PUSCH, it multiplexes the HARQ-ACK and CSI report (if any) in the UCI to the corresponding PUSCH transmission and does not transmit the PUCCH.

Example 2) If the terminal multiplexes aperiocid CSI on the PUSCH and multiplexes UCI containing HARQ-ACK information on the PUCCH overlapping with the PUSCH, the timeline conditions specifically described in Section 9.2.5 of the standard TS 38.213 ( If the timeline condition)) is satisfied, the terminal multiplexes HARQ-ACK information on the PUSCH and does not transmit the PUCCH.

In addition to the operation of multiplexing the UCI described above, the terminal may multiplex the UCI and transmit only some uplink channels according to specific operations described in Section 9 of the 3GPP standard TS 38.213.

In NR Release 17, if the UE multiplexes UCI on PUSCH in a situation that satisfies the timeline conditions and conditions for multiplexing UCI as described above, the UE can multiplex UCI on PUSCH through the following sequence:

- The terminal can check the resources of PUSCH that multiplex UCI. At this time, if the PUSCH is transmitted based on the DCI format received by the terminal, the scheduling information included in the DCI (e.g., time domain resource allocation area, frequency domain resource allocation area, MCS area, SRI area, TPMI area, DMRS port The amount of resources (or TB (transport block) size) of PUSCH can be checked based on the antenna port area for indicating, etc. If the PUSCH is a PUSCH transmission according to the configured settings based on the configured grant, the resource amount (or TB) of the PUSCH is determined by referring to the upper layer settings and the DCI format that activates such transmission or the DCI format that includes scheduling information other than the upper layer settings (transport block) size) can be checked.

- The UE calculates the number of coded modulation symbols per layer according to the type of UCI, as previously described for rate matching of UCI multiplexed to PUSCH. At this time, the terminal determines the amount of resources (or TB (transport block) size) of the scheduled PUSCH, the number of UCI information bits such as HARQ-ACK information and CSI information, the beta offset value for the UCI type, and the code for the code block. The number of coded modulation symbols per layer is calculated based on information such as code rate.

- The terminal performs channel encoding by considering the number of coded bits for the encoded UCI.

- The terminal multiplexes the bits coded for UCI onto the PUSCH. At this time, the terminal maps coded bits for UCI to PUSCH resources and multiplexes them according to the following order according to each UCI information.

를 가지는 OFDM 심볼부터, 그리고 스케줄된 PUSCH의 부반송파들 중 가장 낮은 인덱스를 가지는 부반송파부터, 그리고 스케줄된 PUSCH의 전체 레이어에 대해서, 레이어 - 주파수 - 심볼 순서로 각 인덱스를 증가시키면서 HARQ-ACK 정보를 PUSCH에 multiplex한다. 즉, 해당 부반송파와 심볼에 대해 모든 레이어에 걸쳐서 HARQ-ACK 정보를 순서대로 맵핑시키고 그다음 부반송파 인덱스에 대해 모든 레이어에 걸쳐서 그 이후 HARQ-ACK 정보를 순서대로 맵핑시킨다. 해당 심볼에서 모든 레이어와 부반송파에 걸쳐서 HARQ-ACK 정보를 맵핑시켰으면 그다음 OFDM 심볼 인덱스에 대해서 동일한 multiplex 절차를 수행한다. 단말이 PUSCH에 모든 HARQ-ACK 정보를 우선 multiplex한 이후에 CG-UCI가 있다면 CG-UCI를 HARQ-ACK 정보를 multiplex하는 방법과 동일하게 PUSCH에 CG-UCI를 multiplex할 수 있다. HARQ-ACK 정보와 CG-UCI 정보를 모두 multiplex한 이후 CSI 정보가 있다면 유사하게 PUSCH에 CSI 정보를 multiplex한다. 여기서 CSI 정보는 CSI part1과 CSI part2를 모두 포함하며, 단말은 CSI part1을 먼저 PUSCH에 multiplex하고 이후 CSI part2를 PUSCH에 multiplex한다. 단말은 CSI 정보에 대해서도 유사하게 PUSCH에 multiplex하지만 CSI 정보를 처음 맵핑하는 기준이 되는 OFDM 심볼 인덱스

가

와는 다르게 DMRS를 포함하지 않는 가장 첫 번째 OFDM 심볼의 인덱스로 정의된다. 단말은 OFDM 심볼 인덱스가

인 심볼부터 CSI 정보를 multiplex할 수 있는지 확인하고 앞서 설명한 HARQ-ACK 정보를 맵핑하는 것과 유사하게 레이어 - 주파수 - 심볼 순서로 인덱스를 증가시키며 CSI 정보를 맵핑한다. * The terminal multiplexes HARQ-ACK information first. At this time, if frequency hopping is not performed for the PUSCH, the first OFDM symbol index after the first set of OFDM symbols containing a DMRS (i.e., the OFDM symbol containing the very first DMRS in the time domain in the corresponding PUSCH)

Starting from the OFDM symbol with , and from the subcarrier with the lowest index among the subcarriers of the scheduled PUSCH, and for all layers of the scheduled PUSCH, HARQ-ACK information is increased by increasing each index in the order of layer - frequency - symbol. to multiplex. That is, the HARQ-ACK information is mapped in order across all layers for the corresponding subcarrier and symbol, and then the HARQ-ACK information is mapped in order across all layers for the subcarrier index. Once HARQ-ACK information has been mapped across all layers and subcarriers in the corresponding symbol, the same multiplex procedure is performed on the next OFDM symbol index. If there is a CG-UCI after the UE first multiplexes all HARQ-ACK information on the PUSCH, the CG-UCI can be multiplexed on the PUSCH in the same way as the method of multiplexing the CG-UCI HARQ-ACK information. After multiplexing both HARQ-ACK information and CG-UCI information, if CSI information is present, the CSI information is similarly multiplexed to PUSCH. Here, the CSI information includes both CSI part1 and CSI part2, and the terminal multiplexes CSI part1 to PUSCH first and then multiplexes CSI part2 to PUSCH. The UE similarly multiplexes the PUSCH for CSI information, but the OFDM symbol index is the standard for first mapping the CSI information.

go

Unlike, it is defined as the index of the first OFDM symbol that does not include DMRS. The terminal has an OFDM symbol index

Check whether the CSI information can be multiplexed starting from the symbol, and map the CSI information by increasing the index in the order of layer - frequency - symbol, similar to mapping the HARQ-ACK information described above.

는 첫 번째 주파수 홉에서 DMRS를 포함하는 OFDM 심볼의 첫 번째 세트 이후의 첫 번째 OFDM 심볼의 인덱스로 정의되며,

는 두 번째 주파수 홉에서 DMRS를 포함하는 OFDM 심볼의 첫 번째 세트 이후의 첫 번째 OFDM 심볼의 인덱스로 정의할 수 있다.

는 첫 번째 주파수 홉에서 DMRS를 포함하지 않는 가장 첫 번째 OFDM 심볼의 인덱스로 정의되며,

는 두 번째 주파수 홉에서 DMRS를 포함하지 않는 가장 첫 번째 OFDM 심볼의 인덱스로 정의할 수 있다. 단말은 각 주파수 홉에 대해서 또는 또는 또는 를 참조하여 각 홉에 대해 분할 하였던 각 UCI 정보를 PUSCH에 multiplex한다. * Even when frequency hopping is performed on PUSCH, similar to the case of not performing frequency hopping on PUSCH described above, UCI is multiplexed on PUSCH, but HARQ-ACK or CG-UCI or CSI information is sent to each frequency for each frequency hopping. Each hop is divided into two parts and each part is multiplexed to the PUSCH transmitted on each frequency hop. At this time, the index that serves as the standard for the OFDM symbol to which HARQ-ACK information and CSI information are mapped is defined for each frequency hop.

is defined as the index of the first OFDM symbol after the first set of OFDM symbols containing the DMRS in the first frequency hop,

Can be defined as the index of the first OFDM symbol after the first set of OFDM symbols including the DMRS in the second frequency hop.

is defined as the index of the first OFDM symbol that does not contain a DMRS in the first frequency hop,

Can be defined as the index of the first OFDM symbol that does not include DMRS in the second frequency hop. For each frequency hop, the terminal or or or Referring to , each UCI information divided for each hop is multiplexed to PUSCH.

As described above, up to NR Release 17, the UE multiplexes UCI by considering all resources of the scheduled PUSCH. This may mean that UCI is multiplexed for the entire TB for PUSCH transmission. If UCI is multiplexed in this way, the multiplexed UCI may be transmitted to different TRPs through different panels because simultaneous transmission using multiple panels is not considered. For example, if one TB is divided in the frequency domain and transmitted to each panel as in FDM scheme A (28-00), UCI multiplexed over different frequency domains can be transmitted with different TRPs. In order to decode UCI, the base station must perform joint decoding by combining the received UCI divided into each TRP into one to successfully receive UCI information. As another example, if one TB is divided in the spatial domain and the divided layers are transmitted to each panel, as in the SDM scheme (28-20), UCI multiplexed across different layers can be transmitted with different TRPs. Likewise, in order to decode UCI, the base station must perform joint decoding by combining the received UCI divided into each TRP into one to successfully receive UCI information.

However, blockage in a specific direction may occur between the base station and the terminal, and the channel condition in that direction may not be good. As a result, if the signal transmitted to a specific panel is not successfully received by the corresponding TRP or base station due to blocking, the base station may ultimately fail to receive the entire UCI. Since UCI information, which may include HARQ-ACK or CSI reporting, is relatively more important than data, more reliable transmission may be required. Therefore, even if blockage occurs with a small probability, a transmission method that can guarantee high reliability may be necessary to transmit UCI information so that decoding does not fail due to blockage. The following methods can be considered as UCI multiplexing methods that can guarantee high reliability.

[Method 1] By introducing a new type of beta offset value, UCI can be transmitted to enable highly reliable encoding at a lower code rate. Until NR Release 17, different beta offset values could be set depending on the type of each UCI (HARQ-ACK or CSI part1 or CSI part2). Extending this, when transmitting a PUSCH including UCI through multiple panels, UCI can be encoded according to the extended beta offset setting value.

At this time, the base station and the terminal may operate as follows. First, the terminal can report the terminal capability for multi-panel transmission to the base station. At this time, the terminal can report the multi-panel-based STxMP transmission methods it can support and the detailed information required therefor. Additionally, we can report the ability to use new beta offsets that take STxMP into account. For example, the terminal's ability to use a new beta offset can be reported to the base station by setting the terminal capability called 'betaoffsetforSTxMP' to 'enable'. Alternatively, the terminal may report the terminal to the base station by setting that the corresponding function can be used through a terminal capability area with a different name that performs a similar or identical function. Alternatively, the ability to use a new beta offset may be implicitly included as part of the terminal capability report that STxMP transmission is possible. The base station determines whether to support STxMP based on the terminal capability received from the terminal, and if STxMP is supported for the terminal, the base station can set related upper layer parameters to the terminal. As examples of new upper layer parameters, settings such as new 'BetaOffsets2' or 'BetaOffsetsforSTxMP' can be considered. [Table 43] below describes 'BetaOffsets2', an example of a new upper layer parameter.

[Table 43]

Similar to the upper layer parameter 'BetaOffsets' up to NR Release 17, depending on the number of bits of each HARQ-ACK or CSI part1 or CSI part2, for example, 'betaOffsetACK-Index1' or 'betaOffsetACK-Index2' or 'betaOffsetACK-Index3' You can set different index values together. Here, the candidate value can be expressed as 0 to xx, and the value of xx may be 31, the same as NR Release 17. Or it can be any value that is the exponent of 2 - 1, for example 16-1=15 can be set to xx. As this introduces a new beta offset, it is also possible to define a new table to determine the beta value through the index set as the upper layer parameter. Until NR Release 17, the terminal determines the beta value for multiplexing HARQ-ACK by mapping the index value set in 'BetaOffsets' to Table 9.3-1 ([Table 44] below) within 3GPP standard specification 38.213. As an example, if the setting index value of betaOffsetACK-Index2 for a case where the number of bits of HARQ-ACK information is greater than 2 and less than or equal to 11, the beta value is 6.230, which is the value corresponding to the index 6 in [Table 44] below. After deciding, the terminal can use the beta value to rate match the corresponding HARQ-ACK as described above. The information listed in Table 44 below is merely an example, and the beta offset value may be determined according to other standards and values.

[Table 44]

If the terminal transmits a PUSCH including HARQ-ACK through STxMP, the beta value for HARQ-ACK is not determined by referring to the terminal upper layer parameter 'betaOffsets' and [Table 44], but a new upper layer parameter 'betaOffsets2' (or it can be any upper layer parameter that performs the same function) and [Table 45] below to determine the beta value for HARQ-ACK for STxMP transmission and use it for UCI multiplexing. Similar to the example described above, if the setting index value of betaOffsetACK-Index2 in 'betaOffsets2' for the case where the number of bits of HARQ-ACK information is greater than 2 and less than or equal to 11, the terminal sets ' ‘Value 7 for STxMP’ is determined as the beta value. The terminal can then perform the same calculation of the number of coded modulation symbols per layer and the multiplexing process. Even in the case of CSI part1 and CSI part2, the terminal can determine the beta value by referring to the new upper layer parameters for each UCI and Table 45. The information listed in Table 45 below is merely an example, and the beta offset value may be determined according to other standards and values.

[Table 45]

The method described above is only an example, and a new upper layer parameter can be introduced and the beta value can be determined by referring to [Table 44], same as NR Release 17. Alternatively, the upper layer parameters can be set to 'betaOffsets' the same as in NR Release 17 and the beta value can be determined by referring to [Table 45]. Alternatively, the terminal may determine the beta value for the corresponding UCI based on any combination using the above settings and Table 45. According to [Method 1], the newly defined upper layer parameters and Table 45 are applied to the UE to determine the beta value only when the PUSCH with multiple UCI is STxMP using multiple panels, and if the PUSCH is not transmitted through STxMP, it is applied until NR Release 17. The beta value may be determined in the same way as the terminal operation of. Alternatively, the terminal may not follow the terminal operation up to NR Release 17 and determine the beta value based on the newly defined upper layer parameters and Table 45 for all cases.

[Method 2] The terminal can check the resources of the PUSCH where the UCI is multiplexed and repeatedly transmit the UCI to both panel transmissions according to conditions. Before multiplexing UCI to PUSCH, the terminal checks the amount of resources (or TB) of PUSCH transmitted simultaneously to each panel. At this time, the resource amount (or TB) of PUSCH simultaneously transmitted to each panel is MCS (modulation and coding scheme, which may mean modulation order and target code rate), the number of layers, the number of allocated PRBs, and the allocated OFDM It can be determined depending on the number of symbols and DMRS overhead, etc. If the resource amount (or TB) of the PUSCH transmitted to each panel is the same, the terminal can repeatedly multiplex the same UCI for each PUSCH. At this time, the terminal can multiplex the repeatedly multiplexed UCI coded bits so that they can be mapped to the same position of the PUSCH.

In this way, the terminal can multiplex the UCI so that each TRP (or base station) can combine and decode the received UCI by mapping the same UCI coded bit to the same position of the PUSCH. This is because UCI is channel coded differently from the data mapped to PUSCH. While data is encoded/decoded based on LDPC (low density parity check) code, UCI information can be encoded/decoded using repetition code, Reed-Muller code, or Polar code depending on the number of UCI bits. You can. In particular, the coded bits of UCI encoded based on the Polar code must be guaranteed to have the same coded bit length and the same multiplex position in order for decoding using combining to be possible and performance gains to be achieved. If UCI bits are transmitted repeatedly in this way, even if the uplink signal including UCI transmitted to one panel is not received by the base station due to blocking, the uplink signal including UCI transmitted to another panel is successfully received by the base station. It can be. Afterwards, the base station can understand UCI information by decoding the uplink signal successfully received from one panel. In other words, even if the base station fails to receive the data included in the PUSCH, since each UCI is repeatedly transmitted, even if only the PUSCH transmitted from one panel is successfully received, the UCI can be successfully decoded and the UCI information can be obtained. When multiplexing UCI to PUSCH based on [Method 2], the base station and terminal can perform the following operations. The terminal can report terminal capabilities for multi-panel transmission to the base station. At this time, the terminal can report the multi-panel-based STxMP transmission methods it can support and the detailed information required therefor.

In addition, as in [Method 2], the base station can be notified through a terminal report whether UCI can be repeatedly multiplexed for two panel transmissions depending on the resource amount (or TB) of the PUSCH transmitted for each panel. In this way, the terminal report to report whether [Method 2] is supported may be explicitly reported through a new terminal report parameter. Alternatively, when the terminal reports its capabilities to the base station to support STxMP transmission, the base station and the terminal can define rules in advance that the capability for [Method 2] must also be supported. In this case, since whether the terminal supports the capability for [Method 2] is reported through the terminal capability report for STxMP transmission support, it is defined as whether the capability for [Method 2] is implicitly reported. You may. If the terminal explicitly or implicitly reports to the base station that it can support [Method 2], the base station may first determine whether to support STxMP based on this and then additionally decide whether to support [Method 2]. . Alternatively, if STxMP is supported, [Method 2] may be decided to be supported without additional conditions.

If the base station supports STxMP and [Method 2] for the terminal, the base station can set upper layer parameters for supporting STxMP and [Method 2] for the terminal. The upper layer parameters for supporting STxMP can report the supported STxMP transmission methods and detailed information required for them in the same way as described in [Method 1]. The upper layer parameter to support [Method 2] may be an indicator to indicate whether the UE will repeatedly multiplex UCI to two PUSCHs using two panels according to [Method 2]. For example, set the new upper layer parameter 'UCIrepetition_forSTxMP' (or it may be another named upper layer parameter with similar/same function) to 'enable' (or any value to indicate whether it is supported, such as '1'), etc. It can be. If a new upper layer parameter 'UCIrepetition_forSTxMP' is introduced, but the corresponding upper layer parameter is not set in the UE (absent), the UE determines that the base station does not support [Method 2] and PUSCH UCI in the same manner as NR Release 17. Can be multiplexed. Alternatively, if the base station and the terminal have predefined rules to implicitly support [Method 2] if STxMP is supported, the upper layer parameters for STxMP support are set in the terminal even if a separate new upper layer parameter 'UCIrepetition_forSTxMP' is not introduced. By checking, the terminal may determine that [Method 2] is supported.

Afterwards, the terminal can transmit a scheduling request (SR) for PUSCH transmission to the base station for UCI and uplink data to be transmitted to the base station, and based on this, the base station can transmit a DCI format for scheduling PUSCH to the terminal. The terminal can identify the scheduled PUSCH by receiving the DCI format, and can assume that the scheduled PUSCH is a PUSCH transmitted through STxMP. Alternatively, PUSCH resources may be scheduled based on upper layer parameters based on the configured grant, and the scheduled PUSCH may be identified according to the configured upper layer parameters (in the case of type 2 configured grant PUSCH, the DCI format must be received in addition to the upper layer parameters) Scheduled PUSCH can be identified). At this time, other uplink channels that overlap with the scheduled PUSCH (hereinafter briefly expressed as scheduled PUSCH) transmitted through STxMP can also be confirmed. If there is another uplink channel overlapping with the scheduled PUSCH in the time domain, the uplink channel to be transmitted can be determined and the UCI to be multiplexed can be determined through the same procedure as in NR Release 17. At this time, assuming that the scheduled PUSCH is transmitted by the terminal and UCI is multiplexed to the corresponding PUSCH, the operations of the terminal and base station according to [Method 2] will be described later. The terminal checks whether the resource amount (or TB) of PUSCH transmitted through each panel is the same. If the resource amount (or TB) of PUSCH transmitted through each panel is the same, the terminal calculates the number of coded modulation symbols per layer for UCI by considering the PUSCH resource amount for each panel and performs rate matching. In order for the resource amount (or TB) of PUSCH transmitted through each panel to be the same, prerequisites may be required depending on the FDM method or SDM method. For example, in FDM-based STxMP, all PUSCH resources must be scheduled with an even number of RBs to achieve the same resource amount. This is because only in the case of an even number of RBs, when divided in half, an integer number of RBs can be allocated as resources for the PUSCH transmitted through each panel. Similarly, in SDM-based STxMP, all PUSCH resources must be scheduled into an even number of layers (or ranks) in order to allocate the same amount of resources.

를 고려하는 것이 아니라 FDM 방식에 따라 하나의 패널을 통해 전송되는 PUSCH에 대한 주파수 영역의 부반송파 수

를 고려할 수 있다. 하나의 구체적인 예시로 앞서 [수학식 6]에서 상술한 것과 같이 UL-SCH를 포함하는 PUSCH 반복 전송 타입 B가 아닌 경우의 PUSCH에 multiplexing되는 HARQ-ACK에 대한 레이어 당 coded modulation symbol 계산식에서 FDM 기반의 STxMP 방식으로 전송될 때의 하나의 패널로 전송되는 PUSCH의 부반송파를 고려하여 수정한다면 다음과 같을 수 있다. As described above, if the prerequisites according to the STxMP transmission method are satisfied and the resource amount (or TB) of the PUSCH transmitted to each panel is the same, it is considered to calculate the number of coded modulation symbols per layer according to the STxMP transmission method of the scheduled PUSCH. The parameter values may vary. For example, if the scheduled PUSCH is transmitted in the FDM-based STxMP method, the terminal must calculate the number of subcarriers in the frequency domain scheduled for the PUSCH in order to calculate the number of coded modulation symbols per layer.

Rather than considering the number of subcarriers in the frequency domain for PUSCH transmitted through one panel according to the FDM method,

can be considered. As a specific example, as previously described in [Equation 6], in the case where the PUSCH including the UL-SCH is not a repetitive transmission type B, the FDM-based coded modulation symbol calculation formula per layer for HARQ-ACK multiplexed on the PUSCH is If modified in consideration of the subcarrier of the PUSCH transmitted through one panel when transmitted in the STxMP method, it may be as follows.

[Equation 18]

대신

를 고려할 수 있다. [Equation 18] is a coded modulation symbol calculation formula per layer for HARQ-ACK when the entire PUSCH resource scheduled according to the FDM method is divided in half in the frequency domain and divided into two PUSCHs transmitted to each panel. Similarly, when calculating the coded modulation symbol per layer, considering that CG-UCI or CSI part1 or CSI part2 is divided in half in the frequency domain according to the FDM method

instead

can be considered.

를 고려하여 계산할 수 있다. 이후, UCI 비트 수

를 결정할 때, 단말은 SDM 방식에 따라 절반으로 나누어진 레이어 수를 고려하여

대신

를 이용하여 UCI 비트 수를 계산할 수 있다. If the scheduled PUSCH is transmitted in the SDM-based STxMP method, the terminal uses a coded modulation symbol per layer as described above.

It can be calculated by taking into account . Afterwards, the number of UCI bits

When deciding, the terminal considers the number of layers divided in half according to the SDM method.

instead

You can calculate the number of UCI bits using .

Afterwards, the terminal can encode UCI information according to the calculated number of UCI bits, generate a modulation symbol, and repeatedly multiplex it on the two PUSCHs transmitted to each panel. Since the resource amount (or TB) of the two PUSCHs transmitted to each panel is the same and the modulation symbols for the same UCI are multiplexed, the terminal multiplexes the UCI modulation symbols at the same position within the two PUSCHs. Here, the same location refers to the same or resource location for each PUSCH in the multiplexing process, considering the frequency in FDM and the layer in SDM, as shown in Figure 29, a diagram showing an example of mulxiplexing UCI in an STxMP transmission situation based on FDM and SDM. It may refer to positions that are judged to correspond to each other within an area.

Specifically, according to the FDM schemeA (29-00) method, the UE transmits the first part of the entire PUSCH resource (part including the low index RB) through the first panel (29-01) while multiplexing the UCI You can do it (29-03). Additionally, the UE can multiplex UCI while transmitting the second part of the entire PUSCH resource (the part including the high index RB) through the second panel (29-02) (29-04). Since the UCI transmitted through different parts of the entire PUSCH is the same UCI modulation symbol, the same UCI can be transmitted repeatedly. Unlike this embodiment, it is of course also possible for the first part of the entire PUSCH resource to be transmitted through the second panel and the second portion of the entire PUSCH resource to be transmitted through the first panel. At this time, if one TB is divided in half and transmitted through each panel and transmitted to different TRPs using each panel, a portion of one TB is received as one TRP. Afterwards, depending on implementation, the base station can collect the TBs and UCIs into one and perform joint decoding or separate decoding to receive the signal transmitted by the terminal.

According to the SDM scheme (29-20), the terminal can divide resources in half in the spatial domain and transmit at the same time through each panel. Specifically, the terminal may multiplex UCI while transmitting the first resource part (part containing a low index layer) through the first panel (29-21) (29-23). In addition, the terminal may multiplex the UCI while transmitting the second resource part (part including the high index layer or part other than the first part) through the second panel (29-22) (29-24) . Since UCIs transmitted through different layers of all resources have the same UCI modulation symbol, the same UCI can be transmitted repeatedly. Apart from this embodiment, it is of course also possible for the first resource part to be transmitted via the second panel and the second resource part to be transmitted via the first panel. The DMRS of the PUSCH transmitted to each panel consists of different DMRS ports, and different DMRS ports may be included in different CDM groups. Alternatively, only the DMRS ports may be different from each other and may be included in the same CDM group. At this time, if one TB is divided in half and transmitted through each panel and transmitted to different TRPs using each panel, a portion of one TB is received as one TRP. Afterwards, the base station can receive the signal transmitted by the terminal by collecting the TBs and UCIs into one and jointly decoding or separately decoding them, depending on the base station implementation.

[Method 3] [Method 3] is a method for the operation of the terminal and the base station when the amount of PUSCH resources (or TB) transmitted by the terminal to each panel in [Method 2] is different. If the UE confirms that the resource amount (or TB) of the PUSCH transmitted through each panel is the same, [Method 2] can be defined as a method in which the UE multiplexes UCI on PUSCHs each having the same resource amount. On the other hand, if the terminal checks whether the resource amount (or TB) of the PUSCH transmitted through each panel is the same, but the resource amount of each PUSCH is not the same, the terminal uses a method of multiplexing UCI on PUSCHs with different resource amounts [Method 3] ] It can be defined as follows. [Method 3] can define UE capability reporting and upper layer parameter settings between the base station and the UE in the same way as [Method 2]. Similarly, if explicit [Method 2] and [Method 3] have higher layer parameters (e.g. 'UCIrepetition_forSTxMP') set, or if STxMP is supported, the base station and terminal say that [Method 2] and [Method 3] are implicitly supported. You can understand it. Thereafter, the amount of resources (or TB) of the PUSCH that the terminal wants to transmit can be determined according to the DCI format including PUSCH scheduling information for STxMP transmission or PUSCH scheduling based on configured grant. At this time, if there is another uplink channel that overlaps with the scheduled PUSCH (hereinafter simply referred to as scheduled PUSCH) transmitted through STxMP, the same process is performed as in [Method 2]. If UCI is multiplexed to the scheduled PUSCH thereafter, the terminal checks whether the resource amount (or TB) of the PUSCH transmitted through each panel is the same. If the resource amount (or TB) of the PUSCH transmitted to each panel is not the same, UCI can be multiplexed to the PUSCH according to one or a combination of methods described below.

[Method 3-1: UCI multiplexing only on PUSCH transmitted through one panel] If the resource amounts of the two PUSCHs simultaneously transmitted through two panels are different, the terminal selects one PUSCH transmitted through one panel and uses UCI on the corresponding PUSCH. can be multiplexed and transmitted to the base station. At this time, the terminal may consider one or a combination of several of the following items to select one PUSCH.

- UCI multiplexing by selecting PUSCH containing PRB resources of lower or higher index (for FDM method)

- UCI multiplexing by selecting PUSCH containing layers of lower or higher index (for SDM method)

- UCI multiplexing by comparing the resource amount of PUSCHs transmitted to each panel and selecting a PUSCH with a larger resource amount or a PUSCH with a smaller resource amount

- If the MCS of the PUSCH transmitted to multiple panels is different, UCI multiplexing is performed by selecting the PUSCH with a higher or lower code rate.

[Method 3-2: UCI multiplexing the same as NR release 17] If the resource amounts of the two PUSCHs simultaneously transmitted to the two panels are different, the UE multiplexes the UCI to the PUSCH in the same way as the UCI multiplexing method up to NR release 17. . In other words, UCI is multiplexed across subcarriers in the entire frequency domain and layers in the spatial domain by considering the resource amount of the entire scheduled PUSCH without considering resource division due to each panel transmission. If a PUSCH in which UCI is multiplexed like this is transmitted using each panel, the base station may need to decode UCI information by jointly decoding each transmitted PUSCH.

[Method 4] In order to repeatedly multiplex UCI on the PUSCH transmitted to each panel, the following prerequisites must be met. In other words, if the UE transmits a PUSCH in the STxMP method and needs to multiplex UCI on the PUSCH, it does not expect the conditions below to be met. The following is an example of conditions that must be met when transmitting a PUSCH in the STxMP method and multiplexing UCI on the PUSCH.

- If PUSCH is transmitted using the FDM-based STxMP method and UCI is multiplexed to the corresponding PUSCH, 2 or more even number of PRBs are scheduled as PUSCH resources.

- If PUSCH is transmitted using the SDM-based STxMP method and UCI is multiplexed to the corresponding PUSCH, 2 or more even layers (or ranks) are scheduled for the corresponding PUSCH

- If PUSCH is transmitted in the STxMP method and UCI is multiplexed to the corresponding PUSCH, the MCS for each PUSCH transmission is scheduled to be the same.

- If PUSCH is transmitted in the STxMP method and UCI is multiplexed to the corresponding PUSCH, the same number of OFDM symbols is scheduled for the corresponding PUSCH in the time domain.

In addition to the above-described example, any additional conditions that can schedule the amount of resources of PUSCHs transmitted to each panel to be the same may be included, and the terminal may not expect that the conditions are not met.

<Fourth Embodiment: Overlapping rules for processing overlapping uplink channels when supporting simultaneous uplink transmission using multiple panels>

In the fourth embodiment, when an uplink channel simultaneously transmitted to multiple panels and another scheduled uplink channel overlap in the time domain, a method for determining a transmitting uplink channel and an uplink channel on which UCI is multiplexed are provided. The method is explained in detail.

Until NR release 17, when PUCCH and PUSCH overlap in the time domain, the terminal determines the uplink channel to transmit according to the timeline conditions and the UCI multiplexed on the uplink channel, and UCI multiplexed on the uplink channel that is not transmitted. The uplink channel is transmitted according to an overlapping rule that determines whether to multiplex the transmitted uplink channel. Until NR release 17, the method of transmitting multiple uplink channels simultaneously in the time domain using multiple panels was not supported, so the overlapping rule up to NR release 17 is a method of determining a transmission channel and performing UCI multiplexing considering STxMP transmission. cannot be provided

Meanwhile, up to NR release 17, PUCCH is transmitted repeatedly, and if the PUCCH overlaps with the PUSCH in the time domain, the terminal does not transmit PUSCH in the overlapping slot (in the case of PUSCH repeated transmission type A) or transmits the overlapped actual PUSCH repeated transmission. Do not do this (in case of PUSCH repetitive transmission type B). Likewise, the overlapping rule between PUCCH repetitive transmission and PUSCH up to NR release 17 does not take STxMP transmission into account, so it cannot provide operation that takes this into account.

In the 4-1 embodiment, an enhanced overlapping rule to solve the case where repeated PUSCH and PUCCH transmissions transmitted in the STxMP method using multiple panels overlap in the time domain is explained in detail. In the 4-2 embodiment, when the PUSCH and PUCCH transmitted in the STxMP method overlap in the time domain and the UCI in the PUCCH is multiplexed to the PUSCH, a method of determining the PUSCH on which the UCI is multiplexed among a plurality of PUSCHs will be described in detail.

<Embodiment 4-1: Enhanced overlap rule to resolve the case where repeated PUSCH and PUCCH transmissions transmitted in the STxMP method overlap in the time domain>

In this embodiment 4-1, when a PUSCH transmitted in the STxMP method using multiple panels overlaps a repeatedly transmitted PUCCH in the time domain, an operation for the terminal to process this is explained and proposed in detail.

As described above, up to NR release 17, if repeatedly transmitted PUCCH and PUSCH overlap in the time domain, the terminal transmits PUCCH and overlapping PUSCH regardless of the priority of the UCI included in each channel. Do not transmit. However, if PUSCH can be transmitted simultaneously through multiple panels and reliability can be achieved through sufficient diversity gain by being transmitted through different TRPs, instead of the UE dropping the PUSCH and transmitting only the PUCCH, You can also define a new overlapping rule to multiplex the UCI in the PUCCH to the PUSCH and transmit the PUSCH. That is, if the repetitively transmitted PUCCH and the overlapping PUSCH in the time domain are PUSCHs simultaneously transmitted in the STxMP method using multiple panels, the terminal simultaneously transmits the PUSCH according to one of the following detailed methods or a combination of multiple detailed methods, PUCCH may not be transmitted.

[Method 4-1-1] If the repeatedly transmitted PUCCH and the overlapping PUSCH in the time domain are PUSCHs simultaneously transmitted in the STxMP method using multiple panels, as in [Method 2] of the third embodiment described above, the terminal transmits all Check whether UCI can be multiplexed to all PUSCHs depending on the resource amount (or TB) of the PUSCH transmitted to the panel. Afterwards, if it is possible to multiplex UCI on the PUSCH transmitted to all panels according to [Method 2] of the third embodiment, the terminal repeatedly multiplexes the UCI on the PUSCH transmitted to all panels in the same manner as [Method 2] and transmits the PUCCH do not transmit That is, if the amount of resources of the PUSCH transmitted to all panels is the same, the terminal repeatedly multiplexes and transmits the UCI in the PUCCH to all PUSCHs and does not transmit the PUCCH. At this time, the UCI multiplexed to PUSCH may be determined the same as NR release 17. That is, if no CSI information is multiplexed in the PUSCH, the UE can repeatedly multiplex the HARQ-ACK information and CSI information included in the PUCCH to the PUSCH transmitted to all panels. On the other hand, if CSI information is multiplexed in the PUSCH, the UE can repeatedly multiplex only the HARQ-ACK information included in the PUCCH to the PUSCH transmitted to all panels. Alternatively, regardless of the operation in NR release 17, the UE may repeatedly multiplex all UCI information except SR information included in the PUCCH to the PUSCH transmitted to all panels. The terminal can repeatedly apply the operation of multiplexing UCI to PUSCH to all slots where PUCCH and PUSCH overlap. Alternatively, the terminal may multiplex UCI only for the first overlapping slot and thereafter do not multiplex UCI and may not perform repeated PUCCH transmission.

If the resource amount of the PUSCH transmitted to each panel is not the same, the terminal may not transmit the PUSCH simultaneously transmitted in the STxMP method using multiple panels that overlap in the time domain with the repeatedly transmitted PUCCH. Alternatively, the UE does not repeatedly multiplex the UCI, such as multiplexing the UCI to the PUSCH in NR release 17 rather than dropping the PUSCH, but multiplexes the UCI across all scheduled subcarriers and all layers by considering all scheduled PUSCH resources. You can also send it.

[Method 4-1-2] If the repeatedly transmitted PUCCH and the overlapping PUSCH in the time domain are PUSCHs simultaneously transmitted in the STxMP method using multiple panels, the terminal selects one PUSCH (or multiple PUSCHs) for multiplexing UCI among a plurality of PUSCHs. By selecting two PUSCHs, you can multiplex UCI on the selected PUSCH and not transmit the PUCCH. Alternatively, the terminal may multiplex UCI only for the first overlapping slot and thereafter do not multiplex UCI and may not perform repeated PUCCH transmission.

At this time, [Method 4-1-2] may be applied to all slots where PUCCH and PUSCH overlap during repeated transmission. At this time, the method of selecting the PUSCH in which UCI is multiplexed may be one of the methods described later in the 4-2 embodiment or a combination of multiple methods.

<Example 4-2: When PUSCH and PUCCH transmitted in the STxMP method overlap in the time domain, PUSCH selection and multiplexing method for multiplexing UCI to PUSCH>

In the 4-2 embodiment, when the PUSCH and PUCCH simultaneously transmitted using multiple panels overlap in the time domain and the UCI multiplexed to the PUCCH is multiplexed to the PUSCH, the PUSCH on which the UCI is multiplexed is selected among multiple simultaneously transmitted PUSCHs. And the multiplexing method is explained in detail.

As explained previously, uplink simultaneous transmission using multiple panels was not supported until NR release 17, so only one uplink channel could be transmitted for one serving cell at one time occasion. Therefore, when PUCCH and PUSCH overlap and UCI included in PUCCH is multiplexed to PUSCH, the terminal multiplexes UCI to the overlapping PUSCH without a separate PUSCH selection process. However, if multiple PUSCHs can be transmitted simultaneously at the same time and occasion using multiple panels, the terminal may need to select a PUSCH for multiplexing UCI among the multiple PUSCHs transmitted simultaneously. FIG. 30 is a diagram illustrating an example of a PUSCH simultaneously transmitted through multiple panels scheduled as mDCI (multi DCI) or sDCI (single DCI) and an example of a PUCCH that overlaps the scheduled PUSCH in the time domain.

If simultaneous PUSCH transmission is scheduled based on mDCI (30-00), the base station simultaneously transmits PUSCH using multiple panels to the terminal through multiple DCIs (30-01, 30-02) associated with different CORESETPoolIndex values ( 30-03, 30-04) can be scheduled. In addition, DCI (30-05) received at a time that satisfies the timeline conditions that must be satisfied in order to apply the overlap rule described above uses PDSCH (30-09) and PUCCH (30-06) for HARQ-ACK transmission thereto. You can schedule. At this time, since the scheduled PUSCH (30-03, 30-04) and PUCCH (30-06) overlap in the time domain, the UE applies the overlap rule to transfer the UCI included in PUCCH (30-06) to PUSCH ( 30-03, 30-04), you can decide which PUSCH to multiplex. At this time, because the STxMP-based simultaneous transmission method was not supported until NR release 17, there is no rule for determining PUSCH (30-03, 30-04) for the UE to multiplex UCI within PUCCH (30-06) in this situation. . Similarly, even when simultaneous PUSCH transmission is scheduled based on sDCI (30-10), UCI within PUCCH (30-16) overlaps in the time domain among PUSCH (30-13, 30-14) simultaneously transmitted through multiple panels. There is no rule by which the UE can determine the PUSCH for multiplexing.

In this way, a method is needed to determine the PUSCH for multiplexing the UCI included in the PUCCH. Therefore, the PUSCH for multiplexing UCI can be determined through one of the following methods or a combination of multiple methods.

- [Selection method 1] The terminal can repeatedly multiplex UCI on all simultaneously transmitted PUSCHs. At this time, the method of multiplexing UCI to all PUSCHs can be configured the same as [Method 2] of the third embodiment. That is, check whether the resource amount (or TB) of simultaneously transmitted PUSCHs is the same, and if so, UCI can be repeatedly multiplexed for all PUSCHs as in [Method 2]. On the other hand, check whether the resource amount (or TB) of simultaneously transmitted PUSCH is the same, and if not, you can operate as [Method 3-1] or [Method 3-2] of [Method 3].

- [Selection method 2] UCI may be multiplexed to the PUSCH transmitted on the same uplink transmission beam as the scheduled uplink transmission beam of the PUCCH. The uplink transmission beams of PUCCH and PUSCH can be activated according to the integrated TCI method and determined based on the indicated TCI state. For multiple PUSCHs transmitted simultaneously through multiple panels, multiple TCI states corresponding to the number of PUSCHs transmitted simultaneously may be indicated. The terminal may multiplex UCI for PUSCH transmission indicated with a TCI state that is the same as the TCI state for the scheduled PUCCH among the plurality of TCI states indicated. This [Selection Method 2] can be used both when simultaneous transmission using multiple panels is scheduled based on mDCI and when simultaneous transmission using multiple panels is scheduled based on sDCI.

If overlapping PUCCHs are scheduled to be transmitted through mTRP, the PUSCH on which the UCI is multiplexed can be determined using the following method, or the PUCCH can be transmitted without transmitting the PUSCH. Here, the fact that the PUCCH is scheduled to be transmitted through mTRP may include a case where the PUCCH is also scheduled to be simultaneously transmitted using multiple panels or a case where repeated TDM-based mTRP PUCCH transmission is scheduled.

* 1) The terminal can repeatedly multiplex UCI on all simultaneously transmitted PUSCHs. At this time, the method of multiplexing UCI to all PUSCHs can be configured the same as [Method 2] of the third embodiment.

* 2) (For FDM method) UCI multiplexing by selecting PUSCH containing PRB resources of lower or higher index

* 3) (for SDM method) UCI multiplexing by selecting PUSCH containing layers of lower or higher index

* 4) If PUCCH is scheduled to be transmitted through mTRP, the terminal transmits PUCCH without transmitting overlapping PUSCH.

- [Selection method 3] The UE can multiplex the UCI in the PUCCH to the PUSCH scheduled with the DCI associated with the same CORESETPoolIndex as the DCI that scheduled the PUCCH. This [Selection Method 3] is a method that can be used when simultaneous mDCI-based STxMP-based PUSCH transmission is scheduled. As a specific example, the base station schedules a PUCCH including UCI with a DCI associated with CORESET where CORESETPoolIndex is 0 or is not set, and schedules the first PUSCH simultaneous transmission with a DCI associated with CORESET with CORESETPoolIndex being 0 or not set. , Assume that the second PUSCH simultaneous transmission is scheduled with the DCI associated with CORESET with CORESETPoolIndex of 1. At this time, if the simultaneous transmission of PUCCH, the first PUSCH, and the second PUSCH overlap in the time domain, the UE can multiplex the UCI to the simultaneous transmission of the first PUSCH scheduled from CORESET with the same CORESETPoolIndex as the DCI that scheduled the PUCCH. there is. If the DCI scheduling the PUCCH is received from CORESET with CORESETPoolIndex of 1, the UE can multiplex the UCI for simultaneous transmission of the second PUSCH rather than the simultaneous transmission of the first PUSCH.

- [Selection method 4] The UE can determine the PUSCH for multiplexing the UCI included in the PUCCH by referring to the field included in the DCI. Here, the field in the DCI that the UE references to determine the PUSCH may be a previously existing field included in the DCI up to NR release 17. For example, if mDCI-based STxMP PUSCH transmission is scheduled, the UE can determine the PUSCH by referring to the downlink assignment index (DAI) included in each DCI. Specifically, the terminal compares the DAI included in multiple DCIs scheduling PUSCH with the DAI included in DCI scheduling PDSCH and PUCCH, and selects the PUSCH scheduled by DCI scheduling PUSCH with the same DAI value. UCI within PUCCH can be multiplexed.

Alternatively, the base station can add a new DCI field instead of the existing DCI field and indicate the PUSCH in which UCI is multiplexed to the terminal. For example, if an mDCI-based STxMP PUSCH is scheduled, a new 1-bit field may be added within each DCI. At this time, the terminal may multiplex the UCI on the PUSCH where the bit value of the new field is set to '1', and may not multiplex the UCI on the PUSCH where the bit value of the new field is set to '0'. If both new fields in both DCIs are set to '1' and the resource amount of the two scheduled PUSCHs is the same, the UE can repeatedly multiplex the UCI on both PUSCHs. As another example, if sDCI-based STxMP PUSCH is scheduled, a new 1-bit field in DCI may be added. If the bit value of the new field is '0', the terminal transmits the first PUSCH among simultaneously transmitted PUSCHs (or the PUSCH transmitted to the first panel, or the first TCI state among a plurality of TCI states indicated based on the integrated TCI method). UCI can be multiplexed (can be replaced with expressions such as PUSCH transmitted depending on). Similarly, if the bit value of the new field is '1', the terminal transmits the second PUSCH among PUSCHs transmitted simultaneously (or the PUSCH transmitted to the second panel, or the second TCI among a plurality of TCI states indicated based on the integrated TCI method). UCI can be multiplexed (can be replaced with an expression such as PUSCH transmitted depending on the state). As another example, if sDCI-based STxMP PUSCH is scheduled, a new 2-bit field in DCI may be added. If the bit value of the new field is '00', the same operation can be performed as in the previous case where the new field had 1 bit and the bit value was '0'. If the bit value of the new field is '01', the same operation can be performed as in the case where the new field has 1 bit and the bit value is '1'. If the bit value of the new field is '11' and the amount of resources of the PUSCH transmitted to each panel is the same, the terminal can repeatedly multiplex UCI on all PUSCHs.

<Fifth Embodiment: Method for transmitting uplink channels scheduled to be transmitted to different panels>

In this fifth embodiment, a detailed description will be given of how the terminal performs uplink transmission by taking this into account when different uplink channels overlapping in the time domain are scheduled to transmit to different panels.

Until NR release 17, if different uplink channels overlapped in the time domain for one serving cell, the terminal transmitted only one uplink channel after applying the overlap rule to resolve this. However, if simultaneous transmission is possible using multiple panels, a method of transmitting multiple uplink channels using multiple panels can be considered instead of transmitting only one uplink channel.

As in the fifth embodiment, in order to transmit different uplink channels to multiple panels, a terminal capability report of the terminal may first be required. The terminal can report to the base station the terminal capability that simultaneous transmission using multiple panels is possible. At this time, it can be reported to the base station that different uplink channels can be transmitted using multiple panels through one component of the corresponding terminal capability report or a separate new terminal capability report. Afterwards, the base station sets upper layer parameters to the terminal based on the terminal capability report reported by the terminal. At this time, if the base station uses simultaneous uplink transmission (STxMP) using multiple panels, the base station sets upper layer parameters for STxMP support in the terminal. At this time, to indicate that STxMP is supported, some new upper layer parameter (e.g. 'SupportSTxMP' or any higher layer parameter with the same/similar function) is available (e.g. 'enable' or 'support', etc. ) may be set, and in addition, upper layer parameters to support simultaneous transmission of different uplink channels (for example, 'SupportDiff_ULChannelforSTxMP' or any upper layer parameter with the same/similar function) may be additionally set.

Afterwards, the terminal identifies scheduled uplink channels based on the DCI that schedules the uplink channel (PUSCH or PUCCH or SRS, etc.), or based on configured upper layer parameters for configured grant PUSCH or semi-persistent/periodic PUCCH or SRS. You can identify the scheduled uplink channel. At this time, it can be confirmed that a plurality of scheduled uplink channels overlap in the time domain. If there is no overlap in the time domain, the terminal can transmit each uplink channel. If there is overlap in the time domain, the terminal can check whether the uplink channel is transmitted through the same panel or different panels. At this time, the terminal can determine whether transmission is transmitted through the same panel or different panels through the TCI state indicated according to the integrated TCI method for each uplink channel. This may be based on how the terminal implements uplink transmission, so only the terminal can understand the information.

Alternatively, the terminal may report a combination of group-based TCI state information to the base station to inform the base station whether simultaneous transmission using multiple panels is possible. Alternatively, at the CSI reporting stage, some additional information may be added to the CSI report to indicate that simultaneous transmission using multiple panels is possible. If it is determined that scheduled uplink channels can be transmitted through different panels according to the terminal's uplink transmission implementation method, etc., the terminal can simultaneously transmit each scheduled uplink channel through each panel.

As a specific example, the base station schedules PUCCH to the terminal through DCI, and the PUCCH may be scheduled to be transmitted based on joint TCI state ID 1. At this time, joint TCI state ID 1 is the ID of the first panel among the panels (or the lower SRS resource set ID if a panel or SRS resource set with a lower ID during panel operation of the terminal is associated with transmission through each panel) It may mean transmitting through a panel (which may be defined as a panel related to, etc.). On the other hand, PUSCH can be scheduled to be transmitted based on joint TCI state ID 2. At this time, joint TCI state ID 2 is the second panel among the panels (or a panel with a higher ID during panel operation of the terminal, or a higher SRS resource set if an SRS resource set is associated with transmission through each panel. This may mean transmitting through a panel (which may be defined as a panel associated with an ID, etc.). At this time, if the terminal confirms that PUCCH and PUSCH can be transmitted through different panels, even if the PUCCH and PUSCH overlap in the same time region, the terminal transmits one uplink according to the overlapping rules up to NR Release 17. Instead of determining the link channel, both uplink channels can be transmitted simultaneously using multiple panels.

If uplink channels are scheduled to be transmitted through the same panel, the terminal determines one uplink channel to transmit according to the overlap rule as in NR Release 17, multiplexes UCI accordingly, and transmits the uplink channel determined to be transmitted. And other uplink channels may not be transmitted.

Part or all of the specific embodiments proposed above may be performed in combination with part or all of one or more other embodiments.

<Sixth Embodiment: Overlapping rules for cases where multi-panel-based SFN-based STxMP PUCCH transmission and PUSCH transmission overlap>

In the sixth embodiment, time/frequency resources for transmitting PUCCH in SFN method and time for transmitting PUSCH (for example, may include both repetitive transmission or single transmission) through a multi-panel based uplink simultaneous transmission method / When frequency resources (especially time resources) overlap, a detailed description is given of how to determine the uplink channel to be transmitted among the overlapping uplinks and how to perform this if UCI is multiplexed.

As described above, among the uplink simultaneous transmission techniques using multiple panels, the same data and the same RS can be simultaneously transmitted to each TRP using each panel through the SFN method. This SFN-based simultaneous transmission with multi-panel (STxMP) is a method to improve the reliability of the transmitted uplink, and both uplink repetitive transmission and SFN-based STxMP transmission methods are considered and scheduled. Alternatively, only one of the two techniques may be considered and scheduled. In the sixth embodiment, for convenience of explanation, repeated PUCCH transmission up to NR Release 17 rather than the SFN-based STxMP method is not considered, and SFN-based STxMP PUCCH transmission (can be expressed by replacing SFN PUCCH for convenience of explanation) is scheduled. Explain the case. However, this sixth embodiment is not only applied to the corresponding scheduling environment, but can also be applied to scheduling cases in which both PUCCH repetitive transmission and SFN-based STxMP transmission methods are considered through a simple extension of the technique, or to other cases.

In order to schedule SFN-based STxMP, which uses multiple panels to simultaneously transmit the same data and RS to different TRPs (or may be the same TRP), the UE reports support for the function to the base station (UE capability report) Capability report, for example, setting parameters for terminal reporting on a feature group such as 'enable SFN PUCCH' to an indicator such as 'enable' or 'disable' and reporting, or instructions for components included in the feature group A value can be set and reported (e.g., when SFN PUCCH can be transmitted repeatedly, number of repeated transmissions, etc.), and the base station sets upper layer parameters based on the reported UE capabilities. At this time, the following examples can be considered for upper layer parameters and configured information elements (IE) that can be considered to perform SFN-based STxMP PUCCH transmission. At this time, the terminal can determine that the SFN-based STxMP transmission method is scheduled through a single candidate or a combination of multiple candidates among the examples.

- 'unifiedTCI-StateType-r17' in 'MIMOParam-r17' (or 'MIMOparam-r18' for NR Release 18 or IE that may be associated with any other unified TCI framework) in Serving cell configuration 'ServingCellConfig' (or any parameter to support the enhanced unfied TCI framework in NR Release 18) is set.

- To indicate whether SFN-based STxMP is supported, a higher-layer parameter (e.g., 'sfnSchemePUCCH') must be set to 'MIMOParam-r17' (or 'MIMOparam-r18' for NR Release 18, or any association) in the support cell configuration 'ServingCellConfig'. can be set to higher layer parameters). or,

- To indicate whether to support SFN-based STxMP, an upper layer parameter (e.g., 'sfnSchemePUCCH') is set in the PUCCH setting 'PUCCH-Config' or 'PUCCH-FormatConfig' or in the upper layer parameter associated with another PUCCH setting. or,

- To indicate whether to support SFN-based STxMP, an upper layer parameter (e.g., 'sfnSchemePUCCH') is set in the 'PUCCH-Resource' setting for PUCCH resources or the 'PUCCH-ResourceSet' setting for a PUCCH resource set.

Among these settings, the base station can set one candidate or a combination of multiple candidates to the terminal, and the terminal determines whether SFN-based STxMP PUCCH transmission can be performed based on the received upper layer parameters. Thereafter, the terminal may or may not perform SFN-based STxMP PUCCH transmission based on the scheduling information of the PUCCH scheduled by the base station. For example, if the upper layer parameters for SFN-based STxMP PUCCH transmission are set in 'PUCCH-Resource' unit, for the PUCCH resource indicated by DCI (or upper layer parameters to support periodic/semi-persistent PUCCH) Perform SFN-based STxMP PUCCH transmission if parameters for SFN STxMP transmission are set (or if an indicator or indication value to support it is set), and if parameters for SFN STxMP transmission are not set (or if an indicator or indication value to support it is set), perform SFN-based STxMP PUCCH transmission. If the indication value is set) SFN-based STxMP transmission is not performed.

Assuming that the SFN-based STxMP PUCCH transmission method is not scheduled with repetitive transmission, only the PUCCH resources in one time/frequency resource region are used, the same as the existing scheduled PUCCH, to transmit in different spatial regions (or in a single TRP). are transmitted to the same or similar spatial area). The SFN-based STxMP PUCCH transmission method may be the same in terms of generating the same data and RS (e.g., the same information bit, the same sequence), and the precoding method of the physical channel transmitted to each panel may be the same or different. That is, , It is the same in terms of information, but considering the channel situation, different precoding/beamforming methods for each panel can be supported using the SFN method). Even if only a single time resource area is used, SFN-based STxMP PUCCH is transmitted. can be regarded as repeated transmission (Approach 1). Or, a method of instructing existing PUCCH repeated transmission ('nrofSlots' (NR Release 15/16) in 'PUCCH-FormatConfig' for settings for each PUCCH format or 'PUCCH-ResourceExt' ('PUCCH-Resource') for settings for each PUCCH resource. Since 'pucch-RepetitionNrofSlots' in the IE for additional configuration information along with configuration is not set or does not indicate repetitive transmission, SFN-based STxMP PUSCCH transmission may not be regarded as repetitive transmission (Approach 2). Embodiment 6-1, which will be described later, explains the overlap rules between SFN PUCCH transmission and PUSCH transmission, assuming Approach 1 that considers SFN-based STxMP PUCCH transmission as repeated transmission. Embodiment 6-2, which will be described later, explains the overlap rules between SFN PUCCH transmission and PUSCH transmission, assuming Approach 2, which does not consider SFN-based STxMP PUCCH transmission as repeated transmission. In the 6-1 and 6-2 embodiments described later, overlapping PUCCH transmission and PUSCH transmission are performed according to an overlap rule or a timeline condition (e.g., standard TS) for performing UCI multiplexing. Assume that the following (see Section 9.2.5 in 38.213) is satisfied. If the timeline condition is not met for two overlapping PUCCH and PUSCH transmissions, the base station cannot be sure how the terminal handled the uplink channel transmission. This means that it cannot be guaranteed that the terminal performs the operation specified in the standard or according to the embodiment proposed by the present invention.

<Embodiment 6-1: Overlap rules between SFN PUCCH transmission and PUSCH transmission when SFN-based STxMP PUCCH transmission is considered repeated transmission>

In the 6-1 embodiment, when the SFN PUCCH transmission method is regarded as a method of PUCCH repetitive transmission (or may be interpreted as having the same priority as PUCCH repetitive transmission), overlapping in the time domain This explains the handling method between SFN PUCCH and PUSCH (which can additionally overlap in the frequency domain).

Until NR Release 16/17, the UE does not transmit PUSCH in a slot where repetitive PUCCH transmission and PUSCH (applicable to both single transmission or repetitive transmission) overlap (or performs PUSCH repetition type A or TB processing (TBoMS) over multiple slots) (for a PUSCH that performs PUSCH repetition), and may not transmit actual PUSCH repetitions that overlap within a slot (for a PUSCH that performs PUSCH repetition type B). If the SFN PUCCH transmission method is also considered the same as PUCCH repeated transmission or has the same priority, the overlapping PUSCH can be handled in the same way as PUCCH repeated transmission. That is, the UE does not transmit a PUSCH within an overlapping slot for a PUSCH that overlaps with the SFN PUCCH (for a PUSCH that performs PUSCH repetition type A or TB processing (TBoMS) over multiple slots), or transmits an actual PUSCH that overlaps within a slot. Actual PUSCH repetition may not be transmitted (for PUSCH performing PUSCH repetition type B). Based on this, the case where PUCCH repetitive transmission or SFN PUCCH and PUSCH overlap and the handling method for this can be defined as follows:

(이 때,

는 1보다 큰 값,

>1)에 걸쳐 PUCCH를 전송하거나 또는 단말이 한 PUCCH에 대해 SFN 기반 STxMP 방법 (여기서, 앞서 SFN PUCCH를 지원하고 스케줄하기 위한 후보의 예시들을 고려할 수 있으며, 일례로 상위 계층 파라미터 'sfnSchemePUCCH'가 설정된 경우를 고려할 수 있다. 또는 일례로 단말은 DCI (또는 periodic/semi-persistent PUCCH 전송을 위한 상위 계층 파리미터 설정)으로 스케줄된 PUCCH 자원에 대해 상위 계층 파라미터 'sfnSchemePUCCH'가 설정된 경우를 고려할 수 있다)으로 PUCCH를 전송하며, 슬롯의 두 번째 수에 걸쳐 반복 타입 A (repetition type A) 또는 다중 슬롯에 걸친 TB 처리 (TBoMS)로 PUSCH를 전송해야 하며, 해당 PUCCH 전송이 하나 또는 복수 개의 슬롯에 PUSCH 전송과 중첩되며, PUSCH에 UCI를 multiplexing하기 위한 표준규격 TS 38.213 내 9.2.5 절에 조건들이 중첩되는 슬롯(들)에 대해 만족한다면, 단말은 해당하는 PUCCH를 전송하고 중첩되는 슬롯(들)에 PUSCH를 전송하지 않는다. - If the terminal is the first number of slots for one PUCCH

(At this time,

is a value greater than 1,

>1), or the UE transmits the SFN-based STxMP method for one PUCCH (here, examples of candidates for supporting and scheduling the SFN PUCCH may be considered, for example, where the upper layer parameter 'sfnSchemePUCCH' is set) A case may be considered. Alternatively, as an example, the UE may consider a case where the upper layer parameter 'sfnSchemePUCCH' is set for a PUCCH resource scheduled by DCI (or upper layer parameter setting for periodic/semi-persistent PUCCH transmission). When transmitting PUCCH, PUSCH must be transmitted with repetition type A or TB processing over multiple slots (TBoMS) over the second number of slots, and the corresponding PUCCH transmission is combined with PUSCH transmission in one or more slots. If the conditions in section 9.2.5 of TS 38.213, the standard for multiplexing UCI to PUSCH, are satisfied for the overlapping slot(s), the terminal transmits the corresponding PUCCH and sends PUSCH to the overlapping slot(s). Do not transmit.

(이 때,

는 1보다 큰 값,

>1)에 걸쳐 PUCCH를 전송하거나 또는 단말이 한 PUCCH에 대해 SFN 기반 STxMP 방법 (여기서, 앞서 SFN PUCCH를 지원하고 스케줄하기 위한 후보의 예시들을 고려할 수 있으며, 일례로 상위 계층 파라미터 'sfnSchemePUCCH'가 설정된 경우를 고려할 수 있다. 또는 일례로 DCI (또는 periodic/semi-persistent PUCCH 전송을 위한 상위 계층 파리미터 설정)으로 스케줄된 PUCCH 자원에 대해 상위 계층 파라미터 'sfnSchemePUCCH'가 설정된 경우를 고려할 수 있다)으로 PUCCH를 전송하며, 단말이 슬롯의 두 번째 수에 걸쳐 반복 타입 B (repetition type B)로 PUSCH를 전송해야 하며, 해당 PUCCH 전송이 하나 또는 복수 개의 슬롯에 actual PUSCH 반복 (actual PUSCH repetition)과 중첩되며, PUSCH에 UCI를 multiplexing하기 위한 표준규격 TS 38.213 내 9.2.5 절에 조건들이 중첩되는 슬롯(들)에 대해 만족한다면, 단말은 해당하는 PUCCH를 전송하고 중첩되는 actual PUSCH 반복(들)을 전송하지 않는다.- If the terminal is the first number of slots for one PUCCH

(At this time,

is a value greater than 1,

>1), or the UE transmits the SFN-based STxMP method for one PUCCH (here, examples of candidates for supporting and scheduling the SFN PUCCH may be considered, for example, where the upper layer parameter 'sfnSchemePUCCH' is set) A case can be considered. Alternatively, as an example, a case where the upper layer parameter 'sfnSchemePUCCH' is set for a PUCCH resource scheduled with DCI (or upper layer parameter settings for periodic/semi-persistent PUCCH transmission) can be considered). transmission, the terminal must transmit the PUSCH with repetition type B over the second number of slots, the corresponding PUCCH transmission overlaps the actual PUSCH repetition in one or more slots, and the PUSCH If the conditions in section 9.2.5 of TS 38.213, the standard for multiplexing UCI, are satisfied for overlapping slot(s), the UE transmits the corresponding PUCCH and does not transmit overlapping actual PUSCH repetition(s).

<Example 6-2: Overlap rules between SFN PUCCH transmission and PUSCH transmission when SFN-based STxMP PUCCH transmission is not considered repeated transmission>

In the 6-2 embodiment, if the SFN PUCCH transmission method is not considered to be PUCCH repeated transmission or does not have the same priority, SFN PUCCH and PUSCH that overlap in the time domain (can additionally overlap in the frequency domain) Explains liver handling methods.

Unlike what was assumed in the above-described embodiment 6-1, since SFN PUCCH transmission uses only one time resource, the method may not be regarded as PUCCH repeated transmission (in addition to SFN PUCCH, PUCCH repeated transmission in the time domain (if not supported at the same time). In this way, if the SFN PUCCH transmission method is not considered to be repetitive PUCCH transmission, transmission of the SFN PUCCH may be determined according to an overlap rule that takes into account PUSCH overlapping in the time domain, just like PUCCH transmission, which is not repetitive transmission. Or, considering the purpose of SFN PUCCH and the characteristics of transmission with multiple TRPs, an uplink channel transmitted by considering additional rules in addition to the overlap rule between overlapping PUSCH and non-repetitive PUCCH transmission in the time domain up to NR Release 17 You can decide whether to multiplex UCI. Specifically, in order to determine whether/how to multiplex the transmitted uplink channel and UCI according to the case where the SFN PUCCH and PUSCH overlap, one of the following methods or a method combining a plurality of methods may be considered. Here, it is assumed that the overlapping SFN PUCCH and PUSCH have the same priority index.

- (Method 1: UCI in SFN PUCCH can be multiplexed to overlapping PUSCH in time domain):

Method 1 can determine the same (or similar) transmission uplink channel as when the PUSCH and PUCCH defined in NR Release 17 overlap in the time domain and determine whether to perform UCI multiplexing. For example, if the PUCCH containing UCI overlaps with the PUSCH in the time domain and satisfies the conditions for UCI multiplexing (e.g., conditions specifically specified in section 9.2.5 of the standard specification TS 38.213), the terminal overlaps Depending on whether aperiodic or semi-persistent CSI reporting is multiplexed within the PUSCH, only HARQ-ACK among the UCI included in the PUCCH should be multiplexed to the overlapping PUSCH or HARQ-ACK and HARQ-ACK among the UCI included in the PUCCH. You can decide whether to multiplex the CSI report to PUSCH. If an aperiodic or semi-persistent CSI report is multiplexed within an overlapping PUSCH, the UE multiplexes only the HARQ-ACK among the UCI included in the PUCCH to the overlapping PUSCH and transmits the PUSCH and does not transmit the PUCCH. . If the aperiodic or semi-persistent CSI report is not multiplexed within the overlapping PUSCH, the UE multiplexes the HARQ-ACK and CSI report among the UCI included in the PUSCH to the PUSCH and transmits the PUSCH. I never do that. At this time, the overlapping PUSCH may be a PUSCH defined up to NR Release 17, or a PUSCH defined in NR Release 18 (e.g., repeated mTRP TDMed PUSCH transmission based on the unified TCI framework, or simultaneous uplink transmission based on multiple panels) It may include an SDM PUSCH that supports, or an SFN PUSCH that supports simultaneous uplink transmission based on multiple panels. In PUSCH transmission methods other than the multi-panel-based SFN PUSCH, the UCI within the SFN PUCCH can be multiplexed to the overlapping PUSCH according to the same UCI multiplexing rules defined in existing NR Release 17. For the multi-panel based SFN PUSCH transmission method, the UCI included in the PUCCH is multiplexed so that it is repeated for the same TB transmitted through two panels, and the PUSCH may be rate matched considering this. In other words, the UCI included in the SFN PUCCH is multiplexed to the PUSCH transmitted to the first panel, and the UCI included in the SFN PUCCH is multiplexed equally to the PUSCH transmitted to the second panel (at this time, the multiplexed UCI is transmitted to the first panel). It may be channel-encoded the same as UCI (or the same information bits may be transmitted but may be channel-encoded differently). Alternatively, the terminal may multiplex the UCI included in the SFN PUCCH on the PUSCH transmitted to the first panel and not multiplex the UCI included in the SFN PUCCH on the PUSCH transmitted to the second panel. As another method, the terminal may multiplex the UCI included in the SFN PUCCH over the entire SFN PUSCH transmission to the first and second panels. In this case, some of the total UCI bits may be transmitted to the first panel and the rest may be transmitted to the second panel. Specifically, the terminal may transmit all UCI bits divided into the same number of information bits on the PUSCH transmitted to each panel, or a certain value set as a higher layer parameter (e.g., if each panel (or related to the corresponding PUSCH) Referring to the beta offset value set in the two SRS resource sets whose usage is set to 'codebook' or 'nonCodebook', etc. can be considered and transmitted by dividing into the same number of information bits or dividing into an unequal number of information bits. It may be possible. As another method, the UE can multiplex overlapping PUSCHs by considering the resources of the entire transmitted PUSCH as defined in NR Release 17.

As another method of using Method 1, a different UCI multiplexing method may be applied depending on whether the PUSCH overlapping with the SFN PUCCH is a single TRP-based transmission or multiple TRP-based transmission. As a specific example, if a PUSCH with an overlapped SFN PUCCH is transmitted in a single TRP (including both repeated transmissions or single transmissions) and the conditions for UCI multiplexing are satisfied, the UE uses the same UCI multiplexing method as in NR Release 17 within the SFN PUCCH. UCI can be multiplexed to PUSCH. If a PUSCH with an SFN PUCCH overlapped is transmitted through multiple TRPs and the conditions for UCI multiplexing are satisfied, the UE can multiplex the UCI by repeating the UCI to the first PUSCH transmission transmitted through each TRP. In this case, it is additionally transmitted in association with the first SRS resource set (or SRS resource set with a small SRS resource set ID) among SRS resource sets whose usage is 'codebook' or 'nonCodebook', which is transmitted to the first TRP. (or the second SRS resource set (or SRS resource set with a large SRS resource set ID) among the SRS resource sets whose usage is 'codebook' or 'nonCodebook') transmitted through the symbol of the first PUSCH and the second TRP UCI may be repeated and multiplexed only if the number of symbols of the first PUSCH (transmitted in association) is the same. If the condition for the same number of symbols is not satisfied, UCI may be muliplexed only on the first PUSCH transmitted through the first TRP.

- (Method 2: Depending on the PUSCH transmission method, UCI within the SFN PUCCH may optionally be multiplexed to overlapping PUSCHs in the time domain):

Method 2 is similar to Method 1 in that it determines the transmission uplink channel and determines whether or not to use UCI multiplexing, but can additionally consider the PUSCH transmission method. Although SFN PUCCH is not considered a repetitive PUCCH transmission, the SFN PUCCH transmission method is a method to improve the reliability of PUCCH, so only PUSCH transmitted using a specific PUSCH transmission method that can improve reliability takes this into account. UCI can add nesting rules to allow multiplexing. That is, the terminal confirms that the SFN PUCCH is scheduled, and if a PUSCH that overlaps the SFN PUCCH in the time domain is scheduled, the transmission method of the overlapping PUSCH is additionally configured in addition to the rules up to NR Release 17 for multiplexing UCI in the PUCCH. After confirmation, it is decided whether to multiplex the UCI in the SFN PUCCH to the overlapping PUSCH, and transmit the PUSCH with the UCI multiplexed and not transmit the PUSCH, or fail to multiplex the UCI to the PUSCH and transmit the SFN PUCCH and not transmit the PUSCH. there is.

A specific example of a condition additionally confirmed by the terminal according to Method 2 may be as follows. As one specific example, PUSCH overlapping with SFN PUCCH is a transmission method to improve reliability (e.g., NR Release 17 (or 18)-based single TRP TDM PUSCH repetitive transmission or NR Release 17 (or 18)-based multiple TRP TDM In the case that the SFN PUSCH, etc., which supports repetitive PUSCH transmission or simultaneous uplink transmission based on multiple panels, may be included in the PUSCH transmission method to improve reliability), the terminal multiplexes the UCI in the SFN PUCCH to the overlapping PUSCH ( As described above, if the conditions for UCI multiplexing specified in the standard are also satisfied) PUSCH may be transmitted and SFN PUCCH may not be transmitted. At this time, for the multi-panel based SFN PUSCH transmission method, such as some of the methods described in Method 1 as a specific method of multiplexing UCI to the corresponding PUSCH, the UCI included in the PUCCH is repeated for the same TB transmitted to both panels. PUSCH may be multiplexed and rate matched considering this. Alternatively, for PUSCH repeatedly transmitted through TDM, a method of multiplexing UCI for all repeated transmissions may be supported. Alternatively, as in NR Release 17, a single TRP PUSCH repeated transmission may multiplex the UCI in the SFN PUCCH only to the first slot among overlapping slots or the earliest actual PUSCH repeated transmission among overlapping actual PUSCHs. Or, as in NR Release 17 (or 18), multiple TRP PUSCH repetitive transmission is performed by multiplexing the UCI within the SFN PUCCH only in overlapping slots or the earliest actual PUSCH repeated transmission among overlapping actual PUSCHs, or in the first repetition transmitted to each TRP. UCI within SFN PUCCH may be multiplexed for transmission. At this time, UCI can be multiplexed to a plurality of PUSCHs transmitted to each TRP only if the number of symbols of the first repeatedly transmitted PUSCHs transmitted to each TRP is the same. If not, UCI can be multiplexed only to the first repeated PUSCH transmitted. (Alternatively, even if the condition for the same number of symbols is not met, UCI can be multiplexed on the first PUSCH transmitted to each TRP).

Unlike what was described in Method 2, if PUSCH overlapping with SFN PUCCH is not a method to improve reliability (repeated transmission of single or multiple TRP-based TDM PUSCH or SFN PUSCH as described above), the UE does not transmit PUSCH and transmits SFN PUCCH. Can be transmitted.

- (Method 3: Within the scheduling DCI, the transmitted uplink channel can be determined and UCI multiplexed according to a new DCI area to indicate UCI multiplexing):

If the PUCCH overlaps with another PUSCH in the time domain, whether to multiplex the UCI to the overlapping PUSCH within the DCI (e.g., DCI format 1_1 or DCI format 1_2) that schedules the SFN PUCCH according to Method 3 or transmit the overlapping PUSCH A new DCI field can be added to indicate whether to transmit only the SFN PUCCH instead of transmitting the SFN PUCCH. As a specific example, the bit configuration of the new DCI field may be configured with N bits (e.g., 1 bit). If N=1, whether to multiplex the UCI within the SFN PUCCH to the overlapping PUSCH (e.g., set the value of the corresponding DCI field to '1') or not to transmit the overlapping PUSCH without multiplexing the overlapping PUSCH. The base station can indicate to the UE whether to transmit only the SFN PUCCH (for example, set the value of the corresponding DCI field to '0') using a new DCI field. As another example, whether to multiplex the UCI on a PUSCH that overlaps within a DCI that schedules a PUSCH that overlaps with the SFN PUCCH (e.g., DCI format 0_1 or DCI format 0_2) rather than the DCI that schedules the SFN PUCCH, or (overlapping with the SFN PUCCH) If so) A new DCI field can be added to indicate whether to transmit only the SFN PUCCH without transmitting the overlapping PUSCH. Or, whether to multiplex the UCI to a PUSCH that overlaps within a DCI that schedules a PUSCH that overlaps the SFN PUCCH, rather than the DCI that schedules the SFN PUCCH (e.g., DCI format 0_1 or DCI format 0_2) or (if it overlaps with the SFN PUCCH) A new DCI field can be added to indicate whether to transmit only the scheduled PUSCH without transmitting the SFN PUCCH.

- (Method 4: The transmitted uplink channel can be determined and UCI multiplexed according to a new upper layer parameter (RRC parameter) to indicate UCI multiplexing):

Method 4 can add RRC parameters for the same indication as described in Method 3 in the RRC settings related to SFN PUCCH (e.g., PUCCH-Config or PUCCH-Resource, etc.). For example, the base station sets a new RRC parameter (for example, it may be an RRC parameter named 'enableMultplexingInPUSCH' or another similar name) to the terminal or indicates that multiplexing is possible on the overlapping PUSCH with the value for the corresponding RRC parameter. An indication value (for example, 'enable' or 'true' or '1', etc.) can be set in the terminal. If these parameters are set, the UE can multiplex the UCI in the SFN PUCCH to the overlapping PUSCH, and if not set, the UE can transmit only the SFN PUCCH without multiplexing the overlapping PUSCH and not transmitting the overlapping PUSCH (or may transmit only PUSCH and not transmit SFN PUCCH).

- (Method 5: The terminal can determine the transmitted uplink channel and multiplex the UCI according to the order of the scheduling DCI received):

According to Method 5, the UE is within the SFN PUCCH based on the time when reception is completed for the DCI scheduling the SFN PUCCH (hereinafter DCI1) and the DCI scheduling the PUSCH overlapping with the SFN PUCCH (hereinafter DCI2 or the second DCI). It can be decided whether to multiplex UCI to overlapping PUSCHs or transmit only one uplink channel. For example, if the DCI scheduling the SFN PUCCH is received later than the DCI scheduling the overlapping PUSCH (in this case, assuming that the conditions for UCI multiplexing are satisfied, the conditions for UCI multiplexing are also applied for all cases described below) (assuming that is satisfied), SFN PUCCH transmission is prioritized, so the UE can transmit only SFN PUCCH without performing UCI multiplexing. If the DCI scheduling the overlapping PUSCH is received later than the DCI scheduling the SFN PUCCH, PUSCH transmission is prioritized and the UE can transmit only the PUSCH without multiplexing the UCI. Alternatively, if the DCI scheduling the overlapping PUSCH is received later than the DCI scheduling the SFN PUCCH and PUSCH transmission has priority, but the UCI in the SFN PUCCH can be multiplexed to the PUSCH, the UE multiplexes the UCI in the SFN PUCCH to the overlapping PUSCH Only the corresponding PUSCH can be transmitted.

Alternatively, in the specifically described example, an example in which the scheduled uplink channel is transmitted to the late-received DCI is explained, but the uplink channel scheduled to the first-received DCI is not transmitted, but the uplink channel scheduled to the first-received DCI is transmitted. Transmission cases can also be considered. For example, if the DCI scheduling the SFN PUCCH is received later than the DCI scheduling the overlapping PUSCH, PUSCH transmission is prioritized and the UE can transmit only the PUSCH without multiplexing the UCI. Alternatively, if the DCI scheduling the SFN PUCCH is received later than the DCI scheduling the overlapping PUSCH and PUSCH transmission has priority, but the UCI in the SFN PUCCH can be multiplexed to the PUSCH, the UE multiplexes the UCI in the SFN PUCCH to the overlapping PUSCH Only the corresponding PUSCH can be transmitted. If the DCI scheduling the overlapping PUSCH is received later than the DCI scheduling the SFN PUCCH, SFN PUCCH transmission is given priority and only the SFN PUCCH can be transmitted without performing UCI multiplexing.

이후의 시점. PUSCH의 경우, transmission occasion i의 첫 전송 심볼 또는 첫 전송 심볼로부터 처리시간

)을 기준으로 앞서 DCI 수신 시점을 기반으로 설명한 방법과 유사한 방법으로 (DCI 수신 시점 대신 설명한 시점으로 대체하여 적용) UCI multiplexing를 수행할지 또는 UCI multiplexing을 수행하지 않고 하나의 상향링크 채널만을 전송할지에 대해 결정할 수 있다.Or, in the case of semi-persistent or configured grant-based transmission, a specific point in time to determine whether to schedule based on the corresponding transmission interval i (transmission occasion i) (for example, in the case of PUCCH, when SPS PDSCH reception is completed or when reception is started) From the point of completion

later point in time. For PUSCH, the first transmission symbol of transmission occasion i or processing time from the first transmission symbol

), it is decided whether to perform UCI multiplexing or transmit only one uplink channel without performing UCI multiplexing in a similar way to the method described above based on the DCI reception time (applied by replacing the DCI reception time). You can decide about it.

- (Method 6: Depending on the scheduling method of the uplink channel, the transmitted uplink channel can be determined and UCI can be multiplexed):

Method 6 is when the PUSCH that overlaps with the SFN PUCCH operates in a different time domain (aperiodic, semi-persistent, or periodic), the priority is defined in the order of aperiodic -> semi-persistent -> periodic and based on this. It can be decided whether to perform UCI multiplexing or to transmit only one uplink channel without performing UCI multiplexing. For example, if the time domain operation of the SFN PUCCH is aperiodic and the time domain operation of the overlapping PUSCH is semi-persistent (or configured grant Type 2), SFN PUCCH transmission is prioritized and the UE does not perform UCI multiplexing but only SFN PUCCH. Can be transmitted. Similarly, if the time domain operation of the SFN PUCCH is semi-persistent and the time domain operation of the overlapping PUSCH is aperiodic, PUSCH transmission is prioritized and the UE can transmit only the PUSCH without performing UCI multiplexing. Alternatively, if PUSCH transmission is prioritized because the time domain operation of the SFN PUCCH is semi-persistent and the time domain operation of the overlapping PUSCH is aperiodic, but the UCI in the SFN PUCCH can be multiplexed to the PUSCH, the UE transmits the UCI in the SFN PUCCH to the overlapping UCI. You can multiplex the PUSCH and transmit only the relevant PUSCH.

If the overlapping SFN PUCCH and PUSCH in the time domain have different priority indexes, the transmitted uplink channel and whether/how to multiplex UCI can be determined by considering one or a combination of several of the following items. Likewise, it is assumed that both uplink channels satisfy the conditions for UCI multiplexing.

- When the SFN PUCCH has a higher priority index than the overlapping PUSCH, SFN PUCCH transmission is prioritized and only the SFN PUCCH can be transmitted without performing UCI multiplexing.

- When the SFN PUCCH has a lower priority index than the overlapping PUSCH, PUSCH transmission is prioritized and only the PUSCH can be transmitted without multiplexing the UCI.

- Since the SFN PUCCH has a lower priority index than the overlapping PUSCH, PUSCH transmission is prioritized, but if the UCI in the SFN PUCCH can be multiplexed to the PUSCH, the UCI in the SFN PUCCH can be multiplexed to the overlapping PUSCH and only the corresponding PUSCH can be transmitted.

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

Referring to FIG. 31, the terminal may include a transceiver (referring to the terminal receiver 3100 and the terminal transmitter 3110), a memory (not shown), and a terminal processing unit 3105 (or a terminal control unit or processor). Depending on the communication method of the terminal described above, the terminal's transceiver units (3100, 3110), memory, and terminal processing unit (3105) can operate. However, the components of the terminal are not limited to the examples described above. For example, the 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 a single chip.

The transceiver unit can 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 be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

Additionally, the transceiver may receive a signal through a wireless channel and output it to the terminal processing unit 3105, and transmit the signal output from the terminal processing unit 3105 through a wireless channel.

Memory can store programs and data necessary for the operation of the terminal. Additionally, the memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories.

Additionally, the terminal processing unit 3105 can control a series of processes so that the terminal can operate according to the above-described embodiment. For example, the processor can receive DCI composed of two layers and control the components of the terminal to transmit multiple PUSCHs at the same time. There may be a plurality of processors, and the processor may perform a component control operation of the terminal by executing a program stored in the memory.

FIG. 32 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure. The base station in FIG. 32 may refer to the specific TRP described above.

Referring to FIG. 32, the base station may include a base station receiver 3200, a transceiver unit referring to the base station transmitter 3210, a memory (not shown), and a base station processing unit 3205 (or a base station control unit or processor). According to the above-described communication method of the base station, the base station's transceiver units 3200 and 3210, memory, and base station processing unit 3205 can operate. However, the components of the base station are not limited to the above 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 a single chip.

The transmitting and receiving unit can transmit and receive signals to and from the terminal. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

Additionally, the transceiver may receive a signal through a wireless channel and output it to the base station processing unit 3205, and transmit the signal output from the base station processing unit 3205 through a wireless channel.

The memory can store programs and data necessary for the operation of the base station. Additionally, the memory may store control information or data included in signals transmitted and received by the base station. Memory may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories.

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

Methods according to 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 as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). 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.

These programs (software modules, software) 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: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program can be accessed through a communication network such as the Internet, Intranet, LAN (Local Area Network), WLAN (Wide LAN), or SAN (Storage Area Network), or a combination of these. It may be stored in an attachable storage device that can be accessed. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to the 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 depending on the specific embodiment presented. However, singular or plural expressions are selected to suit 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 may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid 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 can be implemented. Additionally, 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, parts of the first and second embodiments of the present disclosure may be combined to operate the base station and the terminal. In addition, although the above embodiments were presented based on the FDD LTE system, other modifications based on the technical idea of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G or NR system.

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

Alternatively, the drawings explaining the method of the present invention may omit some components and include only some components within the scope that does not impair the essence of the present invention.

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

Various embodiments of the present disclosure have been described above. The above description of the present disclosure is for illustrative purposes, and the embodiments of the present disclosure are not limited to the disclosed embodiments. A person skilled in the art to which this disclosure pertains will understand that the present disclosure can be easily modified into another specific form without changing its technical idea or essential features. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present disclosure. do.

Claims (1)

In 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
A control signal processing method comprising transmitting a second control signal generated based on the processing to the base station.

Images