Method and device for transmitting and receiving data information in satellite communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment in a wireless communication system, according to various embodiments of the present disclosure, comprises the steps of: receiving, from a base station, configuration information regarding an orthogonal cover code (OCC) for a physical uplink shared channel (PUSCH); and transmitting the PUSCH to the base station by applying the OCC on the basis of the configuration information, wherein the OCC can be applied, for one transport block (TB), across a plurality of symbols or applied across a plurality of resource elements (REs) within one symbol.

Description

Method and device for transmitting and receiving data information in a satellite communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a satellite communication system. Specifically, the present disclosure relates to a method for transmitting and receiving data information in a satellite communication system and a device capable of performing the method.

[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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design operation and internalize end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing this technology.

[0008] The disclosed embodiment seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0009] The present disclosure, which aims to solve the above-described problem, is characterized by a method for processing a control signal in a wireless communication system, comprising: an operation of receiving a first control signal transmitted from a base station; an operation of processing the received first control signal; and an operation of transmitting a second control signal generated based on the processing to the base station.

[0010] The disclosed embodiment provides a device and method capable of effectively providing a service in a mobile communication system.

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

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

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

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

[0015] 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.

[0016] FIG. 6 is a diagram illustrating a case in which a terminal can have multiple PDCCH monitoring positions within a slot through Span in a wireless communication system according to one embodiment of the present disclosure.

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

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

[0019] FIG. 9 is a diagram illustrating a TCI indication MAC CE signaling structure for PDCCH DMRS in a wireless communication system according to one embodiment of the present disclosure.

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

[0021] FIG. 11 is a diagram for explaining a method for a base station and a terminal to transmit and 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.

[0022] FIG. 12 is a diagram for explaining a method for selecting a set of control resources that can be received by a terminal in consideration of priority when receiving a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 13 is a diagram illustrating an example of an aperiodic CSI reporting method according to one embodiment of the present disclosure.

[0024] FIG. 14 is a diagram illustrating an example of PUSCH repetition transmission type B in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

[0028] Figure 18 illustrates a procedure for a base station to control the transmission power of a terminal in a cellular system.

[0029] FIG. 19 is a diagram illustrating a process for generating a Type-1 (semi-static) HARQ-ACK codebook by a terminal according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

[0037] FIG. 27 is a diagram showing a method for a terminal to apply an OCC scheme from a time resource perspective when transmitting a PUSCH according to one embodiment of the present disclosure.

[0038] FIG. 28 is a diagram showing a method for applying the OCC method from a frequency resource perspective when a terminal transmits PUSCH according to one embodiment of the present disclosure.

[0039] FIG. 29 is a diagram showing a method for a terminal to apply an OCC scheme from a time resource perspective when transmitting a PUSCH according to one embodiment of the present disclosure.

[0040] FIG. 30 is a diagram showing a method for a terminal to apply an OCC scheme from a time resource perspective when transmitting a PUSCH according to one embodiment of the present disclosure.

[0041] FIG. 31 is a diagram showing a method for applying the OCC method from a frequency resource perspective when a terminal transmits PUSCH according to one embodiment of the present disclosure.

[0042] FIG. 32 is a diagram showing a method for applying the OCC method from a frequency resource perspective when a terminal transmits PUSCH according to one embodiment of the present disclosure.

[0043] FIG. 33 is a diagram illustrating a procedure for performing PUSCH transmission using an OCC method according to one embodiment of the present disclosure.

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

[0045] FIG. 35 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0046] To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G communication systems, or pre-5G communication systems. For this reason, 5G communication systems, or pre-5G communication systems, are also called beyond 4G networks or post-LTE systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, 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.

[0047] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technologies, wireless and wired communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0048] Accordingly, various attempts are being made to apply 5G communication systems (also known as New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN), a big data processing technology described above, can also be considered an example of the convergence of 3eG and IoT technologies.

[0049] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

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

[0051] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0052] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0053] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present 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. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the specification.

[0054] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode 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 a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0055] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0056] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0057] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0058] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 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.

[0059] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in 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 refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0060] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0061] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0062] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage. This may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0063] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and, at the same time, must have a 10 -5The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services. Simultaneously, design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0064] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0065] [NR time-frequency resources]

[0066] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

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

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

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

[0070] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, the cases where μ = 0 (204) and μ = 1 (205) as the subcarrier spacing setting value are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of 1 slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of 2 slots (203). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.

[0071]

[0072] [Bandwidth Part (BWP)]

[0073] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

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

[0075] Figure 3 shows an example in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set the following information for each bandwidth portion.

[0076]

[0077] Of course, the above example is not limited, and in addition to the above configuration information, various parameters related to the bandwidth portion can be configured for the terminal. The above information can be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one bandwidth portion among the configured one or more bandwidth portions can be activated. Whether or not the configured bandwidth portion is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (Downlink Control Information).

[0078] According to some embodiments, a terminal before RRC (Radio Resource Control) connection can receive configuration information for an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive configuration information for a control region (Control Resource Set, CORESET) and a search space where a PDCCH for receiving system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access can be transmitted through the MIB during the initial access phase. The control region and search space configured by the MIB may each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB. In addition, the base station can notify the terminal of configuration information for a monitoring cycle and occasion for control region #0, i.e., configuration information for search space #0, through the MIB. The terminal may consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial connection. At this time, the identifier (ID) of the initial bandwidth portion may be considered as 0.

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

[0080] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0081] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed, and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0082] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 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 receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0083] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part through the MIB (Master Information Block) in the initial access stage. More specifically, the terminal can set a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) for scheduling a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to the purpose of receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0084] [Bandwidth Part (BWP) Change]

[0085] When one or more bandwidth part values ​​are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0086] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as follows, for example:

[0087]

[0088] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0089] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP The completion can be done at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. When the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules the data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

[0090] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth change, the terminal may not perform any transmission or reception during the time period from the third symbol of the slot in which the PDCCH including the DCI is received to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth change in slot n and the slot offset value indicated by the 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).

[0091] [SS / PBCH block]

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

[0093] An SS / PBCH block may refer to a physical layer channel block consisting of a PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

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

[0095] - SSS: It serves as a 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.

[0096] - PBCH: Provides essential system information required for transmission and reception of data and control channels of a terminal. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

[0097] - SS / PBCH Block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be transmitted within a 5ms period, and each transmitted SS / PBCH block can be distinguished by an index.

[0098] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0099] [PDCCH: DCI related]

[0100] Next, we will specifically explain downlink control information (DCI) in the 5G system.

[0101] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0102] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

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

[0104] DCI format 0_0 can be used as a fallback 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 can include, for example, the following information.

[0105]

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

[0107]

[0108]

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

[0110]

[0111] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the following information.

[0112]

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

[0114] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0115] FIG. 4 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and one slot (420) in the time axis. The control regions (401, 402) may be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 404). Referring to the example illustrated in FIG. 4, Control Region #1 (401) is set to a control region length of two symbols, and Control Region #2 (402) is set to a control region length of one symbol.

[0116] In the aforementioned 5G, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, the information may include the following:

[0117]

[0118] In Table 9, 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 region.

[0119] 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. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 503), and a 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 constitute a downlink control channel allocation unit.

[0120] 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), 1 CCE (504) can be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control region. 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.

[0121] The basic unit of the downlink control channel illustrated in FIG. 5, that is, the REG (503), may include both the REs to which the DCI is mapped and the areas to which the DMRS (505), which is a reference signal for decoding the REs, 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, or 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 a 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 (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

[0122] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.

[0123] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot 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 corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the following information can be included.

[0124]

[0125] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0126] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

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

[0128] - 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

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

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

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

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

[0133] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

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

[0137] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0138] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0139] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0140] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

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

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

[0143] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

[0144] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0145] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0146] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

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

[0148]

[0149] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in the following mathematical expression 1.

[0150] <Mathematical Formula 1>

[0151]

[0152] - : Integration level

[0153] - Carrier Index

[0154] - Total number of CCEs existing within the control region p

[0155] - Slot Index

[0156] - Number of PDCCH candidates for aggregation level L

[0157] - PDCCH candidate index for aggregation level L

[0158] -

[0159] -

[0160] - Terminal identifier

[0161] The value can be 0 for a common search space.

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

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

[0164] [PDCCH: span]

[0165] A terminal can perform terminal capability reporting for each subcarrier interval when it has multiple PDCCH monitoring positions within a slot, and at this time, the concept of Span can be used. A Span refers to consecutive symbols within a slot in which the terminal can monitor a PDCCH, and each PDCCH monitoring position is within one Span. A Span can be expressed as (X, Y), where x refers to the minimum number of symbols that must be spaced between the first symbols of two consecutive Spans, and Y refers to the number of consecutive symbols in which the PDCCH can be monitored within one Span. In this case, the terminal can monitor the PDCCH in the section from the first symbol of the Span to within Y symbols within the Span.

[0166] FIG. 6 is a diagram illustrating a case in which a terminal in a wireless communication system can have multiple PDCCH monitoring positions within a slot, using Span. Span can be (X, Y) = (7, 4), (4, 3), (2, 2), and each of the three cases is represented by (6-00), (6-05), and (6-10) in FIG. 6. For example, (6-00) represents a case in which there are two Spans, which can be represented by (7, 4), within a slot. The interval between the first symbols of the two Spans is represented as X = 7, and PDCCH monitoring positions can exist within a total of Y = 3 symbols from the first symbol of each Span, and it is shown that search spaces 1 and 2 each exist within Y = 3 symbols. As another example, (6-05) represents a case where there are a total of three spans within a slot that can be expressed as (4,3), and the gap between the second and third spans is shown to be X'=5 symbols, which is greater than X=4.

[0167] [PDCCH: Terminal Capability Report]

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

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

[0170]

[0171] - Terminal Capability 2 (hereinafter referred to as FG 3-2). This terminal capability refers to the capability to monitor a common search space or a terminal-specific search space, regardless of the starting symbol position of a single monitoring occasion (MO), as shown in Table 13-2 below. This terminal capability is optional, and whether or not the terminal supports this capability is explicitly reported to the base station.

[0172]

[0173] - Terminal capability 3 (hereinafter referred to as FG 3-5, 3-5a, 3-5b). This terminal capability indicates the pattern of MOs that the terminal can monitor when there are multiple monitoring positions (MOs: monitoring occasions) for a common search space or a terminal-specific search space within a slot, as shown in Table 13-3 below. The above-described pattern is composed of the start symbol interval X between different MOs and the maximum symbol length Y for an MO. The combination of (X,Y) supported by the terminal can be one or more of {(2,2), (4,3), (7,3)}. This terminal capability can be selectively supported by the terminal (optional), and whether this capability is supported and the above-described combination of (X,Y) are explicitly reported to the base station.

[0174]

[0175]

[0176] The terminal may report to the base station whether it supports the aforementioned terminal capabilities 2 and / or 3 and related parameters. Based on the reported terminal capabilities, the base station may perform time-domain resource allocation for the common search space and terminal-specific search space. When allocating these resources, the base station may ensure that the MO is not positioned in a location that the terminal cannot monitor.

[0177] [QCL, TCI state]

[0178] In a wireless communication system, one or more different antenna ports (or one or more channels, signals, and combinations thereof, but for convenience, they will be referred to as different antenna ports in the following description of the present disclosure) can be associated with each other by a QCL (Quasi co-location) setting as shown in [Table 14] below. The TCI state is to notify the QCL relationship between the PDCCH (or PDCCH DMRS) and other RSs or channels. When a reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at the antenna port A to the channel measurement from the antenna port B. QCL may need to relate different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Accordingly, NR supports four types of QCL relationships, as shown in Table 14 below.

[0179]

[0180] The above 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 spatial channel correlation.

[0181] The above QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 15 below. Referring to Table 15, the base station can set one or more TCI states to the terminal and inform the RS referencing the ID of the TCI state, i.e., up to two QCL relationships (qcl-Type1, qcl-Type2) for the target RS. At this time, each QCL information (QCL-Info) included in the above TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 14 above.

[0182]

[0183] FIG. 7 is a diagram illustrating an example of base station beam allocation according to TCI state settings. Referring to FIG. 7, the base station can transmit information on N different beams to the terminal through N different TCI states. For example, in case of N=3 as shown in FIG. 7, the base station can notify that antenna ports referencing different TCI states 700, 705, or 710 have different spatial Rx parameters, i.e., are associated with different beams, by setting the qcl-Type2 parameter included in three TCI states (700, 705, 710) to be associated with CSI-RS or SSB corresponding to different beams and to QCL type D.

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

[0185] Table 16 shows valid TCI state settings when the target antenna port is a CSI-RS for tracking (TRS). The TRS refers to an NZP CSI-RS with no repetition parameter set and trs-Info set to true among CSI-RSs. Setting 3 in Table 16 can be used for aperiodic TRS.

[0186]

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

[0188]

[0189] Table 18 shows the valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, synonymous with CSI-RS for L1 RSRP reporting). The CSI-RS for BM refers to an NZP CSI-RS in which the repetition parameter is set to On or Off among CSI-RSs and trs-Info is not set to true.

[0190]

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

[0192]

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

[0194]

[0195] A representative QCL configuration method according to Tables 16 to 20 above is to operate by setting the target antenna port and reference antenna port for each step as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS." Through this, it is possible to link statistical characteristics that can be measured from SSB and TRS to each antenna port to assist the terminal's reception operation.

[0196] [PDCCH: TCI state related]

[0197] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in Table 21 below. The fourth row in Table 21 is the combination assumed by the terminal before RRC configuration, and configuration after RRC is not possible.

[0198]

[0199] NR supports a hierarchical signaling method as illustrated in FIG. 8 for dynamic allocation of PDCCH beams. Referring to FIG. 8, a base station can set N TCI states (805, 810, ..., 820) to a terminal through RRC signaling (800), and can set some of them as TCI states for CORESET (825). Thereafter, the base station can indicate one of the TCI states (830, 835, 840) for CORESET to the terminal through MAC CE signaling (845). Thereafter, the terminal receives the PDCCH based on beam information included in the TCI state indicated by the MAC CE signaling.

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

[0201] FIG. 10 is a diagram illustrating an example of beam configuration of a control resource set (CORESET) and a search space according to the above description. Referring to FIG. 10, a base station can indicate one of the TCI state lists included in the CORESET (1000) configuration through MAC CE signaling (1005). Thereafter, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal considers 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 a problem in that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also has a disadvantage in that the same beam is applied to all CORESETs regardless of the search space characteristics, which makes flexible PDCCH beam operation difficult. The embodiments of the present disclosure below provide a more flexible PDCCH beam configuration and operation method. In explaining embodiments of the present disclosure below, several distinct examples are provided for convenience of explanation, but these are not mutually exclusive and can be applied in appropriate combination depending on the situation.

[0202] A base station can set one or more TCI states for a specific control region to a terminal, and can 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 in control region #1, the base station can transmit a command to the terminal to activate TCI state#0 for control region #1 through MAC CE. Based on the activation command for the TCI state received through MAC CE, the terminal can correctly receive DMRS of the corresponding control region based on QCL information in the activated TCI state.

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

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

[0205] [PDCCH: QCL prioritization rule related]

[0206] Below, the QCL priority determination operation for PDCCH is described in detail.

[0207] When a terminal operates in a single cell or with carrier aggregation within a band, and multiple control resource sets existing within an activated bandwidth portion of a single or multiple cells have the same or different QCL-TypeD characteristics and overlap in time during a specific PDCCH monitoring interval, the terminal may select a specific control resource set according to a QCL priority determination operation and 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. In this case, the criteria for determining the QCL priority may be as follows.

[0208] - Criterion 1. A set of control resources connected to the common search section with the lowest index within the cell corresponding to the lowest index among the cells containing the common search section.

[0209] - Criterion 2. The control resource set associated with the terminal-specific search section with the lowest index within the cell corresponding to the lowest index among the cells containing the terminal-specific search section.

[0210] As described above, if the above criteria are not met, the following criteria are applied. For example, if control resource sets overlap in time in a specific PDCCH monitoring interval, and if all control resource sets are not connected to a common search interval but to a terminal-specific search interval, i.e., if criterion 1 is not met, the terminal may skip applying criterion 1 and apply criterion 2.

[0211] When a terminal selects a control resource set based on the above-described criteria, the terminal may additionally consider the following two items regarding the QCL information set in the control resource set. First, if control resource set 1 has CSI-RS 1 as a reference signal having a QCL-TypeD relationship, and the reference signal of this CSI-RS 1 having a QCL-TypeD relationship is SSB 1, and another control resource set 2 has a reference signal having a QCL-TypeD relationship that is SSB 1, the terminal may consider that these two control resource sets 1 and 2 have different QCL-TypeD characteristics. Second, if control resource set 1 has CSI-RS 1 set in cell 1 as a reference signal having a QCL-TypeD relationship, and the reference signal of this CSI-RS 1 having a QCL-TypeD relationship 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 of this CSI-RS 2 having a QCL-TypeD relationship is the same SSB 1, then the terminal can consider that the two control resource sets have the same QCL-TypeD characteristic.

[0212] FIG. 12 is a diagram for explaining a method for selecting a control resource set that can be received by a terminal in consideration of priorities when receiving a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. For example, the terminal may be configured to receive a plurality of control resource sets that overlap in time in a specific PDCCH monitoring period (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 period, a first control resource set (1215) connected to the first common search space may exist within a first bandwidth portion (1200) of a first cell, and a first control resource set (1220) connected to the first common search space and a second control resource set (1225) connected to the second terminal-specific search space may exist within a first bandwidth portion (1205) of a second cell. Control resource sets (1215) and (1220) may have a relationship of QCL-TypeD with the 1st CSI-RS resource set within the 1st bandwidth portion of the 1st cell, and control resource set (1225) may have a relationship of QCL-TypeD with the 1st CSI-RS resource set within the 1st bandwidth portion of the 2nd cell. Therefore, when criterion 1 is applied to the corresponding PDCCH monitoring section (1210), all other control resource sets having the same QCL-TypeD reference signal as the 1st control resource set (1215) can be received. Therefore, the terminal can receive control resource sets (1215) and (1220) in the corresponding PDCCH monitoring section (1210). As another example, a terminal may be configured to receive multiple control resource sets that overlap in time in a specific PDCCH monitoring interval (1240), and these multiple control resource sets may be associated with a common search space or a terminal-specific search space for multiple cells.Within the corresponding PDCCH monitoring section, within the first bandwidth portion (1230) of the first cell, there may exist a first control resource set (1245) connected to the first terminal-specific search section and a second control resource set (1250) connected to the second terminal-specific search section, and within the first bandwidth portion (1235) of the second cell, there may exist a first control resource set (1255) connected to the first terminal-specific search section and a second control resource set (1260) connected to the third terminal-specific search section. Control resource sets (1245) and (1250) have a relationship with the 1st CSI-RS resource set in the 1st bandwidth part of the 1st cell and QCL-TypeD, control resource set (1255) has a relationship with the 1st CSI-RS resource set in the 1st bandwidth part of the 2nd cell and QCL-TypeD, and control resource set (1260) can have a relationship with the 2nd CSI-RS resource set in the 1st bandwidth part of the 2nd cell 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 the same QCL-TypeD reference signal as the control resource set (1245) can be received. Accordingly, the terminal can receive control resource sets (1245) and (1250) in the corresponding PDCCH monitoring section (1240).

[0213] [Rate matching / Puncturing related]

[0214] Below, the rate matching operation and puncturing operation are described in detail.

[0215] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and reception operations of channel A considering resource C, an area in which resources A and B overlap. The specific operations may follow the contents below.

[0216] Rate Matching Operation

[0217] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that want to transmit symbol sequence A to the terminal. 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 can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0218] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and 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, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except for {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0219] Puncture action

[0220] If a base station wants to transmit symbol sequence A to a terminal, and there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps 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 for the remaining resource areas of resource A excluding resource C. 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 can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and 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 among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0221] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A 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 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 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 it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0222] Below, we describe a method for configuring rate-matching resources for the purpose of rate-matching in 5G communication systems. Rate-matching refers to adjusting the size of a signal based on the amount of resources available for transmission. For example, rate-matching a data channel may mean adjusting the size of data accordingly, without mapping the data channel to a specific time and frequency resource region.

[0223] Figure 11 is a diagram for explaining a method in which a base station and a terminal transmit and receive data by considering downlink data channels and rate matching resources.

[0224] FIG. 11 illustrates a downlink data channel (PDSCH, 1101) and a rate matching resource (1102). A base station can configure one or more rate matching resources (1102) to a terminal through upper layer signaling (e.g., RRC signaling). The rate matching resource (1102) configuration information can include time-domain resource allocation information (1103), frequency-domain resource allocation information (1104), and period information (1105). In the following, the bitmap corresponding to the frequency-domain resource allocation information (1104) is named "the first bitmap", the bitmap corresponding to the time-domain resource allocation information (1103) is named "the second bitmap", and the bitmap corresponding to the period information (1105) is named "the third bitmap". When all or part of the time and frequency resources of a scheduled data channel (1101) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (1101) 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.

[0225] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the "rate-matching indicator" in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as "1", and if rate matching is not required, it can be indicated as "0".

[0226] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following setting method can be followed.

[0227] RB symbol level

[0228] A terminal can set up to four RateMatchPatterns for each bandwidth section through upper layer signaling, and one RateMatchPattern can include the following contents.

[0229] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. 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 additionally be set.

[0230] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0231] RE level

[0232] The terminal can be configured with the following contents through upper layer signaling.

[0233] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0234] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0235] [Regarding LTE CRS rate match]

[0236] Next, the rate match process for the LTE CRS described above will be described in detail. In order to coexist between LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR provides a function to set a pattern of LTE's CRS (Cell Specific Reference Signal) to NR terminals. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter in the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the parameters can include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0237] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides a function that allows one CRS pattern to be set per serving cell. In Rel-16 NR, the function has been extended to allow multiple CRS patterns to be set per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can have one CRS pattern set per LTE carrier, and a multi-TRP configured terminal can have two CRS patterns set per LTE carrier. For example, a single-TRP configured terminal can have up to three CRS patterns set per serving cell through the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can have CRS set per TRP. That is, the CRS pattern for TRP1 can be 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 set as above, whether both the CRS patterns of TRP1 and TRP2 or only the CRS pattern for one TRP is applied to a specific PDSCH (Physical Downlink Shared Channel) 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, and in other cases, the CRS patterns of both TRPs are applied.

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

[0239]

[0240]

[0241]

[0242] [PDSCH: Processing Time]

[0243] Next, the PDSCH processing procedure time (PDSCH processing procedure time) will be described. When a base station schedules a UE to transmit a PDSCH using DCI format 1_0, 1_1, or 1_2, the UE may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated through the DCI (modulation and coding instruction index (MCS), demodulation reference signal-related information, time and frequency resource allocation information, etc.). NR takes this into account and defines the PDSCH processing time. The PDSCH processing time of the UE can follow the following [Mathematical Formula 2].

[0244]

[0245] T as described in mathematical formula 2 proc,1 In , each variable can have the following meanings:

[0246] - N1: The number of symbols determined by the UE processing capability 1 or 2 and the numerology μ according to the capability of the terminal. If the UE processing capability is reported as 1 according to the capability report of the terminal, it may have the value of [Table 24], and if the UE processing capability is reported as 2 and the availability of the UE processing capability 2 is set through upper layer signaling, it may have the value of [Table 25]. The numerology μ is determined by the T proc,1 to maximize μ PDCCH , μ PDSCH, μ UL It can correspond to the minimum value of μ PDCCH , μ PDSCH, μ UL Each may mean the numerology of the PDCCH that schedules the PDSCH, the numerology of the scheduled PDSCH, and the numerology of the uplink channel on which the HARQ-ACK is to be transmitted.

[0247]

[0248]

[0249] - : 64

[0250] - 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.

[0251] - If l1 indicating the PDSCH DMRS location value is 12, N1,0 in the above [Table x2-2] has a value of 14, otherwise it has a value of 13.

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

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

[0254] - If PDSCH mapping type B is used for terminal processing capability 1, d 1,1 The value can be determined based on the number of symbols L of the scheduled PDSCH and the number d of overlapping symbols between the PDCCH that schedules the PDSCH and the scheduled PDSCH.

[0255] - d if L ≥ 7 1,1 = 0.

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

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

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

[0259] - If PDSCH mapping type B is used for terminal processing capability 2, d 1,1 The value can be determined based on the number of symbols L of the scheduled PDSCH and the number d of overlapping symbols between the PDCCH that schedules the PDSCH and the scheduled PDSCH.

[0260] - d if L ≥ 7 1,1 = 0.

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

[0262] - If L = 2,

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

[0264] - If not, d 1,1 = d.

[0265] - For a terminal supporting capability 2 within a given serving cell, the PDSCH processing time according to terminal processing capability 2 can be applied when the terminal sets processingType2Enabled, which is an upper layer signaling for the cell, to enable.

[0266] If the position of the first uplink transmission symbol of PUCCH containing HARQ-ACK information (the position may be considered K1, which is defined as the transmission time of HARQ-ACK, PUCCH resources used for HARQ-ACK transmission, and timing advance effect) is T after the last symbol of PDSCH proc,1 If the first uplink transmission symbol that appears after a time period of T is not started, the terminal must transmit a valid HARQ-ACK message. That is, the terminal must transmit a PUCCH containing a HARQ-ACK only when there is sufficient PDSCH processing time. Otherwise, the terminal cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. The above T proc,1 can be used for both general and extended CP cases. In case of PDSCH with two PDSCH transmission locations within one slot, d 1,1 is calculated based on the first PDSCH transmission position within the slot.

[0267] [PDSCH: Reception Preparation Time during Cross-Carrier Scheduling]

[0268] Next, the numerology μ in which the scheduled PDCCH is transmitted PDCCH μ, which is the numerology through which the PDSCH scheduled through the corresponding PDCCH is transmitted. PDSCH In case of different cross-carrier scheduling, N is the PDSCH reception preparation time of the terminal defined for the time interval between the PDCCH and the PDSCH. pdsch Explains about.

[0269] 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 that follows the symbol. The transmission symbol of the corresponding PDSCH may include a DM-RS.

[0270] 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 from the symbol onwards. The transmission symbol of the corresponding PDSCH can include DM-RS.

[0271]

[0272] [SRS related]

[0273] Next, we describe an uplink channel estimation method using the Sounding Reference Signal (SRS) transmission of a terminal. The base station can configure at least one SRS configuration for each uplink BWP to convey configuration information for SRS transmission to the terminal, and can also configure at least one SRS resource set for each SRS configuration. For example, the base station and the terminal can exchange the following upper-level signaling information to convey information regarding the SRS resource set.

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

[0275] - srs-ResourceIdList: A set of SRS resource indices referenced in the SRS resource set.

[0276] - resourceType: This is the time axis transmission setting of the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information can be provided depending on the usage of the SRS resource set. If set to 'aperiodic', an aperiodic SRS resource trigger list and slot offset information can be provided, and associated CSI-RS information can be provided depending on the usage of the SRS resource set.

[0277] - usage: This is a setting for the usage of the SRS resource referenced in the SRS resource set, and can be set to one of 'beamManagement', 'codebook', 'nonCodebook', and 'antennaSwitching'.

[0278] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for adjusting the transmission power of the SRS resource referenced in the SRS resource set.

[0279] The terminal can understand that the SRS resource included in the set of SRS resource indices referenced in the SRS resource set follows the information set in the SRS resource set.

[0280] In addition, the base station and the terminal can transmit and receive upper layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource can include time-frequency axis mapping information within the slot of the SRS resource, which can include information about frequency hopping within the slot or between slots of the SRS resource. In addition, the individual configuration information for the SRS resource can include the time axis transmission configuration of the SRS resource, which can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. This can be restricted to have the same time axis transmission configuration as the SRS resource set including the SRS resource. If the time axis transmission configuration of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) can additionally be included in the time axis transmission configuration.

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

[0282] For example, a base station can activate or deactivate semi-persistent SRS transmission to a terminal through upper layer signaling. The base station can instruct the terminal to activate an SRS resource set through MAC CE signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. The SRS resource set activated through MAC CE signaling can be limited to an SRS resource set with resourceType set to semi-persistent. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource, and the slot mapping including the transmission period and slot offset follows the periodicityAndOffset configured in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or the associated CSI-RS information configured in the SRS resource set that includes the SRS resource. If spatial relation info is configured in an SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information for spatial relation info transmitted through MAC CE signaling that activates semi-persistent SRS transmission without following it. The terminal can transmit SRS resources within the activated uplink BWP for the semi-persistent SRS resource activated through upper layer signaling.

[0283] For example, a base station can trigger aperiodic SRS transmission to a terminal via 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 can understand that an SRS resource set including the aperiodic SRS resource trigger indicated via DCI in the aperiodic SRS resource trigger list among the configuration information of the SRS resource set has been triggered. The terminal can transmit an SRS resource referenced in the triggered SRS resource set. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource. In addition, the slot mapping of the transmitted SRS resource can be determined through a slot offset between a PDCCH including the DCI and the SRS resource, which can refer to value(s) included in a slot offset set configured in the SRS resource set. Specifically, the slot offset between the PDCCH including DCI and the SRS resource can be applied by applying the value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or can refer to the associated CSI-RS information configured in the SRS resource set including the SRS resource. The UE can transmit the SRS resource within the activated uplink BWP for the aperiodic SRS resource triggered through the DCI.

[0284] When a base station triggers aperiodic SRS transmission to a terminal through DCI, a minimum time interval may be required between a PDCCH including the DCI that triggers aperiodic SRS transmission and the SRS to be transmitted, so that the terminal can transmit the SRS by applying configuration information for the SRS resource. The time interval for SRS transmission of the terminal can be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers aperiodic SRS transmission and the first symbol to which the first SRS resource to be transmitted among the SRS resource(s) is mapped. The minimum time interval can be determined with reference to the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. In addition, the minimum time interval can have different values ​​depending on the usage of the SRS resource set including the SRS resource to be transmitted. For example, the minimum time interval can be determined as N2 symbols, which are defined by considering the terminal processing ability according to the capability of the terminal with reference to the PUSCH preparation procedure time of the terminal. In addition, considering the usage of the SRS resource set including the SRS resource being transmitted, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal may transmit an aperiodic SRS if the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, and may ignore the DCI that triggers the aperiodic SRS if the time interval for aperiodic SRS transmission is less than the minimum time interval.

[0285]

[0286] The spatialRelationInfo setting information in [Table 24] above refers to a single reference signal and applies the beam information of the reference signal to the beam used for the corresponding SRS transmission. For example, the spatialRelationInfo setting may include information such as [Table 28] below.

[0287]

[0288] Referring to the above spatialRelationInfo setting, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal, i.e., the SS / PBCH block index, CSI-RS index, or SRS index can be set. The upper signaling referenceSignal is setting information indicating which beam information of which reference signal is to be referenced for the corresponding SRS transmission, ssb-Index means the index of the SS / PBCH block, csi-RS-Index means the index of the CSI-RS, and srs means the index of the SRS, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the reception beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the reception beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used when transmitting the SRS corresponding to the srs as the transmission beam for the corresponding SRS transmission.

[0289] [PUSCH: Transmission Method Related]

[0290] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

[0291] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 29] through higher-level signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 29] through higher-level signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-level signaling of [Table 29], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 29]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 29], the terminal applies tp-pi2BPSK in pusch-Config of [Table 29] to PUSCH transmission operated by the configured grant.

[0292]

[0293]

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

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

[0296]

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

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

[0299] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0300] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

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

[0302] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0303] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can 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 UE is less than 42 symbols, the UE does not expect information about the precoder for SRS transmission to be updated.

[0304] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence 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'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0305] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS in the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS in the upper-level signaling SRS-ResourceSet to be configured together.

[0306] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or can be configured through the upper signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the UE is provided with an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

[0307] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0308] [PUSCH: Preparation time]

[0309] Next, the PUSCH preparation procedure time is described. When the base station schedules a UE to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method indicated through the DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). NR takes this into account and defines the PUSCH preparation procedure time. The PUSCH preparation procedure time of the UE can follow the following [Mathematical Formula 3].

[0310]

[0311] T as described in mathematical formula 3 proc,2 In , each variable can have the following meanings:

[0312] - N2: The number of symbols determined by the UE processing capability (UE processing capability) 1 or 2 and the numerology μ according to the UE's capability. If UE processing capability 1 is reported according to the UE's capability report, it has the value of [Table 31]. If UE processing capability 2 is reported and the availability of UE processing capability 2 is set through upper layer signaling, it can have the value of [Table 32].

[0313]

[0314]

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

[0316] - : 64

[0317] - μ: or Medium, T proc,2 This follows the larger value. refers to the numerology of the downlink in which the PDCCH containing the DCI for scheduling the PUSCH is transmitted, It refers to the numerology of the uplink in which PUSCH is transmitted.

[0318] - T c : has

[0319] - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it has 0.

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

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

[0322] - 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.

[0323] When the base station and the terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, the base station and the terminal determine T from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2If the first symbol of the PUSCH begins before the first uplink symbol of the CP, the PUSCH preparation time is determined to be insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the PUSCH preparation time is insufficient.

[0324] [PUSCH: Repetitive Transmission Related]

[0325] The following describes in detail the repetitive transmission of uplink data channels in 5G systems. 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 be configured with either PUSCH repetitive transmission type A or B via upper layer signaling.

[0326] PUSCH repetitive transmission type A

[0327] - As described above, the symbol length and the position of the start symbol of the uplink data channel are determined by the time domain resource allocation method within one 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).

[0328] - The terminal can repeatedly transmit an uplink data channel with the same length and start symbol as the uplink data channel set based on the number of repeated transmissions received from the base station in consecutive slots. In this case, if at least one symbol among the slots set by the base station to the terminal as downlink or the symbols of the uplink data channel set to the terminal is set as downlink, the terminal skips the uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel.

[0329] PUSCH repetitive transmission type B

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

[0331] - First, the nominal repetition of the uplink data channel is determined based on the start symbol and length of the established uplink data channel as follows. The slot where the nth nominal repetition starts is The symbol given by and starting from that slot is is given by . The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is is given by . Here, n=0,..., numberofrepetitions-1, S represents the start symbol of the established uplink data channel, and L represents the symbol length of the established uplink data channel. indicates the slot in which the PUSCH transmission starts. Indicates the number of symbols per slot.

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

[0333] After determining invalid symbols, the terminal may consider symbols other than invalid symbols as valid symbols for each nominal repetition. If each nominal repetition includes at least one valid symbol, the nominal repetition may include one or more actual repetitions. Here, each actual repetition includes a contiguous set of valid symbols that can be used for PUSCH repetitive transmission type B within a single slot.

[0334] FIG. 14 is a diagram illustrating an example of PUSCH repetitive transmission type B in a wireless communication system according to an embodiment of the present disclosure. A terminal may set the start symbol S of an uplink data channel to 0, the length L of the uplink data channel to 14, and the number of repetitive transmissions to 16. In this case, the nominal repetition is indicated in 16 consecutive slots (1401). Thereafter, the terminal may determine that a symbol set as a downlink symbol in each nominal repetition (1401) is an invalid symbol. In addition, the terminal determines that symbols set to 1 in the invalid symbol pattern (1402) are invalid symbols. If valid symbols that are not invalid symbols in each nominal repetition consist of one or more consecutive symbols in one slot, they are set as an actual repetition and transmitted (1403).

[0335] Additionally, for PUSCH repetitive transmissions, NR Release 16 can define the following additional methods for UL grant-based PUSCH transmissions across slot boundaries and configured grant-based PUSCH transmissions:

[0336] - Method 1 (mini-slot level repetition): Two or more PUSCH repetitive transmissions are scheduled within a slot or across the boundaries of consecutive slots through a single UL grant. In addition, for Method 1, the time-domain resource allocation information in the DCI indicates the resources of the first repetitive transmission. In addition, the time-domain resource information of the first repetitive transmission and the time-domain resource information of the remaining repetitive transmissions can be determined based on the uplink or downlink direction determined for each symbol in each slot. Each repetitive transmission occupies consecutive symbols.

[0337] - Method 2 (multi-segment transmission): Two or more repeated PUSCH transmissions are scheduled in consecutive slots through a single UL grant. At this time, one transmission is designated for each slot, and each transmission may have a different starting point or repetition length. In addition, in Method 2, the time-domain resource allocation information in the DCI indicates the starting point and repetition length of all repeated transmissions. In addition, when performing repeated transmissions in a single slot through Method 2, if there are multiple sets of consecutive uplink symbols in the slot, each repeated transmission is performed for each set of uplink symbols. If there is only one set of consecutive uplink symbols in the slot, one repeated PUSCH transmission is performed according to the method of NR Release 15.

[0338] - Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive slots via two or more UL grants. In this case, one transmission is designated for each slot, and the nth UL grant can be received before the PUSCH transmission scheduled for the n-1th UL grant ends.

[0339] - Method 4: One or more PUSCH repetitive transmissions within a single slot, or two or more PUSCH repetitive transmissions across the boundaries of consecutive slots, can be supported through one UL grant or one configured grant. The number of repetitions indicated by the base station to the terminal is only a nominal value, and the number of PUSCH repetitive transmissions actually performed by the terminal may be greater than the nominal number of repetitions. The time-domain resource allocation information in the DCI or the configured grant indicates the resources of the first repetitive transmission indicated by the base station. The time-domain resource information of the remaining repetitive transmissions can be determined by referring to at least the resource information of the first repetitive transmission and the uplink or downlink direction of the symbols. If the time-domain resource information of the repetitive transmission indicated by the base station crosses a slot boundary or includes an uplink / downlink switchover point, the repetitive transmission can be divided into multiple repetitive transmissions. In this case, one repetitive transmission can be included for each uplink period within one slot.

[0340] The above-described repetitive transmission can be applied to both DG (Dynamic Grant) PUSCH and CG (Configured Grant) PUSCH. DG PUSCH is a method in which all PUSCH scheduling information is provided by DCI, and CG PUSCH means a method in which PUSCH scheduling information is provided only by higher-order signals or by some DCI. In addition, DG PUSCH is a method in which a terminal transmits PUSCH only in the scheduling region provided by DCI, and CG PUSCH is a method in which a terminal periodically transmits PUSCH without receiving a separate DCI according to a period set by a higher-order signal.

[0341] [PUSCH: Frequency Hopping Process]

[0342] Below, we specifically describe frequency hopping of the uplink data channel (Physical Uplink Shared Channel; PUSCH) in a 5G system.

[0343] In 5G, two methods are supported for frequency hopping of uplink data channels for each PUSCH repetition transmission type. First, PUSCH repetition transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, while PUSCH repetition transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

[0344] The intra-slot frequency hopping method supported by PUSCH repetitive transmission type A is a method in which a terminal transmits by changing the allocated frequency domain resources by a set frequency offset in two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be expressed using mathematical equation 4.

[0345]

[0346] In Equation 4, i=0 and i=1 represent the first hop and the second hop, respectively. Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. The upper layer parameter indicates the frequency offset between two hops. The number of symbols in the first hop is can be represented as , and the number of symbols in the second hop is can be expressed as is the length of PUSCH transmission within one slot, expressed as the number of OFDM symbols.

[0347] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal changes the allocated resources of the frequency domain by a set frequency offset for each slot and transmits them. In inter-slot frequency hopping, The starting RB during a slot can be expressed by Equation 5.

[0348]

[0349] In mathematical equation 5, is the current slot number in multi-slot PUSCH transmission, Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. Indicates the frequency offset between two hops through upper layer parameters.

[0350] Next, the inter-repetition frequency hopping method supported by PUSCH repetitive transmission type B is to transmit the allocated resources in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. RB is the index of the starting RB in the frequency domain for one or more actual repetitions within the nth nominal repetition. start (n) can follow the following mathematical formula 6.

[0351]

[0352] In mathematical expression 6, n is the index of nominal repetition, Indicates the RB offset between two hops via upper layer parameters.

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

[0354] Hereinafter, a method for measuring and reporting a channel state in a 5G communication system will be described in detail. Channel state information (CSI) may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), and / or L1-RSRP (Reference Signal Received Power). A base station may control time and frequency resources for the aforementioned CSI measurement and reporting of a terminal.

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

[0356]

[0357]

[0358]

[0359]

[0360]

[0361]

[0362]

[0363]

[0364]

[0365]

[0366]

[0367]

[0368]

[0369] For the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with one downlink (DL) bandwidth part identified by the upper layer parameter bandwidth part identifier (bwp-id) given by the CSI resource setting, CSI-ResourceConfig, associated with the corresponding report setting. For the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, which can be configured from the base station to the terminal by the reportConfigType parameter configured from the upper layer. The semi-persistent CSI reporting method supports 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. For periodic or semi-permanent CSI reporting methods, the UE can receive PUCCH or PUSCH resources for transmitting CSI from the base station through higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources for transmitting CSI can be given as numerology of the uplink (UL) bandwidth portion configured for CSI report transmission. For aperiodic CSI reporting methods, the UE can receive scheduling of PUSCH resources for transmitting CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

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

[0371] - CSI-IM resources for interference measurements

[0372] - NZP CSI-RS resources for interference measurements

[0373] - NZP CSI-RS resources for channel measurements

[0374] For CSI-RS resource sets associated with resource settings where the upper layer parameter resourceType is set to 'aperiodic', 'periodic', or 'semi-persistent', the trigger state for the CSI report setting where reportType is set to 'aperiodic' and the resource settings for channel or interference measurements for one or more component cells (CCs) can be set with the upper layer parameter CSI-AperiodicTriggerStateList.

[0375] Aperiodic CSI reporting of a terminal can utilize PUSCH, periodic CSI reporting can utilize PUCCH, and semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or PUCCH after activation by MAC control element (MAC CE). As mentioned above, CSI resource settings can also be configured as aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 40] below.

[0376]

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

[0378] - If all bits in the CSI request field are 0, this may mean that no CSI report is requested.

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

[0380] - 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 can be indicated by the CSI request field.

[0381] [Table 41] below shows an example of the relationship between a CSI request indicator and the CSI trigger state that can be indicated by the indicator.

[0382]

[0383] A terminal may perform measurement on a CSI resource within a CSI trigger state triggered by a CSI request field, and may generate CSI (including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) therefrom. The terminal may transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. If 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 ​​indicates "1", uplink data (UL-SCH) and the acquired CSI may be multiplexed and transmitted on the PUSCH resource scheduled by the DCI format 0_1. If 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", only CSI can be mapped and transmitted without uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0384] Figure 13 is a diagram illustrating an example of an aperiodic CSI reporting method.

[0385] In an example (1300) of FIG. 13, the terminal can monitor the PDCCH (1301) to obtain DCI format 0_1, from which scheduling information and CSI request information for the PUSCH (1305) can be obtained. The terminal can obtain resource information for the CSI-RS (1302) to be measured from the received CSI request indicator. The terminal can determine when to perform measurement on the transmitted CSI-RS (1302) resource based on the time point of receiving DCI format 0_1 ​​and the parameter (aperiodicTriggeringOffset described above) for the offset in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the terminal can receive an offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station through upper layer signaling, and the set offset value X can mean an offset between a slot in which a DCI that triggers aperiodic CSI reporting is received and a slot in which a CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have a mapping relationship described in [Table 42] below.

[0386]

[0387] An example (1300) of Fig. 13 shows an example in which the aforementioned offset value is set to X=0. In this case, the terminal can receive a CSI-RS (1302) in a slot (corresponding to slot 0 (1306) of Fig. 13) in which DCI format 0_1 ​​that triggers aperiodic CSI reporting is received, and can report CSI information measured with the received CSI-RS to the base station via PUSCH (1305). The terminal can obtain scheduling information (information corresponding to each field of the aforementioned DCI format 0_1) for the PUSCH (1305) for CSI reporting from the DCI format 0_1. As an example, the terminal can obtain information on a slot in which the PUSCH (1305) is to be transmitted from the aforementioned time domain resource allocation information for the PUSCH (1305) in the DCI format 0_1. In an example (1300) of FIG. 13, the terminal acquires a K2 value corresponding to a slot offset value for PDCCH-to-PUSCH as 3, and accordingly, the PUSCH (1305) can be transmitted in slot 3 (1309), which is 3 slots away from slot 0 (1306), at the time when the PDCCH (1301) is received.

[0388] In an example (1310) of FIG. 13, the terminal can monitor the PDCCH (1311) to obtain DCI format 0_1, and from this, can obtain scheduling information and CSI request information for the PUSCH (1315). The terminal can obtain resource information for the CSI-RS (1312) to be measured from the received CSI request indicator. An example (1310) of FIG. 13 shows an example 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 a slot in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received (corresponding to slot 0 (1316) of FIG. 13), and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (1315).

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

[0390]

[0391]

[0392] In particular, in the case of PUSCH repetition transmission methods A and B, the UE can transmit the aperiodic CSI report by multiplexing it only in the first repetition transmission among the PUSCH repetition transmissions. This is because the aperiodic CSI report information to be multiplexed is encoded in a polar code manner, and in this case, in order to be multiplexed in multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, so the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition.

[0393] In addition, for PUSCH repetition transmission scheme B, if the UE schedules aperiodic CSI reporting without scheduling a transport block or receives a DCI activating semi-persistent CSI reporting, the nominal repetition value may be assumed to be 1 even if the number of PUSCH repetition transmissions configured by upper layer signaling is greater than 1. In addition, if the UE schedules or activates aperiodic or semi-persistent CSI reporting without scheduling a transport block based on PUSCH repetition transmission scheme B, the UE may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including semi-persistent CSI based on PUSCH repetition transmission scheme B without scheduling a DCI after semi-persistent CSI reporting is activated by DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0394] [Regarding terminal capability reporting]

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

[0396] A base station can transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station, or the base station can include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can compose a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, a UE capability request can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). Additionally, the terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but the base station may request it under any conditions when necessary.

[0397] In the above step, the terminal that receives the UE capability report request from the base station configures the terminal capability based on the RAT type and band information requested from the base station. Below is a summary of how the terminal configures the UE capability in the NR system.

[0398] 1. If the UE receives a list of LTE and / or NR bands through a UE capability request from the base station, the UE configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it configures a candidate list of BCs for EN-DC and NR SA based on the bands requested to the base station via FreqBandList. Furthermore, the bands are prioritized in the order listed in FreqBandList.

[0399] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the UE completely removes NR SA BCs from the configured BC candidate list. This operation can only occur when the LTE base station (eNB) requests the "eutra" capability.

[0400] 3. The terminal then removes fallback BCs from the BC candidate list constructed in the above step. Here, a fallback BC is a BC obtained by removing at least one band corresponding to an SCell from a random BC. This step can be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step also applies to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list."

[0401] 4. The terminal selects BCs to report by selecting BCs that match the requested RAT type from the final "candidate BC list" above. In this step, the terminal constructs the supportedBandCombinationList in a set order. That is, the terminal constructs BCs and UE capabilities to report in the order of the preset rat-Type (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0402] 5. Also, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set is included only in UE-NR-Capabilities.

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

[0404] [CA / DC related]

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

[0406] Referring to FIG. 15, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol 1525, 1570), NR PDCP (Packet Data Convergence Protocol 1530, 1565), NR RLC (Radio Link Control 1535, 1560), and NR MAC (Medium Access Control 1540, 1555) in the terminal and NR base station, respectively.

[0407] Key features of NR SDAP (1525, 1570) may include some of the following:

[0408] - Transfer of user plane data

[0409] - Mapping function between QoS flow and data bearer for both DL and UL

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

[0411] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0412] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

[0413] The main functions of NR PDCP (1530, 1565) may include some of the following functions:

[0414] - Header compression and decompression (ROHC only)

[0415] - User data transfer function

[0416] - In-sequence delivery of upper layer PDUs

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

[0418] - PDCP PDU reordering for reception

[0419] - Duplicate detection of lower layer SDUs

[0420] - Retransmission function (Retransmission of PDCP SDUs)

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

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

[0423] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0424] The main functions of NR RLC (1535, 1560) may include some of the following functions:

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

[0426] - In-sequence delivery of upper layer PDUs

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

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

[0429] - Concatenation, segmentation and reassembly of RLC SDUs

[0430] - Re-segmentation of RLC data PDUs

[0431] - Reordering of RLC data PDUs

[0432] - Duplicate detection function

[0433] - Protocol error detection

[0434] - RLC SDU discard function

[0435] - RLC re-establishment function

[0436] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the 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 an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0437] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0438] NR MAC (1540, 1555) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

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

[0440] - Multiplexing / demultiplexing of MAC SDUs

[0441] - Scheduling information reporting function

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

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

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

[0445] - MBMS service identification function

[0446] - Transport format selection function

[0447] - Padding function

[0448] The NR PHY layer (1545, 1550) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols, and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0449] The above wireless protocol structure can have various detailed structures 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 use a protocol structure that has a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

[0450] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support PDCCH repetitive transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for repetitively transmitting PDCCHs through multiple transmission points (TRPs) to improve PDCCH reception reliability at a terminal. Specific methods are described in detail in the following examples.

[0451] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0452] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, the case where the terminal receives the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.

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

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

[0455] [NC-JT related]

[0456] According to one embodiment of the present disclosure, Non-Coherent Joint Transmission (NC-JT) may be used for a terminal to receive PDSCH from multiple TRPs.

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

[0458] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication, which increases the signal strength or processing rate received by a terminal by transmitting a signal to a single terminal through a number of different cells, TRPs, or / and beams. At this time, the channel between each cell, TRP, or / and beam and the terminal may have significantly different characteristics, and in particular, in the case of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP, or / and beam, individual precoding, MCS, resource allocation, TCI indication, etc. may be required depending on the channel characteristics of each link between each cell, TRP, or / and beam and the terminal.

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

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

[0461] Referring to FIG. 16, examples for PDSCH transmission are explained for each technique of joint transmission (JT), and examples for allocating radio resources for each TRP are shown.

[0462] Referring to FIG. 16, an example (N000) for coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP or / and beam is illustrated.

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

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

[0465] In the case of NC-JT, PDSCH is transmitted to the terminal (N035) for each cell, TRP or / and beam, and individual precoding can be applied to each PDSCH. Each cell, TRP or / and beam transmits a different PDSCH or a different PDSCH layer to the terminal, thereby improving the throughput compared to single cell, TRP or / and beam transmission. In addition, each cell, TRP or / and beam repeatedly transmits the same PDSCH to the terminal, thereby improving the reliability compared to single cell, TRP or / and beam transmission. For convenience of explanation, cells, TRPs or / and beams are collectively referred to as TRPs hereinafter.

[0466] At this time, various radio resource allocations can 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).

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

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

[0469] Referring to FIG. 17, case #1 (N100) is an example in which, in addition to the serving TRP (TRP#0) used for single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently from the control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain control information for 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, and the payloads between the DCIs may also be the same or different. In the aforementioned case #1, each PDSCH control or allocation freedom can be fully guaranteed, but if each DCI is transmitted in different TRPs, coverage differences may occur for each DCI, which may deteriorate reception performance.

[0470] Case #2 (N105) shows an example 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 single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted respectively, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0471] For example, in the case of DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), it includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but in the case of shortened DCI (hereinafter, sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it 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, which transmits control information for PDSCHs transmitted from cooperative TRPs, since the payload is smaller than that of normal DCI (nDCI), which transmits PDSCH-related control information transmitted from a serving TRP, it is possible to include reserved bits compared to nDCI.

[0472] In the aforementioned case #2, the degree of freedom in controlling or allocating each PDSCH may be limited depending on the content of the information elements included in sDCI, but since the reception performance of sDCI is superior to that of nDCI, the probability of a difference in coverage by DCI may be reduced.

[0473] Case #3 (N110) shows an example 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 single PDSCH transmission, one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0474] For example, in the case of DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), it includes 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 only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into one 'secondary' DCI (sDCI) and transmit them. For example, the sDCI may include at least one piece of information among HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs. In addition, for information not included in sDCI, such as BWP (bandwidth part) indicator or carrier indicator, the DCI (DCI#0, normal DCI, nDCI) of serving TRP can be followed.

[0475] Case #3 (N110) may limit the degree of freedom in controlling or allocating each PDSCH depending on the content of the information element included in sDCI, but it is possible to control the reception performance of sDCI and the complexity of blind decoding of DCI of the terminal may be reduced compared to case #1 (N100) or case #2 (N105).

[0476] Case #4 (N115) is an example of transmitting control information for PDSCHs transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for single PDSCH transmission in the same DCI (Long DCI) as the control information for PDSCHs transmitted from the serving TRP. That is, the UE can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4 (N115), the complexity of DCI blind decoding of the UE may not increase, but the number of cooperative TRPs may be limited due to the long DCI payload limitation, and thus the degree of freedom in PDSCH control or allocation may be low.

[0477] In the following description and examples, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI format 1_0 to 1_1 described above) containing PDSCH control information transmitted in a cooperative TRP, and unless a special limitation is specified, the description is similarly applicable to the various auxiliary DCIs described above.

[0478] In the following description and examples, the aforementioned cases #1 (N100), #2 (N105), and #3 (N110), in which more than one DCI (PDCCH) is 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 PDSCH 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 DCI of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. As a method for distinguishing the CORESETs, there may be a method for distinguishing through an upper layer indicator for each CORESET, a method for distinguishing through beam setting for each CORESET, etc. Additionally, in single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH with multiple layers is scheduled, and the multiple layers described above can be transmitted from multiple TRPs. In this case, the connection relationship between a layer and the TRP transmitting the layer can be indicated through a Transmission Configuration Indicator (TCI) indication for the layer.

[0479] 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.

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

[0481] The wireless protocol architecture for NC-JT in the present disclosure 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 (CA-like method) similar to S10 of FIG. 15 is possible. On the other hand, when the backhaul delay between cooperative TRPs is so large that it cannot be ignored (for example, when more than 2 ms is required for information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method (DC-like method) is possible to secure delay-robust characteristics by using an independent structure for each TRP starting from the RLC layer, similar to S20 of FIG. 15.

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

[0483] [Multi-DCI based Multi-TRP]

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

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

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

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

[0488] * CORESET Beam / Beam Group Configuration: The TRP corresponding to the CORESET can be distinguished through the beam or beam group configured for each CORESET. For example, if the same TCI state is set for multiple CORESETs, the CORESETs can be considered to be transmitted through the same TRP, or the PDCCH that schedules the PDSCH of the same TRP can be considered to be transmitted in the CORESET.

[0489] * Search space beam / beam group configuration: A beam or beam group is configured for each search space, and this allows TRPs for each search space to be distinguished. For example, if the same beam / beam group or TCI state is set for multiple search spaces, it can be considered that the same TRP transmits a PDCCH in the corresponding search space, or that a PDCCH that schedules the PDSCH of the same TRP is transmitted in the corresponding search space.

[0490] By dividing the CORESET or search space by TRP as described above, PDSCH and HARQ-ACK information classification for each TRP is possible, and this enables independent HARQ-ACK codebook generation and independent PUCCH resource use for each TRP.

[0491] The above settings can be independent for each cell or BWP. For example, a PCell may have two different CORESETPoolIndex values, while a specific SCell may not have a CORESETPoolIndex value set. In this case, it can be assumed that NC-JT transmission is configured for the PCell, while NC-JT transmission is not configured for the SCell without the CORESETPoolIndex value set.

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

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

[0494] In single PDCCH-based NC-JT, PDSCHs transmitted by multiple TRPs can be scheduled with a single DCI. At this time, the number of TCI states can be used as a method of indicating the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is two, it can be considered as a single PDCCH-based NC-JT transmission, and if the number of TCI states is one, it can be considered as a single-TRP transmission. The TCI states indicated in the above DCI can correspond to one or both of 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 this can be the case when there are two TCI states activated by MAC-CE corresponding to the above TCI codepoint.

[0495] The above configuration can be independent on a per-cell or per-BWP basis. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, while a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, it can be assumed that NC-JT transmission is configured on the PCell, while NC-JT transmission is not configured on the aforementioned SCell.

[0496] [PHR]

[0497] Figure 18 illustrates a procedure for a base station to control the transmission power of a terminal in a cellular system. In step 18-10 of Figure 18, a terminal within the coverage of the base station can perform downlink synchronization with the base station and acquire system information. In some embodiments, downlink synchronization can be achieved through a synchronization signal PSS / SSS (Primary Synchronization Signal / Secondary Synchronization Signal) received from the base station. Terminals that have performed downlink synchronization can receive a Master Information Block (MIB) and a System Information Block (SIB) from the base station and acquire system information. In step 18-15, the terminal can perform uplink synchronization with the base station through a random access procedure and establish an RRC (Raido Resource Control) connection. In the random access procedure, the terminal can transmit a random access preamble and message 3 (msg3) to the base station through the uplink. At this time, uplink transmission power can be controlled during transmission of the random access preamble and message 3. Specifically, the terminal can receive parameters for uplink transmission power control from the base station through acquired system information, for example, SIB, or can control the uplink transmission power using promised parameters. In another embodiment of the present disclosure, the terminal can measure the RSRP (Reference Signal Received Power) from the path attenuation estimation signal transmitted by the base station and estimate the downlink path attenuation value as in [Mathematical Formula 7]. Then, the terminal can set the uplink transmission power value for transmitting the random access preamble and message 3 based on the estimated path attenuation value.

[0498] [Equation 7]

[0499] Downlink path loss = base station signal transmission power - RSRP measured by terminal

[0500] In [Mathematical Formula 7], the transmission power of the base station signal refers to the transmission power of the downlink path attenuation estimation signal transmitted by the base station. The downlink path attenuation estimation signal transmitted by the base station may be a Cell-specific Reference Signal (CRS) or a Synchronization Signal Block (SSB). If the path attenuation estimation signal is a Cell-specific Reference Signal (CRS), the transmission power of the base station signal refers to the transmission power of the CRS, and can be transmitted to the terminal through the referenceSignalPower parameter of the system information. If the path attenuation estimation signal is a Synchronization Signal Block (SSB), the transmission power of the base station signal refers to the transmission power of the Secondary Synchronization Signal (SSS) and the Demodulation Reference Signal (DMRS) transmitted on the PBCH, and can be transmitted to the terminal through the ss-PBCH-BlockPower parameter of the system information. In steps 18-20, the UE may receive RRC parameters for uplink transmission power control from the base station through UE-specific RRC or common RRC. The received transmission power control parameters may differ depending on the type of uplink channel and signal transmitted in the uplink. That is, the transmission power control parameters applied to transmission of the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), and the sounding reference signal (SRS) may differ from each other.In addition, as described above, the transmission power control parameters that the terminal receives from the base station through SIB before the RRC connection is established or the transmission power control parameters that the terminal used as pre-agreed values ​​before the RRC connection is established may be included in the RRC parameters transmitted from the base station after the RRC connection is established. The terminal may use the RRC parameter values ​​received from the base station after the RRC connection is established for uplink transmission power control. In steps 18-25, the terminal may receive a path loss estimation signal from the base station. More specifically, the base station may configure a CSI-RS (Channel State Information-Reference Signal) as the path loss estimation signal of the terminal after the RRC connection is established of the terminal. In this case, the base station may transmit information about the transmission power of the CSI-RS to the terminal through the powerControlOffsetSS parameter of the UE dedicated RRC information. In this case, the powerControlOffsetSS may mean a difference (offset) in the transmission power of the SSB and the CSI-RS. In steps 18-30, the terminal can estimate a downlink path attenuation value and set an uplink transmission power value. More specifically, the terminal can measure a downlink RSRP using CSI-RS and estimate a downlink path attenuation value using [Mathematical Formula 1] using information about the transmission power of the CSI-RS received from the base station. Then, based on the estimated path attenuation value, the terminal can set an uplink transmission power value for PUCCH, PUSCH, and SRS transmission. In steps 18-35, the terminal can report a power headroom (PHR) to the base station. The power headroom can mean the difference between the current transmission power of the terminal and the maximum output power of the terminal.In steps 18-40, the base station can optimize system operation based on the reported power headroom. For example, if a specific terminal reports a positive power headroom value to the base station, the base station can allocate more resources (RBs: Resource Blocks) to the terminal to increase system throughput. In steps 18-45, the terminal can receive a transmission power control command (TPC) from the base station. For example, if a specific terminal reports a negative power headroom value to the base station, the base station can allocate fewer resources to the terminal or reduce the transmission power of the terminal through the transmission power control command (TPC). This can increase system throughput or reduce unnecessary power consumption of the terminal. In steps 18-50, the terminal can update the transmission power based on the TPC command. At this time, the TPC command can be transmitted to the terminal through UE-specific DCI or group common DCI. Therefore, the base station can dynamically control the transmission power of the terminal through TPC commands. In steps 18-55, the terminal can perform uplink transmission based on the updated transmission power.

[0501] [PUSCH power control]

[0502] The PUSCH transmission power can be determined through the following [Mathematical Formula 8].

[0503]

[0504] In [Equation 8] is the maximum transmission power set to the terminal for carrier f of serving cell c at PUSCH transmission time point i. is a reference transmission power setting value according to the activated uplink bandwidth part (BWP) b of carrier f of serving cell c, and has different values ​​depending on various transmission types j. It can have different values ​​depending on whether the PUSCH transmission is a message 3 PUSCH for random access, or whether the PUSCH is a configured grant PUSCH, or whether the PUSCH is a scheduled PUSCH. means the frequency size to which PUSCH is allocated. refers to a compensation ratio value for the path loss of UL BWP b of carrier f of serving cell c, and can be set by an upper signal and can have different values ​​depending on j. is a downlink path loss estimation value of UL BWP b of carrier f of serving cell c, and uses a value measured through a reference signal in an activated downlink bandwidth section. The reference signal may be an SS / PBCH block or a CSI-RS. The downlink path loss can be calculated as described in [Mathematical Formula 7]. In another embodiment of the present disclosure, is a downlink warning attenuation value, which is the path attenuation calculated by the terminal as in [Mathematical Formula 7]. The terminal calculates the path attenuation based on the reference signal resource linked to the SS / PBCH block or CSI-RS, depending on whether the upper signal is set. The reference signal resource can be selected from among several sets of reference signal resources by the upper signal or L1 signal, and the terminal calculates the path attenuation based on the reference signal resource. is a value determined by the MCS (Modulation and Coding Scheme) value of the PUSCH at the PUSCH transmission time point i of the UL BWP b of the carrier f of the serving cell c. is a power control adaptation value that can dynamically adjust the power value by a TPC command. In addition, it may be possible to determine a specific value by [Table 43-1] below.

[0505]

[0506] The TPC command is divided into accumulated mode and absolute mode, and one of the two modes is determined by the upper signal. In accumulated mode, the currently determined power control adaptation value is accumulated to the value indicated by the TPC command, and can be increased or decreased depending on the TPC command. have a relationship with is the value indicated by the TPC command. Absolute mode is determined by the TPC command regardless of the currently determined power control adaptation value. . [Table 44] below shows the values ​​that can be specified in the TPC command.

[0507]

[0508] [PUCCH power control]

[0509] The following [Mathematical Formula 9] is a mathematical formula that determines PUCCH transmission power.

[0510]

[0511] In [Equation 9] is the standard setting transmission power setting value, and various transmission types It has different values ​​depending on the MAC CE and the value can be changed by a higher level signal such as RRC or MAC CE. When the value is changed by MAC CE, if the slot in which HARQ-ACK is transmitted for the PDSCH that received MAC CE is k, then k + k offset It is determined that the value is applied from the slot k offsethas different values ​​depending on the subcarrier spacing, and can have 3ms as an example. is the size of the frequency resource region to which PUCCH is allocated. is the path attenuation estimation value of the terminal, and as described in [Mathematical Formula 7], the terminal calculates it based on a specific reference signal among various CSI-RS or SS / PBCH depending on whether and what type of upper signal is set. For repetitively transmitted PUCCHs, the same is applied. The same applies to repetitively transmitted PUCCHs. is applied.

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

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

[0514] Other than that, the HARQ-ACK codebook determination method is followed according to the method described below.

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

[0516] [Begin pseudo-code 1]

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

[0518] - Step 2: Set R as a set of rows in a table containing slot information, start symbol information, number of symbols, or length information to which the PDSCH is mapped. If the PDSCH-capable mapping symbol indicated by each value of R is set to a UL symbol according to the DL and UL settings set above, delete the corresponding row from R.

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

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

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

[0522] [End of pseudo-code 1]

[0523] Taking the above-described psudo-code 1 as an example in Fig. 19, in order to perform HARQ-ACK PUCCH transmission in slot#k(1908), all slot candidates for which PDSCH-to-HARQ-ACK timing that can indicate slot#k(1908) is possible are considered. In Fig. 19, it is assumed that HARQ-ACK transmission is possible in slot#k(1908) 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 schedulable PDSCHs for each slot is derived by considering the time domain resource configuration information of the schedulable PDSCHs in slots 1902, 1904, and 1906, and the information indicating whether the symbol in the slot is a downlink or an uplink. For example, if two PDSCHs can be scheduled at maximum in slot 1902, three PDSCHs can be scheduled at maximum in slot 1904, and two PDSCHs can be scheduled at maximum in slot 1906, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted at slot 1908 is seven. This is called the cardinality of the HARQ-ACK codebook.

[0524] Within a specific slot, the above step 3-2 is described through the following [Table 45] (Default PDSCH time domain resource allocation A for normal CP).

[0525]

[0526] Table 44 is a time resource allocation table in which a terminal operates by default before receiving time resource allocation through a separate RRC signal. Note that in addition to separately indicating the row index value to RRC, the PDSCH time resource allocation value is determined by the terminal common RRC signal dmrs-TypeA-Position. In Table 44 above, the ending and order columns are values ​​added separately for convenience of explanation, and may not actually exist. The meaning of the ending column refers to the end symbol of the scheduled PDSCH, and the order column refers to the code position value located within a specific codebook in the semi-static HARQ-ACK codebook. This table is applied to the time resource allocation applied in DCI format 1_0 of the common search area of ​​the PDCCH.

[0527] To determine the HARQ-ACK codebook by calculating the maximum number of non-overlapping PDSCHs within a specific slot, the terminal performs the following steps.

[0528] * Step 1: Find the PDSCH allocation value that ends earliest within the slot among all rows of the PDSCH time resource allocation table. In Table 44, we can see that row index 14 ends earliest. This is marked as 1 in the order column. In addition, other row indices that overlap row index 14 by at least one symbol are marked as 1x in the order column.

[0529] * Step 2: Then, search for the PDSCH allocation value that ends first among the remaining row indices not indicated in the Order column. In Table 44, this corresponds to the row with row index 7 and dmrs-TypeA-Position value 3. In addition, other row indices that overlap with the corresponding row index by at least one symbol are marked as 2x in the Order column.

[0530] * Step 3: Repeat Step 2 and display the order value in increasing order. For example, in Table 44, search for the PDSCH allocation value that ends first among the row indices not displayed in the order column. In Table 44, this corresponds to the row with row index 6 and dmrs-TypeA-Position value 3. In addition, other row indices that overlap with the corresponding row index by at least one symbol are displayed as 3x in the order column.

[0531] * Step 4: If an order is displayed for all row indices, the process ends. The size of the order is the maximum number of PDSCHs that can be scheduled without time overlap within the slot. Scheduling without time overlap means that different PDSCHs are scheduled using TDM.

[0532] In the order column of Table 44, the maximum value of order means the HARQ-ACK codebook size of the corresponding slot, and the order value means the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the corresponding scheduled PDSCH is located. For example, row index 16 in Table 44 means that it exists at the second code position in the semi-static HARQ-ACK codebook with a size of 3. A terminal transmitting HARQ-ACK feedback selects a set of PDSCH reception candidate cases (occasions for candidates PDSCH receptions) in serving cell c as M A,c If so, M is divided into [pseudo-code 1] or [pseudo-code 2] steps. A,c can be obtained. M A,c can be used to determine the number of HARQ-ACK bits that the terminal should transmit. Specifically, M A,c The HARQ-ACK codebook can be constructed using the cardinality of the set.

[0533] As another example, considerations for determining a semi-static HARQ-ACK codebook (or type 1 HARQ-ACK codebook) may include:

[0534]

[0535] As another example, the pseudo-code for HARQ-ACK codebook determination could be as follows.

[0536]

[0537]

[0538]

[0539] In pseudo-code 2, the location of the HARQ-ACK codebook containing HARQ-ACK information for the DCI indicating DL SPS release is based on the location where the DL SPS PDSCH is received. For example, if the start symbol for transmitting the DL SPS PDSCH starts from the 4th OFDM symbol based on the slot and is 5 symbols long, the HARQ-ACK information including the DL SPS release indicating the release of the corresponding SPS is assumed to be mapped as if a PDSCH starting from the 4th OFDM symbol of the slot in which the DL SPS release is transmitted and having a length of 5 symbols is mapped, and the corresponding HARQ-ACK information is determined through the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information indicating the DL SPS release. As another example, if the start symbol for transmitting a DL SPS PDSCH starts from the 4th OFDM symbol based on a slot and is 5 symbols long, HARQ-ACK information including a DL SPS release indicating release of the corresponding SPS is assumed to be mapped to a PDSCH starting from the 4th OFDM symbol of the slot indicated by the TDRA (Time domain resource allocation) of the DCI, which is a DL SPS release, and having a length of 5 symbols, and the corresponding HARQ-ACK information is determined through a PDSCH-to-HARQ-ACK timing indicator and a PUSCH resource indicator included in the control information indicating the DL SPS release.

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

[0541] The terminal transmits HARQ-ACK information to be transmitted within a PUCCH in slot n based on the 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. Specifically, for the above-described HARQ-ACK information transmission, the terminal determines the PDSCH-to-HARQ_feedback timing based on the DAI included in the DCI indicating the PDSCH or SPS PDSCH release and the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by K0.

[0542] The above DAI is composed of Counter DAI and Total DAI. Counter DAI is information indicating the position of HARQ-ACK information corresponding to the PDSCH scheduled in DCI format 1_0 or DCI format 1_1 within the HARQ-ACK codebook. Specifically, the value of counter DAI in DCI format 1_0 or 1_1 indicates the accumulated value of 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 accumulated value is set based on the PDCCH monitoring occasion and serving cell where the scheduled DCI exists.

[0543] Total DAI is a value indicating the size of the HARQ-ACK codebook. Specifically, the Total DAI value represents the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time at which the DCI was scheduled. Furthermore, Total DAI is a parameter used in a CA (Carrier Aggregation) situation when HARQ-ACK information on serving cell c also includes HARQ-ACK information for PDSCHs scheduled in other cells, including serving cell c. In other words, in a system operating with a single cell, there is no Total DAI parameter.

[0544] An example of the operation of the above DAI is shown in Fig. 20. In Fig. 20, when a terminal transmits a HARQ-ACK codebook selected based on DAI in the nth slot of carrier 0 (2002) on PUCCH (2020) in a situation where two carriers are set, the values ​​of Counter DAI (C-DAI) and Total DAI (T-DAI) indicated by the DCI searched for each PDCCH monitoring occasion set for each carrier are shown. First, the DCI searched at m=0 (2006) indicates that C-DAI and T-DAI each have a value of 1 (2012). The DCI searched at m=1 (2008) indicates that C-DAI and T-DAI each have a value of 2 (2014). The DCI probed on carrier 0 (c=0, 2002) of m=2 (2010) indicates a C-DAI of 3 (2016). The DCI probed on carrier 1 (c=1, 2004) of m=2 (2010) indicates a C-DAI of 4 (2018). In this case, if carriers 0 and 1 are scheduled in the same monitoring occasion, both T-DAIs are indicated as 4.

[0545] In FIGS. 19 and 20, the HARQ-ACK codebook determination operates in a situation where only one PUCCH containing HARQ-ACK information is transmitted within a slot. This is called Mode 1. As an example of how one PUCCH transmission resource is determined within a slot, when PDSCHs scheduled in different DCIs are multiplexed and transmitted as one HARQ-ACK codebook within the same slot, the PUCCH resource selected for HARQ-ACK transmission is determined as the PUCCH resource indicated by the PUCCH resource field indicated in the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated in the DCI scheduled before the DCI is ignored.

[0546] The following description defines a method and devices for determining a HARQ-ACK codebook in a situation where two or more PUCCHs containing HARQ-ACK information can be transmitted within a single slot. This is called Mode 2. A terminal may be able to operate only in Mode 1 (only one HARQ-ACK PUCCH is transmitted within a single slot) or only in Mode 2 (one or more HARQ-ACK PUCCHs are transmitted within a single slot). Alternatively, a terminal that supports both Mode 1 and Mode 2 may be configured by the base station to operate in only one mode through higher-level signaling, or Mode 1 and Mode 2 may be implicitly determined by DCI format, RNTI, DCI-specific field values, scrambling, etc. For example, a PDSCH scheduled with DCI format A and its associated HARQ-ACK information are based on Mode 1, and a PDSCH scheduled with DCI format B and its associated HARQ-ACK information are based on Mode 2. Whether the HARQ-ACK codebook described above is semi-static or dynamic is determined by the RRC signal.

[0547] [Satellite Communication Structure Description]

[0548] Hereinafter, the characteristics of satellite communication will be described. Satellites for communication can be classified into low Earth Orbit (LEO), middle Earth Orbit (MEO), and geostationary Earth Orbit (GEO) satellites depending on their orbits. Generally, GEO refers to a satellite with an altitude of approximately 36,000 km, MEO refers to a satellite with an altitude of 5,000 to 15,000 km, and LEO refers to a satellite with an altitude of 500 to 1,000 km. Of course, GEO, MEO, and LEO are not limited to the examples above. According to one embodiment of the present disclosure, the Earth's orbital period may vary depending on the altitude. 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 are at relatively low altitudes, so propagation delay (which can be understood as the time it takes for a signal transmitted from a transmitter to reach a receiver) and loss may be advantageous compared to geostationary (36,000 km) satellites. FIG. 21 is a diagram illustrating the Earth orbital period of a communication satellite according to the altitude or height of the satellite according to one embodiment of the present disclosure. Assuming that a terminal communicates with a satellite located at an altitude of 1,200 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 1,200 km, but when the elevation angle between the satellite and the terminal is 10 degrees, the distance between the terminal and the satellite is approximately 3,135 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 like a low Earth orbit satellite.In addition, since the distance between the terminal and the satellite in satellite communication is much longer than the distance between the terminal and the base station in a terrestrial network, it may be necessary to transmit control information and data information in the form of data transmission with a low code rate or repeated transmission.

[0549] [OCC-based PUCCH transmission]

[0550] Hereinafter, a PUCCH transmission method utilizing the OCC (Orthogonal Cover Code) of a terminal will be described. LTE PUCCH format 5 is one of the signals transmitted on the PUCCH, an uplink control channel, and can be mainly used to convey ACK / NACK (positive acknowledgment / negative acknowledgment) feedback for downlink data transmission. PUCCH format 5 combines the frequency division multiple access (FDMA) scheme and the time division multiple access (TDMA) scheme to distinguish signals transmitted from different terminals (i.e., the OFDMA scheme) and transmits signals using cyclic shift technology. To implement this function, LTE PUCCH format 5 applies OCC technology utilizing orthogonality. OCC is used to distinguish signals transmitted from different terminals, and each terminal selects an OCC sequence based on a predefined OCC index and covers the ACK / NACK bits with the selected sequence for transmission. Therefore, PUCCH format 5 applying OCC can improve the overall performance of the LTE system by enabling efficient control channel transmission in a multiple access environment. Fig. 22 is a block diagram illustrating a method for generating LTE PUCCH format 5 according to an embodiment. After the terminal generates HARQ ACK / NACK bits, it creates coded bits through a channel coding and scrambling process. Then, it divides and allocates 72 modulated symbols to a total of 12 OFDM symbols through QPSK modulation and de-multiplexing processes. Then, the 6 modulated symbols assigned to each symbol are mapped to 12 frequency tones through OCC spreading.Spreading schemes may be able to operate by mapping QPSK modulation symbols to a larger number of virtual frequency tones. This may prevent signals from multiple users from interfering with each other. While 12 QPSK modulation symbols can be mapped to one RB (Resource Block) SC-FDM symbol in other existing LTE PUCCH formats, only 6 QPSK modulation symbols are mapped to one RB and SC-FDM symbol in LTE PUCCH 5, as shown in Figure 22. Furthermore, the CDM index utilized in the spreading scheme is a value assigned to each user and can have a value of 0 or 1. This value determines how each user's signal will be spread. For example, a user with a CDM index of 0 will have their signal duplicated twice and mapped to 12 virtual frequency tones, while a user with a CDM index of 1 will have their signal duplicated twice, but half of them will be multiplied by -1 and mapped to 12 virtual frequency tones. This allows each user's signal to be distributed over a wider bandwidth, making it possible to avoid interference even in a multi-user environment. How interference can be avoided despite using the same time and frequency resources is further described with reference to FIG. 23. FIG. 23 is a diagram illustrating a method for different terminals to map different OCC values ​​to virtual frequency tones according to an embodiment. In FIG. 23, a first terminal repeatedly maps information of (A1, A2, A3, A4, A5, A6) to 1RB. A second terminal repeatedly maps information of (B1, B2, B3, B4, B5, B6) to 1RB, mapping half of the values ​​multiplied by 1 and the other half of the values ​​multiplied by -1. After performing DFT and IFFT, the first and second terminals transmit information.After receiving this, the base station performs a de-spreading process, and for example, it may be possible to decode A1 and B1 through the "A1+B1" value and the "A1-B1" value, respectively. In this way, it may be possible for the base station to decode the remaining information, that is, information A2, A3, A4, A5, and A6 of the first terminal and B2, B3, B4, B5, and B6 of the second terminal. Although FIG. 22 and FIG. 23 describe the OCC spreading method from a frequency axis perspective as an example, it may be possible to apply the OCC spreading method from a time axis perspective. In addition, although FIGS. 22 and 23 consider a method of applying OCC sequences of (1,1) and (1,-1) to two different terminals based on an OCC length of 2, it is possible to consider a sequence having an OCC length greater than 2, and in this case, it may be possible for two or more different terminals to transmit PUCCH using the same time and frequency resources.

[0551] [OCC-based PUSCH transmission]

[0552] Below, we describe a PUSCH transmission method utilizing the OCC scheme. Essentially, when a terminal has data to send to a base station, it can perform processing for PUSCH transmission through the following series of procedures, as illustrated in Figure 24. The following procedures are merely examples; some of them may be omitted, or the order of the procedures may be reversed for the terminal to apply.

[0553] ㆍ Transport block CRC Attachment: Error checking code is attached to the data.

[0554] ㆍ LDPC base graph selection: An appropriate LDPC graph is selected for channel coding.

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

[0556] ㆍ Channel Coding: Blocks are encoded to prevent transmission errors.

[0557] ㆍ Rate Matching: Encoded data is mapped to available transmission resources.

[0558] ㆍ Code Block Concatenation: Encoded blocks are re-concatenated.

[0559] ㆍ Data and Control Multiplexing: When there are control resources that overlap with data resources, the control information is multiplexed with the data information.

[0560] ㆍScrambling: Scrambling data to prevent predictable patterns that could degrade signal quality.

[0561] ㆍ Modulation: Scrambled data is modulated onto the carrier wave.

[0562] ㆍ Layer Mapping: Data is mapped across transmission layers.

[0563] ㆍ OCC spreading: Applying OCC to data mapped to layers. Applicable to Figure 23 or other methods.

[0564] Transform Precoding: Reconstructing frequency-domain signals into time-domain signals using the Discrete Fourier Transform (DFT). This step is particularly useful in scenarios with a single transmission layer, improving signal orthogonality and reducing interference.

[0565] 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 its directionality and improve reception at the receiver, taking into account various antenna configurations and channel conditions.

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

[0567] ㆍ Mapping from RB to PRB (Physical Resource Block): Then, the virtual resource block is mapped to a physical resource block for actual transmission.

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

[0569] For example, when a terminal repeatedly transmits a PUSCH for each slot, it may be possible to apply an OCC sequence for each slot. FIG. 25 is a diagram showing a method for applying an OCC scheme when a terminal repeatedly transmits a PUSCH for each slot, according to an embodiment. In a situation where the OCC length is 2, two different terminals repeatedly transmit PUSCHs through the same time and frequency resources. The first terminal transmits PUSCH A, and the second terminal transmits PUSCH B. The first terminal generates (2500) the same data (a1) and repeatedly transmits it in slot n and slot n+1 (2502). The second terminal maps (2501) data (b1) to b1 in slot n and -b1, which is obtained by multiplying -1, to slot n+1. The second terminal then transmits b1 to PUSCH B in slot n and -b1 to PUSCH B in slot n+1. In FIG. 25, PUSCH A and PUSCH B transmitted in slot n and slot n+1 are illustrated as being transmitted by the first terminal and the second terminal through the same time and frequency resources, but it may be possible that only some time and frequency resources overlap and other different time and frequency resources are used. In addition, 2500 and 2501 in FIG. 25 are conceptual diagrams that illustrate that each data is transmitted by the first terminal and the second terminal through PUSCH, rather than being generated in slot n and slot n+1, and in reality, it may be possible that they are generated before slot n, which is when the PUSCH is transmitted from the beginning.In FIG. 25, the base station receives a1+b1 information through PUSCH A and PUSCH B transmitted by the first and second terminals in slot n, and receives a1-b1 information through PUSCH A and PUSCH B transmitted by the first and second terminals in slot n+1. Therefore, the base station may be able to receive a1 and b1, respectively, through the OCC despreading method for the received a1+b1 and a1-b1. Here, a1 and b1 represent a set of symbols in which a series of data is channel-coded and modulated. Alternatively, they may be a set of data before DFT. In order to apply the OCC method as in FIG. 25, the base station may be able to indicate to the terminals in advance through an upper signal or an L1 signal an OCC sequence value to be applied for each slot when repeatedly transmitting PUSCH. For example, in the case of the second terminal, if a DCI field called OCC index exists in the L1 signal and the corresponding value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may be able to apply '1' in slot n and '-1' in slot n+1. Specifically, the DCI field called OCC index exists as 1 bit, and if it is 0, the OCC sequence may be (1,1), and if it is 1, the OCC sequence may be able to indicate (1,-1) or (-1,1). The type of the OCC sequence and the size of the DCI field may be determined by upper signal settings. The length of the OCC sequence may be a value greater than the length 2 described in the example above. In addition, in FIG. 25, the first terminal is described as applying the OCC sequence as (1,1), but regardless of this, the first terminal may be able to perform conventional PUSCH repeated transmission without applying the OCC sequence. Therefore, in FIG. 25, the first terminal may be capable of sending or not sending the terminal capability to apply the OCC spreading method.On the other hand, the second terminal may be able to apply it only when the terminal capability to apply the OCC spreading method has been transmitted. Fig. 25 exemplifies a case where the first terminal and the second terminal apply two repeated transmissions, but it may also be possible for the number of slots to be repeatedly transmitted to be 4, 8, or more. In this case, assuming that the OCC sequence (1, -1) applied by the second terminal is repeatedly transmitted 4 times, it may be possible for slot n to be b1, slot n+1 to be -b1, slot n+2 to be b1, and slot n+3 to be -b1, or for slot n to be b1, slot n+1 to be b1, slot n+2 to be -b1, and slot n+3 to be -b1. Alternatively, it may be possible for even slots to always apply an OCC sequence of 1 (or -1) and odd slots to always apply an OCC sequence of -1 (or 1). Alternatively, it may be possible to apply the OCC sequence by modular operation. Since the OCC sequence (1, -1) has a length of 2, the OCC sequence value applied to the PUSCH in the nth slot may be 1 (or -1) if the mod (n / 2) value is 1, and -1 (or 1) if the mod (n / 2) value is 0. In addition, although FIG. 25 illustrates that the first terminal and the second terminal start the same number of repeated transmissions from the same slot, it may also be possible to apply the same method even when they start from different slots or perform different numbers of repeated transmissions. In order for the terminal to determine whether to perform the OCC-based PUSCH transmission, the base station provides the terminal with relevant information through an upper signal, an L1 signal, or a combination thereof. The terminal can determine, by receiving the information, whether the PUSCH transmitted by the terminal is subject to the OCC sequence.Additionally, specific OCC sequence information is provided to the terminal through an upper signal or an L1 signal, and the terminal may be able to determine the OCC sequence size and OCC sequence type through this.

[0570] As another example, when a terminal repeatedly transmits a PUSCH within a slot, it may be possible to apply an OCC sequence for each PUSCH transmission unit that is repeatedly transmitted. FIG. 26 is a diagram showing a method for applying an OCC scheme when a terminal repeatedly transmits a PUSCH within a slot according to an embodiment. It is basically similar to the operation in FIG. 25. In a situation where the OCC length is 2, two different terminals repeatedly transmit PUSCHs through the same time and frequency resources. The first terminal transmits PUSCH A, and the second terminal transmits PUSCH B. The first terminal generates (2600) the same data (a1) and performs repeated transmission (2602) in one slot n. The second terminal maps (2601) data (b1) to the first PUSCH B of one slot n by b1 and to the second PUSCH B by multiplying -1 by -b1. And the second terminal transmits b1 to the first PUSCH B of slot n, and -b1 to the second PUSCH B of slot n. In Fig. 26, 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 it may be possible that only some time and frequency resources overlap and other different time and frequency resources are used. In addition, 2600 and 2601 in Fig. 26 are conceptual diagrams that illustrate that each data is not generated in slot n, but rather that the first terminal and the second terminal transmit through PUSCH, and in reality, it may be possible that the data is generated before slot n, which transmits the PUSCH from the beginning.In FIG. 26, the base station receives a1+b1 information through the first PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, respectively, and receives a1-b1 information through the second PUSCH A and PUSCH B transmitted by the first terminal and the second terminal in slot n, respectively. Therefore, the base station may be able to receive a1 and b1 through the OCC despreading method for the received a1+b1 and a1-b1. Here, a1 and b1 represent a set of symbols in which a series of data is channel-coded and modulated. Alternatively, they may be a set of data before DFT. In order to apply the OCC method as in FIG. 26, the base station may be able to indicate to the terminals in advance through an upper signal or an L1 signal an OCC sequence value to be applied to each PUSCH transmission section when repeatedly transmitting PUSCH. For example, in the case of the second terminal, if a DCI field called OCC index exists in the L1 signal and the corresponding value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may be able to apply '1' to the first PUSCH and '-1' to the second PUSCH. Specifically, the DCI field called OCC index exists as 1 bit, and if it is 0, the OCC sequence may be (1,1), and if it is 1, the OCC sequence may be able to indicate (1,-1) or (-1,1). The type of the OCC sequence and the size of the DCI field may be determined by upper signal settings. The length of the OCC sequence may be a value greater than the length 2 described in the example above. In addition, in FIG. 26, the first terminal is described as applying the OCC sequence as (1,1), but regardless of this, the first terminal may be able to perform conventional PUSCH repeated transmission without applying the OCC sequence.Accordingly, in FIG. 26, the first terminal may be able to transmit the terminal capability to apply the OCC spreading method, whether or not it is transmitted. On the other hand, the second terminal may be able to apply the OCC spreading method only when it has transmitted the terminal capability to apply the OCC spreading method. Although FIG. 26 exemplifies a case where the first and second terminals apply two repeated transmissions, it may also be possible to apply a value of 4, 8, or more PUSCHs to be repeatedly transmitted. In addition, it may also be possible for the PUSCH to be repeatedly transmitted across multiple slots rather than just one slot. At this time, assuming that the OCC sequence (1, -1) applied by the second terminal is repeatedly transmitted 4 times, it may be possible to apply b1 for the first PUSCH, -b1 for the second PUSCH, b1 for the third PUSCH, and -b1 for the fourth PUSCH, or it may be possible to apply b1 for the first PUSCH, b1 for the second PUSCH, -b1 for the third PUSCH, and -b1 for the fourth PUSCH. Alternatively, it may be possible that an OCC sequence of 1 (or -1) is always applied to even-numbered PUSCH transmissions and an OCC sequence of -1 (or 1) is always applied to odd-numbered PUSCH transmissions. Alternatively, it may be possible that the OCC sequence is applied by modular operation. Since the OCC sequence (1,-1) has a length of 2, it may be possible to apply 1 (or -1) to the OCC sequence value applied to the nth PUSCH if the mod (n / 2) value is 1, and apply -1 (or 1) if the mod (n / 2) value is 0. In addition, although FIG. 26 illustrates that the first terminal and the second terminal start the same number of repeated transmissions from the same slot, it may also be possible to apply it even when they start from different slots or perform different numbers of repeated transmissions.

[0571] As another example, it may be possible to apply an OCC sequence between pieces of information belonging to different time resources within a single PUSCH. FIG. 27 is a diagram illustrating a method for a terminal to apply an OCC scheme in terms of time resources when transmitting a PUSCH according to an embodiment. If a first terminal and a second terminal apply an OCC scheme with a length of 2 in terms of time resources, it may be possible to determine the actual TBS value as the value obtained by dividing the PUSCH resource size allocated to the corresponding terminal by 2 when calculating TBS. Alternatively, it may be possible for the TBS calculation to separately consider the size of the actual PUSCH transmission resource region. The size of the PUSCH transmission resource region is determined by the frequency resource size (number of RBs) and the time resource size (number of symbols). Thereafter, the terminals prepare for data transmission according to the procedure described in FIG. 24. And, in the OCC spreading step, as illustrated in Fig. 27, the first terminal sequentially arranges two identical data a1 from a time resource perspective and applies the OCC sequence (1,1) to the first a1 and the second a1 for each (2700). Then, it transmits them in the PUSCH A resource region allocated by the base station (2702). The second terminal also sequentially arranges two identical data b1 from a time resource perspective and applies the OCC sequence (1,-1) to the first b1 and the second b1 for each (2701). Then, it transmits them in the PUSCH B resource region allocated by the base station (2702). Although Fig. 27 illustrates that the data to which OCC is applied is divided into two equal parts from a time resource perspective, it may be possible to divide it into three equal parts, four equal parts, or more equal parts and apply it. When the same data is mapped into four equal parts, it may be possible for the first terminal to generate (a1, a1, a1, a1), and for the second terminal to generate (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1).In addition, although the method of OCC spreading and despreading was explained in terms of the frequency axis in FIG. 23, it is quite possible to convert it to the time axis and apply it, and it may be the same or somewhat similar. 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 it may be possible that only some time and frequency resources overlap and other different time and frequency resources are used. In addition, 2700 and 2701 in FIG. 27 are conceptual diagrams that illustrate that each data is not generated in slot n, but rather that the first terminal and the second terminal transmit through PUSCH. In reality, it may be possible that the data is generated before slot n, which transmits the PUSCH from the beginning. In Fig. 27, since the base station receives information a1+b1 and a1-b1 through PUSCH A and PUSCH B transmitted by the first and second terminals in slot n, the base station may be able to receive a1 and b1, respectively, through the OCC despreading method for the received a1+b1 and a1-b1. Here, a1 and b1 represent a set of symbols in which a series of data is channel-coded and modulated. Or, they may be a set of data before DFT. In order to apply the OCC method as in Fig. 27, the base station may be able to indicate to the terminals in advance through an upper layer signal or an L1 signal an OCC sequence value to be applied when repeatedly transmitting PUSCH. For example, in the case of the second terminal, if there is a DCI field called OCC index in the L1 signal and the corresponding value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may be able to apply '1' to the first part of the PUSCH and '-1' to the second part.Specifically, the OCC index is a DCI field with 1 bit, and if it is 0, the OCC sequence is (1,1), and if it is 1, the OCC sequence may indicate (1,-1) or (-1,1). The OCC sequence type and DCI field size may be determined by upper signal settings. The length of the OCC sequence may use a value greater than the length 2 described in the example above. In FIG. 27, the first terminal and the second terminal may both transmit or not transmit the terminal capability that can apply the OCC spreading method. Although FIG. 27 illustrates a case where one PUSCH is transmitted, the present invention is not limited thereto, and a case where the PUSCH is repeatedly transmitted across multiple slots may also be possible. In addition, although FIG. 27 illustrates that the first terminal and the second terminal start PUSCH transmission from the same slot, it may also be applicable to cases where they start from different slots or perform different numbers of repeated transmissions.

[0572] As another example, it may be possible to apply an OCC sequence between pieces of information belonging to different frequency resources within a single PUSCH. FIG. 28 is a diagram illustrating a method for a UE to apply an OCC scheme in terms of frequency resources when transmitting a PUSCH according to an embodiment. If a first UE and a second UE apply an OCC scheme with a length of 2 in terms of frequency resources, it may be possible to determine the actual TBS value as the value obtained by dividing the PUSCH resource size allocated to the corresponding UE by 2 when calculating TBS. Alternatively, it may be possible for the TBS calculation to separately consider the size of the actual PUSCH transmission resource region. The size of the PUSCH transmission resource region is determined by the frequency resource size (number of RBs) and the time resource size (number of symbols). Thereafter, the UEs prepare for data transmission according to the procedure described in FIG. 24. And, in the OCC spreading step, as illustrated in Fig. 28, the first terminal sequentially arranges two identical data a1 in terms of frequency resources and applies the OCC sequence (1,1) to the first a1 and the second a1 for each (2800). Then, it transmits them in the PUSCH A resource region allocated by the base station (2802). The second terminal also sequentially arranges two identical data b1 in terms of time resources and applies the OCC sequence (1,-1) to the first b1 and the second b1 for each (2801). Then, it transmits them in the PUSCH B resource region allocated by the base station (2702). Although Fig. 28 illustrates that the data to which OCC is applied is divided into two equal parts in terms of frequency resources, it may be possible to divide it into three equal parts, four equal parts, or more equal parts and apply it. When the same data is mapped into four equal parts, it may be possible for the first terminal to generate (a1, a1, a1, a1), and for the second terminal to generate (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1).In addition, the method of OCC spreading and despreading may be the same as or partially similar to that described in FIG. 23. In FIG. 28, 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 it may be possible that only some time and frequency resources overlap and other different time and frequency resources are used. In addition, 2800 and 2801 in FIG. 28 are conceptual diagrams that illustrate that each data is not generated in slot n, but rather transmitted by the first terminal and the second terminal through PUSCH. In reality, it may be possible for the data to be generated before slot n, which is when the PUSCH is transmitted from the beginning. In Fig. 28, since the base station receives information a1+b1 and a1-b1 through PUSCH A and PUSCH B transmitted by the first and second terminals in slot n, the base station may be able to receive a1 and b1, respectively, through the OCC despreading method for the received a1+b1 and a1-b1. Here, a1 and b1 represent a set of symbols in which a series of data is channel-coded and modulated. Or, they may be a set of data before DFT. In order to apply the OCC method as in Fig. 28, the base station may be able to indicate to the terminals in advance through an upper layer signal or an L1 signal the OCC sequence value to be applied when repeatedly transmitting PUSCH. For example, in the case of the second terminal, if there is a DCI field called OCC index in the L1 signal and the corresponding value indicates a bit value corresponding to the OCC sequence (1,-1), the second terminal may be able to apply '1' to the first part of the PUSCH and '-1' to the second part. Specifically, the OCC index DCI field 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 above OCC sequence type and DCI field size may be determined by upper signal settings. The length of the OCC sequence may be a value greater than the length 2 described in the example above. In FIG. 28, the first terminal and the second terminal may both transmit or not transmit the terminal capability that can apply the OCC spreading method. Although FIG. 28 illustrates a case where one PUSCH is transmitted, the present invention is not limited thereto, and a case where the PUSCH is repeatedly transmitted across multiple slots may also be possible. In addition, although FIG. 28 illustrates that the first terminal and the second terminal start PUSCH transmission from the same slot, it may also be applicable when they start from different slots or perform different numbers of repeated transmissions.

[0573] [TBS Decision Method]

[0574] Below, we describe how a terminal determines its Transport Block Size (TBS). The terminal can calculate TBS using the MCS (Modulation and Coding Scheme) field and time and frequency resource allocation information within the DCI format provided by the base station. Specifically, TBS can be determined according to the procedure in [Table 46].

[0575]

[0576]

[0577] [UCI Rate Matching]

[0578] Hereinafter, the description describes a method for determining the number of rate matching bits of a UCI when the UCI is transmitted in a PUSCH. The UCI may correspond to HARQ-ACK, CSI part 1, or CSI part 2. The UE may be able to determine the number of rate matching bits of the UCI included in the PUSCH according to the procedure in [Table 47] below.

[0579] [Table 47]

[0580]

[0581]

[0582]

[0583]

[0584]

[0585]

[0586]

[0587]

[0588] Hereinafter, the application of OCC-based PUSCH transmission to satellite communications will be described. The methods described below may also be applicable to terrestrial networks. A satellite communication system may include three components: a terminal, a ground station (base station), and a satellite. The link between the terminal and the satellite may be referred to as a "service link," and the link between the ground station and the satellite may be referred to as a feeder link. In the service link, the downlink is usually a link from the satellite to the terminal (UE), and the uplink is a link from the terminal to the satellite (UE to satellite). Similar to terrestrial networks, in satellite communications, uplink coverage may be insufficient because the transmission power of the terminal may be significantly lower than that of the satellite. To compensate for the insufficient uplink coverage, the terminal may typically perform repeated transmissions for uplink data transmission.

[0589] If all terminals within satellite coverage repeatedly transmit the same data via uplink, the satellite network may run out of available frequency and time resources. To address this issue, code resources, in addition to frequency and time resources, must be utilized to support a greater number of terminals. Therefore, terminals may consider using the aforementioned OCC method to transmit uplink data.

[0590] FIGS. 29 to 32 are diagrams showing a process of mapping one TB to a wireless resource by applying the OCC technique. FIGS. 29 and 30 show examples of mapping one TB to a wireless resource by applying the OCC technique from a symbol level perspective, and FIGS. 31 and 32 show examples of mapping one TB to a wireless resource by applying the OCC technique from an RE level or RB level perspective. FIGS. 29 to 32 show examples of a case where the OCC length is 2, and w1 and w2 are OCC codes and can have values ​​of

[0011] or [1 -1]. In FIGS. 29 to 32, 2900, 3000, 3100, and 3200 can be information that is modulated after a series of transmission processing processes are performed on one TB as described in FIG. 24, or information that is transform precoded. This information (2900, 3000, 3100, 3200 in FIGS. 29 to 32) is classified into two copies as described in FIGS. 29 to 32, and each copy is multiplied by w1 and w2, and then mapped from a time resource perspective or a frequency resource perspective, respectively. 2902, 3002, 3102, and 3202 represent one PUSCH resource. Examples of the OCC code may include a Walsh sequence, a binary sequence, or a DFT sequence. Therefore, the time resource and frequency resource as factors determining the TBS size described above can be determined based on whether spreading is performed for the OCC from a time resource perspective or a frequency resource perspective.

[0591] Hereinafter, a method for determining the TBS of a terminal in a situation where OCC is applied to PUSCH from a time resource perspective as illustrated in FIG. 29 or FIG. 30 is described. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal may be able to determine the TBS through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function (rounding function), is the ceiling function (rounding function), is considered as a floor function (lowering function).

[0592] Method 1-1: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0593] Method 1-2: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0594] Method 1-3: Between step 1 and step 2 in [Table 46] can be added. Or, between step 1 and step 2 in [Table 45]. can be added. Or, between step 1 and step 2 in [Table 46]. can be added. Or, between step 1 and step 2 in [Table 46]. may be added.

[0595] Method 1-4: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0596] Method 1-5: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0597] Method 1-6: Step 2 of [Table 46] instead can be applied. Or, in step 2 of [Table 46] instead can be applied. Or, in step 2 of [Table 46] instead can be applied. Or, in step 2 of [Table 46] instead can be applied.

[0598] Hereinafter, a method for determining the TBS of a terminal in a situation where OCC is applied to PUSCH from a frequency resource perspective, as illustrated in FIG. 31 or FIG. 32, is described. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal can determine the TBS through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function, is the ceiling function, is considered as a floor function.

[0599] Method 2-1: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0600] Method 2-2: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0601] Method 2-3: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0602] Method 2-4: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0603] Method 2-5: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0604] Method 2-6: Step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied. Or, in step 1 of [Table 46] instead can be applied.

[0605] Hereinafter, a method for determining a TBS included in a PDSCH or PUSCH in a situation where the OCC scheme is applied to the PDSCH or PUSCH is described. The terminal can determine the resource size of the PDSCH or PUSCH provided for TB transmission related to the TBS determination for TBS determination. The resource size of the PDSCH and PUSCH can be determined through the time resource size and the frequency resource size, and information about the time resource size and the frequency resource size for determining the resource size of the PDSCH and PUSCH can be provided to the terminal from the base station through a higher layer signal and an L1 signal. At this time, if the terminal determines that the OCC scheme is applied for TB transmission, the terminal may be able to recalculate the time resource size and the frequency resource size for determining the TBS. First, whether the OCC scheme is applied can be provided to the terminal through a higher layer signal or an L1 signal. For example, if the terminal determines that the OCC scheme is applied in terms of time resources through at least one of the upper layer signals or L1 signals, the terminal may determine the time resource size of the PDSCH or PUSCH scheduled by the base station as a value obtained by dividing the time resource size by the length of the OCC sequence when calculating TBS. For example, if the time resource size of the PDSCH or PUSCH is 6 symbols and the OCC sequence length is 2, the terminal may regard / determine the time resource information as 3 symbols when calculating TBS. As another example, if the terminal determines that the OCC scheme is applied in terms of frequency resources through at least one of the upper layer signals or L1 signals, the terminal may determine the frequency resource size of the PDSCH or PUSCH scheduled by the base station as a value obtained by dividing the time resource size by the length of the OCC sequence when calculating TBS.For example, if the frequency resource size of PDSCH or PUSCH is 2 RBs and the OCC sequence length is 2, the terminal may regard / judge the frequency resource information as 1 RB when calculating TBS. As another example, if the terminal determines that the OCC method is applied in terms of time and frequency resources through at least one of the upper layer signals or L1 signals, the terminal may be able to determine the time and frequency resource size of the PDSCH or PUSCH scheduled by the base station as a value divided by the OCC sequence length when calculating TBS. For example, if the time and frequency resource size of the PDSCH or PUSCH consists of 100 REs and the OCC sequence length is 2, the terminal may regard / judge the time and frequency resource information as 50 REs when calculating TBS.

[0606] Below, a method for determining the number of rate matching bits of UCI when UCI is mapped to PUSCH to which OCC method is applied from a time resource perspective is described. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal may be able to determine the number of rate matching bits of the UCI through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function, is the ceiling function, is considered as a floor function.

[0607] Method 4-1: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0608] Method 4-2: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0609] Below, the description explains how to determine the number of rate matching bits of UCI when UCI is mapped to PUSCH to which OCC method is applied from a frequency resource perspective. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal may be able to determine the number of rate matching bits of the UCI through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function, is the ceiling function, is considered as a floor function.

[0610] Method 5-1: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0611] Method 5-2: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied.. or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0612] Method 5-3: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead can be applied. The above-described method may be applied to all parts of the PUSCH to which the OCC method is applied, or may be applied to a specific part of the PUSCH to which the OCC method is applied.

[0613] Below, a method for determining the transmission power of a PUSCH with the OCC scheme applied from a time resource perspective is described. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal may be able to determine the number of rate matching bits of the UCI through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function, is the ceiling function, is considered as a floor function.

[0614] Method 6-1: In [Table 43-1] instead may be applied. Or, in [Table 43-1] instead may be applied. Or, in [Table 43-1] instead may be applied. Or, in [Table 43-1] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0615] Below, a method for determining the transmission power of a PUSCH to which the OCC method is applied is described from a frequency resource perspective. When the number of terminals multiplexed with OCC, or the total number of OCC spreading factors, or the total number of parameters applied to the OCC spreading sequence, or the size of the sequence used in the OCC code, the terminal may be able to determine the number of rate matching bits of the UCI through at least one of the following methods or some combination thereof. In the following description, for convenience of explanation, is the round function, is the ceiling function, is considered as a floor function.

[0616] Method 7-1: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0617] Method 7-2: In [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead may be applied. Or, in [Table 47] instead The above-described method can be applied to all parts of the PUSCH to which the OCC method is applied, or to a specific part of the PUSCH to which the OCC method is applied.

[0618] FIG. 33 is a diagram illustrating a procedure for performing PUSCH transmission using the OCC scheme according to one embodiment of the present disclosure. When transmitting a PUSCH to a base station, a terminal may transmit terminal capability information indicating whether an OCC sequence can be applied to the PUSCH to the base station. Thereafter, the base station may provide OCC-related higher layer signaling information to the terminal. Thereafter, when scheduling the PUSCH, the base station may inform the terminal of whether the OCC is applied through a higher layer signal or an L1 signal. The terminal may determine the TBS size of the PUSCH, determine the number of rate matching bits of UCI transmitted through the PUSCH, or determine the transmission power of the PUSCH by applying the OCC scheme by at least one of the aforementioned methods or some combination thereof. Based on at least one of the determined TBS size, the determined number of rate matching bits of UCI, or the transmission power of the PUSCH, the terminal may transmit the corresponding PUSCH. Afterwards, the base station can perform demodulation / decoding of data from multiple terminals by applying the OCC despreading method through the reception signals received from multiple terminals.

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

[0620] Referring to FIG. 34, the terminal may include a transceiver, which refers to a terminal receiving unit (3400) and a terminal transmitting unit (3410), a memory (not shown), and a terminal processing unit (3405, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (3400, 3410), the memory, and the terminal processing unit (3405) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0621] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0622] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0623] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0624] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform terminal component control operations by executing programs stored in memory.

[0625] FIG. 35 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0626] Referring to FIG. 35, the base station may include a transceiver, which refers to a base station receiver (3500) and a base station transmitter (3510), a memory (not shown), and a base station processor (3505, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (3500, 3510), the memory, and the base station processor (3505) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0627] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0628] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

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

[0630] The processor can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0631] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0633] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0634] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0635] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0636] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

[0637] Meanwhile, the order of description in the drawings explaining the method of the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0638] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

[0639] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the disclosure.

[0640] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. In a method performed by a terminal (user equipment) in a wireless communication system, A step of receiving configuration information for an orthogonal cover code (OCC) for a physical uplink shared channel (PUSCH) from a base station; and A step of transmitting the PUSCH to the base station by applying the OCC based on the setting information, A method in which the above OCC is applied across multiple symbols for one transport block (TB) or across multiple resource elements (REs) within one symbol.

2. In claim 1, A method in which the above setting information indicates whether the OCC of the PUSCH is applied.

3. In claim 1, When the OCC is applied across the plurality of symbols, the plurality of symbols include symbols having symbol indices 1 to 7 or symbol indices 1, 3, 5, 7, 9, 11, and 13 within a slot, A method wherein, when the OCC is applied across the plurality of REs within the one symbol, the plurality of REs include subcarriers having subcarrier indices 1 to 7 or subcarrier indices 1, 3, 5, 7, 9, 11, and 13.

4. In claim 3, The size of the above one TB is determined based on the value obtained by dividing the size of the PUSCH by the length of the OCC, A method wherein the length of the above OCC is indicated as 2 or 4 in the above setting information.

5. In claim 1, A method in which the above OCC is applied to the above PUSCH for each slot.

6. In claim 1, The method further includes a step of transmitting terminal capability information to the base station, A method wherein the terminal capability information includes information indicating whether the terminal can apply the OCC to the PUSCH.

7. In a wireless communication system, in the terminal (user equipment), transceiver; and including a controller coupled with the above transmitter and receiver, The above controller, Receive configuration information for an orthogonal cover code (OCC) for a physical uplink shared channel (PUSCH) from a base station, The base station is configured to transmit the PUSCH by applying the OCC based on the configuration information, The above OCC is applied across multiple symbols for one transport block (TB) or across multiple REs (resource elements) within one symbol.

8. In claim 7, The above setting information indicates whether the OCC of the PUSCH is applied to the terminal.

9. In claim 7, When the OCC is applied across the plurality of symbols, the plurality of symbols include symbols having symbol indices 1 to 7 or symbol indices 1, 3, 5, 7, 9, 11, and 13 within a slot, A terminal, wherein when the OCC is applied across the plurality of REs within the one symbol, the plurality of REs include subcarriers having subcarrier indices 1 to 7 or subcarrier indices 1, 3, 5, 7, 9, 11, and 13.

10. In claim 9, The size of the above one TB is determined based on the value obtained by dividing the size of the PUSCH by the length of the OCC, The length of the above OCC is indicated as 2 or 4 in the above setting information, terminal.

11. In claim 7, The above OCC is applied to the PUSCH by slot, the terminal.

12. In claim 7, the controller, It is further set to transmit terminal capability information to the above base station, The terminal capability information includes information indicating whether the terminal can apply the OCC to the PUSCH.

13. In a method performed by a base station in a wireless communication system, A step of transmitting configuration information for an orthogonal cover code (OCC) for a physical uplink shared channel (PUSCH) to a terminal (user equipment); and A step of receiving the PUSCH to which the OCC is applied based on the setting information from the terminal, A method in which the above OCC is applied across multiple symbols for one transport block (TB) or across multiple resource elements (REs) within one symbol.

14. In claim 13, When the OCC is applied across the plurality of symbols, the plurality of symbols include symbols having symbol indices 1 to 7 or symbol indices 1, 3, 5, 7, 9, 11, and 13 within a slot, A method in which, when the OCC is applied across the plurality of REs within the one symbol, the plurality of REs include subcarriers having subcarrier indices 1 to 7 or subcarrier indices 1, 3, 5, 7, 9, 11, and 13.

15. In a base station in a wireless communication system, transceiver; and including a controller coupled with the above transmitter and receiver, The above controller, Transmit configuration information for an orthogonal cover code (OCC) for a PUSCH (physical uplink shared channel) to a terminal (user equipment), From the terminal, the PUSCH to which the OCC is applied is set to be received based on the setting information, A base station in which the above OCC is applied across multiple symbols for one transport block (TB) or across multiple resource elements (REs) within one symbol.

Images