Method and device for transmitting and receiving data information about half-duplex terminal in satellite communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. This method performed by a user equipment (UE) comprises the steps of: receiving first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); receiving second DCI for scheduling a physical uplink shared channel (PUSCH), wherein an inter-slot orthogonal cover code (OCC) is enabled for the PUSCH; identifying an overlap between the PUSCH and at least one symbol in a set of symbols associated with the PDSCH; and when the first DCI is not received in a common search space (CSS) and transmission of the PUSCH does not start within a designated time from the last symbol of the first DCI, receiving the PDSCH without transmission of a first PUSCH associated with the overlap in an OCC group of the PUSCH, wherein, when the first PUSCH is not transmitted, PUSCHs in the OCC group including the first PUSCH may not be transmitted.

Description

Method and apparatus for transmitting and receiving data information of a half-duplex terminal in a satellite communication system

[0001] The present disclosure relates to a satellite communication system, and more specifically, the present disclosure relates to a method and apparatus for transmitting and receiving data information of a half-duplex terminal in a satellite communication system.

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

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

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

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] According to one embodiment of the present disclosure, an apparatus and method capable of effectively providing services in a mobile communication system are provided.

[0009] According to one embodiment of the present disclosure, a method performed by user equipment (UE) comprises receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), receiving a second DCI for scheduling a physical uplink shared channel (PUSCH), enabling an inter-slot orthogonal cover code (OCC) for the PUSCH, identifying an overlap between at least one symbol of a set of symbols associated with the PDSCH and the PUSCH, and receiving the PDSCH without transmitting the first PUSCH associated with the overlap within the OCC group of the PUSCH when the first DCI is not received within a common search space (CSS) and transmission of the PUSCH does not begin within a specified time from the last symbol of the first DCI, and when the first PUSCH is not transmitted, the PUSCHs within the OCC group including the first PUSCH may not be transmitted.

[0010] According to one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided.

[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

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

[0015] FIG. 4 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 6 is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system according to one embodiment of the present disclosure may have a plurality of PDCCH (physical downlink control channel) monitoring locations within a slot.

[0018] FIG. 7 is a diagram illustrating an example of base station beam allocation according to TCI state setting in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 8 is a diagram illustrating an example of a method for allocating a TCI state to a PDCCH in a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 9 is a diagram illustrating a TCI (transmission configuration indicator) indication MAC (medium access control) CE (control element) signaling structure for a PDCCH DMRS (demodulation reference signal) in a wireless communication system according to one embodiment of the present disclosure.

[0021] FIG. 10 is a drawing illustrating an example of beam configuration of a control resource set and a search space in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 11 is a diagram illustrating a method for a base station and a terminal to transmit and / or receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 12 is a diagram illustrating a method for selecting a set of receivable control resources by considering priority when a terminal receives a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 13 is a diagram illustrating an example of a non-periodic CSI (channel state information) reporting method according to one embodiment of the present disclosure.

[0025] FIG. 14 is a drawing illustrating an example of a PUSCH (physical uplink shared channel) repetitive transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0026] FIG. 15 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, CA (carrier aggregation), and DC (dual connectivity) situation in a wireless communication system according to one embodiment of the present disclosure.

[0027] FIG. 16 is a drawing illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0028] FIG. 17 is a diagram illustrating an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 18 illustrates a procedure in which a base station controls the transmission power of a terminal in a cellular system.

[0030] FIG. 19 is a diagram illustrating the process of a terminal according to one embodiment of the present disclosure generating a Type-1 (quasi-static) HARQ (hybrid automatic repeat request)-ACK (acknowledgement) codebook.

[0031] FIG. 20 is a diagram illustrating the process of a terminal according to one embodiment of the present disclosure generating a Type-2 (dynamic) HARQ-ACK codebook.

[0032] FIG. 21 is a diagram illustrating the orbital period of a communication satellite according to the altitude or height of the satellite according to one embodiment of the present disclosure.

[0033] FIG. 22 is a block diagram illustrating a method for generating LTE PUCCH format 5 according to one embodiment of the present disclosure.

[0034] FIG. 23 is a diagram illustrating a method of mapping different terminals to a virtual frequency tone by applying different OCC values ​​according to one embodiment of the present disclosure.

[0035] FIG. 24 is a flowchart showing a terminal processing procedure for PUSCH transmission according to one embodiment of the present disclosure.

[0036] FIG. 25 is a diagram showing a method of applying an OCC method when a terminal according to an embodiment of the present disclosure repeatedly transmits PUSCH per slot.

[0037] FIG. 26 is a diagram showing a method of applying an OCC method when a terminal according to one embodiment of the present disclosure repeatedly transmits PUSCH within one slot.

[0038] FIG. 27 is a diagram showing a method of applying an OCC method in terms of time resources when a terminal according to one embodiment of the present disclosure transmits PUSCH.

[0039] FIG. 28 is a diagram showing a method of applying an OCC method in terms of frequency resources when a terminal according to one embodiment of the present disclosure transmits PUSCH.

[0040] FIG. 29 is a drawing illustrating an uplink skipping operation according to one embodiment of the present disclosure.

[0041] FIG. 30 is a diagram illustrating an uplink skipping operation in a situation where uplink control and data channels overlap according to one embodiment of the present disclosure.

[0042] FIG. 31 is a diagram showing a situation in which a PUSCH is repeatedly transmitted with an OCC method according to one embodiment of the present disclosure, and a PUSCH overlaps with a PUCCH in a specific slot.

[0043] FIG. 32 is a diagram showing a situation in which a PUSCH is repeatedly transmitted with an OCC method according to one embodiment of the present disclosure, and a PUSCH overlaps with a PUCCH in a specific slot.

[0044] FIG. 33 is a flowchart showing the process of selecting an initial transmission resource of a transmission block of a terminal according to one embodiment of the present disclosure.

[0045] FIG. 34 is a flowchart showing a process in which a terminal according to one embodiment of the present disclosure determines a condition for termination when repeatedly transmitting CG PUSCH.

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

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

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

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

[0050] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing may be assigned substantially the same reference number.

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

[0052] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B (next generation node B), an eNode B (E-URTRA node B), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) may be referred to as the wireless transmission path of a signal transmitted by the base station to the terminal, and the uplink (UL) may be referred to as the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, while LTE (long term evolution) or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure, at the discretion of a person with skilled technical knowledge.

[0053] At this time, it can be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that execute a computer or other programmable data processing equipment by performing a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer may also provide steps for executing the functions described in the flowchart block(s).

[0054] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0055] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0056] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed and high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

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

[0058] As a future communication system following LTE, that is, a 5G (fifth generation) communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously may need to be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0059] eMBB can aim to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A (advanced), or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, improvements in various transmission and reception technologies are required, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

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

[0061] Finally, URLLC can be a mission-critical cellular-based wireless communication service. For example, services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts may be considered. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and may simultaneously require a packet error rate of 10^-5 or less. Consequently, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than for other services, and design considerations may be required to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0062] The three 5G services (e.g., eMBB, URLLC, mMTC) can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0063] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0064] Meanwhile, the Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing techniques via connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate connections between objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and / or advanced medical services.

[0065] Accordingly, various attempts are being made to apply 5G communication systems (5th generation communication systems or New Radio (NR)) to IoT (Internet of Things) networks. For example, technologies such as sensor networks, Machine to Machine (M2M) communication, and Machine Type Communication (MTC) are being implemented using 5G communication technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 3G and IoT technologies.

[0066] As a result of the aforementioned developments and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to facilitate the smooth provision of these services.

[0067] [NR Time-Frequency Resources]

[0068] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

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

[0070] The horizontal axis of FIG. 1 may represent the time domain, and the vertical axis may represent the frequency domain. For example, in the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104).

[0071] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0072] Referring to FIG. 2, an example of a frame (200), subframe (201), and slot (202) structure according to one embodiment is illustrated. One frame (200) may be defined as 10ms. One subframe (201) may be defined as 1ms, and thus one frame (200) may consist of a total of 10 subframes (201). One slot (202, 203) may be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are set as the subcarrier spacing value are illustrated. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by Table 1 below.

[0073]

[0074] [Bandwidth Section (BWP)]

[0075] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0076] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0077] FIG. 3 illustrates an example in which a terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). A base station may configure one or more bandwidth portions for a terminal and may configure the following information for each bandwidth portion.

[0078]

[0079] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to the configuration information described above. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, radio resource control (RRC) signaling. Among the one or more configured bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via downlink control information (DCI).

[0080] According to one embodiment, prior to the Radio Resource Control (RRC) connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information regarding a Control Resource Set (CORESET) and a Search Space via the MIB, through which a Physical Downlink Control Channel (PDCCH) can be transmitted to receive system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. In addition, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for control area #0, i.e., configuration information for search area #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. In this case, the identifier (identity, ID) of the initial bandwidth portion may be identified as 0.

[0081] The settings for the bandwidth supported by 5G can be used for various purposes.

[0082] According to one embodiment, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through a bandwidth portion setting. For example, by setting a frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and / or receive data at a specific frequency position within the system bandwidth.

[0083] According to one embodiment, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, the two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0084] According to one embodiment, for the purpose of reducing the power consumption of the terminal, a base station may set a bandwidth portion having a different bandwidth size for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and / or receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, monitoring an unnecessary downlink control channel using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. For the purpose of reducing the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. 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, it can transmit and / or receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0085] Regarding the method of configuring the bandwidth part, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part through the Master Information Block (MIB) during the initial connection phase. For example, a terminal can receive a Control Resource Set (CORESET) for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIBs) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set by the MIB can be considered (or identified) as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and / or Random Access.

[0086] [Bandwidth Section (BWP) Change]

[0087] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, referring to FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may indicate Bandwidth Part #2 (302) to the terminal using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0088] As mentioned above, DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH. Therefore, when a terminal receives a request for a bandwidth portion change, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the DCI within the changed bandwidth portion without difficulty. To this end, the standard specifies the required delay time (T) for bandwidth portion changes. BWP The requirements for ) have been defined, and can be defined as, for example, as follows.

[0089]

[0090] The requirements for bandwidth portion change delay time may support Type 1 or Type 2 depending on the terminal's capability. The terminal may report the supported bandwidth portion delay time type to the base station.

[0091] According to one embodiment, in accordance with the requirements for the aforementioned bandwidth portion change delay time, when a terminal receives a DCI including a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be performed at a time no later than this. In this case, the terminal may perform transmission and / or reception for the data channel (or data) scheduled by the DCI in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWPBy considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0092] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the received DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0093] [SS / PBCH Block]

[0094] Next, we will explain the SS (Synchronization Signal) / PBCH block in 5G.

[0095] An SS / PBCH block can be referred to as a physical layer channel block composed of PSS (Primary SS), SSS (Secondary SS), and PBCH. Specific details are as follows.

[0096] - PSS: A signal that serves as the reference for downlink time / frequency synchronization and provides some information about the cell ID (identity).

[0097] - SSS: Serves as the reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0098] - PBCH: Provides essential system information required for transmitting and / or receiving data channels and control channels of the terminal. The essential system information may include search space-related control information representing wireless resource mapping information of the control channel and / or scheduling control information for a separate data channel that transmits system information.

[0099] - SS / PBCH block: An SS / PBCH block consists of a combination of PSS, SSS, and / or PBCH. One or more SS / PBCH blocks may be transmitted within a time of 5ms, and each transmitted SS / PBCH block may be distinguished by an index.

[0100] According to one embodiment, the terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. The terminal can obtain MIB from PBCH and receive a Control Resource Set (CORESET) #0 from it (which may correspond to a control resource set with a control resource index of 0). The terminal can perform monitoring of Control Resource Set #0 by assuming that the selected SS / PBCH block and the Demodulation Reference Signal (DMRS) transmitted from Control Resource Set #0 are Quasi-Co-Locationed (QCL). The terminal can receive system information as downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to Random Access Channel (RACH) required for initial connection from the received system information. The terminal can transmit a Physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information regarding the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among the respective SS / PBCH blocks and is monitoring the associated control area #0.

[0101] [PDCCH: DCI related]

[0102] Next, Downlink Control Information (DCI) in a 5G system is explained in detail.

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

[0104] According to one embodiment, the DCI can be transmitted through a Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the terminal. Different RNTIs may be used depending on the purpose of the DCI message (e.g., terminal-specific (UE-specific) data transmission, power control commands, or random access responses). That is, the RNTI may not be explicitly transmitted but may be included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI, and if the result of the CRC check is correct, the terminal can identify that the message was transmitted to the terminal.

[0105] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).

[0106] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0107]

[0108] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH. In this case, the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, at least some of the following information.

[0109]

[0110]

[0111] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH. In this case, the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, at least some of the following information.

[0112]

[0113] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0114]

[0115]

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

[0117] In the following, the downlink control channel in a 5G communication system is explained in more detail with reference to the drawings.

[0118] FIG. 4 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. For example, FIG. 4 may illustrate an example in which two control resources (control resource #1 (401), control resource #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) in the frequency axis and one slot (420) in the time axis.

[0119] Referring to FIG. 4, control areas (401, 402) can be set to a specific frequency resource (403) within the entire terminal bandwidth portion (410) along the frequency axis. Along the time axis, they can be set to one or more OFDM symbols, which can be defined as the control resource set duration (404). Referring to the example illustrated in FIG. 4, control area #1 (401) may be set to a control resource set duration of 2 symbols, and control area #2 (402) may be set to a control resource set duration of 1 symbol.

[0120] The control domain in the aforementioned 5G can be configured by a base station to a terminal via upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring a control domain to a terminal means providing information such as a control domain identifier, the frequency location of the control domain, and / or the symbol length of the control domain. For example, information for configuring a control domain may include at least some of the following information.

[0121]

[0122]

[0123] In [Table 8], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control area.

[0124] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. For example, according to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be referenced as a REG (Resource Element Group, 503). For example, the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0125] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 504), then 1 CCE (504) can be composed of multiple REGs (503). For example, if the multiple REGs (503) illustrated in FIG. 5 are described, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), then 1 CCE (504) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to and transmitted by one or multiple CCEs (504) according to the Aggregation Level (AL) within the control area. The CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0126] The basic unit of the downlink control channel, namely the REG (503) illustrated in FIG. 5, may include both the REs to which the DCI is mapped and the DMRS (505), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 5, three DMRSs (505) may be transmitted within one REG (503). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, and 16 depending on the Aggregation Level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode on a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces on all configured aggregation levels.

[0127] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a set of pre-agreed CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0128] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and / or the control domain index to be monitored in the search space. For example, it may include at least some of the following information.

[0129]

[0130]

[0131] According to the configuration information, the base station may configure one or multiple sets of search spaces for the terminal. According to one embodiment, the base station may configure search space set 1 and search space set 2 for the terminal, and the base station may configure DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and the base station may configure DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in a terminal-specific search space.

[0132] Based on configuration information, one or more sets of search spaces may exist in a common search space or a terminal-specific search space. For example, Search Space Set #1 and Search Space Set #2 may be configured as a common search space, and Search Space Set #3 and Search Space Set #4 may be configured as a terminal-specific search space.

[0133] In the common search space, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

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

[0135] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0136] - DCI format 2_1 with CRC scrambled by INT-RNTI

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

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

[0139] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the following examples.

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

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

[0142] The specified RNTIs may follow the definitions and uses below.

[0143] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0144] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0145] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0146] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

[0147] P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted.

[0148] SI-RNTI (System Information RNTI): Used for PDSCH scheduling where system information is transmitted.

[0149] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH has been punctured.

[0150] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0151] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0152] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

[0153] The aforementioned specified DCI formats may follow the definitions below.

[0154]

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

[0156]

[0157] The value may be 0 for the common search space.

[0158] In the case of a terminal-specific search space, the value may correspond to a value that varies according to the terminal's identity (C-RNTI or ID set by the base station for the terminal) and the time index.

[0159] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., parameters in Table 10), the set of search space sets monitored by the terminal may vary at each point in time. For example, if search space set #1 is configured for an X-slot period and search space set #2 is configured for a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0160] [PDCCH: span]

[0161] A terminal may perform terminal capability reporting for cases where it has multiple PDCCH monitoring locations within a slot at each subcarrier interval, and the concept of a Span may be used. A Span may refer to consecutive symbols within a slot through which the terminal can monitor a PDCCH, and each PDCCH monitoring location is within one Span. A Span can be expressed as (X,Y). Here, x represents the minimum number of symbols that must be separated between the first symbols of two consecutive Spans, and Y may be referenced as the number of consecutive symbols through which a PDCCH can be monitored within one Span. In this case, the terminal can monitor a PDCCH within a Span in a interval of Y symbols from the first symbol of the Span.

[0162] Figure 6 is a diagram illustrating, through a span, a case in which a terminal in a wireless communication system can have multiple PDCCH (physical downlink control channel) monitoring locations within a slot.

[0163] Referring to Fig. 6, the Span can be (X,Y) = (7,4), (4,3), or (2,2), and each of the three cases is represented as (6-00), (6-05), and (6-10) within Fig. 6. For example, (6-00) represents the case where there are two Spans that can be represented as (7,4) within the slot. The distance between the first symbols of the two Spans is represented as X=7, and PDCCH monitoring locations can exist within a total of Y=3 symbols from the first symbol of each Span, indicating that search spaces 1 and 2 exist respectively within Y=3 symbols. As another example, (6-05) represents the case where there are a total of three Spans that can be represented as (4,3) within the slot, and the distance between the second and third Spans is shown to be X'=5 symbols, which is greater than X=4.

[0164] [PDCCH: Terminal Capability Report]

[0165] The slot locations where the aforementioned common search space and terminal-specific search space are located are indicated by the monitoringSymbolsWithinSlot parameter in [Table 9], and the symbol locations within the slots are indicated by a bitmap through the monitoringSymbolsWithinSlot parameter in [Table 9]. Meanwhile, the symbol locations within the slots where the terminal can monitor the search space can be reported to the base station through the following terminal capabilities (UE capabilities).

[0166] - Terminal capability 1 (hereinafter referred to as FG 3-1). This terminal capability may mean the capability to monitor a monitoring occasion (MO) when that MO is located within the first 3 symbols of the slot, provided that there is one monitoring occasion for a Type 1 and Type 3 common search space or a terminal-specific search space within the slot, as shown in [Table 11] below. This terminal capability is a mandatory capability that all terminals supporting NR must support, and whether this capability is supported may not be explicitly reported to the base station.

[0167]

[0168] - Terminal capability 2 (hereinafter referred to as FG 3-2). This terminal capability may be referred to as a monitoring capability regardless of the starting symbol position of a monitoring occasion (MO) for a common search space or a terminal-specific search space, as shown in [Table 12] below, where there is one monitoring occasion within the slot. This terminal capability may be optionally supported by the terminal, and support for this capability may be explicitly reported to the base station.

[0169]

[0170] - Terminal capability 3 (hereinafter referred to as FG 3-5, 3-5a, and 3-5b). This terminal capability may indicate a pattern of monitoring occasions (MOs) that the terminal can monitor when multiple monitoring occasions exist within a slot for a common search space or a terminal-specific search space, as shown in [Table 13] below. The aforementioned pattern may consist of an interval X between start symbols between different MOs and a maximum symbol length Y for one MO. The combinations of (X,Y) supported by the terminal may be one or more of {(2,2), (4,3), (7,3)}. This terminal capability is optional for the terminal to support, and whether this capability is supported and the aforementioned combinations of (X,Y) may be explicitly reported to the base station.

[0171]

[0172]

[0173] According to one embodiment, the terminal may report to the base station whether it supports the above-described terminal capability 2 and / or terminal capability 3 and related parameters. Based on the reported terminal capability, the base station may perform time-axis resource allocation for a common search space and a terminal-specific search space. When allocating resources, the base station may ensure that the terminal does not place a monitoring occasion (MO) in a location where it cannot be monitored.

[0174] [QCL, TCI state]

[0175] In a wireless communication system, one or more different antenna ports (or may be replaced by one or more channels, signals, and combinations thereof, but for convenience in the following description of the disclosure, they will be referred to collectively as different antenna ports) may be associated with each other by a QCL (Quasi co-location) setting as shown in [Table 14] below. A TCI (transmission configuration indication) state is intended to indicate the QCL relationship between a PDCCH (or PDCCH DMRS) and another RS ​​(reference signal) or channel. When a reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are QCLed with each other, it may mean that the terminal is permitted to apply some or all of the large-scale channel parameters estimated from the antenna port A to the channel measurement from the antenna port B. QCL may require associating different parameters depending on at least one of the following situations: 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) BM (beam management) affected by spatial parameters. Accordingly, NR can support four types of QCL relationships as shown in Table 14 below.

[0176]

[0177] According to one embodiment, the spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming and / or spatial channel correlation.

[0178] According to one embodiment, QCL relationships may be set for a terminal through the radio resource control (RRC) parameters TCI-State and QCL-Info as shown in [Table 15] below. Referring to [Table 15], the base station may set one or more TCI states for the terminal and provide up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS that references the ID of the TCI state, i.e., the target RS. At this time, each QCL information (e.g., QCL-Info) included in each TCI state may include the serving cell index and BWP index of the reference RS pointed to by the QCL information, the type and ID of the reference RS, and / or a QCL type such as [Table 14].

[0179]

[0180] Figure 7 is a diagram illustrating an example of base station beam allocation according to TCI state settings.

[0181] Referring to FIG. 7, a base station according to one embodiment can transmit information about N different beams to a terminal through N different TCI states. For example, as in FIG. 7, when N=3, the base station can notify that antenna ports referencing the different TCI states (e.g., 700, 705, or 710) are associated with different spatial Rx parameters (e.g., different beams) by setting the qcl-Type2 parameters included in the three TCI states (700, 705, 710) to be associated with CSI-RS or SSB corresponding to different beams and set to QCL type D.

[0182] Tables 16 through 20 below show valid TCI state settings according to the target antenna port type.

[0183] [Table 16] shows valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). TRS can be referenced as an NZP CSI-RS in which the repetition parameter is not set and trs-Info is set to true. In [Table 16], setting 3 can be used for aperiodic TRS.

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

[0185]

[0186] [Table 17] shows the valid TCI state settings when the target antenna port is CSI-RS for CSI. CSI-RS for CSI can be referred to as NZP (non-zero power) CSI-RS in which the parameter indicating repetition (e.g., repetition parameter) is not set and trs-Info is also not set to true.

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

[0188]

[0189] [Table 18] may indicate valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, which is the same meaning as CSI-RS for L1 RSRP reporting). CSI-RS for BM can be referenced as an NZP CSI-RS in which the repetition parameter is set to On or Off and trs-Info is not set to true.

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

[0191]

[0192] [Table 19] shows the valid TCI state settings when the target antenna port is a PDCCH DMRS.

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

[0194]

[0195] [Table 20] shows the valid TCI state settings when the target antenna port is PDSCH DMRS.

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

[0197]

[0198] A representative QCL setting method according to [Table 16] to [Table 20] may be operated by setting the target antenna port and reference antenna port for each stage as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS". Through this, it may be possible to link statistical characteristics measurable from SSB and TRS to each antenna port to assist the reception operation of the terminal.

[0199] [PDCCH: TCI state related]

[0200] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port may be as shown in [Table 21] below. In [Table 21], the fourth row represents the combinations assumed by the terminal prior to RRC setup, and setup after RRC may not be possible.

[0201]

[0202] NR (new radio) can support a hierarchical signaling method as illustrated in FIG. 8 for dynamic allocation of PDCCH beams. Referring to FIG. 8, the base station can set N TCI states (805, 810, ..., 820) to the terminal through RRC signaling (800), and some of the set N TCI states can be set as TCI states for CORESET (control resource set) (825). Subsequently, the base station can instruct the terminal to one of the TCI states for CORESET (830, 835, 840) through MAC CE signaling (845). Subsequently, the terminal can receive PDCCH based on beam information contained in the TCI state indicated by MAC CE signaling.

[0203] FIG. 9 is a diagram illustrating a TCI (transmission configuration indicator) indication MAC (medium access control) CE (control element) signaling structure for a PDCCH DMRS (demodulation reference signal) in a wireless communication system according to one embodiment of the present disclosure.

[0204] Referring to FIG. 9, the TCI indication MAC CE signaling for PDCCH DMRS consists of 2 bytes (16 bits) and may include a 5-bit serving cell ID (915), a 4-bit CORESET ID (920), and a 7-bit TCI state ID (925).

[0205] FIG. 10 is a diagram illustrating an example of beam configuration for a control resource set (CORESET) and a search space according to the above description.

[0206] Referring to FIG. 10, a base station may indicate one of the TCI state lists included in the CORESET (1000) setting through MAC CE signaling (1005). Subsequently, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal may consider that the same QCL information (beam #1, 1005) is applied to all one or more search spaces (1010, 1015, 1020) connected to the CORESET. The above-described PDCCH beam allocation method has the disadvantage that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also that the same beam is applied collectively to all CORESETs regardless of search space characteristics, which may cause problems that make flexible PDCCH beam operation difficult. The embodiments of the present disclosure below may provide a more flexible PDCCH beam setting and operation method. In describing the embodiments of the present disclosure below, several distinct examples are provided for convenience of explanation, but they are not mutually exclusive and may be appropriately combined and applied depending on the situation.

[0207] The base station may set one or more TCI states for a specific control area for the terminal, and may activate one of the set TCI states through a MAC CE activation command. For example, if {TCI state#0, TCI state#1, TCI state#2} are set as TCI states for control area #1, the base station may transmit a command to the terminal via MAC CE to activate TCI state#0 as the TCI state for control area #1. For example, based on the activation command for the TCI state received via MAC CE, the terminal can correctly receive the DMRS of the corresponding control area based on the QCL information within the activated TCI state.

[0208] For a control area (control area #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control area #0, it can be assumed that the terminal has QCL with an SS / PBCH block identified in a non-contention-based random access process that is not triggered by an initial access process or a PDCCH command for DMRS transmitted from control area #0.

[0209] For a control area (control area #X) where the index is set to a value other than 0, if the terminal has not received a TCI state for control area #X, or has received one or more TCI states but has not received a MAC CE activation command to activate one of them, it can be assumed that the terminal has QCL with the SS / PBCH block identified during the initial connection process with the DMRS transmitted from control area #X.

[0210] [PDCCH: QCL prioritization rule related]

[0211] The QCL priority determination operation for PDCCH is described below.

[0212] According to one embodiment, a terminal operates as a carrier aggregation within a single cell or band, and when multiple control resource sets existing within an active bandwidth portion of a single or multiple cells overlap in time while having the same or different QCL-TypeD characteristics during a specific PDCCH monitoring interval, the terminal selects a specific control resource set according to a QCL priority determination operation and can monitor control resource sets having the same QCL-TypeD characteristics as the selected control resource set. That is, when multiple control resource sets overlap in time, only one QCL-TypeD characteristic can be received. At this time, the criteria for determining QCL priority may be as follows.

[0213] - Criterion 1. Within the cell corresponding to the lowest index among the cells containing the common search interval, the control resource set connected to the common search interval of the lowest index.

[0214] - Criterion 2. Within the cell corresponding to the lowest index among cells containing the terminal-specific search range, the control resource set connected to the terminal-specific search range of the lowest index.

[0215] As described above, if the corresponding criterion is not satisfied, the following criterion may be applied. For example, if control resource sets overlap in time during a specific PDCCH monitoring interval, and if not all control resource sets are connected to a terminal-specific search interval rather than a common search interval, that is, if criterion 1 is not satisfied, the terminal may omit the application of criterion 1 and apply criterion 2.

[0216] When a terminal selects a control resource set based on the criteria described above, it may additionally consider two matters regarding the QCL information set in the control resource set as follows. First, if control resource set 1 has CSI-RS 1 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 1 is SSB 1, and another control resource set 2 has SSB 1 as a reference signal having a QCL-TypeD relationship, the terminal may consider that these two control resource sets 1 and 2 have different QCL-TypeD characteristics. Secondly, if control resource set 1 has CSI-RS 1 set in cell 1 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 1 is SSB 1, and control resource set 2 has CSI-RS 2 set in cell 2 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 2 is the same SSB 1, then the terminal can consider that the two control resource sets have the same QCL-TypeD characteristics.

[0217] FIG. 12 is a diagram illustrating a method for selecting a set of receivable control resources by considering priority when a terminal receives a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0218] According to one embodiment, the terminal may be configured to receive a plurality of control resource sets that overlap in time during a specific PDCCH monitoring interval (1210), and these plurality of control resource sets may be connected to a common search space or a terminal-specific search space for a plurality of cells. Within the PDCCH monitoring interval, within the first bandwidth portion (1200) of cell 1, there may be a first control resource set (1215) connected to the first common search portion, and within the first bandwidth portion (1205) of cell 2, there may be a first control resource set (1220) connected to the first common search portion and a second control resource set (1225) connected to the second terminal-specific search portion. Control resource sets (1215) and (1220) have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 1, and control resource set (1225) can have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 2. Therefore, if reference 1 is applied to the corresponding PDCCH monitoring section (1210), all other control resource sets having a reference signal of QCL-TypeD, such as the first control resource set (1215), can be received. Therefore, the terminal can receive control resource sets (1215) and (1220) in the PDCCH monitoring section (1210). In one embodiment, the terminal may be configured to receive a plurality of control resource sets that overlap in time during a specific PDCCH monitoring interval (1240), and these plurality of control resource sets may be connected to a common search space or a terminal-specific search space for a plurality of cells.Within the PDCCH monitoring section, within the first bandwidth section (1230) of cell 1, there may be a first control resource set (1245) connected to a specific search section of terminal 1 and a second control resource set (1250) connected to a specific search section of terminal 2, and within the first bandwidth section (1235) of cell 2, there may be a first control resource set (1255) connected to a specific search section of terminal 1 and a second control resource set (1260) connected to a specific search section of terminal 3. Control resource sets (1245) and (1250) have a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 1 and QCL-TypeD, control resource set (1255) has a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD, and control resource set (1260) can have a relationship with the second CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD. However, if criterion 1 is applied to the corresponding PDCCH monitoring section (1240), there is no common search section, so the next criterion, criterion 2, can be applied. If criterion 2 is applied to the corresponding PDCCH monitoring section (1240), all other control resource sets having a reference signal of QCL-TypeD, such as control resource set (1245), can be received. Therefore, the terminal can receive control resource sets (1245) and (1250) in the corresponding PDCCH monitoring section (1240).

[0219] [Regarding Rate Matching / Puncturing]

[0220] Rate matching and puncturing operations are described below.

[0221] When a time and frequency resource A intended to transmit an arbitrary symbol sequence A overlaps with an arbitrary time and frequency resource B, rate matching or puncturing operations may be considered as transmission and reception operations of channel A, taking into account the area resource C where resource A and resource B overlap. Specific operations may follow the details below.

[0222] Rate Matching Operation

[0223] - According to one embodiment, a base station may transmit a symbol sequence A to a terminal by mapping channel A only to the remaining resource area, excluding resource C which corresponds to the area overlapping with resource B among the entire resource A. For example, if symbol sequence A is composed of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the base station may sequentially map and send symbol sequence A to {Resource #1, Resource #2, Resource #4}, which are the remaining resources excluding {Resource #3}, which corresponds to resource C among resource A. Consequently, the base station may transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #3} by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0224] According to one embodiment, a terminal can determine resources A and resources B from scheduling information for a symbol sequence A from a base station, and thereby determine (or identify) resource C, which is an area where resources A and resources B overlap. The terminal can receive symbol sequence A by assuming that symbol sequence A is mapped and transmitted to the remaining area of ​​all resources A, excluding resource C. For example, if symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol 4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A by assuming that it is sequentially mapped to the remaining resources {resource #1, resource #2, resource #4}, excluding {resource #3} which corresponds to resource C among resources A. Consequently, the terminal can perform a subsequent series of receiving operations by assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #3} is transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0225] Puncturing action

[0226] According to one embodiment, if there is a resource C corresponding to an area overlapping with resource B among all resources A to which a base station intends to transmit a symbol sequence A to a terminal, the base station maps the symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only in the remaining resource area of ​​resource A excluding resource C. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the base station can map symbol sequence A {Symbol #1, Symbol #2, Symbol #3, Symbol #4} to resource A {Resource #1, Resource #2, Resource #3, Resource #4} respectively, and can transmit only the symbol sequence {Symbol #1, Symbol #2, Symbol #4} corresponding to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3} corresponding to resource C, and may not transmit {Symbol #3} mapped to {Resource #3} corresponding to resource C. Consequently, the base station can map and transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #4} to {Resource #1, Resource #2, Resource #4} respectively.

[0227] According to one embodiment, a terminal can determine resource A and resource B from scheduling information for symbol sequence A from a base station, and thereby determine resource C, which is an area where resource A and resource B overlap. The terminal can receive symbol sequence A by assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the terminal can assume that symbol sequence A {Symbol #1, Symbol #2, Symbol #3, Symbol #4} is mapped to resource A {Resource #1, Resource #2, Resource #3, Resource #4} respectively, but {Symbol #3} mapped to {Resource #3} corresponding to resource C is not transmitted, and can receive by assuming that symbol sequence {Symbol #1, Symbol #2, Symbol #4} corresponding to the remaining resources {Resource #1, Resource #2, Resource #4}—excluding {Resource #3} corresponding to resource C—is mapped and transmitted. Consequently, the terminal can perform a subsequent series of receiving operations by assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #4} has been transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0228] In the following, a method for setting rate matching resources for the purpose of rate matching in a 5G communication system is described. For example, rate matching can be understood as adjusting the size of a signal by considering the amount of resources available to transmit the signal. For example, rate matching of a data channel can be understood as adjusting the size of the data by mapping the data channel to a specific time and frequency resource range so that it is not transmitted.

[0229] FIG. 11 is a diagram illustrating a method for a base station and a terminal to transmit and / or receive data by considering downlink data channels and rate matching resources.

[0230] FIG. 11 illustrates a downlink data channel (PDSCH, 1101) and a rate matching resource (1102). A base station may set one or more rate matching resources (1102) to a terminal via upper layer signaling (e.g., RRC signaling). The setting information for the rate matching resource (1102) may include at least one of time axis resource allocation information (1103), frequency axis resource allocation information (1104), and / or period information (1105). In the following description, the bitmap corresponding to the frequency axis resource allocation information (1104) will be referred to as the “first bitmap,” the bitmap corresponding to the time axis resource allocation information (1103) as the “second bitmap,” and the bitmap corresponding to the period information (1105) as the “third bitmap.” If all or part of the time and frequency resources of a scheduled data channel (1101) overlap with a set rate matching resource (602), the base station can transmit the data channel (1101) by rate matching it in the rate matching resource (1102) portion, and the terminal can perform reception and decoding after assuming that the data channel (1101) is rate matched in the rate matching resource (1102) portion.

[0231] According to one embodiment, the base station may dynamically notify the terminal via DCI whether to rate match a data channel in the set rate matching resource portion through additional settings (corresponding to the “rate matching indicator” in the aforementioned DCI format). For example, the base station may select some of the set rate matching resources and group them into rate matching resource groups, and may indicate to the terminal via DCI using a bitmap method whether to rate match a data channel for each rate matching resource group. For example, if four rate matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station may set RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4} as rate matching groups, and may indicate to the terminal via a bitmap whether to rate match in RMG#1 and RMG#2, respectively, using 2 bits in the DCI field. For example, the base station may instruct the terminal to "1" if rate matching is required, and "0" if rate matching is not required.

[0232] In 5G, granularity of the “RB (resource block) symbol level” and “RE (resource element) level” can be supported as a method of setting the aforementioned rate matching resources in a terminal. More specifically, the following setting method may be followed.

[0233] RB symbol level

[0234] The terminal can receive up to four RateMatchPatterns as upper layer signaling for each bandwidth portion, and one RateMatchPattern may include the following contents.

[0235] - As a Reserved Resource within the bandwidth portion, a resource may be included in which the time and frequency resource domains of the said Reserved Resource are set as a combination of an RB level bitmap and a symbol level bitmap along the frequency axis. The Reserved Resource may span across one or two slots. Additionally, a time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may be additionally set.

[0236] - It may include time and frequency domain resource areas set as control resource sets within the bandwidth portion, and resource areas corresponding to time domain patterns set as search space settings where the resource areas are repeated.

[0237] RE level

[0238] The terminal can receive the following information through upper-layer signaling (e.g., RRC message).

[0239] - As configuration information for an RE corresponding to an LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern (lte-CRS-ToMatchAround), it may include the number of ports (nrofCRS-Ports) and LTE-CRS-vshift(s) value (v-shift) of the LTE (long term evolution) CRS, information on the location of the LTE carrier's center subcarrier (carrierFreqDL) from a reference frequency point (e.g., reference point A), information on the LTE carrier's bandwidth (carrierBandwidthDL), and subframe configuration information (mbsfn-SubframConfigList) corresponding to a Multiast-broadcast single-frequency network (MBSFN). Based on the aforementioned information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0240] - It may include configuration information for resource sets corresponding to one or more ZP (Zero Power) CSI-RS within the bandwidth portion.

[0241] [Regarding LTE CRS rate match]

[0242] Next, the rate match process for the LTE CRS described above is explained. For the coexistence of LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR is provided with a function to set the pattern of the LTE CRS (Cell Specific Reference Signal) to the NR terminal. For example, the CRS pattern may be provided by RRC signaling that includes at least one parameter within the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0243] In Rel-15 NR, a function is provided to set one CRS pattern per serving cell through the above lte-CRS-ToMatchAround parameter. In Rel-16 NR, the function has been expanded to allow multiple CRS patterns to be set per serving cell. For example, for a Single-TRP (transmission and reception point) configured terminal, one CRS pattern can be set per LTE carrier, and for a Multi-TRP configured terminal, two CRS patterns can be set per LTE carrier. For example, for a Single-TRP configured terminal, up to three CRS patterns per serving cell can be set through the above lte-CRS-PatternList1-r16 parameter. As another example, for a multi-TRP configured terminal, CRS can be set per TRP. In other words, the CRS pattern for TRP1 is set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are configured as described above, whether the CRS patterns of both TRP1 and TRP2 are applied to a specific PDSCH (Physical Downlink Shared Channel), or whether the CRS pattern of only one TRP is applied, is determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter; if the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, whereas otherwise, the CRS patterns of both TRPs may be applied.

[0244] [Table 22] shows a ServingCellConfig IE including the above CRS pattern, and [Table 23] shows a RateMatchPatternLTE-CRS IE including at least one parameter for the CRS pattern.

[0245]

[0246]

[0247]

[0248] [PDSCH: Processing Time]

[0249] In the following, the PDSCH processing procedure time is described. When a base station schedules a terminal to transmit a PDSCH using DCI format 1_0, 1_1, or 1_2, the terminal may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated by the DCI (modulation and coding scheme (MCS), information related to the demodulation reference signal, time and frequency resource allocation information, etc.). In NR, the PDSCH processing time is defined taking this into account. The terminal's PDSCH processing time may be based on [Equation 2] below.

[0250] [Mathematical Formula 2]

[0251] T proc,1 = ( N1+ d 1,1 + d2)( 2048 + 144 ) κ2 -μ T c + T ext

[0252] T in [Mathematical Equation 2] proc,1 In this, each variable can be defined as follows.

[0253] - N1: The number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 based on the terminal's capability and the numerology μ. Depending on the terminal's capability report, it may have the value in [Table 24] if terminal processing capability is reported as 1, and may have the value in [Table 24-2] if terminal processing capability is reported as 2 and the availability of terminal processing capability 2 is established through upper-layer signaling. Numerology μ is the above T proc,1 to maximize μ PDCCH , μ PDSCH, μ UL It can correspond to the minimum value among them, and μ PDCCH , μ PDSCH, μ UL Each can be referenced as the numerology of the PDCCH that scheduled the PDSCH, the numerology of the scheduled PDSCH, and the numerology of the uplink channel to which the HARQ-ACK will be transmitted.

[0254]

[0255]

[0256] - κ: 64

[0257] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext can be calculated and applied to the PDSCH processing time. Otherwise, T ext is assumed to be 0.

[0258] - If l1, which represents the PDSCH DMRS position value, is 12, then N1,0 of [Table 24] above can have a value of 14, otherwise it can have a value of 13.

[0259] - For PDSCH mapping type A, if the last symbol of the PDSCH is the i-th symbol in the slot where the PDSCH is transmitted, and i < 7, then d 1,1 is 7-i, and otherwise d1,1 It can be 0.

[0260] - d2: If a PUCCH with a high priority index and a PUCCH or PUSCH with a low priority index overlap in time, the d2 of the PUCCH with the high priority index may be set to the value reported from the terminal. Otherwise, d2 may be 0.

[0261] - If PDSCH mapping type B is used for terminal processing capability 1, d 1,1 The value can be determined according to L, which is the number of symbols of the scheduled PDSCH, and d, which is the number of overlapping symbols between the PDSCH scheduling the PDSCH and the scheduled PDSCH, as follows.

[0262] - If L ≥ 7, then d 1,1 = 0.

[0263] - If L ≥ 4 and L ≤ 6, then d 1,1 = 7 - L.

[0264] - If L = 3, then d 1,1 = min (d, 1)

[0265] - If L = 2, then d 1,1 = 3 + d.

[0266] - If PDSCH mapping type B is used for terminal processing capability 2, d 1,1 The value can be determined according to L, which is the number of symbols of the scheduled PDSCH, and d, which is the number of overlapping symbols between the PDSCH scheduling the PDSCH and the scheduled PDSCH, as follows.

[0267] - If L ≥ 7, then d 1,1 = 0.

[0268] - If L ≥ 4 and L ≤ 6, then d 1,1 = 7 - L.

[0269] - When L = 2,

[0270] - If the scheduled PDSCH exists within a CORESET consisting of 3 symbols, and the CORESET and the scheduled PDSCH have the same starting symbol, d 1,1 = 3.

[0271] - Otherwise, d 1,1 = d.

[0272] - For a terminal that supports capability 2 within a given serving cell, the PDSCH processing time according to the terminal processing capability 2 can be applied when processingType2Enabled, which is an upper layer signaling (e.g., RRC message) for the cell, is set to enabled.

[0273] According to one embodiment, the location of the first uplink transmission symbol of the PUCCH containing HARQ-ACK information (where the location may take into account K1, which is defined as the transmission time of the HARQ-ACK, the PUCCH resources used for HARQ-ACK transmission, and timing advance effects) is T after the last symbol of the PDSCH. proc,1 If it does not start before the first uplink transmission symbol occurring after a specified amount of time, the terminal may transmit a valid HARQ-ACK message. That is, the terminal may transmit a PUCCH containing a HARQ-ACK only if there is sufficient PDSCH processing time. Otherwise, the terminal may not be able to provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. proc,1 It can be used for both standard and extended CPs. For example, in the case of a PDSCH consisting of two PDSCH transmission positions within a single slot, d 1,1 It can be calculated based on the first PDSCH transmission position within the slot.

[0274] [PDSCH: Readiness time during cross-carrier scheduling]

[0275] μ, the numerology to which the next scheduled PDCCH is transmitted PDCCH and μ, the numerology through which the PDSCH scheduled via the corresponding PDCCH is transmitted PDSCH In the case of different cross-carrier scheduling, N is the terminal's PDSCH reception readiness time defined for the time interval between the PDCCH and PDSCH. pdsch is explained.

[0276] If μ PDCCH < μ PDSCH In this case, the scheduled PDSCH is N from the last symbol of the PDCCH that scheduled the PDSCH. pdsch It cannot be transmitted before the first symbol of the slot following the symbol. The transmission symbol of the corresponding PDSCH may include DM-RS.

[0277] If μ PDCCH > μ PDSCH In this case, the scheduled PDSCH is N from the last symbol of the PDCCH that scheduled the PDSCH. pdsch It can be transmitted starting from the symbol. The transmission symbol of the PDSCH may include DM-RS.

[0278] [Table 25] shows N according to the scheduled PDCCH subcarrier interval. pdsch It represents.

[0279]

[0280] [Regarding SRS]

[0281] Next, a method for estimating an uplink channel using the transmission of a terminal's Sounding Reference Signal (SRS) is described. A base station may set at least one SRS configuration for each uplink bandwidth part (BWP) to transmit configuration information for SRS transmission to the terminal, and may also set at least one SRS resource set for each SRS configuration. In one embodiment, the base station and the terminal may exchange upper signaling information as follows to transmit information regarding the SRS resource set.

[0282] - srs-ResourceSetId: SRS resource set index

[0283] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set

[0284] - resourceType: This is the time-axis transmission setting for 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 usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0285] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0286] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.

[0287] The terminal can base the SRS resources included in the set of SRS resource indices referenced in the SRS resource set on the information set in the SRS resource set.

[0288] According to one embodiment, a base station and a terminal may transmit and receive upper-layer signaling information (e.g., RRC messages and / or MAC CE) to transmit individual configuration information for an SRS resource. For example, the individual configuration information for an SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Additionally, the individual configuration information for an SRS resource may include a time-axis transmission setting for the SRS resource, which may be set to 'periodic', 'semi-persistent', or 'aperiodic'. This may be limited to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

[0289] According to one embodiment, a base station may activate or deactivate or trigger SRS transmission to a terminal through upper layer signaling, including RRC signaling or MAC CE signaling, or L1 (layer 1) signaling (e.g., DCI). For example, the base station may activate or deactivate periodic SRS transmission to the terminal through upper layer signaling. The base station may instruct the terminal to activate an SRS resource set with resourceType set to periodic through upper layer signaling, and the terminal may transmit an SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation information configured in the SRS resource, or may refer to associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is activated for a periodic SRS resource activated through upper layer signaling.

[0290] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to activate an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to an SRS resource set where the resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on 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 associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined based on the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without adhering to it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

[0291] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) via the SRS request field of the DCI. The terminal may understand that an SRS resource set containing the aperiodic SRS resource trigger indicated via the DCI has been triggered from the list of aperiodic SRS resource triggers among the configuration information of the SRS resource set. 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 may be based on the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource may be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which may be based on the value(s) included in the set of slot offsets set in the SRS resource set. For example, the slot offset between a PDCCH containing a DCI and an SRS resource may be the value specified in the time domain resource assignment field of the DCI from among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource or the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.

[0292] According to one embodiment, when a base station triggers aperiodic SRS transmission to a terminal via a DCI, a minimum time interval may be required between the PDCCH containing the DCI that triggers the aperiodic SRS transmission and the transmitted SRS so that the terminal applies configuration information for the SRS resource to transmit the SRS. For example, the time interval for the terminal's SRS transmission may be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggers the aperiodic SRS transmission and the first symbol to which the first transmitted SRS resource among the transmitted SRS resource(s) is mapped. For example, the minimum time interval may be determined based on the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values ​​depending on the use case of the SRS resource set including the transmitted SRS resource. For example, the minimum time interval may be determined by N2 symbols defined by considering the terminal's processing capability according to the terminal's capability, referencing the terminal's PUSCH preparation procedure time. Additionally, 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 determined to be N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be determined to be N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.

[0293]

[0294]

[0295] The spatialRelationInfo setting information in [Table 26] is intended to be applied to the beam information of a reference signal (e.g., the beam used for the SRS transmission) by referencing a single reference signal. For example, the spatialRelationInfo setting may include information such as that in [Table 27] below.

[0296]

[0297] When referring to the spatialRelationInfo setting, an SS / PBCH block index, a CSI-RS index, or an SRS index can be set as the index of the reference signal to be referenced in order to use the beam information of a specific reference signal. The upper signaling referenceSignal is configuration information indicating which reference signal's beam information to reference for the corresponding SRS transmission, and ssb-Index can mean the SS / PBCH block index, csi-RS-Index the CSI-RS index, and srs the SRS index, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting 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 receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used during the transmission of the SRS corresponding to srs as the transmission beam for the transmission of the SRS.

[0298] [PUSCH: Regarding transmission method]

[0299] Next, the scheduling method for PUSCH transmissions is described. PUSCH transmissions can be dynamically scheduled by an uplink (UL) grant within the DCI, or operated by a configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmissions can be provided by DCI format 0_0 or 0_1.

[0300] Configured grant Type 1 PUSCH transmissions can be semi-statically configured by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 28], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 28], through the upper signaling. When PUSCH transmissions are operated by configured grants, parameters applied to the PUSCH transmissions can be applied through configuredGrantConfig, the upper signaling of [Table 28], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 29]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 28], the terminal can apply tp-pi2BPSK in pusch-Config of [Table 29] to PUSCH transmissions operated by the configured grant.

[0301]

[0302]

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

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

[0305]

[0306]

[0307] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the terminal can determine a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (number of PUSCH transmission layers).

[0308] According to one embodiment, the SRI may be provided via the field SRS resource indicator within the DCI or set to the terminal via the higher-level signaling srs-ResourceIndicator. The terminal receives at least one SRS resource during codebook-based PUSCH transmission, and may receive up to two. When the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI may be referenced as the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. Additionally, the TPMI and transmission rank may be provided via the field precoding information and number of layers within the DCI or set to the terminal via the higher-level signaling precodingAndNumberOfLayers. The TPMI may be used to indicate the precoder applied to the PUSCH transmission. When the terminal receives one SRS resource, the TPMI is used to indicate the precoder to be applied to the one configured SRS resource. If the terminal is configured with multiple SRS resources, TPMI can be used to specify the precoder to be applied to the SRS resource indicated by SRI.

[0309] According to one embodiment, a precoder to be used for PUSCH transmission may be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config may be set to at least one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE (user equipment) capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0310] According to one embodiment, a terminal may receive one SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within the said SRS resource set may be indicated via SRI. If multiple SRS resources are set within the SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', the terminal may expect that the value of nrofSRS-Ports within the upper signaling SRS-Resource will be set to the same value for all SRS resources.

[0311] According to one embodiment, a terminal may transmit one or more SRS resources included in an SRS resource set in which the value of usage is set to 'codebook' according to upper signaling to a base station, and the base station may select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using the transmit beam information of the said SRS resource. In this case, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and may be included in the DCI. Additionally, the base station may include information in the DCI that instructs the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal may perform PUSCH transmission by using the SRS resource instructed by the SRI, applying the instructed rank based on the transmit beam of the SRS resource and the precoder instructed by the TPMI.

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

[0313] According to one embodiment, for an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal may receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal may perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than 42 symbols, the terminal may not expect the information for the precoder for SRS transmission to be updated.

[0314] According to one embodiment, if the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS may be indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

[0315] According to one embodiment, if a periodic or semi-continuous SRS resource set is configured, the associated NZP CSI-RS may be indicated through the associated CSI-RS within the SRS-ResourceSet, which is the parent signaling. For non-codebook-based transmission, the terminal does not expect the spatialRelationInfo, which is the parent signaling for the SRS resource, and the associated CSI-RS within the SRS-ResourceSet, which is the parent signaling, to be configured together.

[0316] According to one embodiment, when a terminal receives multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI may be indicated via a field SRS resource indicator within the DCI or set via the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the terminal receives an SRI via the DCI, the SRS resource indicated by the received SRI may be referenced as an SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within a single SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the terminal to the base station. In this case, the SRS resources transmitted simultaneously by the terminal may occupy the same RB. The terminal can configure one SRS port for each SRS resource. Only one SRS resource set can be configured where the value of usage in the upper signaling SRS-ResourceSet is set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook based PUSCH transmission.

[0317] According to one embodiment, a base station transmits one NZP-CSI-RS connected to an SRS resource set to a terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. In this case, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the SRI is included within the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of PUSCH, and the terminal can transmit PUSCH by applying the precoder applied to the transmission of SRS resources to each layer.

[0318] [PUSCH: Preparation Process Time]

[0319] Next, the PUSCH preparation procedure time is described. When a base station schedules a terminal to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the terminal may require PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method specified through the DCI (transmission precoding method of the SRS resource, number of transmission layers, spatial domain transmission filter). In NR, the PUSCH preparation procedure time has been defined taking this into account. The terminal's PUSCH preparation procedure time may follow [Equation 3] below.

[0320] [Mathematical Formula 3]

[0321] T proc,2 = max(( N2+ d 2,1 + d2)( 2048 + 144 ) κ2 -μ T c + T ext + T switch , d 2,2 )

[0322] T in [Equation 3] proc,2 In this, each variable can have the following meanings.

[0323] - N2: A number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the terminal's capability. If the terminal processing capability is reported as 1 according to the terminal's capability report, it has the value of [Table 30], and if the terminal processing capability is reported as 2 and the ability to use terminal processing capability 2 is set through upper layer signaling, it may have the value of [Table 31].

[0324] [Table 30]

[0325]

[0326] [Table 31]

[0327]

[0328] - d 2,1 : The number of symbols determined as 0 if the resource elements of the first OFDM symbol of the PUSCH transmission are all configured to consist only of DM-RS, and 1 otherwise.

[0329] - κ: 64

[0330] - μ: μ DL or μ UL Middle, T proc,2 It follows the value that becomes larger. μ DL can be referenced as the numerology of the downlink through which a PDCCH containing a DCI scheduling PUSCH is transmitted, and μ UL can be referenced as the numerology of the uplink through which PUSCH is transmitted.

[0331] - T c : , , has.

[0332] - d 2,2 : If the DCI scheduling PUSCH directs BWP switching, follow the BWP switching time; otherwise, have 0.

[0333] - d2: If the OFDM symbols of PUCCH, PUSCH with a higher priority index, and PUCCH with a lower priority index overlap in time, the d2 value of PUSCH with the higher priority index is used. Otherwise, d2 is 0.

[0334] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext It can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0335] - T switch: T when the uplink switching interval is triggered switch is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0336] When the base station and terminal consider the time-axis resource mapping information of the PUSCH scheduled via DCI and the influence of uplink-downlink timing advance, from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, T proc,2 Subsequently, if the first symbol of the PUSCH starts before the first uplink symbol initiated by the CP, it can be determined that the PUSCH preparation time is insufficient. Otherwise, the base station and the terminal can determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only if the preparation time is sufficient, and can ignore the DCI scheduling the PUSCH if the preparation time is insufficient.

[0337] [PUSCH: Repetitive transmission related]

[0338] The following describes the repetitive transmission of uplink data channels in a 5G system. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can receive either PUSCH repetitive transmission type A or B as a setting for upper layer signaling.

[0339] PUSCH repetitive transmission type A

[0340] As described above, the symbol length of the uplink data channel and the position of the start symbol are determined by a time domain resource allocation method within a single slot, and the base station can notify the terminal of the number of repeated transmissions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0341] - The terminal may repeatedly transmit an uplink data channel in consecutive slots in which the length and start symbol of the uplink data channel configured based on the number of repeated transmissions received from the base station are substantially the same. In this case, if at least one of the slots configured as downlink by the base station to the terminal, or at least one of the symbols of the uplink data channel configured to the terminal, is configured as downlink, the terminal may omit the transmission of the uplink data channel, but the number of repeated transmissions of the uplink data channel may be counted.

[0342] PUSCH Repeated Transmission Type B

[0343] As described above, in order to allocate time domain resources within a single slot, the start symbol and length of the uplink data channel are determined, and the base station may notify the terminal of the number of repetitions through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0344] - Based on the start symbol and length of the uplink data channel configured 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 in that slot is It can be given by. The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is It is given by, where n=0,..., numberofrepetitions-1 and S represents the start symbol of the configured uplink data channel, L represents the symbol length of the configured uplink data channel. K s indicates the slot where the PUSCH transmission starts. Indicates the number of symbols per slot.

[0345] - The terminal can determine invalid symbols for PUSCH repeat transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as invalid symbols for PUSCH repeat transmission type B. Additionally, invalid symbols can be set in upper layer parameters (e.g., InvalidSymbolPattern). Invalid symbols can be set in upper layer parameters (e.g., InvalidSymbolPattern) by providing a symbol-level bitmap spanning one or two slots. In the bitmap, 1 represents an invalid symbol. Additionally, the periodicity and pattern of the bitmap can be set through upper layer parameters (e.g., periodicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal may apply the invalid symbol pattern.

[0346] After an invalid symbol is determined, for each nominal repetition, the terminal may consider symbols other than the invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Each actual repetition may include a consecutive set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot.

[0347] FIG. 14 is a drawing illustrating an example of a PUSCH (physical uplink shared channel) repetitive transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0348] Referring to FIG. 14, a terminal according to one embodiment may have the start symbol S of the uplink data channel set to 0 and the length L of the uplink data channel set to 14, and the number of repeated transmissions set to 16. In this case, the nominal repetition may be represented in 16 consecutive slots (301). Then, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (301) is an invalid symbol. Additionally, the terminal may determine that the symbols set to 1 in the invalid symbol pattern (302) are invalid symbols. In each nominal repetition, if valid symbols that are not invalid symbols are composed of one or more consecutive symbols in one slot, they may be set as an actual repetition and transmitted (303).

[0349] In one embodiment, for PUSCH repetitive transmissions, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmissions and configured grant-based PUSCH transmissions that cross slot boundaries.

[0350] - Method 1 (mini-slot level repetition): With one UL grant, two or more PUSCH repeat transmissions may be scheduled within a single slot or across the boundaries of consecutive slots. Additionally, for Method 1, time-domain resource allocation information within the DCI may indicate the resources for the first repeat transmission. Additionally, time-domain resource information for the remaining repeat transmissions may be determined based on the time-domain resource information for the first repeat transmission and the uplink or downlink direction determined for each symbol in each slot. Each repeat transmission may occupy consecutive symbols.

[0351] - Method 2 (multi-segment transmission): Two or more PUSCH (physical uplink shared channel) repeat transmissions may be scheduled in consecutive slots through a single UL grant. In this case, one transmission is designated per slot, and each transmission may have a different start point or repeat length. Additionally, in Method 2, time-domain resource allocation information within the DCI may indicate the start point and repeat length of all repeat transmissions. Furthermore, when repeat transmissions are performed within a single slot via Method 2, if there are multiple consecutive uplink symbol bundles within that slot, each repeat transmission may be performed for each uplink symbol bundle. If there is only a unique consecutive uplink symbol bundle within that slot, one PUSCH repeat transmission may be performed according to the method of NR Release 15.

[0352] - Method 3: Two or more repeated PUSCH transmissions may be scheduled in consecutive slots through two or more UL grants. In this case, one transmission is assigned per slot, and the n-th UL grant may be received before the PUSCH transmission scheduled by the n-1-th UL grant is finished.

[0353] - Method 4: Through one UL grant or one configured grant, one or more PUSCH repeat transmissions within a single slot, or two or more PUSCH repeat transmissions across the boundaries of consecutive slots, may be supported. The number of repeats instructed by the base station to the terminal is merely a nominal value, and the number of PUSCH repeat transmissions actually performed by the terminal may be greater than the nominal number of repeats. Time-domain resource allocation information within the DCI or within the configured grant may be referenced as the resource for the first repeat transmission instructed by the base station. Time-domain resource information for the remaining repeat transmissions may be determined by referencing at least the resource information of the first repeat transmission and the uplink or downlink direction of the symbols. For example, if the time-domain resource information for the repeat transmission instructed by the base station spans a slot boundary or includes an uplink / downlink switching point, the repeat transmission may be divided into multiple repeat transmissions. In this case, one repeat transmission may be included within a single slot for each uplink period.

[0354] The above-described repetitive transmission may be applicable to both DG (Dynamic Grant) PUSCH and CG (Configured Grant) PUSCH. DG PUSCH can be referenced as a method in which all PUSCH scheduling information is provided by DCI, and CG PUSCH can be referenced as a method in which PUSCH scheduling information is provided only by upper signals or by some DCIs. Additionally, DG PUSCH can be referenced as a method in which the terminal transmits PUSCH only within the scheduling area provided by DCI, and CG PUSCH can be referenced as a method in which the terminal periodically transmits PUSCH without receiving a separate DCI in accordance with the period set by the upper signals.

[0355] [PUSCH: Frequency Hopping Process]

[0356] Frequency hopping of the uplink data channel (Physical Uplink Shared Channel, PUSCH) in a 5G system is explained below.

[0357] In 5G, two methods can be supported for each PUSCH repeat transmission type as the frequency hopping method for the uplink data channel. In PUSCH repeat transmission type A, intra-slot frequency hopping and inter-slot frequency hopping are supported, and in PUSCH repeat transmission type B, inter-repetition frequency hopping and inter-slot frequency hopping can be supported.

[0358] The intra-slot frequency hopping method supported by PUSCH repeat transmission type A may be a method in which a terminal transmits by changing the allocated resources in the frequency domain by a set frequency offset at two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be represented by [Equation 4].

[0359] [Mathematical Formula 4]

[0360]

[0361] In [Equation 4], i=0 and i=1 represent the first hop and the second hop, respectively, and RB start represents the starting RB within the UL BWP and can be calculated from the frequency resource allocation method. RB offset It can represent the frequency offset between two hops through upper-layer parameters. The number of symbols in the first hop is It can be represented as, and the number of symbols for the second hop is It can be represented as. is the length of PUSCH transmission within one slot, which can represent the number of OFDM (orthogonal frequency division multiplexing) symbols.

[0362] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal transmits by changing the allocated resource in the frequency domain by a set frequency offset for each slot. In inter-slot frequency hopping The starting RB during the slot can be represented through [Equation 5].

[0363] [Mathematical Formula 5]

[0364]

[0365] In [Mathematical Formula 5], is the current slot number in a multi-slot PUSCH transfer, RB start represents the starting RB within the UL BWP and can be calculated from the frequency resource allocation method. RB offset It can represent the frequency offset between two hops through upper layer parameters.

[0366] Next, the inter-repetition frequency hopping method supported by PUSCH repeat transmission type B may involve transmitting resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition, shifted by a set frequency offset. In the frequency domain for one or more actual repetitions within the nth nominal repetition, RB, which is the index of the starting RB, start (n) can follow [Equation 6] below.

[0367] [Mathematical Formula 6]

[0368]

[0369] In [Equation 6], n is the index of the nominal repetition, RB offset can represent the RB offset between two hops through the upper layer parameter.

[0370] [PUSCH: multiplexing rule when AP / SP CSI reporting]

[0371] The following describes a method for measuring and reporting channel status in a 5G communication system.

[0372] Channel state information (CSI) may include channel quality information (CQI), precoding matrix index (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSSBRI), layer indicator (LI), rank indicator (RI), and / or L1-RSRP (Reference Signal Received Power). The base station may control time and frequency resources for the aforementioned CSI measurement and reporting of the terminal.

[0373] For the aforementioned CSI measurement and reporting, the terminal may receive setting information for N (≥1) CSI reports (CSI-ReportConfig), setting information for M (≥1) RS transmission resources (CSI-ResourceConfig), and / or one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) through upper-layer signaling. More specifically, the setting information for the aforementioned CSI measurement and reporting may be as described below in [Table 32] to [Table 38].

[0374] [Table 32] describes CSI-ReportConfig.

[0375]

[0376]

[0377]

[0378]

[0379]

[0380]

[0381] [Table 33] shows CSI-ResourceConfig.

[0382]

[0383]

[0384] [Table 34] shows NZP-CSI-RS-ResourceSet.

[0385]

[0386]

[0387] [Table 35] shows CSI-SSB-ResourceSet.

[0388]

[0389] [Table 36] shows CSI-IM-ResourceSet.

[0390]

[0391] [Table 37] shows the CSI-AperiodicTriggerStateList.

[0392]

[0393]

[0394] [Table 38] shows CSI-SemiPersistentOnPUSCH-TriggerStateList.

[0395]

[0396] According to one embodiment, for the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig may be associated with a downlink (DL) bandwidth portion identified by a bandwidth portion identifier (bwp-id) of an upper-layer parameter given by CSI-ResourceConfig, a CSI resource setting associated with the report setting. As a time-domain reporting operation for each report setting CSI-ReportConfig, 'aperiodic', 'semi-persistent', or 'periodic' methods may be supported, and such methods may be configured from the base station to the terminal by the reportConfigType parameter set from the upper layer. The semi-persistent CSI reporting method may support 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. In the case of a periodic or semi-permanent CSI reporting method, the terminal may receive a PUCCH or PUSCH resource to transmit the CSI from the base station via upper layer signaling. The period and slot offset of the PUCCH or PUSCH resource to transmit the CSI may be given as the numerology of the uplink (UL) bandwidth portion configured for transmitting the CSI report. In the case of a non-periodic CSI reporting method, the terminal may receive a PUSCH resource to transmit the CSI scheduled from the base station via L1 signaling (the aforementioned DCI format 0_1).

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

[0398] - CSI-IM resources for interference measurement

[0399] - NZP CSI-RS resources for interference measurement

[0400] - NZP CSI-RS resources for channel measurement

[0401] For CSI-RS resource sets associated with a resource setting where the upper-level parameter (e.g., resourceType) is set to 'Aperiodic', 'Periodic', or 'Semi-permanent', the Trigger State for a CSI reporting setting where reportType is set to 'Aperiodic' and the resource setting for channel or interference measurements for one or more component cells (CC) can be set as the upper-level parameter CSI-AperiodicTriggerStateList.

[0402] Non-periodic CSI reporting of the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-permanent CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after being activated by the MAC control element (MAC CE). As previously mentioned, CSI resource settings can also be configured as non-periodic, periodic, or semi-permanent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 39] below.

[0403]

[0404] Aperiodic CSI reporting can be triggered by the “CSI request” field of the aforementioned DCI format 0_1, which corresponds to the scheduling DCI for PUSCH. The terminal can monitor PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicators for PUSCH. The CSI request indicator can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by the upper layer signaling (reportTriggerSize). One trigger state among one or more aperiodic CSI reporting trigger states that can be set by the upper layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0405] - If all bits of the CSI request field are 0, this may be interpreted as not requesting a CSI report.

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

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

[0408] The following [Table 40] shows an example of the relationship between a CSI request indicator and a CSI trigger state that can be indicated by that indicator.

[0409]

[0410] According to one embodiment, the terminal can perform a measurement on a CSI resource within a CSI trigger state triggered by a CSI request field and generate a CSI therefrom (e.g., including at least one of CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP). The terminal can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When a 1-bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates “1”, the terminal can multiplex the uplink data (UL-SCH) and the acquired CSI and transmit them to the PUSCH resource scheduled by DCI format 0_1. When the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates “0”, the terminal can transmit by mapping only the CSI without the uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0411] Figure 13 is a diagram illustrating an example of a non-periodic CSI (channel state information) reporting method.

[0412] In one example (1300) of FIG. 13, the terminal can monitor the PDCCH (1301) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (1305). The terminal can obtain resource information for the CSI-RS (1302) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform a measurement on the CSI-RS (1302) resource being transmitted based on the time when the DCI format 0_1 ​​is received and the parameter for the offset within the CSI resource set (e.g., the aperiodicTriggeringOffset described above) within the NZP CSI-RS resource set (NZP-CSI-RS-ResourceSet). For example, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the non-periodic CSI report is received and the slot in which the CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in [Table 41] below.

[0413]

[0414] In one example (1300) of FIG. 13, an example is described in which the aforementioned offset value is set to X=0. In this case, the terminal can receive CSI-RS (1302) in a slot (corresponding to slot 0 (1306) in FIG. 13) that receives DCI format 0_1 ​​that triggers a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (1305). The terminal can obtain scheduling information for PUSCH (1305) for CSI reporting (information corresponding to each field of the aforementioned DCI format 0_1) from DCI format 0_1. For example, the terminal can obtain information about the slot to transmit PUSCH (1305) from the aforementioned time domain resource allocation information for PUSCH (1305) in DCI format 0_1. In one example (1300) of FIG. 13, the terminal obtains a K2 value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and accordingly, at the time when PUSCH (1305) receives PDCCH (1301), it can be transmitted from slot 3 (1309), which is 3 slots away from slot 0 (1306).

[0415] Referring to an example (1310) of FIG. 13, the terminal can monitor the PDCCH (1311) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (1315). The terminal can obtain resource information for the CSI-RS (1312) to be measured from the received CSI request indicator. In an example (1310) of FIG. 13, an example is described in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (1312) in the slot (corresponding to slot 0 (1316) in FIG. 13) that received the DCI format 0_1 ​​triggering a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (1315).

[0416] According to one embodiment, an aperiodic CSI report may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI report is transmitted via PUSCH, it may be multiplexed with a transport block. For multiplexing, a CRC may be inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The insertion of the CRC may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching during multiplexing of CSI part 1 or CSI part 2 included in the aperiodic CSI report may be calculated as shown in [Table 42] below.

[0417]

[0418]

[0419] According to one embodiment, in the case of PUSCH repetition transmission methods A and B, the terminal may transmit aperiodic CSI report by multiplexing it only during the first repetition of the PUSCH repetition transmission. This may be because the aperiodic CSI report information being multiplexed is encoded in a polar code format, and for it to be multiplexed across multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, since each actual repetition may have a different OFDM symbol length, the aperiodic CSI report may be transmitted by multiplexing it only during the first PUSCH repetition.

[0420] According to one embodiment, for PUSCH repetitive transmission method B, if a terminal receives a DCI that schedules a non-periodic CSI report or enables a semi-permanent CSI report without scheduling for a transport block, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repetitive transmissions set by the upper layer signaling is greater than 1. Additionally, if the terminal schedules or enables a non-periodic or semi-permanent CSI report without scheduling for a transport block based on PUSCH repetitive transmission method B, the terminal may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including a semi-permanent CSI based on PUSCH repetitive transmission method B without scheduling for a DCI after the semi-permanent CSI report is enabled by a DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0421] [Regarding Terminal Capability Reporting]

[0422] In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the base station while connected to the serving base station. In the description below, this procedure may be referred to as a UE capability report.

[0423] According to one embodiment, a base station may transmit a UE capability enquiry message requesting a capability report to a connected terminal. The UE capability enquiry message may include a request for a terminal capability by the base station's RAT (radio access technology) type. The request by RAT type may include information on supported frequency band combinations, etc. According to one embodiment, in the case of the UE capability enquiry message, multiple UE capabilities by RAT type may be requested through a single RRC message container transmitted by the base station. Alternatively, in one embodiment, the base station may transmit the UE capability enquiry message, which includes a request for a terminal capability by each RAT type, to the terminal multiple times. For example, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may compose a corresponding UE capability information message and report it to the base station multiple times. In a next-generation mobile communication system, a UE capability request can be made for NR, LTE, EN-DC (E-UTRA (universal terrestrial radio access) - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). In addition, while terminal capability inquiry messages are generally transmitted initially after the terminal connects to the base station, the base station can request them under any conditions when necessary.

[0424] At this stage, a terminal that has received a request from a base station to report UE capability can configure terminal capability according to the RAT type and band information requested from the base station. The method by which a terminal configures UE capability in an NR system is described below.

[0425] 1. When a terminal receives a list of LTE and / or NR bands from a base station via a UE capability request, the terminal can configure a band combination (BC) for EN-DC and NR stand alone (SA). That is, based on the bands requested from the base station via FreqBandList, the terminal can configure a candidate list of BCs for EN-DC and NR SA. Additionally, the bands may have priority in the order listed in FreqBandList.

[0426] 2. If the base station requests a UE capability report by setting the "eutra-nr-only" flag or the "eutra" flag, the terminal may completely remove NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the "eutra" capability.

[0427] 3. The terminal may remove fallback BCs from the candidate list of BCs configured in the above-described step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC, and this step may be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step may also be applied to MR-DC, that is, LTE bands may also be applied. The BCs remaining after this step may be the final "candidate BC list."

[0428] 4. The terminal can select BCs to report by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal can construct the supportedBandCombinationList in a defined order. That is, the terminal can construct the BCs and UE capabilities to report according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, the terminal can construct a featureSetCombination for the constructed supportedBandCombinationList and construct a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0429] 5. If the requested rat Type is eutra-nr and has an influence, featureSetCombinations can be included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set can only be included in UE-NR-Capabilities.

[0430] After terminal capability is configured, the terminal can transmit a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station can subsequently perform appropriate scheduling and transmission / reception management for the terminal.

[0431] [CA / DC Related]

[0432] FIG. 15 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation (CA), dual connectivity (DA) situation according to one embodiment of the present disclosure.

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

[0434] According to one embodiment, the main functions of the NR SDAP (S25, S70) may include at least some of the following functions.

[0435] - User data transfer function (transfer of user plane data)

[0436] - Mapping function between a QoS (quality of service) flow and a DRB (data radio bearer) for both DL and UL for uplink and downlink

[0437] - Marking QoS flow ID for uplink and downlink (marking QoS (quality of service) flow ID in both DL and UL packets)

[0438] - Function to map reflective QoS flow to the data bearer for uplink SDAP PDUs (protocol data units).

[0439] In one embodiment, regarding an SDAP layer device, the terminal may receive a setting via an RRC message regarding whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, or for each bearer, or for each logical channel. If the SDAP header is set, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers to the NAS (non-access stratum) reflective QoS setting 1-bit indicator (NAS reflective QoS) and the AS (access stratum) reflective QoS setting 1-bit indicator (AS reflective QoS) of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

[0440] The main functions of NR PDCP (S30, S65) may include at least some of the following functions.

[0441] - Header compression and decompression features (ROHC only)

[0442] - User data transfer function (Transfer of user data)

[0443] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0444] - Out-of-sequence delivery of upper layer PDUs

[0445] - Reordering function (PDCP PDU reordering for reception)

[0446] - Duplicate detection function (Duplicate detection of lower layer SDU (service data unit)s)

[0447] - Retransmission of PDCP SDUs

[0448] - Encryption and decryption functions (Ciphering and deciphering)

[0449] - Timer-based SDU discard in uplink.

[0450] In one embodiment, the reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on a PDCP SN (sequence number), and may include a function that transmits data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

[0451] The main functions of NR RLC (S35, S60) may include at least some of the following functions.

[0452] - Data transfer function (Transfer of upper layer PDUs)

[0453] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0454] - Out-of-sequence delivery of upper layer PDUs

[0455] - ARQ function (Error Correction through ARQ)

[0456] - Concatenation, segmentation, and reassembly functions (Concatenation, segmentation, and reassembly of RLC SDUs)

[0457] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0458] - Reordering function (Reordering of RLC data PDUs)

[0459] Duplicate detection

[0460] - Error detection function (Protocol error detection)

[0461] -RLC SDU deletion function (RLC SDU discard)

[0462] -RLC (radio link control) re-establishment function (RLC re-establishment)

[0463] In one embodiment, the in-sequence delivery function of the NR RLC device may mean a function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering the RLC SDUs when the original RLC SDU is received divided into multiple RLC SDUs, a function of rearranging the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, or a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs described above may be processed in the order in which they are received (e.g., regardless of the order of sequence number, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0464] In one embodiment, the out-of-sequence delivery function of the NR RLC device may be referred to as a function that delivers RLC SDUs received from a lower layer directly to an upper layer regardless of order, and may include a function to reassemble and deliver them when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function to store the RLC SN or PDCP SN of the received RLC PDUs and to sort the order to record the lost RLC PDUs.

[0465] The NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include at least some of the following functions.

[0466] - Mapping function (Mapping between logical channels and transport channels)

[0467] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0468] - Scheduling information reporting function

[0469] - HARQ function (Error correction through HARQ)

[0470] - Priority handling between logical channels of one UE

[0471] - Priority handling between UEs by means of dynamic scheduling

[0472] -MBMS service identification function (MBMS service identification)

[0473] - Transport format selection function

[0474] --Padding

[0475] The NR PHY layer (S45, S50) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0476] According to one embodiment, the detailed structure of the wireless protocol structure may vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal may use a protocol structure having a single structure up to the RLC, such as S10, but multiplexing the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to the RLC, such as S20, but multiplexing the PHY layer through the MAC layer.

[0477] Referring to the descriptions regarding PDCCH and beam settings mentioned above, PDCCH repeated transmission is not supported in current Rel-15 and Rel-16 NR, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC (ultra-reliable low latency communications). The present invention improves the PDCCH reception reliability of a terminal by providing a PDCCH repeated transmission method through multiple transmission reception points (TRPs). The specific method is described in detail in the following examples.

[0478] Embodiments of the present disclosure are described below together with the accompanying drawings. The contents of the present disclosure may be applicable to FDD and TDD systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a physical layer downlink data channel, or from a terminal to a base station using a physical layer uplink data channel, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC CE).

[0479] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above may be referred to as the NC-JT case.

[0480] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0481] In the following disclosure, the examples are described through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0482] [Regarding NC-JT]

[0483] According to one embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a terminal to receive PDSCH from a plurality of TRPs.

[0484] Unlike existing systems, 5G wireless communication systems can support not only services requiring high transmission speeds but also services requiring very short transmission delays and high connection density. In a wireless communication network comprising multiple cells, TRPs (transmission and reception points), or beams, coordinated transmission between each cell, TRP, or / and beam can satisfy various service requirements by increasing the signal strength received by the terminal or efficiently performing interference control between each cell, TRP, or / and beam.

[0485] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication and can be referred to as a technology that increases the signal strength or throughput received by a terminal by transmitting signals to a single terminal through multiple different cells, TRPs, and / or beams. In this case, the characteristics of the channels between each cell, TRP, or / or beam and the terminal may differ significantly. In particular, in the case of Non-Coherent Joint Transmission (NC-JT), which supports non-coherent precoding between each cell, TRP, or / or beam, individual precoding, MCS, resource allocation, TCI instructions, etc., may be required depending on the link-specific channel characteristics between each cell, TRP, or / or beam and the terminal.

[0486] The aforementioned NC-JT transmission may be applied to at least one of the physical downlink shared channel (PDSCH), physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), or physical uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and / or TCI may be indicated as DL DCI, and for NC-JT transmission, said transmission information may need to be indicated independently per 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 the DCI. Therefore, to support JT in PDSCH, it may be necessary to carefully design the tradeoff between the amount of DCI information and the reception performance of control information.

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

[0488] Referring to Fig. 16, examples for PDSCH transmission are described according to the Joint Transmission (JT) technique, and examples for allocating radio resources by TRP are illustrated.

[0489] According to one embodiment, an example (N000) of a Coherent Joint Transmission (C-JT) that supports coherent precoding between each cell, TRP or / and beam is shown.

[0490] In the case of C-JT, TRP A (N005) and TRP B (N010) transmit a single data (PDSCH) to the terminal (N015), and joint precoding can be performed in multiple TRPs. This can be referenced as TRP A (N005) and TRP B (N010) transmitting DMRS through the same DMRS ports to transmit the same PDSCH. For example, TRP A (N005) and TRP B (N010) can each transmit DMRS to the terminal through DMRS port A and DMRS B. In this case, the terminal can receive one DCI information for receiving a single PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0491] FIG. 16 shows an example (N020) of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0492] In the case of NC-JT, a PDSCH is transmitted to the terminal (N035) for each cell, TRP, and / or beam, and individual precoding may be applied to each PDSCH. Each cell, TRP, and / or beam can transmit a different PDSCH or a different PDSCH layer to the terminal to improve throughput compared to single cell, TRP, and / or beam transmission. Additionally, each cell, TRP, and / or beam can repeatedly transmit the same PDSCH to the terminal to improve reliability compared to single cell, TRP, and / or beam transmission. For convenience of explanation, the cell, TRP, and / or beam may be referred to as TRP below.

[0493] At this time, various wireless resource allocations may be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (N040), when the frequency and time resources used by multiple TRPs do not overlap at all (N045), and when some of the frequency and time resources used by multiple TRPs overlap (N050).

[0494] To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal.

[0495] FIG. 17 is a diagram illustrating an example of the configuration of downlink control information (DCI) for NC-JT in which each TRP transmits different PDSCH or different PDSCH layers to a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0496] Referring to FIG. 17, according to one embodiment, case #1 (N100) may be an example in which, in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently of the control information for the PDSCH transmitted from the serving TRP. For example, a terminal may obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). The formats between the independent DCIs may be the same or different from each other, and the payloads between the DCIs may also be the same or different from each other. In the aforementioned case #1, the degrees of freedom for each PDSCH control or allocation can be fully guaranteed, but if each DCI is transmitted from different TRPs, coverage differences per DCI may occur, which may degrade reception performance.

[0497] According to one embodiment, case #2 (N105) describes a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted to each of them, and each of these DCIs may be dependent on the control information for the PDSCH transmitted from the serving TRP.

[0498] For example, DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCH transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI transmitting control information for PDSCH transmitted from cooperative TRPs, since the payload is smaller compared to normal DCI (nDCI) transmitting PDSCH-related control information transmitted from a serving TRP, it may be possible to include reserved bits compared to nDCI.

[0499] According to one embodiment, case #2 may have the freedom of each PDSCH control or allocation limited depending on the content of the information element included in sDCI, but since the receiving performance of sDCI is superior to that of nDCI, the probability of a coverage difference between DCIs occurring may be reduced.

[0500] According to one embodiment, case #3 (N110) describes a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI may be dependent on the control information for the PDSCH transmitted from the serving TRP.

[0501] For example, in the case of DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), it is possible to include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and in the case of control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it is possible to collect and transmit only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into a single 'secondary' DCI (sDCI). For example, the sDCI may include at least one piece 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) indicators or carrier indicators, the DCI of the serving TRP (DCI#0, normal DCI, nDCI) may be followed.

[0502] According to one embodiment, case #3 (N110) may limit the freedom of each PDSCH control or allocation according to the content of the information element included in sDCI, but the reception performance of sDCI can be adjusted, and the complexity of DCI blind decoding of the terminal can be reduced compared to case #1 (N100) or case #2 (N105).

[0503] According to one embodiment, case #4 (N115) is an example in which, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. For example, a terminal can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of case #4 (N115), the complexity of the terminal's DCI blind decoding may not increase, but the degree of freedom for PDSCH control or allocation may be low, such as when the number of cooperating TRPs is limited by the long DCI payload limit.

[0504] In the following description and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI formats 1_0 to 1_1 described above) containing PDSCH control information transmitted from a cooperative TRP, and unless a specific limitation is specified, the description may be similarly applied to various auxiliary DCIs.

[0505] In the following description and embodiments, the aforementioned cases #1 (N100), #2 (N105), and #3 (N110), in which one or more DCIs (e.g., PDCCH) are used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (N115), in which a single DCI (PDCCH) is used to support NC-JT, may be classified as single PDCCH-based NC-JT. In PDCCH transmission based on multiple PDCCH, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. Methods for distinguishing the CORESETs may include distinguishing them through upper layer indicators for each CORESET, and / or distinguishing them through beam settings for each CORESET. In addition, in a single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH having multiple layers is scheduled, and the aforementioned multiple layers can be transmitted from multiple TRPs. In this case, the connection relationship between a layer and the TRP transmitting that layer can be indicated through a TCI (Transmission Configuration Indicator) indication for the layer.

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

[0507] In the embodiments of the present disclosure, the phrase “where NC-JT is applied” can be interpreted in various ways depending on the situation, such as “where a terminal receives one or more PDSCHs simultaneously in one BWP,” “where a terminal receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications simultaneously in one BWP,” and / or “where the PDSCHs received by the terminal are associated with one or more DMRS port groups,” but for the convenience of explanation, it has been used as a single expression.

[0508] In the present disclosure, 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 using a structure based on MAC layer multiplexing similar to S10 in FIG. 15 (e.g., CA-like method) is possible. On the other hand, when the backhaul delay between cooperative TRPs is large enough to be negligible (e.g., when more than 2 ms is required for the exchange of information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method using a structure independent of each TRP from the RLC layer to secure delay-robust characteristics (DC-like method) similar to S20 in FIG. 15 may be possible.

[0509] According to one embodiment, a terminal supporting C-JT / NC-JT receives C-JT / NC-JT related parameters or setting values, etc., from an upper layer configuration and can set the terminal's RRC parameters based thereon. For the upper layer configuration, the terminal may utilize UE capability parameters, for example, tci-StatePDSCH. For example, UE capability parameters, for example, tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be set to 4, 8, 16, 32, 64, and / or 128 in FR1 and 64 and / or 128 in FR2, 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 via a MAC CE message. The maximum value 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC within 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 beamforming instructions or beamforming change commands for at least one PDSCH in one TRP.

[0510] [Multi-DCI-based Multi-TRP]

[0511] According to one embodiment of the present disclosure, a downlink control channel for NC-JT transmission can be established based on Multi-PDCCH.

[0512] In NC-JT based on multiple PDCCH, when transmitting DCI for the PDSCH schedule of each TRP, a CORESET or search space may be provided for each TRP. The CORESET or search space for each TRP may be configured as in at least one of the following cases.

[0513] - Setting the upper layer index per CORESET: The CORESET setting information configured as the upper layer may include an index value, and the TRP transmitting the PDCCH from the corresponding CORESET can be distinguished by the configured CORESET-specific index value. For example, in a set of CORESETs with the same upper layer index value, it may be assumed that the same TRP transmits the PDCCH, or that a PDCCH scheduling the PDCCH of the same TRP is transmitted. The aforementioned CORESET-specific index may be named as CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value configured, it may be assumed that the PDCCH is transmitted from the same TRP. For a CORESET where the CORESETPoolIndex value is not configured, it may be assumed that the default value of CORESETPoolIndex is configured, and the aforementioned default value may be 0.

[0514] - Multiple PDCCH-Config Settings: Multiple PDCCH-Configs are configured within a single BWP, and each PDCCH-Config may include PDCCH settings per TRP. That is, a single PDCCH-Config may contain a list of CORESETs per TRP and / or a list of search spaces per TRP, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config may be considered to correspond to a specific TRP.

[0515] - CORESET Beam / Beam Group Configuration: TRPs corresponding to a given CORESET can be distinguished through beams or beam groups configured per CORESET. For example, if the same TCI state is configured for multiple CORESETs, those CORESETs can be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP within that CORESET can be considered to be transmitted.

[0516] - Search Space Beam / Beam Group Configuration: Beams or beam groups are configured for each search space, allowing TRPs to be distinguished by search space. For example, if the same beam / beam group or TCI state is set in multiple search spaces, it can be assumed that the same TRP is transmitting a PDCCH in that search space, or that a PDCCH scheduling the same TRP's PDSCH is being transmitted in that search space.

[0517] As described above, by separating the CORESET or search space by TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, thereby enabling the generation of independent HARQ-ACK codebooks and the use of independent PUCCH resources for each TRP.

[0518] The above-described settings may be independent per cell or per BWP. For example, two different CORESETPoolIndex values ​​may be set in a PCell (primary cell), while a specific SCell may not have a CORESETPoolIndex value set. In this case, NC-JT transmission may be configured in the PCell, whereas NC-JT transmission may not be configured in the SCell (secondary cell) where the CORESETPoolIndex value is not set.

[0519] [Single-DCI-based Multi-TRP]

[0520] According to one embodiment of the present disclosure, a downlink beam for NC-JT transmission can be established based on a Single-PDCCH.

[0521] In a single PDCCH-based NC-JT, a single DCI can schedule a PDSCH transmitted by multiple TRPs. In this case, the number of TCI states may be used as a method to indicate the number of TRPs transmitting the PDSCH. For example, if the number of TCI states indicated in the DCI scheduling the PDSCH is 2, it may be considered a single PDCCH-based NC-JT transmission. For example, if the number of TCI states indicated in the DCI scheduling the PDSCH is 1, it may be considered a single-TRP transmission. The TCI states indicated in the above-mentioned DCI may correspond to one or two TCI states among the TCI states activated by MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by MAC-CE, a correspondence relationship is established between the TCI codepoint indicated in the DCI and the TCI states activated by MAC-CE, and there may be two TCI states activated by MAC-CE corresponding to the said TCI codepoint.

[0522] The above-described configuration may be independent per cell or per BWP. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, whereas a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, NC-JT transmission may be configured in the PCell, whereas NC-JT transmission may not be configured in the aforementioned SCell.

[0523] [PHR]

[0524] FIG. 18 illustrates a procedure in which a base station controls the transmission power of a terminal in a cellular system.

[0525] According to one embodiment, with reference to FIG. 18, in step 18-10, a terminal in the coverage area of ​​a base station can perform downlink synchronization with the base station and obtain system information. For example, downlink synchronization can be performed through a synchronization signal PSS / SSS (Primary Synchronization Signal / Secondary Synchronization Signal) received from the base station. The terminals that have performed downlink synchronization can receive a Master Information Block (MIB) and a System Information Block (SIB) from the base station and obtain system information.

[0526] According to one embodiment, with reference to FIG. 18, in step 18-15, the terminal can perform uplink synchronization with the base station through a random access procedure and establish a Raido Resource Control (RRC) connection. In the random access procedure, the terminal can transmit a random access preamble and message 3 (msg3) to the base station via the uplink. Uplink transmit power control can be performed during the transmission of the random access preamble and message 3. For example, the terminal can control uplink transmit power by receiving parameters for uplink transmit power control from the base station via acquired system information, e.g., SIB, or by using agreed parameters. According to one embodiment of the present disclosure, the terminal can measure the Reference Signal Received Power (RSRP) from the path attenuation estimation signal transmitted by the base station and estimate the downlink path attenuation value as in [Equation 7]. Based on the estimated path attenuation value, the terminal can set an uplink transmit power value for transmitting the random access preamble and message 3.

[0527] [Mathematical Formula 7]

[0528] Downlink path attenuation = Base station signal transmission power - RSRP measured by the terminal

[0529] In [Equation 7], the transmission power of the base station signal can be referenced as the transmission power of the downlink path attenuation estimate signal transmitted by the base station. The downlink path attenuation estimate signal transmitted by the base station may be a Cell-specific Reference Signal (CRS) or a Synchronization Signal Block (SSB).

[0530] According to one embodiment, when the path attenuation estimation signal is a Cell-specific Reference Signal (CRS), the transmission power of the base station signal can be referenced as the transmission power of the CRS and can be transmitted to the terminal through the referenceSignalPower parameter of the system information. For example, when the path attenuation estimation signal is a Synchronization Signal Block (SSB), the transmission power of the base station signal can be referenced as the transmission power of the DeModulation Reference Signal (DMRS) transmitted to the Secondary Synchronization Signal (SSS) and PBCH, and can be transmitted to the terminal through the ss-PBCH-BlockPower parameter of the system information.

[0531] Referring to FIG. 18, in steps 18-20, the terminal may receive RRC parameters for uplink transmit power control from the base station via UE-specific RRC or common RRC. The received transmit power control parameters may differ depending on the type of uplink channel and the type of signal transmitted to the uplink. For example, the transmit power control parameters applied to the transmission of the uplink control channel (PUCCH: physical uplink control channel), the uplink data channel (PUSCH: physical uplink shared channel), and the sounding reference signal (SRS: sounding reference signal) may differ from each other.

[0532] According to one embodiment, transmit power control parameters received by the terminal via a system information block (SIB) from a base station prior to RRC connection establishment, or transmit power control parameters used by the terminal as pre-agreed values ​​prior to RRC connection establishment, may be included in the RRC parameters transmitted from the base station after RRC connection establishment. The terminal may use the RRC parameter values ​​received from the base station after RRC connection establishment for uplink transmit power control.

[0533] According to one embodiment, with reference to FIG. 18, in steps 18-25, the terminal may receive a path attenuation estimation signal from the base station. For example, after establishing the RRC connection of the terminal, the base station may configure the CSI-RS (Channel State Information-Reference Signal) as the terminal's path attenuation estimation signal. In this case, the base station may transmit information regarding the transmission power of the CSI-RS to the terminal through the powerControlOffsetSS parameter of the UE dedicated RRC information. At this time, powerControlOffsetSS may be referenced as the difference (offset) in transmission power between the SSB and the CSI-RS.

[0534] According to one embodiment, with reference to FIG. 18, in step 18-30, the terminal can estimate a downlink path attenuation value and set an uplink transmission power value. For example, the terminal can measure the downlink RSRP using CSI-RS and estimate the downlink path attenuation value through [Equation 1] using information on the transmission power of CSI-RS received from the base station. Then, based on the estimated path attenuation value, the uplink transmission power value for PUCCH, PUSCH, and SRS transmission can be set.

[0535] According to one embodiment, with reference to FIG. 18, in step 18-35, the terminal can provide power headroom reporting (PHR) to the base station. Power headroom may be referenced as the difference between the terminal's current transmission power and the terminal's maximum output power.

[0536] According to one embodiment, with reference to FIG. 18, in step 18-40, the base station can optimize system operation based on the reported power headroom. For example, if the power headroom value reported to the base station by a specific terminal is positive, the base station can increase system yield by allocating more resources (RB: Resource Block) to the terminal.

[0537] According to one embodiment, with reference to FIG. 18, in step 18-45, the terminal may receive a transmission power control command (TPC) from the base station. For example, if the power headroom value reported by a specific terminal to the base station is negative, the base station may allocate fewer resources to the terminal or reduce the transmission power of the terminal through the transmission power control command (TPC). This may increase system yield or reduce unnecessary power consumption by the terminal.

[0538] According to one embodiment, with reference to FIG. 18, in step 18-50, the terminal can update the transmit power based on a TPC command. At this time, the TPC command may be transmitted to the terminal via a UE-specific DCI or a group common DCI. Thus, the base station can dynamically control the transmit power of the terminal through the TPC command.

[0539] According to one embodiment, with reference to FIG. 18, in step 18-55, the terminal can perform uplink transmission based on the updated transmission power.

[0540] [PUSCH power control]

[0541] The PUSCH transmission power can be determined through the following [Equation 8].

[0542] [Mathematical Formula 8]

[0543]

[0544] In [Equation 8], P CMAX,f,c (i) is the maximum transmission power set for the terminal for carrier f of serving cell c at time i of PUSCH transmission. is a reference setting transmission power setting value based on the active uplink bandwidth part (BWP) b of the carrier f of the serving cell c, and can have different values ​​depending on various transmission types j. It can have various values ​​depending on whether the PUSCH transmission is message 3 PUSCH for random access, or whether the PUSCH is configured grant PUSCH, or scheduled PUSCH. can be referenced as the frequency magnitude assigned to PUSCH. α b,f,c (j) represents the degree of compensation ratio for the path loss of the UL BWP b of the carrier f of the serving cell c, and can be set by the upper signal and may have different values ​​depending on j. PL b,f,c (q d ) is an estimated value of the downlink path loss of the UL BWP b of the carrier f of the serving cell c, and the value measured through the reference signal in the active downlink bandwidth interval can be used. The reference signal may be an SS / PBCH block or CSI-RS. The downlink path loss can be calculated as described above in [Equation 7]. In one embodiment, PL b,f,c (q d) is a downlink warning attenuation value, which may be a path attenuation calculated by the terminal as in [Equation 7]. Depending on whether the upper signal is set, the terminal may calculate the path attenuation based on a reference signal resource associated with the SS / PBCH block or CSI-RS. The reference signal resource may select one of several sets of reference signal resources by the upper signal or L1 signal, and the terminal may calculate the path attenuation based on that reference signal resource. may be a value determined by the MCS (Modulation and Coding Scheme) value of the PUSCH at time i of transmission of the UL BWP b of the carrier f of the serving cell c. b,f,c (i,l) is a power control adaptive value that can dynamically adjust the power value by the TPC command.

[0545] The TPC command is divided into accumulated and absolute modes, and one of the two modes can be determined by the upper signal. In the accumulated mode, the currently determined power regulation adaptation value is accumulated with the value indicated by the TPC command, and can be increased or decreased according to the TPC command, and f b,f,c (i,l)=f b,f,c It has the relationship (i-i0,l)+∑δPUSCH,b,f,c. δPUSCH,b,f,c can be values ​​specified in the TPC command. The absolute mode is determined by the TPC command regardless of the currently determined power regulation adaptation value, and f b,f,c (i,l) can have the relationship δPUSCH, b, f, c. [Table 43] below shows the values ​​that can be indicated by the TPC command.

[0546]

[0547] [PUCCH power control]

[0548] The following [Equation 9] is the equation for determining PUCCH transmission power.

[0549] [Mathematical Formula 9]

[0550]

[0551] In [Equation 9] is a reference setting transmission power setting value, and various transmission types q u It has different values ​​depending on, and the values ​​can be changed by higher-level signals such as RRC or MAC CE. If the value is changed by MAC CE, the terminal sends a HARQ-ACK to the PDSCH that received the MAC CE; if the slot that sent the HARQ-ACK is k, then k + k offset It can be determined that the corresponding value is applied starting from the slot. k offset It has different values ​​depending on the subcarrier interval, and for example, it can have 3ms. can be the size of the frequency resource area to which PUCCH is allocated. PL b,f,c (q d ) is the estimated path attenuation value of the terminal, and as described in detail in [Equation 7], the terminal can calculate it based on a specific reference signal among various CSI-RS or SS / PBCH depending on whether the upper signal is set and the type thereof. For repeated transmission PUCCHs, the same q d can be applied. For repeated transmission PUCCHs, the same q u It can be applied.

[0552] [HARQ-ACK: Type 1 (semi-static) codebook related]

[0553] In a situation where the number of HARQ-ACK PUCCHs a terminal can transmit within a slot is limited to one, when the terminal receives a semi-static HARQ-ACK codebook upper setting, the terminal may report HARQ-ACK information regarding PDSCH reception or SPS PDSCH release in the HARQ-ACK codebook in the slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_0 or DCI format 1_1. The terminal may report the HARQ-ACK information bit value as NACK (negative-ACK) in the HARQ-ACK codebook in the slot not indicated by the PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0 or DCI format 1_1. If the terminal reports only one SPS PDSCH release or one HARQ-ACK information for one PDSCH reception in the MA,C cases for candidate PDSCH reception, and the report is scheduled by DCI format 1_0 containing information in which the counter DACI field in the Pcell indicates 1, the terminal can determine one HARQ-ACK codebook for the corresponding SPS PDSCH release or the corresponding PDSCH reception.

[0554] Other than that, the HARQ-ACK codebook determination method according to the method described below may be followed.

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

[0556] [pseudo-code 1 start]

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

[0558] - Step 2: Set R as the set of each row in the table containing slot information, start symbol information, and symbol count or length information where PDSCH is mapped. If the PDSCH-possible mapping symbol pointed to by each value in R is set to a UL symbol according to the DL and UL settings established above, delete the corresponding row from R.

[0559] - Step 3-1: If a terminal can receive one unicast PDSCH per slot and R is not an empty set, add 1 to set MA,c.

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

[0561] - Step 4: Increase k by 1 and start again from Step 2.

[0562] [End of pseudo-code 1] With the above-described pseudo-code 1 as an example in FIG. 19, all slot candidates capable of PDSCH-to-HARQ-ACK timing that can indicate slot #k (1908) can be considered in order to perform HARQ-ACK PUCCH transmission in slot #k (1908). In FIG. 19, it is assumed that HARQ-ACK transmission in slot #k (1908) is possible by PDSCH-to-HARQ-ACK timing combinations that are possible only for PDSCHs scheduled in slot #n (1902), slot #n+1 (1904), and slot #n+2 (1906). Then, the maximum number of PDSCHs that can be scheduled per slot can be derived based on time domain resource configuration information of PDSCHs that can be scheduled in slots 1902, 1904, and 1906, respectively, and information indicating whether the symbol within the slot is a downlink or an uplink. For example, assuming that a maximum of 2 PDSCHs are possible in slot 1902, 3 PDSCHs in slot 1904, and 2 PDSCHs in slot 1906, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in slot 1908 can be 7. This is called the cardinality of the HARQ-ACK codebook.

[0563] Step 3-2 within a specific slot is described through the following [Table 44] (Default PDSCH time domain resource allocation A for normal CP).

[0564]

[0565]

[0566] [Table 44] is the time resource allocation table in which the terminal operates by default before receiving time resource allocation via a separate RRC signal. For reference, in addition to separately indicating the row index value via RRC, the PDSCH time resource allocation value can be determined by the terminal common RRC signal, dmrs-TypeA-Position. In [Table 44], the ending and order columns are values ​​added separately for convenience of explanation and may not actually exist. The meaning of the ending column is the termination symbol of the scheduled PDSCH, and the order column may refer to the code position value located within a specific codebook in the quasi-static HARQ-ACK codebook. [Table 44] can be applied to time resource allocation in DCI format 1_0 of the PDCCH common seek area.

[0567] According to one embodiment, to determine the HARQ-ACK codebook by calculating the maximum number of non-overlapping PDSCHs within a specific slot, the terminal may perform the following steps.

[0568] - Step 1: Among all rows in the PDSCH time resource allocation table, you can identify the PDSCH allocation value that terminates first within a slot. In [Table 44], you can see that row index 14 terminates first. This can be indicated as 1 in the order column. Other row indices that overlap with row index 14 by at least one symbol are indicated as 1x in the order column.

[0569] - Step 2: Then, among the remaining row indices not displayed in the Order column, you can look for the PDSCH assignment value that terminates first. In [Table 44], this could be the row with row index 7 and dmrs-TypeA-Position value 3. Other row indices that overlap with that row index by at least one symbol may be indicated as 2x in the order column.

[0570] - Step 3: Repeat Step 2, incrementing the order value. For example, in [Table 44], you can look for the earliest ending PDSCH assignment value among the row indices not displayed in the order column. In [Table 44], this could be the row with row index 6 and dmrs-TypeA-Position value 3. Other row indices that overlap with that row index by at least one symbol can be indicated as 3x in the order column.

[0571] - Step 4: If an order is indicated for all row indices, the process can terminate. The size of that order may represent the maximum number of PDSCHs that can be scheduled within that slot without time overlap. Scheduling without time overlap means that different PDSCHs are scheduled via TDM.

[0572] In the 'order' column of [Table 44], the maximum value of 'order' represents the HARQ-ACK codebook size of the corresponding slot, and the 'order' value may represent the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the scheduled PDSCH is located. For example, row index 16 in [Table 44] may indicate that it exists at the 2nd code position in a semi-static HARQ-ACK codebook of size 3. The terminal transmitting the HARQ-ACK feedback [describes] the set of PDSCH reception candidate occasions M in serving cell c. A,c If so, M into [pseudo-code 1] or [pseudo-code 2] steps A,c can be obtained. M A,c It can be used to determine the number of HARQ-ACK bits that the terminal must transmit. For example, M A,c A HARQ-ACK codebook can be constructed using the cardinality of the set.

[0573] According to one embodiment, the factors to be considered for determining a quasi-static HARQ-ACK codebook (or type 1 HARQ-ACK codebook) may be as follows.

[0574] a) on a set of slot timing values ​​K1associated with the active UL BWP

[0575] (a) If the UE is configured to monitor PDCCH for DCI format 1_0 and is not configured to monitor PDCCH for DCI format 1_1 on serving cell c, K1is provided by the slot timing values ​​{1, 2, 3, 4, 5, 6, 7, 8} for DCI format 1_0

[0576] (b) If the UE is configured to monitor PDCCH for DCI format 1_1 for serving cell c, K1is provided bydl-DataToUL-ACKfor DCI format 1_1

[0577] b) on a set of row indexesRof a table that is provided either by a first set of row indexes of a table that is provided byPDSCH-TimeDomainResourceAllocationListinPDSCH-ConfigCommonor by Default PDSCH time domain resource allocation A [6, TS 38.214], or by the union of the first set of row indexes and a second set of row indexes, if provided byPDSCH-TimeDomainResourceAllocationListinPDSCH-Config, associated with the active DL BWP and defining respective sets of slot offsets K0, start and length indicatorsSLIV, and PDSCH mapping types for PDSCH reception as described in [6, TS 38.214]

[0578] c) on the ratio between the downlink SCS configuration μ DL and the uplink SCS configuration μ ULprovided bysubcarrierSpacinginBWP-DownlinkandBWP-Uplinkfor the active DL BWP and the active UL BWP, respectively

[0579] d) if provided, onTDD-UL-DL-ConfigurationCommonandTDD-UL-DL-ConfigDedicatedas described in Subclause 11.1.

[0580] According to one embodiment, the pseudo-code for determining the HARQ-ACK codebook may be as shown in [Table 45].

[0581]

[0582]

[0583]

[0584] According to one embodiment, the location of the HARQ-ACK codebook containing HARQ-ACK information for a DCI indicating a DL SPS release in pseudo-code 2 may be based on the location where the DL SPS PDSCH is received. For example, if the starting symbol of a DL SPS (semi-persistent scheduling) PDSCH being transmitted starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, the HARQ-ACK information containing a DL SPS release indicating the release of the SPS may be assumed to be mapped to a PDSCH that starts from the 4th OFDM symbol in the slot where the DL SPS release was transmitted and has a length of 5 symbols, and the corresponding HARQ-ACK information may be determined through the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information indicating the DL SPS release. For example, if the starting symbol of the DL SPS PDSCH being transmitted starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, the HARQ-ACK information containing the DL SPS release that instructs the release of the SPS can be assumed to be mapped to the PDSCH that starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, as indicated by the TDRA (Time domain resource allocation) of the DCI, which is the DL SPS release, and the corresponding HARQ-ACK information can be determined through the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information that instructs the DL SPS release.

[0585] [HARQ-ACK: Type 2 (dynamic) codebook related]

[0586] According to one embodiment, a terminal can transmit HARQ-ACK information transmitted within a PUCCH in slot n based on a PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release, and K0, which is transmission slot location information of the PDSCH scheduled in DCI format 1_0 or 1_1. For example, for the transmission of HARQ-ACK information described above, the terminal can determine the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by the PDSCH-to-HARQ_feedback timing and K0 based on a DAI (downlink assignment index) included in the DCI indicating PDSCH or SPS PDSCH release.

[0587] According to one embodiment, the DAI may be composed of a Counter DAI and a Total DAI. The Counter DAI may be information indicating the location within the HARQ-ACK codebook of HARQ-ACK information corresponding to a PDSCH scheduled in DCI format 1_0 or DCI format 1_1. For example, the value of the counter DAI in DCI format 1_0 or 1_1 may indicate the cumulative value of a PDSCH reception or SPS PDSCH release scheduled by DCI format 1_0 or DCI format 1_1 in a specific cell c. The above-described cumulative value may be set based on the PDCCH monitoring occasion and serving cell where the scheduled DCI exists.

[0588] According to one embodiment, Total DAI may be a value indicating the size of the HARQ-ACK codebook. For example, the value of Total DAI may represent the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time when the DCI was scheduled. Additionally, Total DAI may be a parameter used in a Carrier Aggregation (CA) situation where the HARQ-ACK information in serving cell c includes HARQ-ACK information for PDSCHs scheduled in other cells, including serving cell c. In a system operating as a single cell, the Total DAI parameter does not exist.

[0589] According to one embodiment, an example of operation for DAI is illustrated in FIG. 20. In FIG. 20, when a terminal receives two carriers and transmits a HARQ-ACK codebook selected based on DAI in the n-th slot of carrier 0 (2002) to PUCCH (2020), the change in the values ​​of Counter DAI (C-DAI) and Total DAI (T-DAI) indicated by the DCI found for each PDCCH monitoring occasion set for each carrier can be described. First, the DCI found at m=0 (2006) may indicate a value of 1 for C-DAI and T-DAI, respectively (2012). The DCI found at m=1 (2008) may indicate a value of 2 for C-DAI and T-DAI, respectively (2014). The DCI found in carrier 0 (c=0, 2002) of m=2 (2010) may indicate a C-DAI value of 3 (2016). The DCI found in carrier 1 (c=1, 2004) of m=2 (2010) may indicate a C-DAI value of 4 (2018). In this case, if carriers 0 and 1 are scheduled at the same monitoring occasion, the T-DAI may both be indicated as 4.

[0590] In FIGS. 19 and 20, the HARQ-ACK codebook determination may operate in a situation where only one PUCCH containing HARQ-ACK information is transmitted within a single slot, and this may be referred to as Mode 1. As an example of a method in which a single PUCCH transmission resource is determined within a single slot, when PDSCHs scheduled in different DCIs are multiplexed into a single HARQ-ACK codebook and transmitted within the same slot, the PUCCH resource selected for HARQ-ACK transmission may be determined as the PUCCH resource indicated by the PUCCH resource field indicated by the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated by the DCI scheduled prior to the above DCI may be ignored.

[0591] The description below defines methods and devices for determining the HARQ-ACK codebook in situations where two or more PUCCHs containing HARQ-ACK information can be transmitted within a single slot, and this can be referred to as Mode 2. A terminal may be able to operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH within a slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs within a slot). Alternatively, for a terminal that supports both Mode 1 and Mode 2, the base station may be configured to operate in only one mode by upper-level signaling, or Mode 1 and Mode 2 may be implicitly determined by DCI format, RNTI, DCI specific field values, scrambling, etc. For example, PDSCHs scheduled in DCI format A and associated HARQ-ACK information may be based on Mode 1, and PDSCHs scheduled in DCI format B and associated HARQ-ACK information may be based on Mode 2. Whether the aforementioned HARQ-ACK codebook is semi-static or dynamic can be determined by the RRC signal.

[0592] [Explanation of Satellite Communication Structure]

[0593] The characteristics of satellite communication are described below. Satellites for communication can be classified according to their orbits into Low Earth Orbit (LEO), Middle Earth Orbit (MEO), and / or Geostationary Earth Orbit (GEO). For example, GEO refers to a satellite at an altitude of approximately 36,000 km, MEO refers to a satellite at an altitude of 5,000 to 15,000 km, and LEO refers to a satellite at an altitude of 500 to 1,000 km. Of course, the types and altitudes of satellites are not limited to the examples described above.

[0594] According to one embodiment of the present disclosure, the Earth's orbital period varies depending on the altitude, and for GEO, the Earth's orbital period may be approximately 24 hours, for MEO, approximately 6 hours, and for LEO, approximately 90 to 120 minutes. Low Earth orbit (~2,000 km) satellites may have an advantage over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time it takes for a signal transmitted from a transmitter to reach a receiver) and loss due to their relatively low altitude.

[0595] FIG. 21 is a diagram illustrating the orbital period of a communication satellite according to the altitude or height of the satellite according to one embodiment of the present disclosure.

[0596] According to one embodiment, when a terminal communicates with a satellite located at an altitude of 1200 km, the distance between the terminal and the satellite may vary depending on the elevation angle between the satellite and the terminal. For example, when the elevation angle between the satellite and the terminal is 90 degrees, the distance between the terminal and the satellite is 1200 km, but when the elevation angle between the satellite and the terminal is 10 degrees, the distance between the terminal and the satellite may be approximately 3135 km. Therefore, in satellite communication, even if the terminal is fixed, the distance between the satellite and the terminal may vary due to the satellite orbiting periodically, such as a low-orbit satellite. Furthermore, because the distance between the terminal and the satellite in satellite communication is much greater than the distance between a terminal and a base station in a terrestrial network, it may be necessary to transmit control information and / or data information in the form of performing data transmission with a low code rate or repetitive transmission.

[0597] [OCC-based PUCCH transmission]

[0598] Below, a PUCCH transmission method utilizing the terminal's OCC (Orthogonal Cover Code) is described.

[0599] According to one embodiment, LTE PUCCH format 5 is one of the signals transmitted in the PUCCH, which is an uplink control channel, and can be used mainly to transmit ACK (positive acknowledgment) / NACK (negative acknowledgment) feedback for downlink data transmission.

[0600] According to one embodiment, PUCCH format 5 can combine Frequency Division Multiple Access (FDMA) and Time Division Multiple Access (TDMA) methods, and signals transmitted from different terminals can be distinguished (i.e., OFDMA method). In PUCCH format 5, signals can be transmitted using cyclic shift technology. To implement this function, OCC technology utilizing orthogonality can be applied in LTE PUCCH format 5. OCC is used to distinguish signals transmitted from different terminals, and each terminal can select an OCC sequence based on a predefined OCC index and transmit ACK / NACK bits by covering them with the corresponding sequence. Therefore, PUCCH format 5 with applied OCC can improve the overall performance of the LTE system by enabling efficient control channel transmission in a multiple access environment.

[0601] FIG. 22 is a block diagram illustrating a method for generating LTE PUCCH format 5 according to one embodiment.

[0602] Referring to FIG. 22, after generating HARQ ACK / NACK bits, the terminal can generate coded bits through channel coding and scrambling processes.

[0603] The terminal can distribute 72 modulated symbols among a total of 12 OFDM symbols through QPSK modulation and de-multiplexing processes. For example, the terminal can map the 6 modulated symbols assigned to each symbol to 12 frequency tones through OCC spreading. For example, the spreading method can operate by mapping QPSK (Quadrature Phase Shift Keying) modulated symbols to a larger number of virtual frequency tones. Through the spreading method, it may be possible to prevent multiple users' signals from interfering with each other.

[0604] For example, in other existing LTE PUCCH formats, 12 QPSK modulated symbols can be mapped to a single RB (Resource Block) SC-FDM symbol, but in LTE PUCCH 5 as shown in Fig. 22, only 6 QPSK modulated symbols can be mapped to a single RB and SC-FDM (Single-carrier frequency division multiple access) symbol. For example, the CDM (Code Division Multiplexing) index used in the spreading method is a value assigned to each user and can have a value of 0 or 1. The CDM index value can determine how each user's signal will be spread. For example, a user with a CDM index of 0 can duplicate their signal twice and map it to 12 virtual frequency tones. As another example, a user with a CDM index of 1 can repeat their signal twice, but multiply half of them by -1 and map it to 12 virtual frequency tones. This allows the signals of each user to be distributed over a wider bandwidth, making it possible to avoid mutual interference even in multi-user environments. How interference can be avoided despite using the same time and frequency resources is further explained through Fig. 23.

[0605] FIG. 23 is a diagram illustrating a method of mapping different terminals to a virtual frequency tone by applying different OCC values ​​according to one embodiment.

[0606] Referring to FIG. 23, the first terminal can repeatedly map the information of (A1, A2, A3, A4, A5, A6) to 1RB. When the second terminal repeatedly maps the information of (B1, B2, B3, B4, B5, B6) to 1RB, half of the values ​​are mapped by multiplying by 1, and the other half are mapped by multiplying by -1. After performing the Discrete Fourier Transform (DFT) and the Inverse Fast Fourier Transform (IFFT), the first terminal and the second terminal can transmit the information to the base station. After receiving the information from the first terminal and / or the second terminal, the base station can perform a de-spreading process. For example, the base station can decode A1 and B1, respectively, using the values ​​“A1+B1” and “A1-B1”. In this way, the base station can decode the remaining information (e.g., information of the first terminal (A2, A3, A4, A5, A6) and / or information of the second terminal (B2, B3, B4, B5, B6)).

[0607] In FIGS. 22 and 23, the OCC spreading method is described from the perspective of the frequency axis, but the OCC spreading method may also be applied from the perspective of the time axis. Additionally, in FIGS. 22 and 23, a method of applying the OCC sequences (1,1) and (1,-1) to two different terminals based on an OCC length of 2 is described, but sequences with an OCC length greater than 2 may be considered. In this case, two or more different terminals may transmit PUCCH using the same time and / or frequency resources.

[0608] [OCC-based PUSCH transmission]

[0609] Below, a PUSCH transmission method utilizing the OCC method is explained.

[0610] According to one embodiment, basically, when there is data to be sent to a base station, the terminal can perform processing for PUSCH transmission through a series of procedures illustrated in FIG. 24. However, the procedures illustrated in FIG. 24 are merely examples, and some of the procedures illustrated in FIG. 24 may be omitted or the order of each procedure may be changed so that the terminal can apply them, and the terminal is not limited to the illustrated procedures.

[0611] Referring to FIG. 24, the procedure illustrated in FIG. 24 is as follows.

[0612] - Data Block CRC Attachment (Transport block CRC Attachment): An error checking code is attached to the data.

[0613] - LDPC base graph selection: Select an appropriate LDPC graph for channel coding.

[0614] - Code Block Segmentation and CRC Attachment: Data is divided into smaller blocks, and a CRC is attached to each block.

[0615] - Channel Coding: Blocks are encoded to prevent transmission errors.

[0616] - Rate Matching: Encoded data is mapped to available transmission resources.

[0617] - Code Block Concatenation: Encoded blocks are reconnected.

[0618] - Data and Control Multiplexing: If there is a control resource that overlaps with a data resource, the corresponding control information is multiplexed with the data information.

[0619] - Scrambling: Scrambling data to prevent predictable patterns that could degrade signal quality.

[0620] - Modulation: Scrambled data is modulated onto the carrier wave.

[0621] - Layer Mapping: Data is mapped across transmission layers.

[0622] - OCC spreading: Apply OCC to the data mapped to the layer. Fig. 23 or other methods may be applied.

[0623] - Transform Precoding: Reconstructs the frequency domain signal into the time domain signal using the Discrete Fourier Transform (DFT). This step is particularly used in scenarios with a single transport layer and can be utilized to improve signal orthogonality and reduce interference.

[0624] - Precoding: A spatial processing step that optimizes performance by adjusting the converted signal before transmission. This involves applying a matrix to the signal to enhance signal directionality and improve receiver reception, while considering various antenna configurations and channel conditions.

[0625] - Mapping to VRB (Virtual Resource Block): Data is mapped to a virtual resource block in the frequency domain.

[0626] - Mapping from RB to PRB (Physical Resource Block): Then, the virtual resource block is mapped to the physical resource block for actual transfer.

[0627] Among the above procedures, the OCC diffusion method can be applied in various ways.

[0628] According to one embodiment, when the terminal repeatedly transmits PUSCH for each slot, it may apply an OCC sequence for each slot.

[0629] FIG. 25 is a diagram illustrating a method of applying an OCC method when a terminal according to one embodiment repeatedly transmits PUSCH per slot.

[0630] According to one embodiment, in a situation where the OCC length is 2, two different terminals can each repeatedly transmit PUSCH through the same time and frequency resources. There may be a situation where the first terminal transmits PUSCH A and the second terminal transmits PUSCH B.

[0631] According to one embodiment, the first terminal can generate the same data (a1) (2500) and perform repeated transmission (2502) of it in slot n and slot n+1.

[0632] According to one embodiment, the second terminal can map data (b1) to slot n as b1 and to slot n+1 as -b1 multiplied by -1 (2501). The second terminal can transmit b1 to the PUSCH B of slot n and transmit -b1 to the PUSCH B of slot n+1.

[0633] In FIG. 25, PUSCH A and PUSCH B transmitted in slot n and slot n+1 are shown as being transmitted by the first terminal and the second terminal through the same time and frequency resources, but only some time and frequency resources overlap and other different time and frequency resources may be used.

[0634] In addition, 2500 and 2501 in FIG. 25 are conceptual diagrams used to illustrate that the first terminal and the second terminal are transmitted via PUSCH, rather than being generated in slot n and slot n+1, respectively, and in reality, they may be generated before slot n, which transmits PUSCH from the beginning.

[0635] In FIG. 25, the base station can receive a1+b1 information through PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, and receive a1-b1 information through PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n+1. Accordingly, the base station may be able to receive a1 and b1, respectively, through the OCC inverse spreading method of the received a1+b1 and a1-b1. Here, a1 and b1 may be referred to as a set of symbols for which channel coding and modulation have been performed on a series of data, or a1 and b1 may be referred to as a set of data before DFT is performed.

[0636] Referring to FIG. 25, to apply the OCC method, the base station may instruct terminals in advance via an upper signal or L1 (layer 1) signal to apply an OCC sequence value for each slot during repeated PUSCH transmissions. For example, in the case of a second terminal, if a DCI field called the OCC index exists in the L1 signal and the value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may apply '1' in slot n and '-1' in slot n+1. For example, the DCI field called the OCC index exists as 1 bit; if it is 0, the OCC sequence is (1,1), and if it is 1, the OCC sequence is indicated as (1,-1) or (-1,1). The type of OCC sequence and / or the size of the DCI field may be determined by the upper signal settings. The length of the OCC sequence may be a value greater than the value described as an example (e.g., length 2). That is, the numerical limitation of the length of the OCC sequence is merely an example and the present disclosure is not limited thereto.

[0637] Referring to FIG. 25, it is described that the first terminal has applied the OCC sequence as (1,1), but the first terminal may perform conventional PUSCH repeated transmission without applying the OCC sequence. Accordingly, in FIG. 25, at least one of the cases in which the first terminal sends a terminal capability to apply the OCC spreading method and / or does not send it may be possible. For example, the first terminal may or may not send a terminal capability to apply the OCC spreading method.

[0638] On the other hand, the second terminal may be able to apply the OCC spreading method only when it has sent a terminal capability to apply the OCC spreading method. For example, the second terminal may transmit a terminal capability to apply the OCC spreading method.

[0639] FIG. 25 illustrates an example where the first terminal and the second terminal apply two repeated transmissions, but it is possible to apply a value of 4 or 8 or more for the number of slots that are repeatedly transmitted.

[0640] According to one embodiment, assuming that the OCC sequence (1,-1) applied by the second terminal is transmitted 4 times, slot n is b1, slot n+1 is -b1, slot n+2 is b1, and slot n+3 is -b1, or slot n is b1, slot n+1 is b1, slot n+2 is -b1, and slot n+3 is -b1 can be applied.

[0641] According to one embodiment, an OCC sequence of 1 (or -1) may always be applied to even slots, and an OCC sequence of -1 (or 1) may always be applied to odd slots. According to one embodiment, an OCC sequence may be applied by a modular operation. Since the OCC sequence (1, -1) has a length of 2, the OCC sequence value applied to PUSCH in the nth slot may be 1 (or -1) if the modulo (n / 2) value is 1, and -1 (or 1) if the modulo (n / 2) value is 0.

[0642] Although FIG. 25 describes the first terminal and the second terminal starting the same number of repetitive transmissions from the same slot, it may also be applied to cases where they start from different slots or perform different numbers of repetitive transmissions. That is, the present disclosure is not limited to the example illustrated in FIG. 25.

[0643] According to one embodiment, when a terminal repeatedly transmits PUSCH within one slot, it may apply an OCC sequence for each PUSCH transmission unit that is repeatedly transmitted.

[0644] FIG. 26 is a diagram illustrating a method of applying an OCC method when a terminal repeatedly transmits PUSCH within one slot according to one embodiment. The operation illustrated in FIG. 26 may be substantially similar to the operation illustrated in FIG. 25.

[0645] Referring to FIG. 26, in a situation where the OCC length according to one embodiment is 2, two different terminals can each repeatedly transmit PUSCH using the same time and frequency resources. For example, there may be a situation where the first terminal transmits PUSCH A and the second terminal transmits PUSCH B.

[0646] According to one embodiment, the first terminal can generate the same data (a1) (2600) and perform repeated transmission (2602) in one slot n.

[0647] According to one embodiment, the second terminal can map data (b1) to the first PUSCH B of slot n and map -b1 (2601), which is the result of multiplying by -1, to the second PUSCH B. The second terminal can transmit b1 to the first PUSCH B of slot n and transmit -b1 to the second PUSCH B of slot n.

[0648] In FIG. 26, PUSCH A and PUSCH B transmitted in slot n are depicted as being transmitted by the first terminal and the second terminal through the same time and frequency resources, but this is merely an example. For instance, only some time and frequency resources may overlap, and other different time and / or frequency resources may be used.

[0649] Additionally, in FIG. 26, 2600 and 2601 are conceptual diagrams used to illustrate that the data is transmitted via PUSCH by the first terminal and the second terminal, rather than being generated in slot n. Each data may be generated prior to slot n, where PUSCH is transmitted from the beginning. In FIG. 26, the base station can receive a1+b1 information through the respective first PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, and receive a1-b1 information through the respective second PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n. Accordingly, the base station can receive a1 and b1, respectively, from the received a1+b1 and a1-b1 through the OCC inverse spreading method. Here, a1 and b1 can be referenced as a set of symbols for which channel coding and modulation have been performed on a series of data. As another example, a1 and b1 can also be referenced as a set of data prior to DFT performance on a series of data.

[0650] According to one embodiment, in order to apply an OCC method such as that shown in FIG. 26, a base station may instruct terminals in advance via an upper signal or an L1 signal to apply an OCC sequence value for each PUSCH transmission interval when PUSCH is repeatedly transmitted. For example, in the case of a second terminal, if a DCI field called an OCC index exists in the L1 signal and the value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may apply '1' in the first PUSCH and '-1' in the second PUSCH. For example, the DCI field called an OCC index exists as 1 bit, and if it is 0, the OCC sequence is (1,1), and if it is 1, the OCC sequence can be indicated as (1,-1) or (-1,1).

[0651] The OCC sequence type and / or DCI field size can be determined by the upper signal setting. The length of the OCC sequence may be a value greater than the length 2 described in the example above.

[0652] In FIG. 26, the first terminal is described as having applied the OCC sequence as (1,1), but the first terminal can perform conventional PUSCH repeated transmission without applying the OCC sequence regardless of this. Therefore, in FIG. 26, the first terminal may send a terminal capability to apply the OCC spreading method or may not send a terminal capability to apply the OCC spreading method. On the other hand, the second terminal may be applied only when a terminal capability to apply the OCC spreading method is sent.

[0653] FIG. 26 describes an example in which the first terminal and the second terminal perform two repeated transmissions, but this is merely an example. The present disclosure may also apply in cases where the number of repeated PUSCHs is four or eight or more. The present disclosure may also apply in cases where the repeated PUSCH transmissions described above are performed across multiple slots rather than a single slot.

[0654] For example, the OCC sequence (1, -1) applied by the second terminal may apply b1 to the first PUSCH, -b1 to the second PUSCH, b1 to the third PUSCH, and -b1 to the fourth PUSCH when four repeated transmissions are assumed. As another example, the OCC sequence (1, -1) applied by the second terminal may apply b1 to the first PUSCH, b1 to the second PUSCH, -b1 to the third PUSCH, and -b1 to the fourth PUSCH. Alternatively, an OCC sequence of 1 (or -1) may always be applied to even-numbered PUSCH transmissions, and an OCC sequence of -1 (or 1) may always be applied to odd-numbered PUSCH transmissions. Alternatively, the OCC sequence may be applied by modular operation.

[0655] Since the OCC sequence (1,-1) has a length of 2, the OCC sequence value applied to the nth PUSCH can be 1 (or -1) if the mod (n / 2) value is 1. If the mod (n / 2) value is 0, the OCC sequence value applied to the nth PUSCH can be -1 (or 1).

[0656] Additionally, FIG. 26 describes the first terminal and the second terminal starting the same number of repetitive transmissions from the same slot, but this is merely an example. For example, the present disclosure may also apply to cases where they start from different slots or perform different numbers of repetitive transmissions.

[0657] According to one embodiment, an OCC sequence can be applied between information belonging to different time resources within a single PUSCH.

[0658] FIG. 27 illustrates a method for applying an OCC method in terms of time resources when a terminal according to one embodiment transmits PUSCH.

[0659] According to one embodiment, when the first terminal and the second terminal apply an OCC method with a length of 2 in terms of time resources, when calculating the transport block size (TBS), the value obtained by dividing the PUSCH resource size allocated to the terminal by 2 can be determined as the actual TBS value. Alternatively, the TBS calculation may be based on the size of the actual PUSCH transmission resource area separately. For example, the size of the PUSCH transmission resource area may be determined by the frequency resource size (e.g., number of RBs) and the time resource size (e.g., number of symbols).

[0660] Subsequently, the terminals can perform data transmission preparation according to the procedure illustrated in FIG. 24. Then, in the OCC spreading stage, as illustrated in FIG. 27, the first terminal can sequentially arrange two identical data a1s in terms of time resources and apply the OCC sequence (1,1) to each of the first a1 and the second a1 (2700). Then, the first terminal can transmit the data in the PUSCH A resource area allocated by the base station (2702). The second terminal can also sequentially arrange two identical data b1s in terms of time resources and apply the OCC sequence (1,-1) to each of the first b1 and the second b1 (2701). Then, the second terminal can transmit the data in the PUSCH B resource area allocated by the base station (2702).

[0661] In FIG. 27, the data to which OCC is applied is described as being divided into two parts in terms of time resources, but this is merely an example. For example, the data to which OCC is applied can be divided into three, four, or more parts. For example, when the same data is mapped into four parts, the first terminal can generate (a1, a1, a1, a1), and the second terminal can generate (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1).

[0662] In addition, the OCC diffusion and dediffusion method is explained in Fig. 23 from the perspective of the frequency axis, but this is only an example. The OCC diffusion and dediffusion method can also be applied from the perspective of the time axis rather than the frequency axis.

[0663] In FIG. 27, PUSCH A and PUSCH B transmitted in slot n are illustrated as being transmitted by the first terminal and the second terminal through the same time and frequency resources, but this is merely an example. For example, the present disclosure may also apply even when only some time and frequency resources overlap and other different time and frequency resources are used.

[0664] Additionally, 2700 and 2701 in FIG. 27 are conceptual diagrams used to illustrate that the first terminal and the second terminal transmit data via PUSCH, rather than generating the respective data in slot n. In reality, the respective data may be generated before slot n, which transmits PUSCH from the beginning.

[0665] In FIG. 27, since the base station receives information a1+b1 and a1-b1 through PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, the base station can receive a1 and b1 respectively through the OCC inverse spreading method of the received a1+b1 and a1-b1. Here, a1 and b1 can be referred to as a set of symbols for which channel coding and modulation have been performed on a series of data. As another example, a1 and b1 can also be referred to as a set of data before performing DFT on a series of data.

[0666] To apply an OCC method as shown in FIG. 27, the base station may instruct terminals in advance via an upper signal or L1 signal to apply an OCC sequence value when PUSCH is repeatedly transmitted. For example, in the case of a second terminal, if a DCI field called OCC index exists in the L1 signal and the value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may apply '1' to the first part of PUSCH and '-1' to the second part. For example, the DCI field called OCC index exists as 1 bit, and if it is 0, the OCC sequence is (1,1), and if it is 1, the OCC sequence can be indicated as (1,-1) or (-1,1).

[0667] The OCC sequence type and / or DCI field size can be determined by the upper signal setting. For example, the length of the OCC sequence may be greater than the length 2 described in the example above.

[0668] In FIG. 27, at least one of the cases in which the first terminal and the second terminal send a terminal capability to apply the OCC spreading method or do not send a terminal capability to apply the OCC spreading method may be possible. Although FIG. 27 describes the case where a single PUSCH is transmitted as an example, it is not limited thereto, and the PUSCH repeated transmission described above may be performed over multiple slots. Furthermore, FIG. 27 illustrates the first terminal and the second terminal starting PUSCH transmission from the same slot, but this is merely an example. The present disclosure may also apply to cases where they start from different slots or perform a different number of repeated transmissions.

[0669] According to one embodiment, an OCC sequence can be applied between information belonging to different frequency resources within a single PUSCH.

[0670] FIG. 28 is a diagram showing a method of applying an OCC method in terms of frequency resources when a terminal according to one embodiment transmits PUSCH.

[0671] According to one embodiment, when the first terminal and the second terminal apply an OCC scheme with a length of 2 in terms of frequency resources, when calculating TBS, the value obtained by dividing the PUSCH resource size allocated to the terminal by 2 can be determined as the actual TBS value. Alternatively, the TBS calculation may be based on the size of the actual PUSCH transmission resource area separately. The size of the PUSCH transmission resource area may be determined by the frequency resource size (e.g., number of RBs) and the time resource size (e.g., number of symbols).

[0672] Subsequently, the terminals can prepare for data transmission by the procedure illustrated in FIG. 24. In the OCC spreading phase, as illustrated in FIG. 28, the first terminal can sequentially arrange two identical data a1s in terms of frequency resources and apply the OCC sequence (1,1) to the first a1 and the second a1 for each (2800). Then, the first terminal can transmit the data in the PUSCH A resource area allocated by the base station (2802).

[0673] According to one embodiment, the second terminal can sequentially arrange two identical data b1s in terms of time resources and apply an OCC sequence (1,-1) to each of the first b1 and the second b1 (2801). The second terminal can then transmit the data in the PUSCH B resource area allocated by the base station (2702).

[0674] In FIG. 28, the data to which OCC is applied is divided into two parts in terms of frequency resources, but this is merely an example. For example, the data to which OCC is applied may be divided into three, four, or more parts. For example, when the same data is mapped into four parts, the first terminal may generate (a1, a1, a1, a1), and the second terminal may generate (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1). Additionally, the method of OCC spreading and despreading may be substantially the same or partially similar to that shown in FIG. 23.

[0675] In FIG. 28, PUSCH A and PUSCH B transmitted in slot n are depicted as being transmitted by the first terminal and the second terminal using the same time and frequency resources, but this is merely an example. For instance, only some time and frequency resources may overlap, and other different time and frequency resources may be used.

[0676] Additionally, 2800 and 2801 in FIG. 28 are conceptual diagrams merely to illustrate that the first terminal and the second terminal are transmitted via PUSCH, rather than that the respective data is generated in slot n. For example, the respective data may actually be generated before slot n, which transmits PUSCH from the beginning.

[0677] In FIG. 28, since the base station receives information a1+b1 and a1-b1 through PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, the base station can receive a1 and b1 respectively through the received a1+b1 and a1-b1 inverse spreading method. Here, a1 and b1 can be referred to as a set of symbols for which channel coding and modulation have been performed on a series of data. Alternatively, a1 and b1 can be referred to as a set of data before DFT is performed on a series of data.

[0678] To apply an OCC method as shown in FIG. 28, the base station may instruct terminals in advance via an upper signal or L1 signal to apply an OCC sequence value when PUSCH is repeatedly transmitted. For example, in the case of a second terminal, if there is a DCI field called an OCC index in the L1 signal and the value indicates a bit value corresponding to the OCC sequence (1, -1), the second terminal may apply '1' to the first part of PUSCH and '-1' to the second part.

[0679] For example, a DCI field called the OCC index exists as 1 bit, and if it is 0, the OCC sequence is (1,1), and if it is 1, the OCC sequence can indicate (1,-1) or (-1,1). The type of OCC sequence and / or the size of the DCI field can be determined by the upper signal setting. The length of the OCC sequence may use a value greater than the length described in the example above (e.g., 2).

[0680] In FIG. 28, the first terminal and the second terminal may or may not send the terminal capability to apply the OCC spreading method. Although FIG. 28 describes the case where a single PUSCH is transmitted as an example, it is not limited thereto, and it is also possible for the PUSCH to be transmitted repeatedly across multiple slots. Furthermore, although FIG. 28 illustrates the first terminal and the second terminal starting the PUSCH transmission from the same slot, it is also possible to apply it when they start from different slots or perform a different number of repeated transmissions.

[0681] [FDD Half-duplex Terminal]

[0682] In the following description, half-duplex terminal operation in FDD is explained. Basically, in FDD, a normal terminal can simultaneously receive downlink channels and transmit uplink channels. However, a half-duplex terminal can only receive downlink channels or only transmit uplink channels at a specific time.

[0683] For example, a half-duplex terminal cannot perform simultaneous transmission and reception in a serving cell using FDD (or Paired Spectrum). A half-duplex terminal may detect a DCI format scheduling reception in a symbol within a set and may not expect to detect another DCI format scheduling transmission in a symbol within that set. If a half-duplex terminal is configured by an upper layer to receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in a symbol within a set, the half-duplex terminal may receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS if it does not detect a DCI format instructing the half-duplex terminal to transmit PUSCH, PUCCH, PRACH (physical random access channel), or SRS (sounding reference signal) in at least one symbol within that set. Otherwise, the half-duplex terminal may not receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in a symbol within that set.

[0684] If a half-duplex terminal is configured to transmit SRS, PUCCH, or PUSCH from a symbol set configured by the upper layer, and the UE detects (or identifies) a DCI format instructing the half-duplex terminal to receive CSI-RS or PDSCH from a subset of the configured symbols,

[0685] ● The half-duplex terminal is T from the last symbol for the PDCCH reception where the half-duplex terminal detects the DCI format, the first symbol of the configured symbol. proc,2If it occurs within, one may not expect the transmission of PUCCH or PUSCH to be canceled at the set symbol. Otherwise, the half-duplex terminal cancels the actual repetition of PUCCH, PUSCH, or PUSCH. For example, T proc,2 It can be processing time or delay time.

[0686] ● A half-duplex terminal may not expect to cancel the transmission of SRS on some set of symbols occurring within T_(proc,2) from the last symbol of the PDCCH reception where the half-duplex terminal detects the DCI format. The half-duplex terminal may cancel the transmission of SRS on the remaining symbols of some set of symbols (e.g., symbols not located within T_(proc,2)). T proc,2 Assuming d_2,1=1, μ is the PUSCH preparation time for UE processing capability 1 corresponding to the smallest SCS setting among the SCS settings of PDCCH carrying DCI format and SRS, PUCCH, and PUSCH.

[0687] Figure 29 illustrates the processes described above.

[0688] FIGS. 29 and FIGS. 30 are T according to one embodiment of the present disclosure proc,2 This is a diagram explaining a method for determining whether to transmit an uplink of a terminal according to

[0689] For example, PDCCH (2900) may be referred to as a PDCCH containing a DCI format that schedules PDSCH or CSI-RS, and a resource (or signal) (2902) may be referred to as a PDSCH or CSI-RS which is a resource periodically set by an upper signal or an L1 signal or a combination thereof. A resource (or signal) (2904) may be referred to as a PUCCH or PUSCH or SRS.

[0690] As shown in FIG. 29, when at least one symbol overlaps between PDSCH (or CSI-RS) and PUCCH (or PUSCH) at a specific time, the terminal determines (or identifies) the difference (2910) between the last symbol of PDCCH containing the DCI format for scheduling PDSCH (or CSI-RS) and the first symbol of said PUCCH (or PUSCH). The difference (2910) is T proc,2 If it is smaller than, the terminal can transmit PUCCH (or PUSCH). That is, the terminal may not receive PDSCH or CSI-RS. If, the difference (2910) is T proc,2 If it is larger, the terminal may not transmit the above PUCCH (or PUSCH). That is, the terminal may receive PDSCH or CSI-RS.

[0691] Or, as in FIG. 30, if at least one symbol of the PDSCH (or CSI-RS) (3002) and SRS (3004) overlaps at a specific time, the terminal, after the last symbol of the PDCCH (3000) containing the DCI format for scheduling the PDSCH (or CSI-RS), T proc,2 Transmission of SRS symbols included during the interval (3010) can be performed. proc,2 Subsequently, regarding SRS symbols, the terminal can transmit SRS in the section (3015) that does not overlap with the downlink symbol. proc,2 For subsequent SRS symbols, the terminal does not transmit SRS in the sections that overlap with downlink symbols.

[0692] According to one embodiment, a half-duplex terminal may not expect to receive both a dedicated upper-layer parameter for setting up transmission in a symbol set (e.g., RRC signaling) and a dedicated upper-layer parameter for setting up reception in a symbol set (e.g., RRC signaling). A half-duplex terminal may not expect to receive both a Type-0 / 0A / 0B / 1 / 2-PDCCH CSS (common search space) set configuration for PDCCH reception in a symbol set and a dedicated upper-layer parameter. A half-duplex terminal may not expect to receive a Type-2-PDCCH CSS set configuration for PDCCH reception in a symbol set and a dedicated upper-layer parameter. A UE (or terminal, half-duplex terminal) may expect to receive a Type-2-PDCCH CSS set configuration for PDCCH reception such that there is at least one paging opportunity that does not overlap with a Configured grant PUSCH transmission during each SI (system information) update interval.

[0693] A half-duplex terminal may transmit PUSCH, PUCCH, or SRS depending on the settings of the upper layer (e.g., RRC parameters). If the presence of an SS / PBCH block within an active DL BWP is indicated by SIB1 or ssb-PositionsInBurst or NonCellDefiningSSB of ServingCellConfigCommon, the half-duplex terminal may not transmit the following.

[0694] ● If the last symbol of a PUSCH or PUCCH transmission is not at least N_"Tx-Rx" ·T_"c" earlier than the first symbol of the next earliest SS / PBCH block, then PUSCH or PUCCH

[0695] ● If the first symbol of a PUSCH or PUCCH transfer is not at least N_"Rx-Tx" ·T_"c" since the last symbol of the previous most recent SS / PBCH block, then PUSCH or PUCCH

[0696] ● SRS at a symbol that is not N_"Tx-Rx" ·T_"c" prior to the first symbol of the next earliest SS / PBCH block

[0697] ● SRS at least in symbols other than N_"Rx-Tx" ·T_"c" since the last symbol of the previous most recent SS / PBCH block

[0698] A half-duplex terminal may transmit PUSCH, PUCCH, or SRS according to the DCI format, PUSCH, PUCCH, or SRS that it has discovered. If the presence of an SS / PBCH block within an active DL BWP is indicated by SIB1 or ServingCellConfigCommon's ssb-PositionsInBurst or NonCellDefiningSSB, the half-duplex terminal does not transmit PUSCH, PUCCH, and / or PRACH if the transmission overlaps with a symbol in the symbol set, and the half-duplex terminal may not transmit SRS in the symbol set.

[0699] A half-duplex terminal may transmit a PRACH or MsgA PUSCH triggered by an upper layer (e.g., RRC signaling) in a symbol set. If the presence of an SS / PBCH block within a PDCCH, PDSCH, CSI-RS, DL PRS, or active DL BWP is indicated by NonCellDefiningSSB in a symbol containing any symbol in the ssb-PositionsInBurst of ServingCellConfigCommon or any symbol in the symbol set, the half-duplex terminal may choose, depending on the implementation, whether to transmit a PRACH or MsgA PUSCH or receive a PDSCH, CSI-RS, PT(Phase Tracking)-RS, PDCCH, or SS / PBCH block. If a half-duplex terminal receives a PDCCH, PDSCH, CSI-RS, or DL ​​PRS configured by an upper layer, if the presence of an SS / PBCH block within an active DL BWP is indicated by SIB1 or ServingCellConfigCommon's ssb-PositionsInBurst or NonCellDefiningSSB in the symbol set, and / or if the half-duplex terminal transmits a PRACH or MsgA PUSCH triggered by an upper layer starting before or after N_"Rx-Tx" ·T_"c" or N_"Tx-Rx" ·T_"c" in the last or first symbol of the symbol set, the half-duplex terminal may determine (or select) whether to transmit the PRACH or MsgA PUSCH or receive a PDSCH, CSI-RS, DL PRS, PDCCH, and / or SS / PBCH block.

[0700] The following description explains a situation in which a half-duplex terminal supports OCC PUSCH. When a terminal performs repeated PUSCH transmissions with OCC applied, the base station can demodulate the data based on this information because it is aware in advance of the different OCC sequences applied by two or more different terminals. However, if at least one terminal is a half-duplex terminal and the terminal fails to transmit the OCC-applied PUSCH in a specific slot due to the overlap problem with other channels described earlier, the base station must perform blind decoding, which can increase the base station reception complexity.

[0701] In satellite communication, a single satellite communicates with multiple terminals over a wide area, and each terminal transmits an uplink signal to the satellite based on its location information, using time delay and Doppler delay compensation. Consequently, it may be difficult for the satellite to accurately determine whether overlap occurs between the downlink and uplink channels at a specific point in time. Therefore, if OCC is applied to PUSCH signals transmitted repeatedly in slot units as described above, and / or if at least one terminal is a half-duplex terminal, the base station may have to perform blind decoding because it is difficult to accurately identify whether a PUSCH signal in a specific slot is being dropped; this can lead to increased complexity for the base station.

[0702] A simple solution to this problem is to ensure that the terminal does not support OCC-based PUSCH transmission when it is a half-duplex terminal. That is, when reporting terminal capabilities, if the terminal reports to the base station that it is a half-duplex terminal, the terminal may not report terminal capabilities related to OCC-based PUSCH transmission. As another example, if the terminal supports OCC-based PUSCH transmission, the terminal may not report half-duplex terminal capabilities. In summary, the above method can be referenced as not reporting both OCC-based PUSCH transmission capabilities and half-duplex terminal capabilities simultaneously. In other words, the terminal may selectively report either first information regarding OCC-based PUSCH transmission capabilities or second capability information regarding half-duplex terminals to the base station. Half-duplex terminal capabilities or the capabilities of a half-duplex terminal can be referenced as the terminal capability operating in half-duplex mode in FDD.

[0703] Hereinafter, methods for reducing the base station reception burden for OCC PUSCH transmitted by multiple terminals are described, in cases where the terminal is a half-duplex terminal and reports OCC-based PUSCH transmission capability. For example, at least one of the multiple terminals may be a half-duplex terminal, or all terminals may be half-duplex terminals.

[0704] [Example 1]

[0705] In the following embodiments, terminal operation is described for the case where a downlink channel scheduled by DCI and a PUSCH channel set as an upper signal overlap. For example, PUSCH may be a repetitive transmission resource or a single transmission resource. For example, the downlink channel may be CSI-RS or PDSCH.

[0706] According to one embodiment, terminal operation for the case where OCC is not applied to PUSCH is described first. A half-duplex terminal may be configured by an upper layer to transmit PUSCH in a specific symbol set. If the terminal is instructed to receive CSI-RS or PDSCH in a subset of a specific symbol set scheduled in DCI format, the terminal [delivers] T from the last symbol of the PDCCH reception in which the DCI format was detected proc,2 If the first symbol of PUSCH exists within, the terminal is not expected to cancel the transmission of the PUSCH. Otherwise, the terminal may cancel the transmission of the PUSCH.

[0707] If OCC is applied to the PUSCH, the terminal can identify that the PUSCH and PDSCH (or CSI-RS) included within a specific slot overlap in terms of time resources when the PUSCH is repeatedly transmitted. In this case, the terminal may apply at least one of the following methods or some combination thereof. FIGS. 31 and 32 are diagrams showing a situation in which a downlink channel overlaps in a specific slot among the PUSCH repeated transmission resources to which OCC is applied according to an embodiment of the present disclosure.

[0708] ● Method 1-1: The terminal transmits a PUSCH transmission with OCC applied T proc,2 Regardless of this, priority can be given. As illustrated in FIGS. 31 and 32, the terminal may not receive CSI-RS or PDSCH (3150, 3250) that overlap with the OCC PUSCH in terms of time resources. Then, the terminal may prioritize and transmit the OCC PUSCH (3104, 3204) that overlaps with it.

[0709] ● Method 1-2: The terminal may not transmit an OCC PUSCH that overlaps with CSI-RS or PDSCH. Alternatively, the time difference between the last symbol of a PDCCH containing a DCI format scheduling CSI-RS or PDSCH and the first symbol of an overlapped OCC PUSCH is T proc,2 Limited to cases greater than, the terminal may not transmit OCC PUSCH. The terminal T proc,2 In the case of a smaller size, the above OCC PUSCH may be transmitted, and CSI-RS or PDSCH may not be received.

[0710] ● Method 1-3: The terminal may not transmit an OCC PUSCH that overlaps with the CSI-RS or PDSCH, nor other OCC PUSCHs within the same OCC group as the OCC PUSCH. The terminal may receive the CSI-RS or PDSCH. The above-described OCC group may be referred to as a set in which a specific OCC sequence is applied to multiple PUSCHs at the slot level. For example, with reference to FIG. 31, PUSCH 1 (3102) and PUSCH 2 (3104) may be in the same OCC group, PUSCH 3 (3106) and PUSCH 4 (3108) may be in the same OCC group, PUSCH 5 (3112) and PUSCH 6 (3114) may be in the same OCC group, and PUSCH 7 (3116) and PUSCH 8 (3118) may be in the same OCC group. Taking FIG. 32 as an example, PUSCH 1 (3202), PUSCH 2 (3204), PUSCH 3 (3206), and PUSCH 4 (3208) may be in the same OCC group, and PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218) may be in the same OCC group. For example, the time interval T between the last symbol of a PDCCH containing a DCI format scheduling CSI-RS or PDSCH and the first symbol of the first OCC PUSCH within an OCC group containing an OCC PUSCH that overlaps with the corresponding CSI-RS or PDSCH is proc,2 If it is greater than, the terminal may not transmit OCC PUSCHs within the OCC group. For example, the terminal T proc,2 In cases smaller than T from the last symbol of the above PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs may not be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2If it is smaller, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0711] ● Method 1-4: The terminal may not transmit an OCC PUSCH that overlaps with the CSI-RS or PDSCH, nor other OCC PUSCHs that repeatedly transmit the same TB (transport block) as said OCC PUSCH. And, the terminal may receive the CSI-RS or PDSCH. As illustrated in FIG. 31, the terminal may determine an OCC PUSCH (3104) that overlaps with the CSI-RS or PDSCH (3150). The PUSCHs that repeatedly transmit the same TB as said OCC PUSCH (3104) may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and / or PUSCH 8 (3118), and the terminal may not transmit any of them. For example, with reference to FIG. 32, the terminal can determine an OCC PUSCH (3204) that overlaps with CSI-RS or PDSCH (3250), and the PUSCHs that repeatedly transmit the same TB, such as the OCC PUSCH (3204), may be PUSCH 1 (3202), PUSCH 3 (3206), PUSCH 4 (3208), PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218). In this case, the terminal may not transmit all of them. As another example, the time interval T between “the last symbol of a PDCCH containing a DCI format scheduling a CSI-RS or PDSCH” and “the first symbol of the first OCC PUSCH among multiple OCC PUSCHs that repeatedly transmit the same TB as an OCC PUSCH overlapping with a CSI-RS or PDSCH” is proc,2If greater than, the terminal may not transmit overlapping OCC PUSCHs and multiple OCC PUSCHs that repeatedly transmit the same TB. The interval is T proc,2 If it is smaller, the terminal is T from the last symbol of the PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs may not be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2 If it is smaller, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0712] ● Method 1-5: Similar to Method 1-3, but the terminal may not transmit “an OCC PUSCH that overlaps with CSI-RS or PDSCH” and “other OCC PUSCHs following an OCC PUSCH that overlaps with an OCC PUSCH within the same OCC group as the OCC PUSCH” together. Then, the terminal receives CSI-RS or PDSCH. Referring to FIG. 32 as an example, if there is a PUSCH2 (3204) that overlaps with CSI-RS or PDSCH (3250), in Method 1-3 the terminal may not transmit PUSCH1 (3202), PUSCH3 (3206), and / or PUSCH4 (3208) that belong to the same OCC group as PUSCH2 (3204). On the other hand, in Method 1-5, the terminal may not transmit PUSCH3 (3206) and PUSCH4 (3208) that exist after PUSCH2 (3204) and belong to the same OCC group as PUSCH2 (3204), which is a key feature of Method 1-5. Or, the time interval between “the last symbol of PDCCH containing the DCI format scheduling CSI-RS or PDSCH” and “the first symbol of the OCC PUSCH that overlaps with CSI-RS or PDSCH” is T proc,2If greater than, the terminal may not transmit other OCC PUSCHs after an overlapping OCC PUSCH within the same OCC group as the overlapping OCC PUSCH. If the interval is T proc,2 If it is smaller, the terminal is T from the last symbol of the PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and no OCC PUSCHs may be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T based on the last symbol of the PDCCH, proc,2 If smaller, the terminal may not receive CSI-RS or PDSCH.

[0713] ● Method 1-6: Similar to Method 1-4, but the terminal may not transmit together “an OCC PUSCH that overlaps with a CSI-RS or PDSCH” and “other OCC PUSCHs in which the same TB (e.g., the same TB as the TB of the overlapped OCC PUSCH) is repeatedly transmitted as in the overlapped OCC PUSCH.” And, the terminal may receive the CSI-RS or PDSCH. For example, the other OCC PUSCHs may be PUSCHs following the overlapped OCC PUSCH. Taking FIG. 31 as an example, as previously described in Method 1-4, the terminal may determine the OCC PUSCH (3104) that overlaps with the CSI-RS or PDSCH (3150). In this case, the PUSCHs that repeatedly transmit the same TB, such as the OCC PUSCH (3104), are PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and / or PUSCH 8 (3118), and the terminal may not transmit all of them. On the other hand, in Method 1-6, the terminal can determine the OCC PUSCH (3104) that overlaps with the CSI-RS or PDSCH (3150). In this case, the same TB (e.g., the same TB as the TB of OCC PUSCH (3104)) is transmitted repeatedly, such as in OCC PUSCH (3104), and PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118) that exist after OCC PUSCH (3104) may not all be transmitted. Alternatively, the time interval between “the last symbol of the PDCCH containing the DCI format scheduling the CSI-RS or PDSCH” and “the first symbol of the OCC PUSCH that overlaps with the corresponding CSI-RS or PDSCH” is T proc,2If greater than, the terminal may not transmit multiple OCC PUSCHs that repeatedly transmit an overlapping OCC PUSCH and the same TB as the overlapping OCC PUSCH. For example, the multiple OCC PUSCHs may be PUSCHs following the overlapping OCC PUSCH. The interval is T proc,2 If it is smaller, the terminal is T from the last symbol of the PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and no OCC PUSCHs may be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T based on the last symbol of the PDCCH, proc,2 If it is smaller, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0714] ● Method 1-7: The terminal may or may not transmit an OCC PUSCH that overlaps with a CSI-RS or PDSCH. That is, the terminal may receive a CSI-RS or PDSCH or transmit an OCC PUSCH at the terminal's choice. Alternatively, the time interval between the last symbol of a PDCCH containing a DCI format scheduling a CSI-RS or PDSCH and the first symbol of an OCC PUSCH that overlaps with that CSI-RS or PDSCH is T proc,2 If it is larger, the terminal can perform the operation described above. T proc,2 If it is smaller, the terminal performs OCC PUSCH transmission and may not receive CSI-RS or PDSCH.

[0715] The terminal may be capable of supporting at least one of the methods described above. If multiple methods are supported, one method may be instructed to the terminal from the base station by an upper signal, an L1 signal, or a combination thereof. Additionally, the methods described above may be applied as the same method regardless of the OCC sequence length, or different methods may be applied depending on the OCC sequence length. For example, when the OCC sequence length is 2, Method 1-2 may be applied, and when the OCC sequence length is 4, Method 1-1 may be supported. As another example, when the OCC sequence length is 2, Method 1-2 may be applied, and when the OCC sequence length is 4, Method 1-7 may be supported.

[0716] [Example 2]

[0717] In the following embodiments, the operation of a terminal is described when a downlink channel configured as an upper layer signal overlaps with a PUSCH channel scheduled by DCI and to which OCC is applied. The downlink channel may correspond to PDCCH, PDSCH, CSI-RS, or DL ​​PRS (Positioning Reference Signal). The PUSCH may be a repetitive transmission resource or a single transmission resource. The operation of the terminal is described for the case where OCC is not applied to the PUSCH.

[0718] If a half-duplex terminal is configured by an upper layer to receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS from a symbol set, the half-duplex terminal may receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS only if it does not receive (or seek or detect) a DCI format instructing it to transmit PUSCH in at least one symbol of the symbol set. Otherwise (e.g., if it receives a DCI format), the half-duplex terminal does not receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS from the symbol set, and instead the half-duplex terminal may transmit PUSCH according to a DCI format instructing it to transmit PUSCH.

[0719] If OCC is applied to a PUSCH, and / or if the PUSCH is repeatedly transmitted and overlaps with a PDCCH (or PDSCH or CSI-RS or DL ​​PRS) contained within a specific slot in terms of time resources, the terminal may apply at least one of the following methods or some combination thereof.

[0720] ● Method 2-1: The terminal may prioritize PUSCH transmissions to which OCC is applied. As illustrated in FIGS. 31 and 32, the terminal may not receive PDCCH (or PDSCH or CSI-RS or DL ​​PRS) (3150, 3250) that overlaps with the OCC PUSCH in terms of time resources. Then, the terminal may prioritize transmitting the OCC PUSCH (3104, 3204) that overlaps with it.

[0721] ● Method 2-2: The terminal may not transmit an OCC PUSCH that overlaps with the PDCCH (or PDSCH or CSI-RS or DL ​​PRS). The terminal may receive the PDCCH (or PDSCH or CSI-RS or DL ​​PRS).

[0722] ● Method 2-3: The terminal may not transmit an OCC PUSCH that overlaps with a PDCCH (or PDSCH or CSI-RS or DL ​​PRS) and other OCC PUSCHs within the same OCC group as said OCC PUSCH. The terminal may receive said PDCCH (or PDSCH or CSI-RS or DL ​​PRS). For example, the same OCC group may be referred to as a set in which a specific OCC sequence is applied to multiple PUSCHs at the slot level. For example, as illustrated in Fig. 31, PUSCH 1 (3102) and PUSCH 2 (3104) may be in the same OCC group, PUSCH 3 (3106) and PUSCH 4 (3108) may be in the same OCC group, PUSCH 5 (3112) and PUSCH 6 (3114) may be in the same OCC group, and PUSCH 7 (3116) and PUSCH 8 (3118) may be in the same OCC group. For example, as illustrated in Fig. 32, PUSCH 1 (3202), PUSCH 2 (3204), PUSCH 3 (3206), and PUSCH 4 (3208) are in the same OCC group, and PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218) are in the same OCC group.

[0723] ● Method 2-4: The terminal may not transmit other OCC PUSCHs in which the same TB (e.g., the same TB as the TB of the overlapping OCC PUSCH) is repeatedly transmitted, such as the OCC PUSCH overlapping with the PDCCH (or PDSCH or CSI-RS or DL ​​PRS) and the overlapping OCC PUSCH. The terminal may receive the PDCCH (or PDSCH or CSI-RS or DL ​​PRS). As illustrated in FIG. 31, the terminal may determine the OCC PUSCH (3104) overlapping with the CSI-RS or PDSCH (3150). In this case, the PUSCHs that repeatedly transmit the same TB, such as OCC PUSCH (3104), are PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. As illustrated in FIG. 32, the terminal can determine the OCC PUSCH (3204) that overlaps with CSI-RS or PDSCH (3250). In this case, the PUSCHs that repeatedly transmit the same TB (e.g., the same TB as the OCC PUSCH (3204)) as OCC PUSCH (3204) may be PUSCH 1 (3202), PUSCH 3 (3206), PUSCH 4 (3208), PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218), and the terminal may not transmit all of them.

[0724] ● Method 2-5: Similar to Method 2-3, but the terminal may not transmit “an OCC PUSCH overlapping with a PDCCH (or PDSCH or CSI-RS or DL ​​PRS)” and “other OCC PUSCHs within the same OCC group as the said OCC PUSCH” together. For example, other OCC PUSCHs may be PUSCHs following the overlapping OCC PUSCH. The terminal may receive a PDCCH (or PDSCH or CSI-RS or DL ​​PRS). For example, if there is a PUSCH2 (3204) that overlaps with CSI-RS or PDSCH (3250), in Method 2-3, PUSCH1 (3202), PUSCH3 (3206), and PUSCH4 (3208) belonging to the same OCC group as PUSCH2 (3204) are not transmitted, but in Method 2-5, PUSCH3 (3206) and PUSCH4 (3208) that belong to the same OCC group as PUSCH2 (3204) and exist after PUSCH2 (3204) may not be transmitted, and this may be a key feature.

[0725] ● Method 2-6: Similar to Method 2-4, but the terminal may not transmit together “an OCC PUSCH overlapping with a PDCCH (or PDSCH or CSI-RS or DL ​​PRS)” and “other OCC PUSCHs in which the same TB is repeatedly transmitted as in the said OCC PUSCH”. For example, the other OCC PUSCHs may be PUSCHs following the said overlapping OCC PUSCH. The terminal may receive a PDCCH (or PDSCH or CSI-RS or DL ​​PRS). Referring to FIG. 31 as an example, in Method 2-4, as previously described, the terminal may determine an OCC PUSCH (3104) overlapping with a CSI-RS or PDSCH (3150). In this case, the PUSCHs in which the same TB is repeatedly transmitted, such as OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. On the other hand, in Method 2-6, the terminal can determine the OCC PUSCH (3104) that overlaps with CSI-RS or PDSCH (3150). In this case, the terminal may repeatedly transmit the same TB (e.g., the same TB as the TB of OCC PUSCH (3104)) as OCC PUSCH (3104), and may not transmit all of PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118) that exist after OCC PUSCH (3104).

[0726] ● Method 2-7: The terminal may or may not transmit an OCC PUSCH that is overlaid with a PDCCH (or PDSCH or CSI-RS or DL ​​PRS). That is, the terminal may receive a CSI-RS or PDSCH or transmit an OCC PUSCH depending on the terminal's choice.

[0727] The terminal may support at least one of the methods. If the terminal supports multiple methods, one method may be instructed to the terminal from the base station by an upper layer signal (e.g., RRC message) or an L1 signal or a combination thereof.

[0728] Additionally, the same method may be applied regardless of the OCC sequence length, or different methods may be applied depending on the OCC sequence length. For example, when the OCC sequence length is 2, Method 2-2 may be applied, and when the OCC sequence length is 4, Method 2-1 may be supported. As another example, when the OCC sequence length is 2, Method 2-2 may be applied, and when the OCC sequence length is 4, the terminal may support Method 2-7.

[0729] [Example 3]

[0730] In the following embodiments, the operation of a terminal is described when a downlink channel configured with an upper layer signal (e.g., an RRC message) overlaps with a PUSCH channel configured with an upper layer signal and to which OCC is applied. The downlink channel may correspond to a PDCCH, PDSCH, CSI-RS, or DL ​​PRS (Positioning Reference Signal). For example, the PUSCH may be a repetitive transmission resource or a single transmission resource. The operation of the terminal for the case where OCC is not applied to the PUSCH is described below.

[0731] If a half-duplex terminal is configured to receive Type-0 / 0A / 1 / 2 PDCCH CSS in a specific symbol set by an upper layer signal (e.g., an RRC message), and / or is configured to transmit PUSCH by another upper layer signal in at least one symbol of the aforementioned symbol set, the terminal may receive Type-0 / 0A / 1 / 2 PDCCH CSS or transmit PUSCH.

[0732] And for other cases, the half-duplex terminal may be configured to receive PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) in a specific symbol set by an upper layer signal (e.g., RRC message) and may be configured to transmit PUSCH by another upper layer signal in at least one symbol of the aforementioned symbol set. In this case, the terminal may receive PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) and not transmit the PUSCH. If the terminal receives information prioritizing uplink transmission through a separate, different upper layer signal, and / or if the half-duplex terminal is configured to receive PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) in a specific symbol set by an upper layer signal, and is configured to transmit PUSCH by another upper layer signal in at least one symbol of the aforementioned symbol set, the terminal may transmit the PUSCH without receiving PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS).

[0733] If OCC is applied to PUSCH, and / or if the terminal identifies that a PUSCH and a PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) contained within a specific slot overlap in terms of time resources (or, in the time domain, in times), the terminal may apply at least one of the following methods or some combination thereof.

[0734] ● Method 3-1: The terminal may prioritize PUSCH transmissions to which OCC is applied. As illustrated in FIGS. 31 and 32, the terminal may not receive PDSCH (or Type-3 PDCCH CSS or PDCCH USS (User Equipment-Specific Search Space) or CSI-RS or DL ​​PRS (Positioning Reference Signal)) (3150, 3250) that overlaps with the OCC PUSCH in terms of time resources. In addition, the terminal may prioritize transmitting the OCC PUSCH (3104, 3204) that overlaps with it.

[0735] ● Method 3-2: The terminal may not transmit an OCC PUSCH that is overlaid with PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS). The terminal may receive PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS).

[0736] ● Method 3-3: The terminal may not transmit an OCC PUSCH that overlaps with a PDSCH (or, Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) and other OCC PUSCHs within the same OCC group as said OCC PUSCH. The terminal may receive said PDSCH (or, Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS). For example, the same OCC group may be referred to as a set in which a specific OCC sequence is applied to multiple PUSCHs at the slot level. For example, as illustrated in Fig. 31, PUSCH 1 (3102) and PUSCH 2 (3104) may be in the same OCC group, PUSCH 3 (3106) and PUSCH 4 (3108) may be in the same OCC group, PUSCH 5 (3112) and PUSCH 6 (3114) may be in the same OCC group, and PUSCH 7 (3116) and PUSCH 8 (3118) may be in the same OCC group. For example, as illustrated in Fig. 32, PUSCH 1 (3202), PUSCH 2 (3204), PUSCH 3 (3206), and PUSCH 4 (3208) are in the same OCC group, and PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218) are in the same OCC group.

[0737] ● Method 3-4: The terminal may not transmit together an OCC PUSCH that overlaps with a PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) and other OCC PUSCHs in which the same TB is repeatedly transmitted as said OCC PUSCH. The terminal may receive said PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS). Referring to FIG. 31 as an example, the terminal may determine an OCC PUSCH (3104) that overlaps with a CSI-RS or PDSCH (3150). In this case, the PUSCHs in which the same TB is repeatedly transmitted, such as OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. Taking FIG. 32 as an example, the terminal can determine the OCC PUSCH (3204) that overlaps with CSI-RS or PDSCH (3250). In this case, the PUSCHs that repeatedly transmit the same TB (e.g., the same TB as the OCC PUSCH (3204)) as OCC PUSCH (3204) may be PUSCH 1 (3202), PUSCH 3 (3206), PUSCH 4 (3208), PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218), and the terminal may not transmit all of them.

[0738] ● Method 3-5: Similar to Method 3-3, but the terminal may not transmit the “PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS)” and the “nested OCC PUSCH and other OCC PUSCHs within the same OCC group as said OCC PUSCH” together. For example, the other OCC PUSCHs may be PUSCHs following the nested OCC PUSCH. The terminal may receive the said PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS). For example, if there is a PUSCH2 (3204) that overlaps with CSI-RS or PDSCH (3250), in Method 3-3, PUSCH1 (3202), PUSCH3 (3206), and PUSCH4 (3208) belonging to the same OCC group as PUSCH2 (3204) are not transmitted, but in Method 3-5, PUSCH3 (3206) and PUSCH4 (3208) that belong to the same OCC group as PUSCH2 (3204) and exist after PUSCH2 (3204) may not be transmitted, and this may be a key feature.

[0739] ● Method 3-6: Similar to Method 3-4, but the terminal may not transmit together “an OCC PUSCH overlapping with a PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS)” and “other OCC PUSCHs in which the same TB is repeatedly transmitted, such as the overlapping OCC PUSCH.” For example, the other OCC PUSCHs may be PUSCHs following the overlapping OCC PUSCH. The terminal may receive the PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS) described above. Referring to FIG. 31 as an example, as previously described in Method 3-4, the terminal may determine an OCC PUSCH (3104) overlapping with a CSI-RS or PDSCH (3150). In this case, the PUSCHs in which the same TB is repeatedly transmitted, such as OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. On the other hand, in method 3-6, the terminal may determine the OCC PUSCH (3104) that overlaps with CSI-RS or PDSCH (3150). In this case, the terminal may not transmit all of the PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118) that exist after the OCC PUSCH (3104), as the same TB is transmitted repeatedly.

[0740] ● Method 3-7: The terminal may or may not transmit an OCC PUSCH overlaid with PDSCH (or Type-3 PDCCH CSS or PDCCH USS or CSI-RS or DL ​​PRS). That is, the terminal may receive CSI-RS or PDSCH or transmit an OCC PUSCH depending on the terminal's choice.

[0741] The terminal may support at least one of the methods described above. If the terminal supports multiple methods, one method may be instructed to the terminal from the base station by an upper layer signal, an L1 signal, or a combination thereof. Additionally, the methods described above may be applied as the same method regardless of the OCC sequence length, or different methods may be applied depending on the OCC sequence length. For example, when the OCC sequence length is 2, the terminal may apply Method 3-2, and when the OCC sequence length is 4, the terminal may support Method 3-1. As another example, when the OCC sequence length is 2, the terminal may apply Method 3-2, and when the OCC sequence length is 4, the terminal may support Method 3-7.

[0742] [Example 4]

[0743] In the following embodiments, the operation of a terminal is described when a downlink channel scheduled by DCI and a PUSCH channel scheduled by DCI and having OCC applied overlap. The downlink channel described above may correspond to PDSCH or CSI-RS.

[0744] PUSCH may be a recurring transmission resource or a single transmission resource. The operation of a terminal for the case where OCC is not applied to PUSCH is described. When a half-duplex terminal is instructed by an upper layer signal (e.g., an RRC message) to receive a PDSCH scheduled in a DCI format included in a Type-0 / 0A / 1 / 2 PDCCH CSS in a specific symbol set, and / or is instructed to transmit a PUSCH scheduled in a different DCI format in at least one symbol of the above-described symbol set, the terminal may receive the PDSCH or transmit the PUSCH.

[0745] And in other cases, if a half-duplex terminal is instructed to receive a PDSCH or CSI-RS scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS in a specific symbol set, and is instructed to transmit a PUSCH scheduled in another DCI format in at least one symbol of the symbol set, the terminal may receive the PDSCH (or CSI-RS) and may not transmit the PUSCH. If the terminal receives information prioritizing uplink transmission through a separate, different upper signal, and / or if the half-duplex terminal is provided to receive the PDSCH (or CSI-RS) scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS in a specific symbol set, and is instructed to transmit the PUSCH scheduled in another DCI format in at least one symbol of the symbol set, the terminal may not receive the PDSCH (or CSI-RS) scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS and may transmit the PUSCH.

[0746] Alternatively, a half-duplex terminal may be instructed to receive a PDSCH or CSI-RS scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS in a specific symbol set, and to transmit a PUSCH scheduled in another DCI format in at least one symbol of said symbol set. In this case, the terminal may not receive the PDSCH (or CSI-RS) and may transmit the PUSCH. If the terminal is provided with information prioritizing downlink transmission through a separate upper layer signal, and / or the half-duplex terminal is provided with to receive a PDSCH (or CSI-RS) scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS in a specific symbol set, and is instructed to transmit a PUSCH scheduled in another DCI format in at least one symbol of said symbol set, the terminal may receive said PDSCH (or CSI-RS) scheduled in a DCI format included in a Type-3 PDCCH CSS or PDCCH USS and not transmit said PUSCH.

[0747] If OCC is applied to the PUSCH, and / or if the terminal identifies that the PUSCH and PDSCH (or CSI-RS) contained within a specific slot overlap in terms of time resources when the PUSCH is transmitted repeatedly, the terminal may apply at least one of the following methods or some combination thereof. For example, the PDSCH may be scheduled by the DCI format contained in the Type-3 PDCCH CSS or PDCCH USS.

[0748] ● Method 4-1: The terminal transmits a PUSCH transmission with OCC applied T proc,2Regardless of this, priority can be given. As illustrated in FIGS. 31 and 32, the terminal may not receive CSI-RS or PDSCH (3150, 3250) that overlap with the OCC PUSCH in terms of time resources. Then, the terminal may prioritize and transmit the OCC PUSCH (3104, 3204) that overlaps with it.

[0749] ● Method 4-2: The terminal may not transmit an OCC PUSCH that overlaps with CSI-RS or PDSCH. The terminal may receive CSI-RS or PDSCH. Or, the time difference between the last symbol of a PDCCH containing a DCI format scheduling CSI-RS or PDSCH and the first symbol of the overlapped OCC PUSCH is T proc,2 If the time difference is greater than T, the terminal may not transmit OCC PUSCH. proc,2 In cases smaller than this, the terminal may transmit OCC PUSCH and may not receive CSI-RS or PDSCH.

[0750] ● Method 4-3: The terminal may not transmit an OCC PUSCH that overlaps with the CSI-RS or PDSCH, and other OCC PUSCHs within the same OCC group as the said OCC PUSCH. The terminal may receive the said CSI-RS or PDSCH. For example, the same OCC group may be referred to as a set in which a specific OCC sequence is applied to multiple PUSCHs at the slot level. Taking FIG. 31 as an example, PUSCH 1 (3102) and PUSCH 2 (3104) may be in the same OCC group, PUSCH 3 (3106) and PUSCH 4 (3108) may be in the same OCC group, PUSCH 5 (3112) and PUSCH 6 (3114) may be in the same OCC group, and PUSCH 7 (3116) and PUSCH 8 (3118) may be in the same OCC group. Taking FIG. 32 as an example, PUSCH 1 (3202), PUSCH 2 (3204), PUSCH 3 (3206), and PUSCH 4 (3208) belong to the same OCC group, and PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218) belong to the same OCC group. Alternatively, the time interval T between “the last symbol of a PDCCH containing a DCI format scheduling a CSI-RS or PDSCH” and “the first symbol of the first OCC PUSCH within an OCC group containing an OCC PUSCH that overlaps with the corresponding CSI-RS or PDSCH” is proc,2 If it is greater than, the terminal may not transmit OCC PUSCHs within the OCC group. The time interval is T proc,2 In the case where it is smaller, the terminal is T from the last symbol of the above PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs thereafter may not be transmitted. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2In cases where it falls under a smaller category, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0751] ● Method 4-4: The terminal may not transmit together the OCC PUSCH that overlaps with the CSI-RS or PDSCH and other OCC PUSCHs in which the same TB is repeatedly transmitted, such as the OCC PUSCH. The terminal may receive the CSI-RS or PDSCH. As illustrated in FIG. 31, the terminal may determine the OCC PUSCH (3104) that overlaps with the CSI-RS or PDSCH (3150). In this case, the PUSCHs in which the same TB is repeatedly transmitted, such as the OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. For example, with reference to FIG. 32, the terminal can determine an OCC PUSCH (3204) that overlaps with CSI-RS or PDSCH (3250). In this case, the PUSCHs in which the same TB is repeatedly transmitted, such as the OCC PUSCH (3204), may be PUSCH 1 (3202), PUSCH 3 (3206), PUSCH 4 (3208), PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218), and the terminal may not transmit all of them. As another example, the time interval between “the last symbol of a PDCCH containing a DCI format scheduling a CSI-RS or PDSCH” and “the first symbol of the first OCC PUSCH among multiple OCC PUSCHs that repeatedly transmit the same TB as an OCC PUSCH overlapping with a CSI-RS or PDSCH” is T proc,2If it is greater than, the terminal may not transmit overlapping OCC PUSCHs and multiple OCC PUSCHs that repeatedly transmit the same TB. The time interval is T proc,2 In the case where it is smaller, the terminal is T from the last symbol of the above PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs may not be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2 In cases where it falls under a smaller category, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0752] ● Method 4-5: Similar to Method 4-3, but the terminal may not transmit “an OCC PUSCH that overlaps with CSI-RS or PDSCH” and “other OCC PUSCHs within the same OCC group as the OCC PUSCH” together. For example, the other OCC PUSCHs may be PUSCHs following the overlapped OCC PUSCH. The terminal may receive CSI-RS or PDSCH. Referring to FIG. 32 as an example, if there is a PUSCH2 (3204) that overlaps with CSI-RS or PDSCH (3250), in Method 4-3 the terminal may not transmit PUSCH1 (3202), PUSCH3 (3206), and PUSCH4 (3208) that belong to the same OCC group as PUSCH2 (3204). On the other hand, in Method 4-5, the terminal may not transmit PUSCH3 (3206) and PUSCH4 (3208) that exist after PUSCH2 (3204) and belong to the same OCC group as PUSCH2 (3204), which is a key feature. Alternatively, the time interval between the last symbol of a PDCCH containing a DCI format scheduling CSI-RS or PDSCH and the first symbol of an OCC PUSCH that overlaps with the corresponding CSI-RS or PDSCH is T proc,2If greater than, the terminal may not transmit other OCC PUSCHs within the same OCC group as the overlapping OCC PUSCH. For example, the other OCC PUSCHs may be PUSCHs following the overlapping OCC PUSCH. The time interval is T proc,2 If it is smaller, the terminal is T from the last symbol of the PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs may not be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2 In cases where it falls under a smaller category, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0753] ● Method 4-6: Similar to Method 4-4, but the terminal may not transmit together the “OCC PUSCH overlapping with the CSI-RS or PDSCH” and “other OCC PUSCHs that repeat the same TB as the said OCC PUSCH”. For example, the other OCC PUSCHs may be PUSCHs following the said overlapping OCC PUSCH. The terminal may receive the CSI-RS or PDSCH. Taking FIG. 31 as an example, as previously described in Method 4-4, the terminal may determine the OCC PUSCH (3104) overlapping with the CSI-RS or PDSCH (3150). In this case, the PUSCHs that repeatedly transmit the same TB, such as OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. On the other hand, in method 4-6, the terminal can determine the OCC PUSCH (3104) that overlaps with CSI-RS or PDSCH (3150). In this case, the terminal may repeatedly transmit the same TB, such as OCC PUSCH (3104), and may not transmit all of PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118) that exist after OCC PUSCH (3104). As another example, the time interval between the last symbol of a PDCCH containing a DCI format scheduling a CSI-RS or PDSCH and the first symbol of an OCC PUSCH that overlaps with that CSI-RS or PDSCH is T proc,2If greater than, the terminal may not transmit “overlapping OCC PUSCH” and “multiple OCC PUSCHs that repeatedly transmit the same TB as the overlapping OCC PUSCH”. For example, the multiple OCC PUSCHs may be PUSCHs following the overlapping OCC PUSCH. The time interval is T proc,2 In the case where it is smaller, the terminal is T from the last symbol of the above PDCCH proc,2 OCC PUSCHs existing thereafter may be transmitted, and OCC PUSCHs may not be transmitted thereafter. If an OCC PUSCH that overlaps with CSI-RS or PDSCH is T proc,2 In cases where it falls under a smaller category, the terminal may not receive the corresponding CSI-RS or PDSCH.

[0754] ● Method 4-7: The terminal may or may not transmit an OCC PUSCH that overlaps with CSI-RS or PDSCH. That is, the terminal may receive CSI-RS or PDSCH or transmit an OCC PUSCH based on the terminal's choice. As another example, the time interval between the “last symbol of the PDCCH containing the DCI format scheduling the CSI-RS or PDSCH” and the “first symbol of the OCC PUSCH that overlaps with the CSI-RS or PDSCH” is T proc,2 If it is greater than, the described operation (e.g., receiving CSI-RS (or PDSCH) or transmitting OCC PUSCH based on the terminal's selection) may be performed. The time interval is T proc,2 If it is smaller, the terminal performs OCC PUSCH transmission and may not receive CSI-RS or PDSCH.

[0755] The terminal may support at least one of the methods described above. If the terminal supports multiple methods, one method may be instructed to the terminal from the base station by an upper layer signal, an L1 signal, or a combination thereof. Additionally, the methods described above may be applied as the same method regardless of the OCC sequence length, or different methods may be applied depending on the OCC sequence length. For example, when the OCC sequence length is 2, the terminal may apply method 4-2, and when the OCC sequence length is 4, the terminal may support method 4-1. As another example, when the OCC sequence length is 2, the terminal may apply method 4-2, and when the OCC sequence length is 4, the terminal may support method 4-7.

[0756] [Example 5]

[0757] In the following embodiments, the operation of a terminal is described when an SS / PBCH block and a PUSCH channel with an OCC applied (or scheduled in DCI format) configured as an upper layer signal overlap. The SS / PBCH block may be referred to as a resource through which PSS, SSS, and / or PBCH are transmitted. First, the operation of a terminal is described for the case where no OCC is applied to the PUSCH.

[0758] When a half-duplex terminal transmits a PUSCH set by an upper layer (e.g., RRC signaling) and is informed that an SS / PBCH block exists within an active DL BWP via SIB1 or ServingCellConfigCommon's ssb-PositionsInBurst or NonCellDefiningSSB, the half-duplex terminal may not transmit the PUSCH if at least one of the following conditions applies.

[0759] ● Condition 5-1: The last symbol of the PUSCH transmission is at least N times longer than the first symbol of the next fastest SS / PBCH block Tx-Rx· If Tc is not present prior to

[0760] ● Condition 5-2: The first symbol of the PUSCH transmission is at least N since the last symbol of the previous latest SS / PBCH block. Rx-Tx · If not in Tc

[0761] The above N Tx-Rx is 25600 in FR1, and 13792 could correspond to FR2. Tc is T c = And, , It could be.

[0762] Additionally, when a half-duplex terminal receives information that it is transmitting a PUSCH, and the half-duplex terminal is provided with information that an SS / PBCH block exists in a specific symbol set within an active DL BWP by SIB1 or ServingCellConfigCommon's ssb-PositionsInBurst or NonCellDefiningSSB, the half-duplex terminal does not transmit the overlapping PUSCH if the PUSCH overlaps with one of the symbols in the symbol set.

[0763] If OCC is applied to PUSCH, the terminal detects that in a situation where PUSCH is repeatedly transmitted, the PUSCH and SS / PBCH blocks contained within a specific slot overlap in terms of time resources (e.g., time domain), or that the time interval between the last symbol of a specific SS / PBCH block and the first symbol of a subsequent PUSCH is N. Tx-Rx ·Tc, or the time interval between the last symbol of PUSCH and the first symbol of the subsequent SS / PBCH block is N Tx-Rx · It can be identified as Tc. In this case, the terminal may apply at least one of the following methods or some combination thereof.

[0764] ● Method 5-1: The terminal may prioritize the PUSCH transmission to which OCC is applied. Referring to FIGS. 31 and 32 as an example, the terminal may not receive SS / PBCH blocks (3150, 3250) that overlap with the OCC PUSCH in terms of time resources. Then, the terminal may prioritize transmitting the OCC PUSCH (3104, 3204) that overlaps with it. Alternatively, the OCC PUSCH and the SS / PBCH blocks do not overlap in terms of time resources as in FIGS. 31 and 32, but the time interval between the last symbol of a specific SS / PBCH block and the first symbol of a subsequent PUSCH is N Tx-Rx ·Tc, or the time interval between the last symbol of PUSCH and the first symbol of the subsequent SS / PBCH block is N Tx-Rx · When Tc, the terminal may transmit OCC PUSCH without receiving the above SS / PBCH block.

[0765] ● Method 5-2: The terminal may not transmit an OCC PUSCH that overlaps with an SS / PBCH block. The terminal may receive the SS / PBCH block. Alternatively, the OCC PUSCH and the SS / PBCH block may overlap, and the time interval between the last symbol of a specific SS / PBCH block and the first symbol of a subsequent PUSCH is N. Tx-Rx ·Tc, or the time interval between the last symbol of PUSCH and the first symbol of the subsequent SS / PBCH block is N Tx-Rx · When Tc, the terminal may receive the SS / PBCH block and may not transmit OCC PUSCH.

[0766] ● Method 5-3: The terminal may not transmit the OCC PUSCH that overlaps with the SS / PBCH block and other OCC PUSCHs within the same OCC group as said OCC PUSCH together. The terminal may receive said SS / PBCH block. Or, the OCC PUSCH and the SS / PBCH block may have a time interval N between the last symbol of a specific SS / PBCH block and the first symbol of a subsequent PUSCH. Tx-Rx ·Tc, or the time interval between the last symbol of PUSCH and the first symbol of the subsequent SS / PBCH block is N Tx-Rx · When Tc, the terminal may receive the SS / PBCH block, and the terminal may not transmit together “OCC PUSCH that overlaps with the SS / PBCH block” and “other OCC PUSCHs that repeatedly transmit the same TB, such as the OCC PUSCH.” The terminal may not transmit together “overlapping OCC PUSCH” and “other OCC PUSCHs within the same OCC group as the OCC PUSCH.” For example, the same OCC group may be referred to as a set in which a specific OCC sequence is applied to multiple PUSCHs at the slot level. For example, as illustrated in Fig. 31, PUSCH 1 (3102) and PUSCH 2 (3104) may be in the same OCC group, PUSCH 3 (3106) and PUSCH 4 (3108) may be in the same OCC group, PUSCH 5 (3112) and PUSCH 6 (3114) may be in the same OCC group, and PUSCH 7 (3116) and PUSCH 8 (3118) may be in the same OCC group. For example, as illustrated in Fig. 32, PUSCH 1 (3202), PUSCH 2 (3204), PUSCH 3 (3206), and PUSCH 4 (3208) are in the same OCC group, and PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218) are in the same OCC group.

[0767] ● Method 5-4: The terminal may not transmit other OCC PUSCHs that repeat the same TB, such as an OCC PUSCH overlapping an SS / PBCH block and an overlapping OCC PUSCH. The terminal may receive an SS / PBCH block. Alternatively, the OCC PUSCH and the SS / PBCH block may have a time interval N between the last symbol of a specific SS / PBCH block and the first symbol of a subsequent PUSCH. Tx-Rx ·Tc, or the time interval between the last symbol of PUSCH and the first symbol of the subsequent SS / PBCH block is N Tx-Rx · When Tc, the terminal can receive the SS / PBCH block, and the terminal may not transmit together “an OCC PUSCH that overlaps with the SS / PBCH block” and “other OCC PUSCHs that repeatedly transmit the same TB, such as the overlapped OCC PUSCH.” As illustrated in FIG. 31, the terminal can determine the OCC PUSCH (3104) that overlaps with the SS / PBCH block (3150). In this case, the PUSCHs that repeatedly transmit the same TB, such as the OCC PUSCH (3104), may be PUSCH 1 (3102), PUSCH 3 (3106), PUSCH 4 (3108), PUSCH 5 (3112), PUSCH 6 (3114), PUSCH 7 (3116), and PUSCH 8 (3118), and the terminal may not transmit all of them. For example, with reference to FIG. 32, the terminal can determine an OCC PUSCH (3204) that overlaps with an SS / PBCH block (3250). In this case, the PUSCHs that repeatedly transmit the same TB, such as the OCC PUSCH (3204), may be PUSCH 1 (3202), PUSCH 3 (3206), PUSCH 4 (3208), PUSCH 5 (3212), PUSCH 6 (3214), PUSCH 7 (3216), and PUSCH 8 (3218), and the terminal may not transmit all of them.

[0768] ● Method 5-5: Similar to Metho...

Claims

1. In a method performed by UE (user equipment), A step of receiving a first DCI (downlink control information) for scheduling a PDSCH (physical downlink shared channel); A step of receiving a second DCI for scheduling a PUSCH (physical uplink shared channel), and enabling an inter-slot OCC (orthogonal cover code) for the PUSCH; A step of identifying an overlap between at least one symbol of a set of symbols associated with the above PDSCH and the above PUSCH; and If the first DCI is not received within the common search space (CSS) and the transmission of the PUSCH does not begin within a specified time from the last symbol of the first DCI, the method includes the step of receiving the PDSCH without transmitting the first PUSCH associated with the overlap within the OCC group of the PUSCH. A method in which, when the first PUSCH is not transmitted, the PUSCHs within the OCC group including the first PUSCH are not transmitted.

2. In Claim 1, A step of receiving a radio resource control (RRC) message to set uplink signals to transmit from a set of symbols; and The method includes the step of identifying that the first DCI instructs the receiving of the PDSCH in a subset of the set of symbols associated with the uplink signal, and A method in which uplink signals within the OCC group of the uplink signal are not transmitted if the first symbol of the set of symbols associated with the uplink signal does not start within the specified time from the last symbol of the first DCI.

3. In Claim 1, The transmission of the above PUSCH is a method based on the earliest PUSCH within the OCC group.

4. In Claim 1, A method in which the above UE is an HD (half-duplex) UE that is not capable of simultaneous transmission and reception.

5. In Claim 1, The above UE is a method that operates on an NTN (non-terrestrial network) cell.

6. In Claim 1, The above specified time is the PUSCH preparation time.

7. In Claim 1, The above first PUSCH is a method corresponding to a PUSCH repetition.

8. Regarding UE (user equipment), At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receives the first DCI (downlink control information) for scheduling the PDSCH (physical downlink shared channel), and Receives a second DCI for scheduling a PUSCH (physical uplink shared channel), and an inter-slot OCC (orthogonal cover code) is enabled for the PUSCH. Identifying an overlap between at least one symbol of the set of symbols associated with the above PDSCH and the above PUSCH, and If the first DCI is not received within the common search space (CSS) and the transmission of the PUSCH does not begin within a specified time from the last symbol of the first DCI, the PDSCH is to be received without the transmission of the first PUSCH associated with the overlap within the OCC group of the PUSCH. A UE in which, when the first PUSCH is not transmitted, the PUSCHs within the OCC group including the first PUSCH are not transmitted.

9. In Claim 8, The above commands are the above UE: Receives an RRC (radio resource control) message to configure the uplink signal to be transmitted from a set of symbols, and The first DCI identifies that it is instructed to receive the PDSCH in a subset of the set of symbols associated with the uplink signal, and UE, in which uplink signals within the OCC group of the uplink signal are not transmitted if the first symbol of the set of symbols associated with the uplink signal does not start within the specified time from the last symbol of the first DCI.

10. In Claim 8, The transmission of the above PUSCH is based on the earliest PUSCH within the OCC group, with respect to the UE.

11. In Claim 8, The above UE is a UE that is an HD (half-duplex) UE that is not capable of simultaneous transmission and reception.

12. In claim 8, The above UE is a UE operating on an NTN (non-terrestrial network) cell.

13. In claim 8, The above specified time is the PUSCH preparation time, UE.

14. In Claim 8, The above first PUSCH is a UE corresponding to a PUSCH repetition.

15. One or more computer-readable non-transitory storage media storing computer-executable instructions, wherein when the computer-executable instructions are executed individually or collectively by at least one processor of a User Equipment (UE), the UE: Receives the first DCI (downlink control information) for scheduling the PDSCH (physical downlink shared channel), and Receives a second DCI for scheduling a PUSCH (physical uplink shared channel), and an inter-slot OCC (orthogonal cover code) is enabled for the PUSCH. Identifying an overlap between at least one symbol of the set of symbols associated with the above PDSCH and the above PUSCH, and If the first DCI is not received within the common search space (CSS) and the transmission of the PUSCH does not begin within a specified time from the last symbol of the first DCI, operations to receive the PDSCH without the transmission of the first PUSCH associated with the overlap within the orthogonal cover code (OCC) group of the PUSCH are performed. A recording medium in which, when the first PUSCH is not transmitted, the PUSCHs within the OCC group including the first PUSCH are not transmitted.

Images