Method and apparatus for transmitting and receiving periodic signals 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 (UE) in a satellite communication system may comprise the steps of: receiving, from a base station, semi-persistent scheduling (SPS) higher signal information related to at least one of a downlink or an uplink; receiving, from the base station, an L1 signal for activating at least one of an SPS narrowband physical uplink shared channel (NPUSCH) or an SPS narrowband physical downlink shared channel (NPDSCH); and periodically transmitting and receiving, to and from the base station, at least one of the SPS NPUSCH or the SPS NPDSCH.

Description

Method and device for periodic signal transmission and reception 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 an apparatus capable of performing the same.

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

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

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

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

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

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

[0008] Accordingly, various attempts are being made to apply 5G communication systems (5th generation communication systems or 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 technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 3eG and IoT technologies.

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

[0010] The disclosed embodiment aims to provide a method and apparatus for periodic signal transmission and reception in a satellite communication system.

[0011] A method performed by user equipment (UE) in a satellite communication system according to one embodiment of the present disclosure may include: receiving semi-persistent scheduling (SPS) upper signal information related to at least one of a downlink or an uplink from a base station; receiving an L1 signal from the base station that activates at least one of a narrowband physical uplink shared channel (SPS NPUSCH) or a narrowband physical downlink shared channel (SPS NPDSCH); and periodically transmitting and receiving at least one of the SPS NPUSCH or the SPS NPDSCH with the base station.

[0012] A method performed by a base station in a satellite communication system according to one embodiment of the present disclosure may include: transmitting semi-persistent scheduling (SPS) upper signal information associated with at least one of a downlink or an uplink to a terminal; transmitting an L1 signal to the terminal that activates at least one of a narrowband physical uplink shared channel (SPS NPUSCH) or a narrowband physical downlink shared channel (SPS NPDSCH); and periodically transmitting and receiving at least one of the SPS NPUSCH or the SPS NPDSCH with the terminal.

[0013] User equipment (UE) in a satellite communication system according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor, wherein the at least one processor receives semi-persistent scheduling (SPS) upper signal information related to at least one of a downlink or an uplink from a base station, receives an L1 signal from the base station that activates at least one of a narrowband physical uplink shared channel (SPS NPUSCH) or a narrowband physical downlink shared channel (SPS NPDSCH), and may be configured to periodically transmit and receive at least one of the SPS NPUSCH or the SPS NPDSCH with the base station.

[0014] A base station in a satellite communication system according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor, wherein the at least one processor may be configured to transmit semi-persistent scheduling (SPS) upper signal information associated with at least one of a downlink or an uplink to a terminal, transmit an L1 signal to the terminal that activates at least one of an SPS NPUSCH (narrowband physical uplink shared channel) or an SPS NPDSCH (narrowband physical downlink shared channel), and periodically transmit and receive at least one of the SPS NPUSCH or the SPS NPDSCH with the terminal.

[0015] The disclosed embodiments provide an apparatus and method capable of effectively providing services in a mobile communication system.

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

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

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

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

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

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

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

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

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

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

[0026] FIG. 11 is a diagram illustrating a method for transmitting and receiving data in a wireless communication system according to one embodiment of the present disclosure, in consideration of a downlink data channel and a rate matching resource, between a base station and a terminal.

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

[0028] FIG. 13 is a drawing illustrating an example of a non-periodic CSI reporting method according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

[0037] FIG. 22 is a diagram showing a UL scheduling process according to one embodiment of the present disclosure.

[0038] FIG. 23 is a diagram showing a downlink scheduling process according to one embodiment of the present disclosure.

[0039] FIG. 24 is a diagram showing the activation and deactivation process of SPS NPDSCH according to one embodiment of the present disclosure.

[0040] FIG. 25 is a diagram showing the activation and deactivation process of SPS NPUSCH according to one embodiment of the present disclosure.

[0041] FIG. 26 is a diagram showing the process of simultaneously activating and deactivating SPS NPUSCH and SPS NPDSCH in a single DCI format according to one embodiment of the present disclosure.

[0042] FIG. 27 is a diagram showing a terminal monitoring NPDCCH process according to one embodiment of the present disclosure.

[0043] FIG. 28 is a flowchart showing the process of a terminal transmitting and receiving SPS information in an IoT NTN according to one embodiment of the present disclosure.

[0044] FIG. 29 is a flowchart showing the process of a terminal adaptively searching for control information according to one embodiment of the present disclosure. FIG. 30 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

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

[0046] FIG. 32 is a block diagram illustrating the internal structure of a satellite according to one embodiment of the present disclosure.

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

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

[0049] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

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

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

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

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

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

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

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

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

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

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

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

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

[0062] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place 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.

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

[0064] [NR Time-Frequency Resources]

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

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

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

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

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

[0070] [Table 1]

[0071]

[0072] [Bandwidth Section (BWP)]

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

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

[0075] FIG. 3 may show an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the following information for each bandwidth portion. The information for each bandwidth portion may be represented as shown in Table 2.

[0076] [Table 2]

[0077]

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

[0079] According to some embodiments, prior to the Radio Resource Control (RRC) connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a PDCCH can be transmitted to receive system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for Control Resource Set #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

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

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

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

[0083] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz can be very inefficient in terms of power consumption. To reduce the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

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

[0085] [Bandwidth Section (BWP) Change]

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

[0087] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies requirements for the required delay time (TBWP) for bandwidth portion changes, which can be defined, for example, as follows.

[0088] [Table 3]

[0089]

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

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

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

[0093] [SS / PBCH Block]

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

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

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

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

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

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

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

[0101] [PDCCH: DCI related]

[0102] Next, we can specifically explain Downlink Control Information (DCI) in a 5G system.

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

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

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

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

[0107] [Table 4]

[0108]

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

[0110] [Table 5]

[0111]

[0112]

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

[0114] [Table 6]

[0115]

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

[0117] [Table 7]

[0118]

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

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

[0121] FIG. 4 is a diagram illustrating an example of setting a control resource set (CORESET) of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0122] Referring to FIG. 4, FIG. 4 illustrates an example in which two control areas (control area #1 (401), control area #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) on the frequency axis and a slot (420) on the time axis. The control areas (401, 402) can be set in a specific frequency resource (403) within the entire terminal bandwidth part (410) on the frequency axis. On the time axis, they can be set with one or more OFDM symbols and can be defined as the control area length (Control Resource Set Duration, 404). Referring to the example illustrated in FIG. 4, control area #1 (401) is set to a control area length of 2 symbols, and control area #2 (402) is set to a control area length of 1 symbol.

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

[0124] [Table 8]

[0125]

[0126]

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

[0128] 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. According to FIG. 5, the basic unit of time and frequency resources constituting the control channel can be called a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

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

[0130] The basic unit of the downlink control channel, namely the REG (503) shown in FIG. 5, may include both the REs to which the DCI is mapped and the DMRS (505), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 5, three DMRS (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 the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode at a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

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

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

[0133] [Table 9]

[0134]

[0135]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing.

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

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

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

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

[0159] [Table 10]

[0160]

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

[0162] [Mathematical Formula 1]

[0163]

[0164]

[0165]

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

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

[0168] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., the parameters in Table 10), the set of search space sets monitored by the terminal at each point in time may vary. 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 may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0169] [PDCCH: span]

[0170] A terminal can perform terminal capability reporting for each subcarrier interval when it has multiple PDCCH monitoring locations within a slot, and in this case, the concept of a Span can be used. A Span refers to a sequence of consecutive symbols within a slot that allows the terminal to monitor a PDCCH, and each PDCCH monitoring location can be within one Span. A Span can be expressed as (X,Y), where x represents the minimum number of symbols that must be separated between the first symbols of two consecutive Spans, and Y represents the number of consecutive symbols within one Span that allow for PDCCH monitoring. In this case, the terminal can monitor a PDCCH within a Span in a range of Y symbols from the first symbol of the Span.

[0171] FIG. 6 is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system according to one embodiment of the present disclosure may have a plurality of PDCCH monitoring locations within a slot. The Span can be (X,Y) = (7,4), (4,3), or (2,2), and each of the three cases is represented as (6-00), (6-05), and (6-10) in FIG. 6. For example, (6-00) can represent a case in which there are two Spans within a slot that can be represented as (7,4). The spacing between the first symbols of the two Spans is represented as X=7, and PDCCH monitoring locations may exist within a total of Y=3 symbols from the first symbol of each Span, and it can indicate that search spaces 1 and 2 exist respectively within Y=3 symbols. As another example, (6-05) describes a case where there are a total of 3 spans in the slot that can be expressed as (4,3), and the distance between the second and third spans can be shown to be X'=5 symbols greater than X=4.

[0172] [PDCCH: Terminal Capability Report]

[0173] The slot locations where the aforementioned common search space and terminal-specific search space are located are indicated by the monitoringSymbolsWithinSlot parameter in Table 13-1, and the symbol locations within the slot can be 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).

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

[0175] [Table 11]

[0176]

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

[0178] [Table 12]

[0179]

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

[0181] [Table 13]

[0182]

[0183]

[0184]

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

[0186] [QCL, TCI state]

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

[0188] [Table 14]

[0189]

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

[0191] The above QCL relationship can be set for the terminal through the RRC parameter 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 for the terminal and provide up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS that references the ID of the TCI state, i.e., the target RS. At this time, each QCL information (QCL-Info) included in each of the above TCI states may include the serving cell index and BWP index of the reference RS pointed to by the QCL information, the type and ID of the reference RS, and the QCL type as shown in [Table 14] above.

[0192] [Table 15]

[0193]

[0194] 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. Referring to FIG. 7, the base station can transmit information about N different beams to a terminal through N different TCI states. For example, as in FIG. 7, when N=3, the base station can notify that antenna ports referencing the different TCI states 700, 705, or 710 are associated with different spatial Rx parameters, i.e., different beams, by setting the qcl-Type2 parameters included in the three TCI states (700, 705, 710) to QCL type D and associating them with CSI-RS or SSB corresponding to different beams.

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

[0196] [Table 16] shows valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). The TRS mentioned above may refer to an NZP CSI-RS in which the repetition parameter is not set and trs-Info is set to true. Setting 3 in Table 16 may be used for aperiodic TRS. [Table 16] may include valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS).

[0197] [Table 16]

[0198]

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

[0200] [Table 17]

[0201]

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

[0203] [Table 18]

[0204]

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

[0206] [Table 19]

[0207]

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

[0209] [Table 20]

[0210]

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

[0212] [PDCCH: TCI state related]

[0213] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in Table 21 below. The fourth row of Table 21 represents the combinations assumed by the terminal prior to RRC setup, and setup after RRC is not possible.

[0214] [Table 21]

[0215]

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

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

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

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

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

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

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

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

[0224] [PDCCH: QCL prioritization rule related]

[0225] The following describes in detail the QCL priority determination operation for PDCCH.

[0226] A terminal operates with carrier aggregation within a single cell or band, and when multiple control resource sets existing within the active bandwidth portion of a single or multiple cells overlap in time during a specific PDCCH monitoring interval while having the same or different QCL-TypeD characteristics, the terminal selects a specific control resource set according to the QCL priority determination operation and can monitor control resource sets having the same QCL-TypeD characteristics as that 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 QCL priority may be as follows.

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

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

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

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

[0231] FIG. 12 is a diagram illustrating a method for selecting a receivable set of control resources by considering priority when a terminal receives a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. For example, the terminal may be configured to receive a plurality of control resource sets that overlap in time during a specific PDCCH monitoring section (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 section, within the first bandwidth section (1200) of cell 1, there may be a first control resource set (1215) connected to the first common search section, and within the first bandwidth section (1205) of cell 2, there may be a first control resource set (1220) connected to the first common search section and a second control resource set (1225) connected to the second terminal-specific search section. Control resource sets (1215) and (1220) have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 1, and control resource set (1225) can have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 2. Therefore, if reference 1 is applied to the corresponding PDCCH monitoring section (1210), all other control resource sets having a reference signal of QCL-TypeD, such as the first control resource set (1215), can be received. Therefore, the terminal can receive control resource sets (1215) and (1220) in the corresponding PDCCH monitoring section (1210). As another example, the terminal may be configured to receive multiple sets of control resources that overlap in time during a specific PDCCH monitoring interval (1240), and these multiple sets of control resources may be connected to a common search space or a terminal-specific search space for multiple cells.Within the PDCCH monitoring section, within the first bandwidth section (1230) of cell 1, there may be a first control resource set (1245) connected to a specific search section of terminal 1 and a second control resource set (1250) connected to a specific search section of terminal 2, and within the first bandwidth section (1235) of cell 2, there may be a first control resource set (1255) connected to a specific search section of terminal 1 and a second control resource set (1260) connected to a specific search section of terminal 3. Control resource sets (1245) and (1250) have a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 1 and QCL-TypeD, control resource set (1255) has a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD, and control resource set (1260) can have a relationship with the second CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD. However, if criterion 1 is applied to the corresponding PDCCH monitoring section (1240), there is no common search section, so the next criterion, criterion 2, can be applied. If criterion 2 is applied to the corresponding PDCCH monitoring section (1240), all other control resource sets having a reference signal of QCL-TypeD, such as control resource set (1245), can be received. Therefore, the terminal can receive control resource sets (1245) and (1250) in the corresponding PDCCH monitoring section (1240).

[0232] [Regarding Rate Matching / Puncturing]

[0233] In the following, the rate matching operation and puncturing operation may be described in detail.

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

[0235] Rate Matching Operation

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

[0237] The terminal can determine Resource A and Resource B from scheduling information regarding Symbol Sequence A from the base station, and thereby determine Resource C, which is the area where Resource A and Resource B overlap. The terminal can receive Symbol Sequence A by assuming that Symbol Sequence A was transmitted by mapping it to the remaining area of ​​Resource A, excluding Resource C. For example, if Symbol Sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol 4}, Resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and Resource B is {Resource #3, Resource #5}, the terminal can receive Symbol Sequence A by assuming that it was sequentially mapped to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3}, which corresponds to Resource C. Consequently, the terminal can perform a series of subsequent reception operations by assuming that Symbol Sequence {Symbol #1, Symbol #2, Symbol #3} was transmitted by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0238] Puncturing action

[0239] If there is a resource C corresponding to an area overlapping with resource B among all resources A to which the base station intends to transmit symbol sequence A to a terminal, 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 in the remaining resource area of ​​resource A excluding resource C. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the base station can map symbol sequence A {Symbol #1, Symbol #2, Symbol #3, Symbol #4} to resource A {Resource #1, Resource #2, Resource #3, Resource #4} respectively, and can transmit only the symbol sequence {Symbol #1, Symbol #2, Symbol #4} corresponding to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3} corresponding to resource C, and may not transmit {Symbol #3} mapped to {Resource #3} corresponding to resource C. Consequently, the base station can map and transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #4} to {Resource #1, Resource #2, Resource #4} respectively.

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

[0241] In the following, a method for configuring rate matching resources may be described for the purpose of rate matching in a 5G communication system. Rate matching may mean that the size of a signal is adjusted by considering the amount of resources available to transmit the signal. For example, rate matching of a data channel may mean that the data channel is mapped to a specific time and frequency resource range so that the size of the data is adjusted accordingly without transmission.

[0242] FIG. 11 is a diagram illustrating a method for transmitting and receiving data in a wireless communication system according to one embodiment of the present disclosure, in consideration of a downlink data channel and a rate matching resource, between a base station and a terminal.

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

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

[0245] In 5G, granularity of “RB symbol level” and “RE level” can be supported by setting the aforementioned rate matching resources to the terminal. More specifically, the following setting method can be followed.

[0246] RB symbol level

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

[0248] As a Reserved Resource within the bandwidth portion, a resource may be included in which the time and frequency resource domains of the said Reserved Resource are set as a combination of an RB level bitmap and a symbol level bitmap along the frequency axis. The said Reserved Resource may span across 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 be additionally set.

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

[0250] RE level

[0251] The terminal can receive the following settings through upper-layer signaling.

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

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

[0254] [Regarding LTE CRS rate match]

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

[0256] In Rel-15 NR, the lte-CRS-ToMatchAround parameter allows for the configuration of one CRS pattern per serving cell. In Rel-16 NR, this function has been extended to enable the configuration of multiple CRS patterns per serving cell. More specifically, for a Single-TRP (transmission and reception point) configured terminal, one CRS pattern can be configured per LTE carrier, and for a Multi-TRP configured terminal, two CRS patterns can be configured per LTE carrier. For example, for a Single-TRP configured terminal, up to three CRS patterns per serving cell can be configured through the lte-CRS-PatternList1-r16 parameter. As another example, for a multi-TRP configured terminal, CRS can be configured per TRP. In other words, the CRS pattern for TRP1 is set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are configured as described above, whether to apply both the CRS patterns of TRP1 and TRP2 or only the CRS pattern of a single TRP 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 a single TRP is applied, whereas otherwise, both CRS patterns of the two TRPs can be applied.

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

[0258] [Table 22]

[0259]

[0260]

[0261] [Table 23]

[0262]

[0263] [PDSCH: Processing Time]

[0264] Next, the PDSCH processing procedure time can be described. When a base station schedules a terminal to transmit a PDSCH using DCI format 1_0, 1_1, or 1_2, the terminal may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated via DCI (modulation / demodulation and coding instruction index (MCS), information related to the demodulation reference signal, time and frequency resource allocation information, etc.). In NR, the PDSCH processing time has been defined taking this into account. The terminal's PDSCH processing time may follow [Equation 2] below.

[0265] [Mathematical Formula 2]

[0266]

[0267] In Tproc,1 described above with mathematical formula 2, each variable can have the following meanings.

[0268] - N1: The number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the terminal's capability. If the terminal processing capability is reported as 1 according to the terminal's capability report, it may have the value of [Table 24], and if the terminal processing capability is reported as 2 and the availability of terminal processing capability 2 is set through upper layer signaling, it may have the value of [Table 25]. Numerology μ may correspond to the minimum value among μPDCCH, μPDSCH, and μUL to maximize the above Tproc,1, and μPDCCH, μPDSCH, and μUL may represent the numerology of the PDCCH that scheduled the PDSCH, the numerology of the scheduled PDSCH, and the numerology of the uplink channel to which HARQ-ACK (hybrid automatic repeat request-acknowledge) will be transmitted, respectively. [Table 24] may represent the PDSCH processing time when the PDSCH processing capability is 1.

[0269] [Table 24]

[0270]

[0271] [Table 25] shows the PDSCH processing time when the PDSCH processing capability is 2.

[0272] [Table 25]

[0273]

[0274] - κ: 64

[0275] - Text: If the terminal uses a shared spectrum channel access method, the terminal can calculate Text and apply it during PDSCH processing time. Otherwise, Text can be assumed to be 0.

[0276] - If l1, representing the PDSCH DMRS position value, is 12, then N1,0 of [Table 24] or [Table 25] has a value of 14, otherwise it has a value of 13.

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

[0278] - d2: If a PUCCH with a higher priority index overlaps with a PUCCH or PUSCH with a lower priority index in time, the d2 of the PUCCH with the higher priority index can be set to the value reported from the terminal. Otherwise, d2 is 0.

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

[0280] If L ≥ 7, then d1,1 = 0.

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

[0282] - If L = 3, then d1,1 = min (d, 1).

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

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

[0285] If L ≥ 7, then d1,1 = 0.

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

[0287] - When L = 2,

[0288] - If the scheduled PDCCH exists within a CORESET consisting of 3 symbols and the CORESET and the scheduled PDCCH have the same starting symbol, then d1,1 = 3.

[0289] - Otherwise, d1,1 = d.

[0290] - For a terminal that supports capability 2 within a given serving cell, the PDSCH processing time according to the terminal processing capability 2 can be applied when the terminal has the upper layer signaling processingType2Enabled set to enable for the cell.

[0291] If the position of the first uplink transmission symbol of a PUCCH containing HARQ-ACK information (where K1-, defined as the transmission time of the HARQ-ACK, the PUCCH resources used for HARQ-ACK transmission, and timing advance effects may be considered) does not begin before the first uplink transmission symbol that occurs after a time of Tproc,1 from the last symbol of the PDSCH, the terminal may transmit a valid HARQ-ACK message. That is, the terminal may transmit a PUCCH containing HARQ-ACK only if 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 may be used for both standard and extended CP cases. If the PDSCH consists of two PDSCH transmission positions within one slot, d1,1 may be calculated based on the first PDSCH transmission position within that slot.

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

[0293] In the case of cross-carrier scheduling where μPDCCH, the numerology through which the PDCCH scheduled next is transmitted, and μPDSCH, the numerology through which the PDSCH scheduled via that PDCCH is transmitted, are different from each other, N-pdsch, which is the terminal's PDSCH reception readiness time defined for the time interval between the PDCCH and the PDSCH, can be described.

[0294] If μPDCCH < μPDSCH, the scheduled PDSCH cannot be transmitted before the first symbol of the slot following the Npdsch symbol from the last symbol of the PDCCH that scheduled the PDSCH. The transmitted symbol of the PDSCH may include DM-RS.

[0295] If μPDCCH > μPDSCH, the scheduled PDSCH may be transmitted starting from the Npdsch symbol after the last symbol of the PDCCH that scheduled the PDSCH. The transmitted symbol of the PDSCH may include DM-RS. [Table 26] may show the Npdsch according to the scheduled PDCCH subcarrier interval.

[0296] [Table 26]

[0297]

[0298] [Regarding SRS]

[0299] Next, a method for estimating the uplink channel using the transmission of the terminal's Sounding Reference Signal (SRS) can be described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink BWP, and may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.

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

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

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

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

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

[0305] The terminal can understand that the SRS resources included in the set of SRS resource indices referenced in the SRS resource set follow the information set in the SRS resource set.

[0306] Additionally, the base station and the terminal may 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 may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Furthermore, the individual configuration information for the SRS resource may include the time-axis transmission setting of the SRS resource, which may be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. This may be restricted to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

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

[0308] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to enable an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the enabled SRS resource set. The SRS resource set enabled via MAC CE signaling may be limited to an SRS resource set where resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

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

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

[0311] [Table 27]

[0312]

[0313]

[0314] The spatialRelationInfo setting information in [Table 27] above is intended to apply the beam information of a reference signal to the beam used for SRS transmission by referencing a single reference signal. For example, the spatialRelationInfo setting may include information such as that shown in [Table 28] below.

[0315] [Table 28]

[0316]

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

[0318] [PUSCH: Regarding transmission method]

[0319] Next, the scheduling method for PUSCH transfers can be described. PUSCH transfers can be dynamically scheduled by UL grants within the DCI, or operated by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transfers can be provided in DCI format 0_0 or 0_1.

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

[0321] [Table 29]

[0322]

[0323]

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

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

[0326] [Table 30]

[0327]

[0328]

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

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

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

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

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

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

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

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

[0337] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal does not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

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

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

[0340] [PUSCH: Preparation Process Time]

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

[0342] [Mathematical Formula 3]

[0343]

[0344] In Tproc,2 described above in mathematical formula 3, each variable can have the following meanings.

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

[0346] [Table 31]

[0347]

[0348] [Table 32]

[0349]

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

[0351] - κ: 64

[0352] - μ: or Among them, it follows the value where Tproc,2 becomes larger. represents the numerology of the downlink through which a PDCCH containing a DCI that schedules the PUSCH is transmitted, and can refer to the numerology of the uplink through which PUSCH is transmitted.

[0353] - Tc: , , has.

[0354] - d2,2: Follows the BWP switching time if the DCI scheduling PUSCH directs BWP switching, and 0 otherwise.

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

[0356] - Text: If the terminal uses a shared spectrum channel access method, the terminal can calculate Text and apply it during the PUSCH preparation time. Otherwise, Text can be assumed to be 0.

[0357] - Tswitch: If the uplink switching interval is triggered, Tswitch can be assumed to be the switching interval time. Otherwise, it can be assumed to be 0.

[0358] When the base station and the terminal consider the time-axis resource mapping information of the PUSCH scheduled via the DCI and the influence of the uplink-downlink timing advance, they may determine that the PUSCH preparation time is insufficient if the first symbol of the PUSCH starts before the first uplink symbol where the CP begins after Tproc,2, starting from the last symbol of the PDCCH that includes the DCI scheduling the PUSCH. If this is not the case, the base station and the terminal may determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only when the preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the preparation time is insufficient.

[0359] [PUSCH: Regarding repetitive transmission]

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

[0361] PUSCH Repeated Transmission Type A

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

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

[0364] PUSCH Repeated Transmission Type B

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

[0366] Based on the start symbol and length of the uplink data channel configured first, the nominal repetition of the uplink data channel can be determined as follows. The slot where the nth nominal repetition starts is The symbol given by and starting in that slot is It is given by. The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is It is given by, where n=0,…, numberofrepetitions-1 and S represents the starting symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel. indicates the slot where the PUSCH transmission starts. Indicates the number of symbols per slot.

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

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

[0369] FIG. 14 is a diagram illustrating an example of PUSCH repeat transmission type B in a wireless communication system according to one embodiment of the present disclosure. A terminal may set the start symbol S of the uplink data channel to 0 and the length L of the uplink data channel to 14, and may set the number of repeat transmissions to 16. In this case, nominal repetitions are indicated in 16 consecutive slots (1401). Subsequently, the terminal may determine that the symbol set as a downlink symbol in each nominal repetition (1401) is an invalid symbol. Additionally, the terminal may determine that the 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 a single slot, they are set as actual repetitions and transmitted (1403).

[0370] In addition, for PUSCH repeated transmissions, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmissions that cross slot boundaries and configured grant-based PUSCH transmissions.

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

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

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

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

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

[0376] [PUSCH: Frequency Hopping Process]

[0377] In the following, frequency hopping of the uplink data channel (Physical Uplink Shared Channel; PUSCH) in a 5G system can be explained in detail.

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

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

[0380] [Mathematical Formula 4]

[0381]

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

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

[0384] [Mathematical Formula 5]

[0385]

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

[0387] Next, the inter-repetition frequency hopping method supported by PUSCH repeat transmission type B transmits the resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. The index of the starting RB, RBstart(n), in the frequency domain for one or more actual repetitions within the nth nominal repetition can follow [Equation 6] below.

[0388] [Mathematical Formula 6]

[0389]

[0390] In mathematical equation 6, n is the index of the nominal repetition, represents the RB offset between two hops through the upper layer parameter.

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

[0392] In the following, methods for measuring and reporting channel states in a 5G communication system may be described in detail. Channel state information (CSI) may include channel quality information (CQI), precoding matrix index (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSSBRI), layer indicator (LI), rank indicator (RI), and / or L1-RSRP (Reference Signal Received Power). The base station may control time and frequency resources for the aforementioned CSI measurement and reporting by the terminal.

[0393] For the aforementioned CSI measurement and reporting, the terminal may receive setting information for N (≥1) CSI reports (CSI-ReportConfig), setting information for M (≥1) RS transmission resources (CSI-ResourceConfig), and 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 more specifically as described in [Table 33] to [Table 39] below. [Table 33] may represent CSI-ReportConfig.

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

[0019] , clause 5.2.1.

[0395] [표 33]

[0396]

[0397]

[0398]

[0399]

[0400] [표 34]는 CSI-ResourceConfig을 나타낼 수 있다.

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

[0402] [표 34]

[0403]

[0404]

[0405] [Table 35] can represent NZP-CSI-RS-ResourceSet.

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

[0407] [Table 35]

[0408]

[0409]

[0410] [Table 36] can represent CSI-SSB-ResourceSet.

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

[0412] [Table 36]

[0413]

[0414] [Table 37] can represent CSI-IM-ResourceSet.

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

[0416] [Table 37]

[0417]

[0418] [Table 38] can represent CSI-AperiodicTriggerStateList.

[0419] The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state. Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state.

[0420]

[0421] [표 39]는 CSI-SemiPersistentOnPUSCH-TriggerStateList을 나타낼 수 있다.

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

[0019] , clause 5.2.

[0423] [표 39]

[0424]

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

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

[0427] CSI-IM resources for interference measurement

[0428] NZP CSI-RS resources for interference measurement

[0429] NZP CSI-RS resources for channel measurement

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

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

[0432] [Table 40]

[0433]

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

[0435] If all bits of the CSI request field are 0, this may mean that a CSI report is not requested.

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

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

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

[0439] [Table 41]

[0440]

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

[0442] FIG. 13 is a drawing illustrating an example of a non-periodic CSI reporting method according to one embodiment of the present disclosure.

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

[0444] [Table 42]

[0445]

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

[0447] In one example (1310) of FIG. 13, the terminal can monitor the PDCCH (1311) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (1315). The terminal can obtain resource information for the CSI-RS (1312) to be measured from the received CSI request indicator. One 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 the slot (corresponding to slot 0 (1316) in FIG. 13) that received the DCI format 0_1 ​​triggering a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (1315).

[0448] Aperiodic CSI reports may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI reports are transmitted via PUSCH, they may be multiplexed with the transport block. For multiplexing, a CRC is inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The above 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 during the multiplexing of CSI part 1 or CSI part 2 included in the aperiodic CSI reports can be calculated as shown in [Table 43] below.

[0449] [Table 43]

[0450]

[0451]

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

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

[0454] [Regarding Terminal Capability Reporting]

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

[0456] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions whenever necessary.

[0457] In the above step, a terminal that has received a request from a base station to report UE capability can configure terminal capability according to the RAT type and band information requested from the base station. The method for a terminal to configure UE capability in an NR system is summarized below.

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

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

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

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

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

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

[0464] [CA / DC Related]

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

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

[0467] The main functions of NR SDAP (S25, S70) may include some of the following functions.

[0468] User data transfer function (transfer of user plane data)

[0469] Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0470] Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0471] A function that maps reflective QoS flow to the data bearer for the uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

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

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

[0474] Header compression and decompression (ROHC only)

[0475] User data transfer function (Transfer of user data)

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

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

[0478] Reordering function (PDCP PDU reordering for reception)

[0479] Duplicate detection function (Duplicate detection of lower layer SDUs)

[0480] Retransmission of PDCP SDUs

[0481] Encryption and decryption functions (Ciphering and deciphering)

[0482] Timer-based SDU discard in uplink.

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

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

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

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

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

[0488] ARQ function (Error Correction through ARQ)

[0489] Concatenation, segmentation and reassembly of RLC SDUs

[0490] Re-segmentation of RLC data PDUs

[0491] Reordering function (Reordering of RLC data PDUs)

[0492] Duplicate detection

[0493] Error detection function (Protocol error detection)

[0494] RLC SDU discard function

[0495] RLC re-establishment function

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

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

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

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

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

[0501] - Scheduling information reporting function

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

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

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

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

[0506] - Transport format selection function

[0507] -Padding

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

[0509] The above wireless protocol structure may vary in detail depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal may use a protocol structure that has a single structure up to the 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 Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure that has a single structure up to the RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

[0510] Referring to the descriptions regarding PDCCH and beam settings mentioned above, current Rel-15 and Rel-16 NR do not support repeated PDCCH transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present invention provides a method for repeated PDCCH transmission through multiple transmission points (TRPs) to improve the PDCCH reception reliability of a terminal. Specific methods can be described in detail in the following examples.

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

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

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

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

[0515] [Regarding NC-JT]

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

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

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

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

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

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

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

[0523] Referring to FIG. 16, an example (N000) of a Coherent Joint Transmission (C-JT) that supports coherent precoding between each cell, TRP or / and beam can be illustrated.

[0524] 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 in 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) can each transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal can receive one DCI information for receiving a single PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

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

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

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

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

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

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

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

[0532] Case #2 (N105) illustrates a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, wherein control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted separately, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

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

[0534] In the aforementioned case #2, the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information elements included in sDCI, but since the receiving performance of sDCI becomes superior to that of nDCI, the probability of coverage difference between DCIs occurring may be reduced.

[0535] Case #3 (N110) illustrates a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and a single 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.

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

[0537] In case #3 (N110), the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information element included in the sDCI, but the reception performance of the sDCI can be adjusted, and the complexity of the terminal's DCI blind decoding may be reduced compared to case #1 (N100) or case #2 (N105).

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

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

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

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

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

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

[0544] 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 terminal's RRC parameters based on this. For the upper layer configuration, the terminal can utilize UE capability parameters, such as tci-StatePDSCH. Here, UE capability parameters, such as 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, or 128 in FR1, and to 64 or 128 in FR2. Among the set number, up to 8 states can be set, which can be indicated by the 3 bits of the TCI field of the DCI via a MAC CE message. The maximum value 128 may refer to the value indicated by maxNumberConfiguredTCIstatesPerCC within the tci-StatePDSCH parameter included in the terminal's capability signaling. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to beamforming instructions or beamforming change commands for at least one PDSCH in one TRP.

[0545] [Multi-DCI-based Multi-TRP]

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

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

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

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

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

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

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

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

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

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

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

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

[0558] [PHR]

[0559] FIG. 18 illustrates a procedure for a base station to control the transmit power of a terminal in a cellular system. In step 18-10 of FIG. 18, a terminal within the base station's coverage can perform downlink synchronization with the base station and obtain system information. According to some embodiments, downlink synchronization can be performed via 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 obtain system information. In step 18-15, the terminal can perform uplink synchronization with the base station through a random access procedure and establish a Raido Resource Control (RRC) connection. In the random access procedure, the terminal can transmit a random access preamble and message 3 (msg3) to the base station via the uplink. At this time, uplink transmit power control can be performed during the transmission of the random access preamble and message 3. Specifically, the terminal may control uplink transmit power by receiving parameters for uplink transmit power control from the base station via acquired system information, e.g., SIB, or by using agreed parameters. In another embodiment of the present disclosure, the terminal may measure the Reference Signal Received Power (RSRP) from a path attenuation estimation signal transmitted by the base station and estimate the downlink path attenuation value as in [Equation 7]. Then, based on the estimated path attenuation value, the terminal may set the uplink transmit power value for transmitting a random access preamble and message 3.

[0560] [Mathematical Formula 7]

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

[0562] In [Equation 7], the transmission power of the base station signal may refer 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 CRS (Cell-specific Reference Signal) or an SSB (Synchronization Signal Block). If the path attenuation estimation signal is a CRS (Cell-specific Reference Signal), the transmission power of the base station signal refers to the transmission power of the CRS and can be transmitted to the terminal via the referenceSignalPower parameter of the system information. If the path attenuation estimation signal is an SSB (Synchronization Signal Block), the transmission power of the base station signal refers to the transmission power of the DMRS (DeModulation Reference signal) transmitted to the SSS (Secondary Synchronization Signal) and PBCH, and can be transmitted to the terminal via the ss-PBCH-BlockPower parameter of the system information. In steps 18-20, the terminal may receive RRC parameters for uplink transmit power control from the base station via UE-specific RRC or common RRC. The received transmit power control parameters may differ depending on the type of uplink channel and the type of signal transmitted over the uplink. That is, the transmit power control parameters applied to the transmission of the uplink control channel (PUCCH: physical uplink control channel), the uplink data channel (PUSCH: physical uplink shared channel), and the sounding reference signal (SRS: sounding reference signal) may differ.Additionally, as previously explained, transmit power control parameters received by the terminal via the SIB from the base station prior to the RRC connection establishment, or transmit power control parameters used by the terminal as pre-agreed values ​​prior to the RRC connection establishment, may be included in the RRC parameters transmitted from the base station after the RRC connection establishment. The terminal may use the RRC parameter values ​​received from the base station after the RRC connection establishment for uplink transmit power control. In steps 18-25, the terminal may receive a path attenuation estimation signal from the base station. More specifically, after the terminal's RRC connection establishment, the base station may configure the CSI-RS (Channel State Information-Reference Signal) with the terminal's path attenuation estimation signal. In this case, the base station may transmit information regarding the transmit power of the CSI-RS to the terminal via the powerControlOffsetSS parameter of the UE dedicated RRC information. Here, powerControlOffsetSS may represent the transmit power difference (offset) between the SSB and the CSI-RS. In steps 18-30, the terminal can estimate the downlink path attenuation value and set the uplink transmit power value. More specifically, the terminal can measure the downlink RSRP using CSI-RS and estimate the downlink path attenuation value through [Equation 1] using information on the transmit power of the CSI-RS received from the base station. Then, based on the estimated path attenuation value, the terminal can set the uplink transmit power value for PUCCH, PUSCH, and SRS transmission. In step 18-35, the terminal can provide power headroom reporting (PHR) to the base station. Power headroom may refer to the difference between the terminal's current transmit power and the terminal's maximum output power.In steps 18-40, the base station can optimize system operation based on the reported power headroom. For example, if the power headroom value reported by a specific terminal to the base station is positive, the base station can increase system yield by allocating more resources (RB: Resource Block) to that terminal. In steps 18-45, the terminal can receive a transmission power control command (TPC) from the base station. For example, if the power headroom value reported by a specific terminal to the base station is negative, the base station can allocate fewer resources to that terminal or reduce the terminal's transmission power via the transmission power control command (TPC). This can increase system yield or reduce unnecessary power consumption by the terminal. In steps 18-50, the terminal can update its transmission power based on the TPC command. At this time, the TPC command may be transmitted to the terminal via a UE-specific DCI or a group common DCI. Thus, the base station can dynamically control the terminal's transmission power through the TPC command. In steps 18-55, the terminal can perform uplink transmission based on the updated transmit power.

[0563] [PUSCH power control]

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

[0565] [Mathematical Formula 8]

[0566]

[0567] In [Equation 8] is the maximum transmission power set for the terminal for carrier f of serving cell c at time i of PUSCH transmission. is a reference setting transmission power setting value based on the active uplink bandwidth part (BWP) b of the carrier f of the serving cell c, and has different values ​​depending on various transmission types j. It can have various values ​​depending on whether the PUSCH transmission is message 3 PUSCH for random access, or whether the PUSCH is configured grant PUSCH, or scheduled PUSCH. can mean the frequency size assigned to PUSCH. represents the degree of compensation ratio for the path loss of the UL BWP b of the carrier f of the serving cell c, and can be set by the upper signal and may have different values ​​depending on j. is an estimated value of the downlink path loss of the UL BWP b of the carrier f of the serving cell c, and the value measured through a reference signal in the activated downlink bandwidth interval may be used. The reference signal may be an SS / PBCH block or a CSI-RS. The downlink path loss may be calculated as described above in [Equation 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 [Equation 7]. Depending on whether the upper signal is set, the terminal can calculate the path attenuation based on a reference signal resource associated with the SS / PBCH block or CSI-RS. The reference signal resource can select one of several sets of reference signal resources by the upper signal or L1 signal, and the terminal can calculate the path attenuation based on that reference signal resource. is a value determined by the MCS (Modulation and Coding Scheme) value of the PUSCH at time i of the PUSCH transmission of the carrier f of the serving cell c and the UL BWP b. The power value can be dynamically adjusted by the TPC command as a power adjustment adaptive value. In addition, it may be possible to determine a specific value according to [Table 44] below.

[0568] [Table 44]

[0569]

[0570] The TPC command is divided into accumulated and absolute modes, and one of the two modes can be determined by the upper signal. The accumulated mode is a form in which the currently determined power regulation adaptation value is accumulated with the value indicated by the TPC command, and can be increased or decreased according to the TPC command. It has a relationship with is the value specified in the TPC command. In absolute mode, the value is determined by the TPC command regardless of the currently determined power regulation adaptation value, and It has the relationship. [Table 45] below shows the values ​​that can be indicated by the TPC command. [Table 45] can represent the TPC command.

[0571] [Table 45]

[0572]

[0573] [PUCCH power control]

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

[0575] [Mathematical Formula 9]

[0576]

[0577] In [Equation 9] is a reference setting transmission power setting value, and various transmission types It has different values ​​depending on the, and the value may be changed by higher signals such as RRC or MAC CE. If the value is changed by MAC CE, the terminal can determine that the value is applied starting from the k + koffset slot if the slot in which the HARQ-ACK was transmitted for the PDSCH that received the MAC CE is k. koffset has different values ​​depending on the subcarrier interval, and for example, it can be 3ms. is the size of the frequency resource area allocated to PUCCH. is an estimated path attenuation value of the terminal, and as described in [Equation 7], the terminal can calculate it based on a specific reference signal among various CSI-RS or SS / PBCH depending on whether the upper signal is set and the type thereof. For repeated transmission PUCCHs, the same This can be applied. For repeated transmission PUCCHs, the same It can be applied.

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

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

[0580] Except for that, the HARQ-ACK codebook determination method according to the method described above is followed.

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

[0582] [pseudo-code 1 start]

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

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

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

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

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

[0588] [End of pseudo-code 1]

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

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

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

[0592] [Table 46]

[0593]

[0594] [Table 46] is a time resource allocation table in which the terminal operates by default before receiving time resource allocation via a separate RRC signal. For reference, in addition to separately indicating the row index value via RRC, the PDSCH time resource allocation value can be determined by the terminal common RRC signal, dmrs-TypeA-Position. In Table 46 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 termination symbol of the scheduled PDSCH, and the order column may refer to the code position value located within a specific codebook in the quasi-static HARQ-ACK codebook. This table can be applied to time resource allocation in DCI format 1_0 of the PDCCH common seek area.

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

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

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

[0598] Step 3: Step 2 can be repeated, and the order value can be incremented to display. For example, in Table 46, the PDSCH assignment value that terminates first among the row indices not displayed in the order column can be identified. In Table 46, this could be the row with row index 6 and a dmrs-TypeA-Position value of 3. Other row indices that overlap with that row index by at least one symbol can be indicated as 3x in the order column.

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

[0600] In the order column of [Table 46], the maximum value of order represents the HARQ-ACK codebook size of the corresponding slot, and the order value may represent the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the corresponding scheduled PDSCH is located. For example, row index 16 in Table 46 may mean that it exists at the 2nd code position in a semi-static HARQ-ACK codebook of size 3. If MA,c is the set of occasions for candidates PDSCH receptions in the serving cell c, the terminal transmitting the HARQ-ACK feedback can obtain MA,c through [pseudo-code 1] or [pseudo-code 2] steps. MA,c can be used to determine the number of HARQ-ACK bits that the terminal must transmit. Specifically, the HARQ-ACK codebook can be constructed using the cardinality of the set MA,c.

[0601] As another example, the factors to consider for determining a quasi-static HARQ-ACK codebook (or type 1 HARQ-ACK codebook) may be as follows.

[0602] a) on a set of slot timing values associated with the active UL BWP

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

[0604] (b) If the UE is configured to monitor PDCCH for DCI format 1_1 for serving cell c, is provided by dl-DataToUL-ACK for DCI format 1_1

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

[0606] c) on the ratio between the downlink SCS configuration and the uplink SCS configuration provided by subcarrierSpacing in BWP-Downlink and BWP-Uplink for the active DL BWP and the active UL BWP, respectively

[0607] d) if provided, on TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated as described in Subclause 11.1.

[0608] 또 다른 일례로, HARQ-ACK 코드북 결정을 위한 pseudo-code는 다음과 같을 수 있다.

[0609] [pseudo-code 2 시작]

[0610] For the set of slot timing values , the UE determines a set of occasions for candidate PDSCH receptions or SPS PDSCH releases according to the following pseudo-code. A location in the Type-1 HARQ-ACK codebook for HARQ-ACK information corresponding to a SPS PDSCH release is same as for a corresponding SPS PDSCH reception.

[0611] Set - index of occasion for candidate PDSCH reception or SPS PDSCH release

[0612] Set

[0613] Set

[0614] Set to the cardinality of set

[0615] Set k =0 - index of slot timing values , in descending order of the slot timing values, in set for serving cell

[0616] while

[0617] if

[0618] Set - index of a DL slot within an UL slot

[0619] while

[0620] Set R to the set of rows

[0621] Set to the cardinality of R

[0622] Set r=0 - index of row in set R

[0623] if slot starts at a same time as or after a slot for an active DL BWP change on serving cell c or an active UL BWP change on the PCell and slot is before the slot for the active DL BWP change on serving cell c or the active UL BWP change on the PCell

[0624] continue;

[0625] else

[0626] while

[0627] if the UE is provided TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigDedicated and, for each slot from slot to slot , at least one symbol of the PDSCH time resource derived by row r is configured as UL where is the k-th slot timing value in set ,

[0628] ;

[0629] end if

[0630] r=r+1;

[0631] end while

[0632] if the UE does not indicate a capability to receive more than one unicast PDSCH per slot and ,

[0633] ;

[0634] j=j+1;

[0635] The UE does not expect to receive SPS PDSCH release and unicast PDSCH in a same slot;

[0636] else

[0637] Set to the cardinality of R

[0638] Set m to the smallest last OFDM symbol index, as determined by the SLIV, among all rows of R

[0639] while

[0640] Set r=0

[0641] while

[0642] if for start OFDM symbol index S for row r

[0643] ; - index of occasion for candidate PDSCH reception or SPS PDSCH release associated with row r

[0644] R=R / r;

[0645] ;

[0646] end if

[0647] r=r+1;

[0648] end while

[0649]

[0650] j=j+1;

[0651] Set m to the smallest last OFDM symbol index among all rows of R;

[0652] end while

[0653] end if

[0654] end if

[0655] ;

[0656] end while

[0657] end if

[0658] ;

[0659] end while

[0660] [pseudo-code 2 종료]

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

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

[0663] The terminal can transmit HARQ-ACK information 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 transmission of HARQ-ACK information described above, the terminal can determine the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by the PDSCH-to-HARQ_feedback timing and K0 based on the DAI included in the DCI indicating PDSCH or SPS PDSCH release.

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

[0665] Total DAI is a value that indicates the size of the HARQ-ACK codebook. Specifically, the value of Total DAI can represent the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time when the DCI was scheduled. Furthermore, Total DAI is a parameter used in Carrier Aggregation (CA) situations where the HARQ-ACK information in serving cell c includes HARQ-ACK information for PDSCHs scheduled in other cells, including serving cell c. In other words, the Total DAI parameter does not exist in systems operating as a single cell.

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

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

[0668] 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 single slot. This can be referred to as Mode 1. As an example of a method for determining a single PUCCH transmission resource within a slot, when PDSCHs scheduled in different DCIs are multiplexed into a single HARQ-ACK codebook and transmitted within the same slot, the PUCCH resource selected for HARQ-ACK transmission can be determined as the PUCCH resource indicated by the PUCCH resource field indicated by the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated by the DCI scheduled prior to the above DCI can be ignored.

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

[0670] [Explanation of Satellite Communication Structure]

[0671] The following description may explain the characteristics of satellite communication. 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 at an altitude of approximately 36,000 km, MEO refers to a satellite at an altitude of 5,000 to 15,000 km, and LEO refers to a satellite at an altitude of 500 to 1,000 km. Of course, the above examples are not limited. According to one embodiment of the present disclosure, the Earth's orbital period varies depending on the altitude; for GEO, the Earth's orbital period is approximately 24 hours, for MEO, it is approximately 6 hours, and for LEO, it is approximately 90 to 120 minutes. Low Earth orbit (~2,000 km) satellites may have advantages over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time it takes for a signal transmitted from a transmitter to reach a receiver) and loss due to their relatively low altitude.

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

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

[0674] [NB-IoT General]

[0675] Narrowband IoT (NB-IoT) is a Low Power Wide Area (LPWA) technology standardized in 3GPP Release 13, designed for IoT applications. NB-IoT can provide enhanced coverage, high connection density, and low power consumption while leveraging existing LTE infrastructure. Regarding frequency allocation and deployment modes, NB-IoT can operate in the following three deployment modes.

[0676] In-band deployment: Enables coexistence with LTE services by utilizing resource blocks from existing LTE carriers. This allows for increased spectrum efficiency by using the same frequency band as LTE.

[0677] Guard Band Deployment: By utilizing unused resource blocks in the LTE guard band, interference with adjacent LTE carriers can be minimized, and the spectrum can be used efficiently.

[0678] Standalone deployment: NB-IoT can be deployed in dedicated spectrum outside of LTE bands, enabling flexible spectrum allocation, but additional infrastructure may be required.

[0679] NB-IoT can typically operate in a narrowband manner using a single LTE resource block (180 kHz). Additionally, while it primarily aims for single-carrier operation, it can coexist through dynamic spectrum sharing with other carriers. Furthermore, NB-IoT has introduced various modifications to the physical layer to support narrowband and low-power requirements.

[0680] a. OFDM and Single Carrier Method

[0681] OFDM (Orthogonal Frequency Division Multiplexing): Can be used for downlink transmission by leveraging the strengths of multiple carrier modulation.

[0682] Single Carrier FDMA (SC-FDMA): Can be used to reduce PAPR (Peak-to-Average Power Ratio) in uplink transmission to increase the power efficiency of IoT terminals.

[0683] b. Modulation method

[0684] QPSK and BPSK: NB-IoT primarily uses QPSK for robust communication, while BPSK can be used in coverage extension scenarios that are more robust against noise and interference.

[0685] c. Resource Grid and Synchronization

[0686] Resource Grid Adaptation: NB-IoT can adjust the LTE resource grid to meet narrowband requirements and allocate resource elements for synchronization signals and reference signals.

[0687] Synchronization Signal (PSS / SSS): An essential signal for cell search and time synchronization, specific patterns and configurations can be defined to optimize detection even in restricted environments.

[0688] Specifically, the above synchronization signals PSS / SSS can be used as NPSS (Narrow-Band PSS) and NSSS (Narrow-Band SSS) in NB-IoT. NPSS can basically be transmitted and received in the 6th subframe of every radio frame. NSSS can basically be transmitted and received in the 1st subframe of every even-numbered radio frame. And NPBCH (Narrow-Band PBCH) can be transmitted and received in the 10th subframe of every radio frame. The above radio frame refers to a frame with a length of 10ms composed of 10 subframes, and the x-th subframe may refer to the subframe located at the x-th position in chronological order among the subframes belonging to the corresponding radio frame. The remaining subframes can be used to transmit NPDCCH or NPDSCH.

[0689] [NB-IoT NPDCCH]

[0690] The NPDCCH can be explained below. The NPDCCH can be used to transmit and receive down-control information (DCI). The terminal requires the NPDCCH to monitor the following three types of information: 1) UL grant information (DCI format N0, 23 bits), 2) DL scheduling information (DCI format N1, 23 bits), and 3) indicators of paging or SI updates (DCI format N2, 15 bits). An NPDCCH subframe is divided into two narrow-band control channel elements (NCCE). NCCE0 can take the six lowest subcarriers, and NCCE1 can take the six highest subcarriers. The number of REs available in a single NCCE depends on the NB-IoT deployment mode and the number of logical antenna ports, and for in-band placement within the frequency band in which LTE operates, it depends on the LTE cell configuration. After cell selection and system information acquisition, the terminal can understand the accurate mapping of NPDCCH REs within the NPDCCH subframe. For example, in the case of in-band placement, the NPDCCH is not mapped to the first few OFDM symbols of a subframe. This is intended to avoid the LTE downlink control region. The index of the starting OFDM symbol within the NPDCCH subframe depends on the size of the LTE downlink control region and can be signaled to the device. Accordingly, the number of possible REs per NCCE varies from a minimum of 50 to 80. The DCI can be mapped to a single NCCE, which is referred to as Aggregation Level (AL) 1, or it can be mapped to both NCCEs of the same subframe, which is referred to as AL 2. First, the DCI is attached with a 16-bit CRC, which can be masked by a sequence determined by the Radio Network Temporary Identifier (RNTI). The RNTI is an identifier used to address one or more devices.After CRC attachment and RNTI mask processing, and after TBCC encoding and rate matching are applied, the length of the generated codeword can be generated to match the number of available encoding bits. Since QPSK modulation is used for NPDCCH, the codeword length is 100 to 160 for AL 1 or 200 to 320 for AL 2. Baseband signal generation can use QPSK symbols as input to generate a baseband waveform.

[0691] NPDCCH AL 2 can be used to increase the coverage of the NPDCCH. If more RE is used to transmit the DCI message, the energy level per information bit increases. Further coverage improvement can be provided through subframe-level iterations. An NPDCCH transmission using AL 2 and 8 iterations is shown. The NPDCCH bit stream can be scrambled before being mapped to symbols. The same scrambling sequence is used across a set of four consecutive subframes, which means that the same NPDCCH symbol is transmitted in each of the four subframes. This allows the device to optimize performance by using coherent coupling for received power estimation and frequency offset estimation. As shown in the figure, the scrambling sequence is re-initialized after 4 iterations to randomize the transmitted waveform. NB-IoT can allow the same NPDCCH to be repeated up to 2048 times. Therefore, in the worst case, the DCI can be transmitted across 2048 subframes. To prevent DCI from blocking DL NPDCCH / NPDSCH resources for a long time, transmission intervals can be configured through RRC signaling.

[0692] [NB-IoT NPDSCH]

[0693] NPDSCH can be explained below. NPDSCH can be used to transmit unicast data. Data packets from the upper layer are split into one or more TBs, and NPDSCH can transmit one TB at a time. NPDSCH can also be used to transmit broadcast information, such as System Information (SI) messages. The subframe-level resource mapping of NPDSCH is similar to that of NPDCCH. However, there are the following two differences.

[0694] NPDCCH can transmit two DCI messages by multiplexing resources within a subframe, but a single NPDCCH subframe can transmit and receive at most one TB. That is, the basic RU of NPDCCH is a single PRB pair.

[0695] In in-band mode, the starting OFDM symbol of an NPDSCH subframe may differ from the starting OFDM symbol of an NPDCCH subframe when the subframe is used to transmit a SIB1-NB. As with NPDCCH, the location of the starting OFDM symbol of an NPDSCH subframe in in-band mode may be determined by the LTE control area size. This information may be included in the SIB1-NB. However, the terminal may need to be able to acquire the SIB1-NB even without knowing the LTE control area size. Therefore, when an NPDSCH subframe is used to transmit a SIB1-NB, the starting OFDM symbol location is always the fourth symbol of the subframe.

[0696] NPDSCH uses QPSK and supports a maximum TB size of 680 bits for terminal category Cat-N1. A TB can be mapped to the number of NPDSCH subframes. LTE TBCC is the only forward error correction code for NPDSCH. NPDSCH TB processing is as follows: First, a 24-bit CRC can be calculated and attached to the TB. The TB with the attached CRC is encoded using a TBCC encoder and scaled proportionally based on the number of NPDSCH subframes allocated to it and the number of REs per subframe to determine the codeword length. Therefore, the TB size and the number of NPDSCH subframes allocated to the TB can determine the coding ratio. To limit the requirements of the terminal receiver, only a single redundant version may be specified for the NPDSCH encoding. For larger TB sizes, allocating more NPDSCH subframes increases the energy level per information bit and, in most cases, also yields higher coding gain, thereby achieving better coverage.

[0697] A maximum NSF = 10 NPDSCH subframe can be used to transmit and receive a single NPDSCH TB (or codeword). Bits of the encoded TB may be scrambled before being mapped to QPSK symbols. Scrambling is re-initialized for every iteration of the codeword's Min(NREP, 4), where NREP is the configured number of iterations. A maximum of 2048 iterations may be transmitted. After mapping the NPDSCH codeword to a subframe, the subframe may be repeated at least (NREP, 4) times before the codeword mapping continues. For example, if two subframes are applied to transmit a single TB, and this TB consists of a total of eight iterations, the first subframe may be repeated four times before the second subframe continues. After the second subframe is repeated four times, scrambling is re-initialized, and this procedure is repeated one more time to complete a total of eight codeword iterations.

[0698] Repeated subframes, as in the case of NPDCCH, can allow coherent coupling for received power estimation and frequency offset estimation. Additionally, the terminal can attempt to decode the codeword before the transmission is complete. For example, if two subframes are applied to transmit a single TB, and this TB consists of a total of eight repetitions, it can support decoding the entire codeword after eight subframes. Due to the large number of supported repetitions, an NPDSCH TB can be mapped to up to 20,480 NPDSCH subframes. NPDSCH transmission intervals can be configured to ensure that one long NPDSCH transmission does not block other NPDCCH or NPDSCH transmissions. NPDSCH can also be used for the transmission of SIBs. However, such transmissions follow slightly different principles than those just described. For SIB1-NB, the TBS is always NSF = 8 subframes, and the available TBS set can be limited to a set of {208, 328, 440, 680} bits. For other SIBs, the TBS is NSF = 2 or 8 subframes, and the available TBS set can be limited to {56, 120, 208, 256, 328, 440, 552, 680} bits. The scrambling of the NPDSCH transmitting and receiving the SIB can be re-initialized for each iteration. This allows all terminals with good coverage to already have the SIB decoded after the first transmission.

[0699] [NB-IoT NPUSCH]

[0700] NPUSCH can be explained below. NPUSCH can be used to transmit UL user data and control information at the upper layer. Additionally, NPUSCH can transmit HARQ acknowledgments for NPDSCH. The waveform adopted by NPUSCH is, in principle, identical to the LTE SC-FDMA waveform. However, in LTE, SC-FDMA can support terminal bandwidth subdivided into a single PRB (i.e., 12 subcarriers). A terminal can be reserved with 12K subcarriers if K is a positive integer. Therefore, the minimum terminal reserved bandwidth allocation in LTE can be one or 12 subcarriers. However, since NB-IoT uses only one PRB, the maximum terminal reserved bandwidth is necessarily one PRB. The following considerations may motivate NB-IoT to include lower terminal reserved bandwidth options. NB-IoT targets ultra-low-cost IoT use cases, in which small data packets may often occur. Therefore, in many cases, a terminal may not need to use the entire wireless resource of a PRB (180 kHz). NB-IoT can target terminals in coverage-limited scenarios. These terminals operate in power-limited areas rather than bandwidth-limited areas, and thus having a higher terminal bandwidth is not an advantage.

[0701] For terminals at the edge of network coverage, low PAPR waveforms are critical, primarily related to battery life. NPUSCH must include waveforms with a PAPR of nearly 0 dB to provide optimal support for terminals at the edge of network coverage. Consequently, NPUSCH adds sub-PRB reserved bandwidth options and can include single-tone transmissions that benefit from a PAPR close to 0 dB. Depending on the data, NPUSCH can use two transmission formats. NPUSCH format 1 is used for UL data transmission and can use the same turbo codes used in LTE for error correction. The maximum TBS for NPUSCH is 1,000 bits for terminal category Cat-N1. NPUSCH format 2 is used to signal HARQ feedback for NPDSCH and can use repeat codes for error correction. Both NPUSCH format 1 and NPUSCH format 2 can use SC-FDMA waveforms that include CP insertion during DFT preprocessing and waveform generation. As mentioned earlier, NPUSCH can support both multi-tone and single-tone terminal reserved bandwidth options. In the single-tone case, waveform generation can omit DFT preprocessing. All multi-tone NPUSCH transmissions are based on a 15 kHz subcarrier interval, but single-tone transmissions can use a 15 kHz or 3.75 kHz subcarrier interval.

[0702] The definitions of CP and OFDM symbol duration in NPUSCH format 1 are the same as those described for LTE for a 15 kHz subcarrier interval. For single-tone transmission using a 3.75 kHz subcarrier interval, the slot length is 2 ms, which can consist of seven SC-FDMA symbols and a guard period at the end. Each SC-FDMA symbol is 275 µs, which can include a CP of 8.33 µs. The guard period can be created to avoid collisions with the LTE Sounding Reference Signal (SRS). The LTE terminal can be configured to transmit the SRS in the PRB used as the NB-IoT carrier. The SRS can use only the last OFDM symbol of the LTE subframe, and the periodicity can be set from a minimum of 2 ms to a maximum of 320 ms. Collisions between the SRS and NPUSCH symbols can be prevented by puncturing the NPUSCH symbols.

[0703] For a 15 kHz subcarrier spacing, an intermediate OFDM symbol in each slot is used as the Demodulation Reference Symbol (DMRS), which allows the base station to estimate UL propagation conditions. For a 3.75 kHz subcarrier spacing, the DMRS placement is shifted to the fifth OFDM symbol in the slot, intended to avoid SRS. NPUSCH Format 2 uses the same slot format but uses three OFDM symbols as the DMRS, leaving only four information-carrying symbols per slot. As with NPUSCH Format 1, the placement of the DMRS is designed to avoid collisions with LTE SRS. In the 15 kHz subcarrier spacing, using the intermediate three OFDM symbols avoids collisions with LTE SRS, while in 3.75 kHz, using the first three OFDM symbols achieves the same result. The basic NPUSCH time scheduling unit is referred to as the RU (Resource Unit). It is specified by the number of slots and may vary depending on user bandwidth allocation and the NPUSCH format. The terminal can have up to 1, 2, 3, 4, 5, 6, 8, or 10 RUs per repeat transmission, thereby shortening the transmission interval per repeat to up to 1ms and using one RU with a 180kHz reserved bandwidth, and extending it to up to 320ms and using 10 RUs with a 3.75kHz reserved bandwidth.

[0704] For NPUSCH Format 1, the smallest supported TBS is 16 bits long, and the largest is 1,000 bits long. Some TBSs can only be used for multi-tone transmissions because their block sizes are too large for single-tone transmissions. Other TBSs can be used for both single-tone and multi-tone transmissions. A 24-bit CRC can be included in the TBS. QPSK can be used for all multi-tone transmissions. For single-tone transmissions, 15 and 3.75 kHz logic can be used for either BPSK or QPSK depending on the TBS index. BPSK is used when ITBS = 0 or 2, while QPSK can be used for all other ITBS values. The reason for extending BPSK up to ITBS = 2 is to allow the use of BPSK for higher TBSs up to 424 bits. Similarly, using QPSK for ITBS = 1 enables the use of QPSK for smaller TBSs. Later, BPSK and QPSK modulations can be converted to p / 2-BPSK and p / 4-QPSK, respectively, during the baseband signal generation process. P / 2 and p / 4 rotations for single-tone transmission are intended to reduce PAPR, which is to improve PA efficiency. To achieve better coverage for TB sizes, more RUs can be allocated to increase the energy level per information bit, and in most cases, higher coding gain can also be obtained.

[0705] The processing of NPUSCH Format 2 differs from NPUSCH Format 1 in that it lacks CRC attachment and complex repeating codes, and simply repeats the HARQ feedback bits 16 times. NPUSCH Format 2 uses only BPSK, and as with Format 1, it can be converted to p / 2-BPSK during the baseband signal generation process to help reduce PAPR. Before the bits of the encoded TB are modulated into BPSK or QPSK symbols, the bits can be scrambled. When single-tone transmission is used, scrambling can be re-initialized for each iteration. For multi-tone transmission, scrambling can be re-initialized for at least (NREP / 2, 4) iterations of the codeword, and the redundancy version can be changed simultaneously. A maximum of 128 iterations can be transmitted.

[0706] After mapping codewords to slot pairs for a 15 kHz carrier interval, the slot pairs may be repeated at least (NREP / 2, 4) times before codeword mapping continues. For 3.75 kHz transmission, mapping may be performed in a single slot and then repeated. Repeated slots may allow matched coupling for received power estimation and frequency offset estimation, as in the case of NPDCCH and NPDSCH. Additionally, the base station may attempt to decode the codeword before the transmission is complete.

[0707] [NB-IoT UL scheduling]

[0708] NB-IoT uplink scheduling can be described below. When a base station (or network) needs to schedule a terminal, it may transmit a DCI addressing the terminal in one of the search interval candidates monitored by the terminal. A C-RNTI with the DCI CRC masked can be used to identify the terminal. The NPDCCH may transmit and receive a DCI containing information necessary to support resource allocation (including both time and frequency resource domains), modulation and encoding schemes (MCS), and HARQ operation.

[0709] [Table 47]

[0710]

[0711] When uplink scheduling (i.e., scheduling that directs NPUSCH transmission), the DCI format N0 used for UL scheduling can convey information as shown in [Table 47].

[0712] FIG. 22 is a diagram showing a UL scheduling process according to one embodiment of the present disclosure.

[0713] Referring to FIG. 22, for UL data transmission, subframes may need to be scheduled with a minimum time interval of 8 ms between the last DCI subframe (2022) and the first scheduled NPUSCH (2210) subframe. This time interval allows the terminal to decode the DCI, switch from receive mode to transmit mode, and prepare for UL transmission. This time interval is called the scheduling delay and may be included in the DCI and transmitted. After the terminal completes the NPUSCH transmission, there is a minimum interval of 3 ms until the terminal switches from transmit mode to receive mode and is ready to monitor the next NPDCCH search interval candidate. This means that the network cannot send the next DCI to the terminal using the second NPDCCH search interval (2204, 2206) because the terminal skips both search interval candidates since both are within 3 ms of the end of its NPUSCH transmission. The base station may need to follow this timing relationship when determining when to send the DCI.

[0714] DCI format N0 can provide information regarding the start subframe and the total number of subframes of a scheduled NPUSCH resource. As previously mentioned, the time interval between the last NPDCCH subframe carrying the DCI and the first scheduled NPUSCH slot can be indicated in the DCI. To determine which subframe is the last subframe carrying the DCI, the terminal may include information on the number of NPDCCH subframe repetitions in the DCI. With this information, if the terminal can decode the DCI using one of the first subframes available in the search interval, it knows that the DCI is repeated one more time, which can be the last subframe carrying the DCI. Generally, due to the NPDCCH subframe repetition information, if the terminal can decode the DCI using any subframe of the search interval candidate, it can clearly determine the start and end subframes of this specific search interval candidate.

[0715] The total number of scheduled NPUSCH slots can be determined by the number of RUs per iteration, the number of iterations, and the length of the RUs. The length of the RUs can be inferred from the number of subcarriers used in NPUSCH format 1. For example, one RU for NPUSCH format 1, which uses 12 subcarriers and consists of 12 tones, is 1 ms. Therefore, the length of the time resource, consisting of 2 iterations and 3 RUs per iteration, is a total of 6 ms. FIG. 22 shows NPUSCH (2210) scheduled over a total length of 6 ms.

[0716] The modulation format is determined by the MCS index, and the coding method can be determined based on the MCS index, the number of RUs, and the RV version. For example, if the MCS index according to DCI is 8, it maps to a TBS index of 9, and the TBS can be determined as 456 based on the information that each iteration uses three RUs. When the number of data symbols per RU is 144 symbols, and there are QPSK and three RUs per iteration, a total of 864 encoded bits are available. If the TBS is 456 bits, the codeword length is 864 bits, and the redundancy version is 0, a TB (or codeword) can be generated using the LTE rate matching framework. If the terminal supports only one HARQ process, there is no need to signal the process number; however, if it supports two HARQ processes, information indicating the HARQ process can be included in the DCI format and transmitted / received. From the terminal's perspective, it is sufficient to know only whether the same TB or a new TB needs to be transmitted. HARQ acknowledgment can be implicitly signaled using the DCI's NDI. When the NDI is toggled, the terminal can consider the previous transmission acknowledged.

[0717] [NB-IoT DL scheduling]

[0718] Below, NB-IoT downlink scheduling can be explained. NPDSCH scheduling can be transmitted and received via DCI format N1 using parameter values ​​of various information elements included in [Table 48].

[0719] FIG. 23 is a diagram illustrating a downlink scheduling process according to one embodiment of the present disclosure. Referring to FIG. 23, most downlink (DL) scheduling processes are similar to those used in uplink (UL) scheduling, but the exact parameter values ​​are different. For example, cross-subframe scheduling is also used in DL scheduling, but the minimum time interval between the last DCI subframe (2302) and the first scheduled NPDSCH subframe (2308) is 4 ms. In the case of UL cross-subframe scheduling, this interval is at least 8 ms. The reason for considering a smaller minimum interval in DL scheduling, unlike UL scheduling, is that the terminal does not need to switch from receiving to transmitting before starting to receive NPDSCH after receiving DCI.

[0720] [Table 48]

[0721]

[0722] First, DCI indicates that there is no additional scheduling delay, and therefore the scheduled NPDSCH can start after at least 4ms of the last subframe transmitting and receiving DCI. For example, as shown in FIG. 23, DCI indicates that one subframe is used for each NPDSCH iteration and that there are two iterations (2308, 2309). Based on this information, the terminal can know that two subframes are allocated for its NPDSCH reception. These two subframes are the first two subframes (2308, 2309) available from the NPDSCH scheduling start point. The available subframes here are subframes that are not used as NPBCH, NPSS, NSSS, or SI and are not marked as invalid subframes. Accordingly, as illustrated in FIG. 23, if the next subframe (2308) is available at the scheduled NPDSCH start point but the next second subframe is used consecutively for NSSS and NPBCH, resources can be allocated (2309) excluding it. That is, after the NPBCH subframe, the next subframe can be used to perform NPDSCH transmission and reception (2309).

[0723] The main difference between DL and UL scheduling is that in the case of DL, the base station may also need to schedule NPUSCH format 2 resources for signaling HARQ feedback. This information may be provided to the DCI in the form of a subcarrier index and a time offset. The time offset may be defined between the end subframe of the scheduled NPDSCH and the start slot of NPUSCH format 2. For example, this time offset should be at least 12 ms, which may be considered as the interval between the end of the NPDSCH (2309) and the start of the NPUSCH format 2 (2310) being at least 12 ms. This offset is merely an example, and other values ​​may be applied. This interval is intended to allow sufficient NPDSCH decoding time at the terminal and to provide the time required to transition from receiving to transmitting and to prepare for NPUSCH format 2 transmission. NPUSCH format 2 uses single-tone transmission and may use a 15 kHz or 3.75 kHz subcarrier interval. The RU of NPUSCH format 2 is 2ms for a 15kHz subcarrier interval or 8ms for a 3.75kHz subcarrier interval. Whether the terminal uses a 15kHz or 3.75kHz subcarrier interval can be configured through RRC signaling. Additionally, NPUSCH format 2 transmission can be configured with multiple repetitions. However, this information is not included in the DCI, and the upper signal can be configured separately. Taking FIG. 23 as an example, it can be assumed that the terminal is configured to use four repetitions for NPUSCH format 2 (2310) (15kHz subcarrier interval).

[0724] Immediately after the terminal completes the transmission of NPUSCH format 2, there is no need to monitor the NPDCCH search interval (2307) again for 3ms. This is because switching is required to allow the terminal to exit transmission mode and prepare to receive NPDCCH again. If the subframe immediately following the NPSS subframe is another candidate for the NPDCCH search interval and is not within the 3ms interval, then the DCI can use this subframe (2320) to send.

[0725] [Introduction to the Example]

[0726] Conventional NB-IoT technology was introduced for IoT terminals that send small-sized data that is not sensitive to latency. Consequently, it lacks functionality for resources that are transmitted periodically, such as voice. The present invention describes a method for setting periodic transmission resources for voice support and a method for configuring necessary information between a base station and a terminal for this purpose. Through the present invention, a terminal supporting NB-IoT can support voice communication in addition to supporting satellite communication functions.

[0727] [Example 1]

[0728] In the following embodiments, a method for semi-persistent scheduling of uplink periodic resources of an NB-IoT terminal may be described. Specifically, the terminal may be allocated NPUSCH resources through DCI format N0 within NPDCCH. At this time, if the CRC of DCI format N0 is scrambled with CS-RNTI, the DCI format may be used for scheduling periodic NPUSCH (hereinafter referred to as SPS NPUSCH). For example, if at least one of the following conditions, or a combination of some or all thereof, is satisfied, the terminal may determine that SPS NPUSCH is activated.

[0729] Condition 1-1: If the CRC of DCI format N0 is scrambled with a CS-RNTI or SPS-related RNTI

[0730] Condition 1-2: When the NDI value consisting of a 1-bit DCI format N0 is indicated as 0 (or 1)

[0731] Condition 1-3: When the 1-bit RV value of DCI format N0 is indicated as 0 (or 1)

[0732] Condition 1-4: When the first MSB (Most Significant Bit) of the 6-bit subcarrier indication in DCI format N0 is indicated as 0 (or 1)

[0733] Condition 1-5: When the first MSB value of the 3-bit resource assignment in DCI format N0 is indicated as 0 (or 1)

[0734] Condition 1-6: When the first MSB value of the 2-bit scheduling delay in DCI format N0 is indicated as 0 (or 1)

[0735] Condition 1-7: When the first MSB value of the 4-bit MCS of DCI format N0 is indicated as 0 (or 1)

[0736] Condition 1-8: When the first MSB value of the 3-bit repetition in DCI format N0 is indicated as 0 (or 1)

[0737] Condition 1-9: When the first MSB value of the 2-bit DCI subframe repetition number of DCI format N0 is indicated as 0 (or 1)

[0738] Condition 1-10: When the unicast value consisting of the 1-bit DCI format N0 Number of scheduled TB is indicated as 0 (or 1)

[0739] Condition 1-11: If the HARQ process number value, consisting of a 1-bit DCI format N0, is indicated as 0 (or 1)

[0740] Condition 1-12: When the 1-bit Resource reservation value of DCI format N0 is indicated as 0 (or 1)

[0741] Condition 1-13: When the SPS activation / release indication value, consisting of a 1-bit DCI format N0, is indicated as 0 (or 1)

[0742] Among the above conditions, fields with a number of bits greater than 1 were considered for use in indicating whether SPS NPUSCH is enabled by utilizing the value of the first MSB; however, this is not limited to this, and it may also be possible to use n MSB values ​​to indicate whether SPS NPUSCH is enabled. For example, if three MSB values ​​are used, and the value is indicated as 000 (or 111), it may be possible to determine the DCI format indicating whether SPS NPUSCH is enabled. Furthermore, it is entirely possible to apply the LSB (Least Significant Bit) as a substitute for the MSB. Additionally, if some bits of the MSB or LSB are used as code points for enabling SPS NPUSCH, the remaining fields may be used for scheduling existing NPUSCH resources. However, since some bits of the MSB or LSB are not used, resource scheduling flexibility may be reduced.

[0743] FIG. 25 is a diagram showing the activation and deactivation process of SPS NPUSCH according to one embodiment of the present disclosure.

[0744] Referring to FIG. 25, as another example, if at least one of the following conditions or a combination of some or all of them is satisfied, the terminal may determine that the previously activated SPS NPUSCH is deactivated.

[0745] Condition 2-1: If the CRC of DCI format N0 is scrambled with a CS-RNTI or SPS-related RNTI

[0746] Condition 2-2: When the NDI value consisting of a 1-bit DCI format N0 is indicated as 0 (or 1)

[0747] Condition 2-3: When the 1-bit RV value of DCI format N0 is indicated as 0 (or 1)

[0748] Condition 2-4: When all values ​​of the 6-bit subcarrier indication in DCI format N0 are indicated as 0 (or 1)

[0749] Condition 2-5: When all values ​​of the 3-bit resource assignment in DCI format N0 are indicated as 0 (or 1)

[0750] Condition 2-6: When all values ​​of the 2-bit scheduling delay in DCI format N0 are indicated as 0 (or 1)

[0751] Condition 2-7: When all values ​​of the 4-bit MCS in DCI format N0 are indicated as 0 (or 1)

[0752] Condition 2-8: When all values ​​of the 3-bit repetition in DCI format N0 are indicated as 0 (or 1)

[0753] Condition 2-9: When all values ​​of the 2-bit DCI subframe repetition number of DCI format N0 are indicated as 0 (or 1)

[0754] Condition 2-10: When the unicast value consisting of the 1-bit DCI format N0 Number of scheduled TB is indicated as 0 (or 1)

[0755] Condition 2-11: If the HARQ process number value consisting of a 1-bit DCI format N0 is indicated as 0 (or 1)

[0756] Condition 2-12: When the 1-bit Resource reservation value of DCI format N0 is indicated as 0 (or 1)

[0757] Condition 2-13: When the SPS activation / release indication value, consisting of a 1-bit DCI format N0, is indicated as 0 (or 1)

[0758] The activation and deactivation process of the above SPS NPUSCH can be explained through Fig. 25.

[0759] A terminal receives a DCI format N0 within an NPDCCH (2500), and if the DCI format N0 satisfies at least one of conditions 1-1 to 1-13 or a combination thereof, the terminal may determine that the DCI format N0 contained within the NPDCCH (2500) is a DCI format indicating SPS NPUSCH activation. Then, the terminal may transmit an SPS NPUSCH (2502) by applying the offset, time and frequency resources, and the number of repeated transmissions of the DCI format N0. The period (2512, 2514) value between SPS NPUSCHs may be set in advance as a higher signal. The unit of the value may be a slot unit, a subframe unit, or a ms unit. Subsequently, the terminal receives a DCI format N0 within another NPDCCH (2508), and if the DCI format N0 satisfies at least one of conditions 2-1 to 2-13 or a combination thereof, the terminal may determine that the DCI format N0 included in the NPDCCH (2508) is a DCI format indicating the release of the SPS NPUSCH. Subsequently, after receiving the NPDCCH (2508), the terminal may transmit a response or confirmation message including that it has successfully received the release information via the SPS NPUSCH (2510) through an existing periodic resource. This is merely an example, and it may be possible for the terminal to receive only the DCI format indicating the release of the SPS NPUSCH within the NPDCCH (2508) and not perform any separate transmission thereafter. Although the NPDCCH and NPUSCH are each depicted as a single transmission in FIG. 25, it is also possible for two or more to be transmitted repeatedly. When NPUSCH is transmitted repeatedly, it may be possible to ensure that the transmitted NPUSCH is always included within one cycle.

[0760] [Example 2]

[0761] In the following embodiments, a method for semi-persistent scheduling of downlink periodic resources of an NB-IoT terminal may be described. Specifically, the terminal may be allocated NPDSCH resources through DCI format N1 within NPDCCH. At this time, if the CRC of DCI format N1 is scrambled with CS-RNTI, the corresponding DCI format may be used for scheduling periodic NPDSCH (hereinafter referred to as SPS NPDSCH). For example, if at least one of the following conditions, or a combination of some or all thereof, is satisfied, the terminal may determine that SPS NPDSCH is activated.

[0762] Condition 3-1: If the CRC of DCI format N1 is scrambled with a CS-RNTI or SPS-related RNTI

[0763] Condition 3-2: When the NDI value consisting of a 1-bit DCI format N1 is indicated as 0 (or 1)

[0764] Condition 3-3: When the PDCCH order indicator value, consisting of a 1-bit DCI format N1, is indicated as 0 (or 1)

[0765] Condition 3-4: When the first MSB (Most Significant Bit) of the 3-bit scheduling delay in DCI format N1 is indicated as 0 (or 1)

[0766] Condition 3-5: When the first MSB value of the 3-bit resource assignment in DCI format N1 is specified as 0 (or 1)

[0767] Condition 3-6: When the first MSB value of the 4-bit MCS of DCI format N1 is indicated as 0 (or 1)

[0768] Condition 3-7: When the first MSB value of the 4-bit repetition number of DCI format N1 is indicated as 0 (or 1)

[0769] Condition 3-8: If the first MSB value of the 4-bit HARQ-ACK resource in DCI format N1 is indicated as 0 (or 1)

[0770] Condition 3-9: When the first MSB value of the 2-bit DCI subframe repetition number of DCI format N1 is indicated as 0 (or 1)

[0771] Condition 3-10: If the first MSB value of the 3-bit Number of scheduled TB for SC-MTCH in DCI format N1 is indicated as 0 (or 1)

[0772] Condition 3-11: When the unicast value of the Number of scheduled TB, consisting of 1 bit of DCI format N1, is indicated as 0 (or 1)

[0773] Condition 3-12: When the HARQ process number value consisting of 1 bit of DCI format N1 is indicated as 0 (or 1)

[0774] Condition 3-13: When the 1-bit Resource reservation value of DCI format N1 is indicated as 0 (or 1)

[0775] Condition 3-14: When the SPS activation / release indication value, consisting of a 1-bit DCI format N1, is indicated as 0 (or 1)

[0776] Among the above conditions, fields with a number of bits greater than 1 were considered for use in indicating whether SPS NPDSCH is enabled by utilizing the value of the first MSB; however, this is not limited to this, and it may also be possible to use n MSB values ​​to indicate whether SPS NPDSCH is enabled. For example, if three MSB values ​​are used, and the value is indicated as 000 (or 111), it may be possible to determine the DCI format indicating whether SPS NPDSCH is enabled. Furthermore, it is entirely possible to apply the LSB (Least Significant Bit) as a substitute for the MSB. Additionally, if some bits of the MSB or LSB are used as code points for enabling SPS NPDSCH, the remaining fields may be used for scheduling existing NPDSCH resources. However, since some bits of the MSB or LSB are not used, resource scheduling flexibility may be reduced.

[0777] FIG. 24 is a diagram showing the activation and deactivation process of SPS NPDSCH according to one embodiment of the present disclosure.

[0778] Referring to FIG. 24, as another example, if at least one of the following conditions or a combination of some or all of them is satisfied, the terminal may determine that the previously activated SPS NPDSCH is deactivated.

[0779] Condition 4-1: If the CRC of DCI format N1 is scrambled with a CS-RNTI or SPS-related RNTI

[0780] Condition 4-2: When the NDI value consisting of a 1-bit DCI format N1 is indicated as 0 (or 1)

[0781] Condition 4-3: When the PDCCH order indicator value, consisting of a 1-bit DCI format N1, is indicated as 0 (or 1)

[0782] Condition 4-4: When all values ​​of the 3-bit scheduling delay in DCI format N1 are indicated as 0 (or 1)

[0783] Condition 4-5: When all values ​​of the 3-bit resource assignment in DCI format N1 are indicated as 0 (or 1)

[0784] Condition 4-6: When all values ​​of the 4-bit MCS of DCI format N1 are indicated as 0 (or 1)

[0785] Condition 4-7: When all values ​​of the 4-bit repetition number of DCI format N1 are indicated as 0 (or 1)

[0786] Condition 4-8: If all values ​​of the 4-bit HARQ-ACK resource in DCI format N1 are indicated as 0 (or 1)

[0787] Condition 4-9: When all values ​​of the 2-bit DCI subframe repetition number of DCI format N1 are indicated as 0 (or 1)

[0788] Condition 4-10: If all values ​​of the 3-bit Number of scheduled TB for SC-MTCH in DCI format N1 are indicated as 0 (or 1)

[0789] Condition 4-11: When the unicast value of the Number of scheduled TB, consisting of 1 bit of DCI format N1, is indicated as 0 (or 1)

[0790] Condition 4-12: When the HARQ process number value consisting of 1 bit of DCI format N1 is indicated as 0 (or 1)

[0791] Condition 4-13: When the 1-bit Resource reservation value of DCI format N1 is indicated as 0 (or 1)

[0792] Condition 4-14: When the SPS activation / release indication value, consisting of a 1-bit DCI format N1, is indicated as 0 (or 1)

[0793] The activation and deactivation process of the above SPS NPDSCH can be explained through FIG. 24. A terminal receives a DCI format N1 within an NPDCCH (2400), and if the DCI format N1 satisfies at least one of conditions 3-1 to 3-14 or a combination thereof, the terminal can determine that the DCI format N1 included in the NPDCCH (2400) is a DCI format indicating SPS NPDSCH activation. Then, the terminal can periodically transmit an NPUSCH (2406) containing HARQ-ACK information for the reception of the SPS NPDSCH (2402) by applying the offset, time and frequency resources, and the number of repeated transmissions of the DCI format N1. In addition, the period values ​​(2412, 2414) between SPS NPDSCHs can be set in advance as upper signals. Additionally, the location of the NPUSCH time and frequency resource containing HARQ-ACK information for the SPS NPDSCH, or the interval between the NPUSCH and the associated SPS NPDSCH, or the NPUSCH period value of the NPUSCH may be set in advance as a higher signal. In this case, it is possible that the NPUSCH resource containing the HARQ-ACK information does not exist, and in such a case, the terminal may determine that it does not transmit HARQ-ACK information. The units of the values ​​may be slot units, subframe units, or ms units. Subsequently, the terminal receives DCI format N1 in another NPDCCH (2408), and if the DCI format N1 satisfies at least one of conditions 4-1 to 4-14 or a combination thereof, the terminal may determine that the DCI format N0 contained in the NPDCCH (2408) is a DCI format indicating the release of the SPS NPUSCH.Subsequently, after receiving NPDCCH (2408), the terminal may transmit NPUSCH (2410) including HARQ-ACK information regarding the reception of the corresponding deactivation information via SPS NPUSCH (2410). In FIG. 24, the interval between NPDCCH (2408) and NPUSCH (2410) may be indicated in advance by a higher signal or determined by a specific DCI field (e.g., scheduling delay or HARQ-ACK resource) of DCI format N1 indicating deactivation within NPDCCH (2408). This is merely an example, and it may be possible for the terminal to receive only the DCI format indicating SPS NPUSCH deactivation within NPDCCH (2408) and not perform any separate transmission thereafter. Additionally, although NPDCCH and NPUSCH are each depicted as single transmissions in FIG. 24, it may be possible for two or more to be transmitted repeatedly. When NPUSCH is transmitted repeatedly, it may be possible to ensure that the transmitted NPUSCH is always included within one cycle.

[0794] [Example 3]

[0795] The embodiments 1 and 2 described above illustrate methods for enabling and disabling SPS NPUSCH and SPS NPDSCH, respectively. However, a key characteristic of voice calls is that uplink and downlink resources are periodically configured together. Therefore, a method to simultaneously enable or disable SPS NPUSCH and NPDSCH using a single DCI format may be required. For example, by introducing a specific DCI format NX other than the existing DCI formats N0 and N1 that schedule NPUSCH and NPDSCH respectively, it may be possible for the terminal to enable SPS NPUSCH and SPS NPDSCH simultaneously when the corresponding DCI format is scheduled. The following [Table 49] shows the configuration of DCI format NX. [Table 49] is merely an example; specific fields may be omitted or their bit values ​​may be replaced with different values ​​for application. In [Table 28], Scheduling delay for SPS NPUSCH is a field that indicates the interval between the last subframe containing the DCI format NX and the first subframe where SPS NPUSCH is scheduled. This field may be replaced with Scheduling delay for SPS NPDSCH instead of Scheduling delay for SPS NPUSCH. In this case, Scheduling delay for SPS NPDSCH is a field that indicates the interval between the last subframe containing the DCI format NX and the first subframe where SPS NPDSCH is scheduled. Repetition number for SPS NPUSCH is a value that indicates the number of repeated transmissions of NPUSCH, and Repetition number for SPS NPDSCH is a value that indicates the number of repeated transmissions of NPDSCH.These two fields may be configured as a single common field, in which case a repetition value determined as a single value may be applied commonly to SPS NPUSCH and SPS NPDSCH. Alternatively, even if it is a single value, if different repetition values ​​are previously set for the same code point in the upper signal, the terminal may apply the repetition value determined according to the upper signal setting to SPS NPUSCH and SPS NPDSCH, respectively. The HARQ-ACK resource for SPS NPDSCH is a field that indicates resource information for NPUSCH containing HARQ-ACK information for SPS PDSCH; however, the said resource may be included in SPS NPUSCH and transmitted, in which case the HARQ-ACK resource for SPS NPDSCH field may be omitted. Alternatively, the HARQ-ACK resource for SPS NPDSCH field may be omitted even if the terminal does not transmit HARQ-ACK information for SPS PDSCH. And, if all DCI fields of [Table 49] (or DCI fields of specific combinations) indicate 0 or 1, the terminal can determine that the DCI format NX is considered to disable SPS NPDSCH and SPS NPUSCH.

[0796] [Table 49]

[0797]

[0798] FIG. 26 is a diagram showing the process of simultaneously activating and deactivating SPS NPUSCH and SPS NPDSCH in a single DCI format according to one embodiment of the present disclosure.

[0799] Referring to FIG. 26, the terminal receives a DCI format NX within an NPDCCH (2600), and if the corresponding field indicates the activation of the SPS NPDSCH and SPS NPUSCH, the terminal can determine the time and frequency resources of the SPS NPDSCH (2602) and SPS NPUSCH (2606) scheduled in the DCI format NX. Additionally, at least one of the period between consecutive SPS PDSCHs (2612, 2614) and the time interval information between the SPS PDSCH and SPS PUSCH (2616, 2618) may be set as a higher signal in advance. In the figure, it may be assumed that HARQ-ACK information for the SPS PDSCH is not transmitted or received separately, or is included in the SPS PUSCH. Subsequently, when the terminal receives a DCI format NX that disables the SPS NPUSCH and SPS NPDSCH via another NPDCCH (2608), the terminal may include HARQ-ACK information including whether the DCI format NX was received in the NPUSCH (2610). In this way, when the terminal performs a voice call, it does not need to separately receive a DCI format to individually enable or disable the SPS NPDSCH and SPS NPUSCH, so the voice call resource provision delay time and NPDCCH resource usage overhead can be reduced.

[0800] Alternatively, the terminal may obtain SPS NPUSCH information in DCI format N0 through a method similar to Example 1, and the SPS NPUSCH may follow a value that is pre-set as a higher signal. Specifically, information such as time and frequency resource information for SPS NPUSCH scheduling, MCS, repetitive transmission, and HARQ-ACK resource information (or presence / absence) may be pre-set as a higher signal, and this higher signal may be applied when the SPS NPUSCH is activated. Therefore, although FIG. 26 illustrates that the SPS NPUSCH is scheduled first and then the SPS NPUSCH is present, the opposite case may be possible.

[0801] Alternatively, the terminal may obtain SPS NPDSCH information in DCI format N1 through a method similar to Example 2, and the SPS NPUSCH may follow a value previously set as a higher signal. Specifically, information such as time and frequency resource information for SPS NPUSCH scheduling, MCS, and repetitive transmission may be set as a higher signal in advance, and this higher signal may be applied when the SPS NPDSCH is activated. Accordingly, with reference to FIG. 26, the terminal activates the SPS NPDSCH in the same manner as Example 2, and subsequently, the terminal may periodically transmit data based on the information related to the SPS NPUSCH scheduling information previously set as a higher signal.

[0802] Through the above method, the terminal may be able to receive periodic downlink and uplink resources through a single activation DCI format.

[0803] [Example 4]

[0804] In the following embodiments, a method for reducing power consumption of a terminal can be described when the terminal has one uplink and one downlink HARQ process. Basically, in a situation where the terminal has one uplink and one downlink HARQ process, if SPS NPDSCH and SPS NPUSCH are periodically activated, it may be impossible to receive NPDSCH and NPUSCH scheduling. This is because it is difficult to secure an additional HARQ process for other data processing while the terminal is using one HARQ process to handle SPS PDSCH and SPS PUSCH respectively. Therefore, in such a case, it may be possible for the terminal not to monitor the DCI format for NPDSCH and NPUSCH scheduling. Through this, the terminal can omit monitoring unnecessary control information, thereby reducing power consumption.

[0805] FIG. 27 is a diagram showing a terminal monitoring NPDCCH process according to one embodiment of the present disclosure.

[0806] Referring to FIG. 27, the terminal can periodically perform NPDCCH monitoring through 2700, 2701, 2702, 2703, 2704, 2705, 2706, and 2707. At this time, after NPDCCH 2701, the terminal receives activation information for SPS PDSCH or SPS PUSCH or both, and immediately after the procedure is completed, the terminal may not monitor NPDCCH (2702, 2703, 2704, 2705), or may not monitor DCI format N0 or DCI format N1 that schedules NPUSCH or NPDSCH within the NPDCCH, or may not monitor DCI format N0 or DCI format N1 containing a CRC scrambled with C-RNTI that schedules NPUSCH or NPDSCH within the NPDCCH. Subsequently, the terminal receives release information for the SPS PDSCH or SPS NPUSCH or both, and after the procedure is completed, it may again monitor the NPDCCH (2702, 2703, 2704, 2705) in the NPDCCH (2706, 2707), or monitor the DCI format N0 or DCI format N1 that schedules the NPUSCH or NPDSCH within the NPDCCH, or monitor the DCI format N0 or DCI format N1 containing a CRC scrambled with C-RNTI that schedules the NPUSCH or NPDSCH within the NPDCCH. Accordingly, in FIG. 27, the terminal may be able to consume power by not monitoring the NPDCCH containing a specific type of DCI format during the interval (2712) between 2710 and 2711.In FIG. 27, 2710 is described as the point in time when activation information is received for SPS PDSCH or SPS PUSCH, or both, and the procedure is completed; however, it is not limited to this and may be replaced with other conditions. For example, it may be the point in time when the terminal receives a DCI format instructing activation, or the point in time when the terminal transmits confirmation information regarding it after the activation instruction, or the point in time when the terminal receives the first SPS NPDSCH or transmits the first SPS NPUSCH after activation, or the point in time when the terminal receives the last transmitted / received SPS NPDSCH for the same TB or transmits the last transmitted / received SPS NPUSCH for the same TB. In FIG. 27, 2711 is described as the point in time when release information is received for SPS PDSCH or SPS PUSCH, or both, and the procedure is completed; however, it is not limited to this and may be replaced with other conditions. For example, at the time when the terminal receives a DCI format instructing release, or at the time when the terminal transmits confirmation information regarding it after the release instruction, or at the time when the terminal receives an SPS NPDSCH and transmits an NPUSCH containing HARQ-ACK information regarding it, or after 2710, a specific offset value may be replaced and applied.

[0807] Alternatively, if, within the NPDCCH, a DCI format instructing the release of the SPS NPDSCH and a DCI format instructing the scheduling of the NPDSCH exist together after the SPS NPDSCH is activated and before it is released, the terminal may be able to monitor only the DCI format instructing the release of the SPS NPDSCH. If, within the NPDCCH, a DCI format containing a CRC scrambled with CS-RNTI instructing the release of the SPS NPDSCH and a DCI format containing a CRC scrambled with C-RNTI instructing the scheduling of the NPDSCH exist together, the terminal may be able to monitor only the DCI format containing a CRC scrambled with CS-RNTI instructing the release of the SPS NPDSCH.

[0808] Alternatively, if, within the NPDCCH, a DCI format instructing the release of the SPS NPUSCH and a DCI format instructing the scheduling of the NPDSCH exist together after the SPS NPUSCH is activated and before it is released, the terminal may be able to monitor only the DCI format instructing the release of the SPS NPUSCH. If, within the NPDCCH, a DCI format containing a CRC scrambled with CS-RNTI instructing the release of the SPS NPUSCH and a DCI format containing a CRC scrambled with C-RNTI instructing the scheduling of the NPUSCH exist together, the terminal may be able to monitor only the DCI format containing a CRC scrambled with CS-RNTI instructing the release of the SPS NPUSCH.

[0809] [Example 5]

[0810] In the following embodiments, terminal operation can be described in cases where SPS PDSCH and SPS PUSCH overlap in terms of time resources. NB-IoT terminals may inherently have half-duplex constraints. Consequently, it is difficult for the terminal to perform simultaneous transmission and reception, even within the FDD band. Furthermore, in satellite communication, since the terminal calculates the Timing Advance (TA) based on satellite position and terminal position information, it may be possible for at least one symbol of SPS PDSCH and SPS PUSCH to overlap in terms of time resources at a specific point in time from the terminal's perspective. Therefore, when such a case occurs, it is necessary to define terminal operation. The terminal may be able to apply at least one of the following methods or a combination of some thereof.

[0811] Method a-1: Always transmit with priority to SPS NPUSCH and do not receive SPS NPDSCH. Accordingly, the terminal does not transmit HARQ-ACK information associated with SPS NPDSCH.

[0812] Method a-2: Always receive SPS NPDSCH first and do not transmit SPS NPUSCH.

[0813] Method a-3: It may be possible to select either Method a-1 or Method a-2 based on the upper signal or L1 signal.

[0814] Method a-4: It may be possible to determine Method a-1 or Method a-2 based on the order in which SPS NPUSCH and SPS NPDSCH are activated. For example, if SPS NPUSCH is activated before SPS NPDSCH, the terminal may be able to apply Method a-1 (or Method a-2). Or, for example, if SPS NPDSCH is activated before SPS NPUSCH, the terminal may be able to apply Method a-1 (or Method a-2).

[0815] FIG. 28 is a flowchart showing the process of a terminal transmitting and receiving SPS information in an IoT NTN according to one embodiment of the present disclosure.

[0816] Referring to FIG. 28, according to the previously described embodiments 1 to 4, the terminal may receive SPS upper signal information related to the downlink or uplink after connecting to a cell operating as NB-IoT (2810). Subsequently, the terminal may receive an L1 signal that activates SPS NPUSCH or SPS NPDSCH (2820). Subsequently, the terminal may periodically transmit and receive SPS NPUSCH or SPS NPDSCH (2830). Subsequently, the terminal may receive an L1 signal from the base station that releases (or deactivates) the previously activated SPS NPUSCH or SPS NPDSCH (2840). Subsequently, the terminal may not transmit or receive the previously periodically set SPS NPUSCH or SPS NPDSCH (2850).

[0817] [Example 6]

[0818] This embodiment proposes an integrated framework for efficiently controlling traffic in which periodic and small packets occur bidirectionally, such as VoIP (Voice over IP), particularly in an NTN environment including geostationary (GEO) satellites. Conventional NB-IoT technology relied on dynamic scheduling, but this can cause long latency and excessive control channel overhead in NTN. Accordingly, this embodiment proposes a method to simultaneously activate (Joint Activation) or release (Joint Release) downlink (DL) and uplink (UL) resources through field reinterpretation without changing the payload size of the DCI (Downlink Control Information) format N0 and N1 defined in existing 3GPP standards.

[0819] A terminal (UE) and a base station (eNB) according to one embodiment of the present invention can operate considering long round-trip delay time (RTT) in an NTN environment. Before a voice call session is established, or simultaneously with its establishment, the base station can set common parameters for SPS operation and link-specific implicit parameters to the terminal through Radio Resource Control (RRC) signaling.

[0820] Specifically, an RRC configuration message (e.g., SPS-Config-NTN) may include the following information.

[0821] First, SPS-C-RNTI, a unique identifier for identifying SPS operations, is set.

[0822] Second, a joint activation offset is defined. This is a time interval parameter that determines the transmission time of a secondary link based on the transmission time of a primary link. In particular, in this embodiment, the offset can be set within a sufficiently large range (e.g., 40ms to 640ms or more) to absorb delays in the hundreds of milliseconds (ms) and the terminal's timing advance (TA) value, going beyond a simple switching gap.

[0823] Third, implicit parameters are set for each link. Since DCI format N1 can carry only downlink information and DCI format N0 can carry only uplink information, when a terminal activates bidirectional communication with a single DCI, information about the opposite link that is not included in the DCI may be required. To this end, the RRC message may include implicit parameters for the uplink (UL MCS, resource unit, number of repetitions, etc.) and implicit parameters for the downlink (DL MCS, resource allocation, number of repetitions, etc.) in the form of a structure, respectively.

[0824] Fourth, considering the latency sensitivity of voice traffic, a flag (e.g., harq-FeedbackEnabler-Voice) indicating whether to use HARQ feedback may be included. In an NTN environment, since delays caused by retransmissions lead to voice quality degradation, the flag may be set to 'False' to rely on blind repetition.

[0825] The base station may initiate a bidirectional SPS by selecting either a downlink grant (DCI N1) or an uplink grant (DCI N0) depending on the source of the traffic (terminal utterance or counterparty utterance). This embodiment may follow a consistent 'explicit primary - implicit secondary' structure regardless of which DCI format is used.

[0826] (1) Mode 1: Downlink-driven activation using DCI format N1

[0827] When a base station intends to activate bidirectional communication by starting downlink transmission, it may transmit DCI format N1. At this time, the terminal can check the 'NPDCCH Order Indicator' field after confirming that the received DCI has been scrambled into SPS-C-RNTI.

[0828] In existing standards, when the corresponding field is '0', it refers to a standard DCI N1. In this embodiment, when the corresponding field is set to '1', it is defined as a 'Joint Activation' trigger. This utilizes a field combination not used in existing standards, thereby ensuring backward compatibility.

[0829] A terminal that detects an order indicator set to '1' operates as follows.

[0830] First, at least one of the Resource Assignment, MCS, Scheduling Delay, and Repetition Number fields included in DCI N1 can be decoded to determine the Downlink (DL) SPS resource (Explicit Activation).

[0831] At the same time, the terminal may load (or apply) uplink implicit parameters (Implicit UL Parameters) that are pre-stored in RRC to obtain uplink information that does not exist in DCI N1. The terminal may calculate the uplink transmission time (T_{UL}) by adding the previously set jointActivationOffset at the time when downlink reception ends (or starts), and activate the uplink (UL) SPS by applying the parameters stored at that time.

[0832] At this time, the New Data Indicator (NDI) may be set to '0' for the validation of DCI N1. Additionally, if the aforementioned HARQ feedback is disabled, the 'HARQ-ACK Resource' field, which has a size of 4 bits within DCI N1, no longer needs to indicate the ACK / NACK resource. Therefore, in this embodiment, these 4 bits may be ignored (Reserved) or dedicated to additional offset information for fine timing adjustments.

[0833] (2) Second mode: Uplink-driven activation using DCI format N0

[0834] If the terminal needs to transmit voice data first, the base station can instruct activation by transmitting DCI format N0. Since the payload size of DCI N0 is very limited (typically 23 bits), it may be difficult to allocate a separate flag bit.

[0835] To address this, the present embodiment takes into account that voice traffic uses a low transmission rate and a robust modulation scheme (QPSK). That is, the upper bits indicating the high index of the 4-bit MCS field may be unnecessary in voice services.

[0836] Accordingly, the present embodiment can reinterpret the most significant bit (MSB) of the MCS field of DCI N0 as a 'joint enable flag'. When the MCS MSB of DCI N0 masked with SPS-C-RNTI is '1', the terminal recognizes this as a joint enable command and can determine the actual uplink MCS (range 0 to 7) using only the remaining lower 3 bits.

[0837] In this case, the operation of the terminal may be symmetric to the first mode. The terminal may activate the uplink (UL) SPS (Explicit Activation) using at least one of the subcarrier indication, resource allocation, and MCS (lower 3 bits) of DCI N0. At the same time, it may load (or apply) the downlink implicit parameters stored in RRC and open the downlink (DL) SPS reception window at a time calculated by applying jointActivationOffset at the time of uplink transmission.

[0838] (3) Strategy to ensure performance equivalence in validation

[0839] High reliability is required for the SPS activation signal because it causes continuous resource conflicts when a false alarm occurs. DCI N1 can produce a 'Virtual CRC' effect of about 5 bits or more by utilizing NDI (1 bit) and HARQ-ACK resources (4 bits). On the other hand, DCI N0 has low reliability because it lacks spare bits, so conventionally only NDI (1 bit) and RV (1 bit) are used for verification.

[0840] This embodiment applies a 'Field Fixing' technique to ensure verification performance (approximately 5 bits) equivalent to DCI N1 even when DCI N0-based activation is enabled.

[0841] Since voice traffic is periodic, fine scheduling delay adjustments for the initial transmission are not essential. Therefore, in this embodiment, the scheduling delay field (2 bits) of DCI N0 can be fixed to '00' and dedicated as a verification bit. Additionally, the second MSB (1 bit) of the MCS field can also be fixed to '0', and the existing fixed conditions for NDI (1 bit) and RV (1 bit) can be maintained.

[0842] As a result, DCI N0 secures a total of 5 bits [NDI(1) + RV(1) + delay(2) + MCS 2nd MSB(1)] for verification purposes, which can provide a level of robustness equivalent to DCI N1.

[0843] When a voice call ends or enters a silent period, the base station may release resources. At this time, depending on the situation, both bidirectional resources may be released (Joint Release), or only resources in a specific direction may be released (Single Release) to correct a state mismatch of the terminal. This embodiment can be implemented by introducing a 'Scope Field' in addition to the existing release condition (Validation Check), without defining a separate DCI format for release.

[0844] When release is instructed using DCI format N1, the terminal can verify whether the resource allocation field is set to '111', the MCS to '1111', etc., in accordance with existing standards. In addition, this embodiment can check the value of the HARQ-ACK resource field (4 bits). If the corresponding field is '0000', the terminal releases only the downlink SPS setting and maintains the uplink SPS. On the other hand, if the corresponding field is set to '1111', the terminal immediately releases both the downlink and uplink SPS settings and terminates communication.

[0845] Similarly, when release is instructed using DCI format N0, the terminal checks conditions such as resource allocation '111' and MCS '1111', and then checks the Subcarrier Indication field (6 bits). For example, if the field is '111111', only the uplink SPS is released, and if it is '000000', both bidirectional SPS are released.

[0846] This selective release mechanism provides base stations with scheduling flexibility and offers a means to explicitly resolve link-to-link state mismatch issues that can occur due to long latency, particularly in NTN environments.

[0847] The terminal according to the above-described embodiment can periodically monitor the search space. When a scrambled DCI in SPS-C-RNTI is detected, the processor of the terminal can first determine the type of DCI format (N0 or N1).

[0848] If DCI is N1, the processor can determine whether the joint is enabled by checking whether the NPDCCH order indicator is '1'. If the joint is enabled, the receiving circuit can be controlled with parameters decoded from DCI to receive downlink packets, and the transmitting circuit can be controlled by retrieving uplink parameters from RRC memory to transmit uplink packets after an offset time.

[0849] If DCI is N0, the processor can verify whether the MSB of the MCS is '1' and whether the scheduling delay field, etc., has a fixed value ('00'). Once verification is complete, the uplink packet is transmitted with the DCI parameter, and the downlink receive window can be opened at a time calculated based on the RRC parameter and offset.

[0850] According to the present invention, when supporting voice traffic in an NB-IoT NTN system, not only is the dynamic scheduling overhead that occurs with every packet transmission eliminated, but the double overhead of having to activate the downlink and uplink separately is also reduced by 50%. In addition, by maintaining the DCI payload size and reinterpreting existing fields, it is possible to implement the system without increasing the complexity of blind decoding in the terminal. Furthermore, through offset settings considering the large latency of NTN, support for HARQ disabling, and an enhanced validation technique for DCI N0, it is possible to provide reliable and uninterrupted voice call services even in a satellite communication environment.

[0851] FIG. 29 is a flowchart showing the process of a terminal adaptively searching for control information according to one embodiment of the present disclosure.

[0852] Referring to FIG. 29, according to Examples 1 to 6, the terminal may receive SPS upper signal information related to the downlink or uplink after connecting to a cell operating as NB-IoT (2910). Subsequently, the terminal may receive an L1 signal that activates the SPS NPUSCH or SPS NPDSCH (2920). Subsequently, if the terminal supports only one HARQ process for the uplink or downlink data, the terminal may not perform a search for a DCI format including a CRC scrambled with a specific DCI format or a specific RNTI in a specific NPDCCH interval (2930). Subsequently, the terminal may receive an L1 signal from the base station that releases (or deactivates) the previously activated SPS NPUSCH or SPS NPDSCH (2940). Afterwards, the terminal can perform a search again for a DCI format including a CRC scrambled with a specific DCI format or a specific RNTI in the specific NPDCCH section where the search was not performed (2950).

[0853] Although the entity transmitting and receiving by the terminal in the above embodiments has been primarily described as a base station, in satellite communication, it is not limited to this, and a satellite may be the entity.

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

[0855] Referring to FIG. 30, the terminal may include a transceiver (referring to a terminal receiver (3000) and a terminal transmitter (3010)), a memory (not shown), and a terminal processing unit (3005, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (3000, 3010), memory, and terminal processing unit (3005) 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 components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

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

[0857] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

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

[0859] In addition, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.

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

[0861] Referring to FIG. 31, a base station may include a transceiver unit (referring to a base station receiver unit (3100) and a base station transmitter unit (3110), a memory (not shown), and a base station processing unit (3105, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (3100, 3110), the memory, and the base station processing unit (3105) 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 components or fewer components than the components described above. Furthermore, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

[0863] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

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

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

[0866] FIG. 32 is a block diagram illustrating the internal structure of a satellite according to one embodiment of the present disclosure.

[0867] As illustrated in FIG. 32, the satellite of the present disclosure may include a satellite receiver (3200), a satellite transmitter (3220), and a satellite processing unit (3210). The receiver, transmitter, and processing unit may be composed of multiple units. That is, it may be composed of a receiver and a transmitter for transmitting and receiving signals from a terminal, and a receiver and a transmitter for transmitting and receiving signals from a base station (and a receiver and a transmitter for transmitting and receiving signals from another satellite). Of course, it is not limited to the above examples, and the satellite may include more or fewer components. Additionally, the satellite receiver (3200), the satellite transmitter (3220), and the satellite processing unit (3210) may be composed of a single chip.

[0868] In the embodiment of the present invention, the satellite receiver (3200) and the satellite transmitter (3220) may be collectively referred to as the satellite transceiver. The transceiver can transmit and receive signals with a terminal and a base station. The signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. Of course, the components of the transceiver are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver may receive a signal through a wireless channel and output it to a satellite processing unit (3210), and transmit the signal output from the satellite processing unit (3210) through a wireless channel. The satellite processing unit (3210) may include a compensator (pre-compensator) for correcting frequency offset or Doppler shift, and may include a device capable of tracking a location from GPS, etc. Additionally, the satellite processing unit (3210) may include a frequency shift function capable of shifting the center frequency of the received signal. The satellite processing unit (3210) may control a series of processes to enable the satellite, base station, and terminal to operate according to the embodiment of the present invention described above. For example, the satellite receiving unit (3200) may receive a PRACH preamble from the terminal, transmit the corresponding RAR back to the terminal, and decide to transmit TA information to the base station. Subsequently, the satellite transmitting unit (3220) may transmit the corresponding signals at a determined time. In this disclosure, the satellite processing unit (3210) may be defined as a circuit or an application-specific integrated circuit or at least one processor. Of course, it is not limited to the above examples.

[0869] According to one embodiment of the present disclosure, the satellite may include a memory (not shown). The memory may store programs and data necessary for the operation of the satellite. Additionally, the memory may store control information or data included in signals acquired from the satellite. The memory may be composed of a storage medium or a combination of storage media, such as ROM, RAM, a hard disk, a CD-ROM, and a DVD.

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

[0871] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. 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 this disclosure.

[0872] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0873] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.

[0874] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0875] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

[0876] Meanwhile, the order of description in the drawings illustrating the method of the present invention does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.

[0877] Alternatively, drawings describing the method of the present invention may omit some components and include only some components to the extent that the essence of the present invention is not impaired.

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

[0879] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and is not limited to the embodiments disclosed. Those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included within the scope of the present disclosure.

Claims

1. In a method performed by UE (user equipment) in a satellite communication system, A step of receiving semi-persistent scheduling (SPS) upper signal information related to at least one of a downlink or an uplink from a base station; A step of receiving an L1 signal from the base station that activates at least one of an SPS NPUSCH (narrowband physical uplink shared channel) or an SPS NPDSCH (narrowband physical downlink shared channel); and A method comprising the step of periodically transmitting and receiving at least one of the above SPS NPUSCH or the above SPS NPDSCH with the base station.

2. The method of claim 1, wherein the L1 signal is a DCI (downlink control information) containing instructions to activate the SPS NPUSCH and the SPS NPDSCH.

3. In paragraph 2, the above SPS upper signal information is, A method comprising at least one of period information between the SPS NPDSCH, time interval information between the SPS NPDSCH or the SPS NPUSCH.

4. In paragraph 1, the SPS upper signal information is, A method comprising at least one of an identifier for identifying SPS operations, a joint activation offset, implicit parameters per uplink and downlink, or a flag indicating whether to use HARQ (hybrid automatic repeat request) feedback.

5. In Paragraph 2, If the above DCI is a first format, a step of identifying that joint activation has been triggered based on an indicator included in the above DCI; In response to identifying that the joint activation is triggered, a step of determining a downlink SPS resource based on at least one of the resource allocation, MCS (modulation and coding scheme), scheduling delay, or iteration count fields included in the DCI; and A method further comprising the step of applying an uplink parameter in response to identifying that the above joint activation is triggered.

6. In Paragraph 2, If the above DCI is a second format, a step of identifying that joint activation has been triggered based on at least one bit information included in the above DCI; In response to identifying that the joint activation is triggered, a step of activating an uplink SPS using at least one of a subcarrier indication, resource allocation, and modulation and coding scheme (MCS) included in the DCI; and A method further comprising the step of applying a downlink implicit parameter in response to identifying that the above joint activation is a trigger.

7. In Paragraph 1, A method comprising the step of receiving an L1 signal from the base station that disables at least one of the previously activated SPS NPUSCH or SPS NPDSCH.

8. In the method performed by a base station in a satellite communication system, A step of transmitting SPS (semi-persistent scheduling) upper signal information associated with at least one of a downlink or an uplink to a terminal; A step of transmitting an L1 signal to the terminal that activates at least one of SPS NPUSCH (narrowband physical uplink shared channel) or SPS NPDSCH (narrowband physical downlink shared channel); and A method comprising the step of periodically transmitting and receiving at least one of the SPS NPUSCH or the SPS NPDSCH with the terminal.

9. A method according to claim 8, wherein the L1 signal is a DCI (downlink control information) containing instructions to activate the SPS NPUSCH and the SPS NPDSCH.

10. In paragraph 9, the above SPS upper signal information is, A method comprising at least one of period information between the SPS NPDSCH, time interval information between the SPS NPDSCH or the SPS NPUSCH.

11. In paragraph 8, the above SPS upper signal information is, A method comprising at least one of an identifier for identifying SPS operations, a joint activation offset, implicit parameters per uplink and downlink, or a flag indicating whether to use HARQ (hybrid automatic repeat request) feedback.

12. In Paragraph 8, A method comprising the step of transmitting an L1 signal to disable at least one of the SPS NPUSCH or SPS NPDSCH that is already activated to the terminal.

13. In a satellite communication system, regarding UE (user equipment), Transmitter / receiver; and It includes at least one processor, and the at least one processor, Receiving semi-persistent scheduling (SPS) upper signal information related to at least one of the downlink or uplink from a base station, and Receiving an L1 signal from the base station that activates at least one of SPS NPUSCH (narrowband physical uplink shared channel) or SPS NPDSCH (narrowband physical downlink shared channel), and A UE configured to periodically transmit and receive at least one of the SPS NPUSCH or the SPS NPDSCH with the base station.

14. In paragraph 13, the UE, wherein the L1 signal is a DCI (downlink control information) containing instructions to activate the SPS NPUSCH and the SPS NPDSCH.

15. In a base station of a satellite communication system, Transmitter / receiver; and It includes at least one processor, and the at least one processor, Transmit SPS (semi-persistent scheduling) upper signal information related to at least one of the downlink or uplink to a terminal, and Transmitting an L1 signal to the terminal that activates at least one of SPS NPUSCH (narrowband physical uplink shared channel) or SPS NPDSCH (narrowband physical downlink shared channel), and A base station configured to periodically transmit and receive at least one of the above SPS NPUSCH or the above SPS NPDSCH with the terminal.

Images