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

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. More specifically, the present disclosure provides a method performed by a terminal in a satellite communication system, the method comprising the steps of: receiving, from a base station, information for configuring an operation scheme when collision occurs between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) scheme of the terminal, wherein the information indicates any one of a first scheme in which the uplink signal transmission is prioritized over the downlink signal reception when the collision occurs, and a second scheme in which downlink signal reception is prioritized over the uplink signal transmission when the collision occurs; and performing, with the base station, the uplink signal transmission and the downlink signal reception, on the basis of any one of the first scheme and the second scheme, wherein the uplink signal transmission and the downlink signal reception are based on dynamic scheduling on the basis of downlink control information or semi-persistent scheduling on the basis of higher layer signaling.

Description

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

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

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

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

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

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

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

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. This could serve as a foundation for the development of next-generation distributed computing technologies that utilize these technologies. As described above, with the advancement of wireless communication systems, a variety of services can be provided, and thus, methods for providing these services seamlessly are required.

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

[0009] According to one embodiment of the present disclosure, a method performed by a terminal in a satellite communication system comprises the steps of: receiving, from a base station, information for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) scheme of the terminal; the information indicating either a first scheme in which the uplink signal transmission is prioritized over the downlink signal reception in the case of collision or a second scheme in which the downlink signal transmission is prioritized over the uplink signal transmission in the case of collision; and performing, with the base station, the uplink signal transmission and the downlink signal reception based on either the first scheme or the second scheme, wherein the uplink signal transmission and the downlink signal reception may be based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on higher layer signaling.

[0010] According to one embodiment of the present disclosure, a method performed by a base station in a satellite communication system comprises the steps of: receiving, from a terminal, information for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) scheme of the terminal; the information indicating either a first scheme in which the uplink signal transmission is prioritized over the downlink signal reception in the case of collision or a second scheme in which the downlink signal transmission is prioritized over the uplink signal transmission in the case of collision; and performing, based on either one of the first scheme and the second scheme, transmission for reception of the uplink signal transmission by the terminal and transmission for reception of the downlink signal by the terminal, wherein the uplink signal transmission by the terminal and the downlink signal reception by the terminal may be based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on higher layer signaling.

[0011] According to one embodiment of the present disclosure, in a satellite communication system, a terminal includes: a transceiver; and a controller connected to the transceiver, wherein the controller receives, from a base station, information for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) method of the terminal, the information indicating either a first method in which the uplink signal transmission is prioritized over the downlink signal reception in case of collision, or a second method in which the downlink signal transmission is prioritized over the uplink signal transmission in case of collision, and is configured to perform, with the base station, the uplink signal transmission and the downlink signal reception based on either the first method or the second method, wherein the uplink signal transmission and the downlink signal reception may be based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on higher layer signaling.

[0012] According to one embodiment of the present disclosure, in a satellite communication system, a base station comprises: a transceiver; And a controller connected to the transceiver, wherein the controller receives, from a terminal, information for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) method of the terminal, the information indicating either a first method in which the uplink signal transmission is prioritized over the downlink signal reception in case of collision or a second method in which the downlink signal transmission is prioritized over the uplink signal transmission in case of collision, and is configured to perform transmission for reception of the uplink signal transmission of the terminal and the downlink signal reception of the terminal based on either one of the first method and the second method, wherein the uplink signal transmission of the terminal and the downlink signal reception of the terminal may be based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on higher layer signaling.

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

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

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

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

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

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

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

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

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

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

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

[0024] FIG. 11 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0031] FIG. 18 illustrates a procedure for a base station to control transmission power of a terminal in a cellular system according to one embodiment of the present disclosure.

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

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

[0034] FIG. 21 is a diagram illustrating the distance between a terminal and a satellite of a communication satellite according to the elevation angle between the satellite and the terminal according to one embodiment of the present disclosure.

[0035] FIG. 22 is a diagram showing a situation in which a half-duplex terminal receives uplink and downlink scheduling according to one embodiment of the present disclosure.

[0036] FIG. 23 is a diagram showing a situation in which a half-duplex terminal receives uplink and downlink scheduling according to one embodiment of the present disclosure.

[0037] FIG. 24 is a diagram illustrating a processing time of a terminal according to timing advance when the terminal receives a first signal and transmits a second signal corresponding thereto in a 5G or NR system according to an embodiment of the present disclosure.

[0038] FIG. 25 is a diagram illustrating a situation in which a half-duplex terminal according to one embodiment of the present disclosure is scheduled in a satellite communication system.

[0039] FIG. 26 is a diagram illustrating a situation in which downlink resources and uplink resources are periodically set in a satellite communication system according to one embodiment of the present disclosure.

[0040] FIG. 27 is a diagram illustrating a TA reporting MAC CE structure reported by a terminal to a base station according to one embodiment.

[0041] FIG. 28 is a flowchart illustrating a procedure for a half-duplex terminal to operate in a satellite network according to one embodiment of the present disclosure.

[0042] FIG. 29 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0043] FIG. 30 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

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

[0048] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a satellite, a gateway, a ground station, a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although a 5G system or a next-generation system may be described as an example below, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communications and mobile communications technologies developed after the fifth generation of mobile communications technology (5G, new radio, NR). The term "5G" below may also encompass existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

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

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

[0051] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

[0053] As a representative example of a broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The multiple access method typically allocates and operates the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so that orthogonality is achieved, thereby distinguishing the data or control information of each user.

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

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

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

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

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

[0059] [NR time-frequency resources]

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

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

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

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

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

[0065] μ 0141011142022144043148084141601651432032

[0066] [Bandwidth Part (BWP)]

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

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

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

[0070]

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

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

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

[0074] In one embodiment, if the bandwidth supported by a terminal is smaller than the system bandwidth, the terminal can be supported through bandwidth-part configuration. For example, the base station can configure the frequency location (configuration information 2) of the bandwidth portion for the terminal, and the terminal can transmit and receive data at a specific frequency location within the system bandwidth.

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

[0076] Furthermore, according to one embodiment, to reduce power consumption of the terminal, the base station can set bandwidth portions with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a traffic-free situation can be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station can set a bandwidth portion with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free situation, 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.

[0077] In the method of configuring the bandwidth part, terminals before RRC connection (Connected) can receive configuration information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which downlink control information (DCI) that schedules a system information block (SIB) can be transmitted from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control region configured by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the physical downlink shared channel (PDSCH) on which the SIB is transmitted through the configured initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0078] [Bandwidth Part (BWP) Change]

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

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

[0081]

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

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

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

[0085] [SS / PBCH block]

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

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

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

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

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

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

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

[0093] [PDCCH: DCI related]

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

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

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

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

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

[0099]

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

[0101]

[0102]

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

[0104]

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

[0106]

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

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

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

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

[0111]

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

[0113] FIG. 5 is a diagram illustrating a structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. Referring to FIG. 5, an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in 5G is illustrated. According to FIG. 5, the basic unit of time and frequency resources constituting the control channel may be referred to as a REG (Resource Element Group, 503), and a REG (503) may be defined as 1 OFDM symbol (501) in the time axis and 1 PRB (Physical Resource Block, 502) in the frequency axis, i.e., 12 subcarriers. A base station may concatenate REGs (503) to configure a downlink control channel allocation unit.

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

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

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

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

[0118]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0142]

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

[0144] [Mathematical Formula 1]

[0145]

[0146] - L: Integration level

[0147] - n CI : Carrier Index

[0148] - N CCE,p : Total number of CCEs existing within the control region p

[0149] - : slot index

[0150] - : Number of PDCCH candidates for aggregation level L

[0151] - =0, ... , -1: PDCCH candidate index of aggregation level L

[0152] - i=0, ..., L-1

[0153] - , Y p,-1 =n RNTI ≠0, A p =39827 for pmod3=0, A p=39829 for pmod3=1, A p =39839 for pmod3=2, D=65537

[0154] - n RNTI : Terminal identifier

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

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

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

[0158] [PDCCH: span]

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

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

[0161] [PDCCH: Terminal Capability Report]

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

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

[0164]

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

[0166]

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

[0168]

[0169]

[0170] A terminal can report to the base station whether it supports the aforementioned terminal capabilities 2 and / or 3 and related parameters. Based on the reported terminal capabilities, the base station can allocate time-domain resources for the common search space and terminal-specific search space. When allocating resources, the base station can ensure that the MO is not placed in a location that the terminal cannot monitor.

[0171] [QCL, TCI state]

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

[0173]

[0174] The spatial RX parameter can 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.

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

[0176]

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

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

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

[0180]

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

[0182]

[0183] Table 16-3 shows the valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, which is synonymous with CSI-RS for L1 RSRP (Reference Signal Received Power) reporting). CSI-RS for BM refers to NZP CSI-RS with a repetition parameter set to On or Off among CSI-RSs and trs-Info not set to true.

[0184]

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

[0186]

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

[0188]

[0189] A representative QCL configuration method according to Tables 16 to 20 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 statistical characteristics that can be measured from SSB and TRS to each antenna port to assist the terminal's reception operation.

[0190] [PDCCH: TCI state related]

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

[0192]

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

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

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

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

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

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

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

[0200] [PDCCH: QCL prioritization rule related]

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

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

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

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

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

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

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

[0208] [Rate matching / Puncturing related]

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

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

[0211] Rate Matching Operation

[0212] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that want to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

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

[0214] Puncture action

[0215] If a base station wants to transmit symbol sequence A to a terminal, and there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0216] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

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

[0218] FIG. 11 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

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

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

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

[0222] RB symbol level

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

[0224] - As a reserved resource within the bandwidth section, the time and frequency resource domains of the reserved resource may be set by combining RB-level bitmaps and symbol-level bitmaps along the frequency axis. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB-level and symbol-level bitmap pair are repeated may additionally be set.

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

[0226] RE level

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

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

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

[0230] [Regarding LTE CRS rate match]

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

[0232] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides a function that allows one CRS pattern to be configured per serving cell. In Rel-16 NR, this function has been extended to allow multiple CRS patterns to be configured per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can configure one CRS pattern per LTE carrier, and a multi-TRP configured terminal can configure two CRS patterns per LTE carrier. For example, a single-TRP configured terminal can configure up to three CRS patterns per serving cell via the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can configure CRS per TRP. That is, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are set as above, whether both the CRS patterns of TRP1 and TRP2 are applied to a specific PDSCH (Physical Downlink Shared Channel) or only the CRS pattern for one TRP is determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, and in other cases, the CRS patterns of both TRPs are applied.

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

[0234]

[0235]

[0236]

[0237] [PDSCH: Processing Time]

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

[0239] [Equation 2]

[0240]

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

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

[0243]

[0244]

[0245] -κ:64

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

[0247] - If l1, which indicates the PDSCH DMRS location value, is 12, N in [Table 24] 1,0 has a value of 14, otherwise it has a value of 13.

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

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

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

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

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

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

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

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

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

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

[0258] - If L = 2,

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

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

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

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

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

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

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

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

[0267] N according to the scheduled PDCCH subcarrier spacing according to one embodiment pdsch is as shown in the table below.

[0268]

[0269] [SRS related]

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

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

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

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

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

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

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

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

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

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

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

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

[0282]

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

[0284]

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

[0286] [PUSCH: Transmission method related]

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

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

[0289]

[0290]

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

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

[0293]

[0294]

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

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

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

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

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

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

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

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

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

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

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

[0306] [PUSCH: Preparation time]

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

[0308] [Equation 3]

[0309]

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

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

[0312] μPUSCH preparation time N2[symbols]010112223336

[0313] μPUSCH preparation time N2[symbols]0515.5211 for frequency range 1

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

[0315] - κ:64

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

[0317] - T c: 1(Δf max ·N f ), Δf max =480·10 3 Hz, N f =4096.

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

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

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

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

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

[0323] [PUSCH: Repetitive Transmission Related]

[0324] The following describes in detail the repetitive transmission of uplink data channels in 5G systems. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can be configured with either PUSCH repetitive transmission type A or B via upper layer signaling.

[0325] PUSCH repetitive transmission type A

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

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

[0328] PUSCH repetitive transmission type B

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

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

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

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

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

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

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

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

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

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

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

[0340] [PUSCH: Frequency Hopping Process]

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

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

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

[0344] [Equation 4]

[0345]

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

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

[0348] [Equation 5]

[0349]

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

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

[0352] [Equation 6]

[0353]

[0354] In Equation 6, n is the index of nominal repetition, RB Offset Indicates the RB offset between two hops via upper layer parameters.

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

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

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

[0358]

[0359]

[0360]

[0361]

[0362]

[0363]

[0364]

[0365]

[0366]

[0367]

[0368]

[0369]

[0370]

[0371]

[0372]

[0373]

[0374]

[0375]

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

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

[0378] - CSI-IM resources for interference measurements

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

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

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

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

[0383]

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

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

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

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

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

[0389] CSI request fieldCSI trigger stateCSI-ReportConfigldCSI-ResourceConfigld00no CSI requestN / AN / A01CSI trigger state#1CSI report#1CSI resource#1,CSI report#2CSI resource#210CSI trigger state#2CSI report#3CSI resource#311CSI trigger state#3CSI report#4CSI resource#4

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

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

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

[0393] aperiodicTriggeringOffsetOffset X00 slot11 slot22 slot33 slot44 slot516 slot624 slot

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

[0395] In an example (1310) of FIG. 13, the terminal can monitor the PDCCH (1311) to obtain DCI format 0_1, and from this, can obtain scheduling information and CSI request information for the PUSCH (1315). The terminal can obtain resource information for the CSI-RS (1312) to be measured from the received CSI request indicator. An example (1310) of FIG. 13 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (1312) in a slot in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received (corresponding to slot 0 (1316) of FIG. 13), and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (1315).

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

[0397]

[0398]

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

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

[0401] [Regarding terminal capability reporting]

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

[0403] A base station can transmit a UE capability inquiry message requesting capability reporting to a connected UE. The UE capability inquiry message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on supported frequency band combinations. Furthermore, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station. Alternatively, the base station can include multiple UE capability inquiry messages containing UE capability requests for each RAT type and transmit them to the UE. In other words, the UE capability inquiry can be repeated multiple times within a single message, and the UE can compose and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, EN-DC (E-UTRA - NR dual connectivity). Furthermore, although the UE capability inquiry message is typically transmitted initially after the UE is connected to the base station, the base station can request it under any conditions when necessary.

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

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

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

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

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

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

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

[0411] [CA / DC related]

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

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

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

[0415] - Transfer of user plane data

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

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

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

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

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

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

[0422] - User data transfer function

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

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

[0425] - PDCP PDU reordering for reception

[0426] - Duplicate detection of lower layer SDUs

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

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

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

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

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

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

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

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

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

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

[0437] - Re-segmentation of RLC data PDUs

[0438] - Reordering of RLC data PDUs

[0439] - Duplicate detection function

[0440] - Protocol error detection

[0441] - RLC SDU discard function

[0442] - RLC re-establishment function

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

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

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

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

[0447] - Multiplexing / demultiplexing of MAC SDUs

[0448] - Scheduling information reporting function

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

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

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

[0452] - MBMS service identification function

[0453] - Transport format selection function

[0454] - Padding function

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

[0456] The detailed structure of the wireless protocol structure can change in various ways depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, as in 1500. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, as in 1510, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, as in 1520, but multiplexes the PHY layer through the MAC layer.

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

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

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

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

[0461] In the present disclosure below, the above examples are described through multiple embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0462] [NC-JT related]

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

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

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

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

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

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

[0469] Referring to FIG. 16, an example (1600) for Coherent Joint Transmission (C-JT) supporting coherent precoding between each cell, TRP or / and beam is illustrated.

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

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

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

[0473] At this time, various wireless resource allocations can be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1640), when the frequency and time resources used by multiple TRPs do not overlap at all (1645), and when some of the frequency and time resources used by multiple TRPs overlap (1650).

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

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

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

[0477] Case #2 (1705) shows an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted respectively, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

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

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

[0480] Case #3 (1710) shows an example in which, in a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for single PDSCH transmission, one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

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

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

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

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

[0485] In the following description and examples, the aforementioned cases #1 (1700), #2 (1705), and #3 (1710), in which more than one DCI (PDCCH) is used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (1715), in which a single DCI (PDCCH) is used to support NC-JT, may be classified as single PDCCH-based NC-JT. In PDSCH transmission based on multiple PDCCH, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCI of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. As a method for distinguishing the CORESETs, there may be a method for distinguishing through an upper layer indicator for each CORESET, a method for distinguishing through beam setting for each CORESET, etc. Additionally, in single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH with multiple layers is scheduled, and the aforementioned multiple layers can be transmitted from multiple Transmission Relays (TRPs). In this case, the connection relationship between a layer and the TRP transmitting the layer can be indicated through a Transmission Configuration Indicator (TCI) indication for the layer.

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

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

[0488] The wireless protocol architecture for NC-JT in the present disclosure can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) similar to 1510 of FIG. 15 is possible. On the other hand, when the backhaul delay between cooperative TRPs is so large that it cannot be ignored (for example, when it takes more than 2 ms to exchange information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method (DC-like method) is possible to secure delay-robust characteristics by using an independent structure for each TRP starting from the RLC layer similar to 1520 of FIG. 15.

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

[0490] [Multi-DCI based Multi-TRP]

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

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

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

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

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

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

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

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

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

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

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

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

[0503] [PHR]

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

[0505] [Equation 7]

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

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

[0508] [PUSCH power control]

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

[0510] [Equation 8]

[0511]

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

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

[0514]

[0515] [PUCCH power control]

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

[0517] [Equation 9]

[0518]

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

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

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

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

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

[0524] [Begin pseudo-code 1]

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

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

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

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

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

[0530] [End of pseudo-code 1]

[0531] FIG. 19 is a diagram illustrating a process for generating a Type-1 (semi-static) HARQ-ACK codebook by a terminal according to an embodiment of the present disclosure. Taking FIG. 19 as an example to explain pseudo-code 1, in order to perform HARQ-ACK PUCCH transmission in slot#k(1908), all slot candidates that can indicate slot#k(1908) and have PDSCH-to-HARQ-ACK timing possible can be considered. In FIG. 19, only PDSCHs scheduled in slot#n(1902), slot#n+1(1904), and slot#n+2(1906) can enable HARQ-ACK transmission in slot#k(1908) by a possible PDSCH-to-HARQ-ACK timing combination. And, considering the time domain resource configuration information of the schedulable PDSCHs in slots 1902, 1904, and 1906 and the information indicating whether the symbol in the slot is a downlink or an uplink, the maximum number of schedulable PDSCHs for each slot is derived. For example, when 2 PDSCHs are schedulable in slot 1902, 3 PDSCHs are schedulable in slot 1904, and 2 PDSCHs are schedulable in slot 1906, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in slot 1908 is 7 in total. This is called the cardinality of the HARQ-ACK codebook.

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

[0533]

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

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

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

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

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

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

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

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

[0542]

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

[0544] [Begin pseudo-code 2]

[0545]

[0546]

[0547]

[0548] [pseudo-code 2 end]

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

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

[0551] The terminal transmits HARQ-ACK information to be transmitted within a PUCCH in slot n based on the PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release and K0, which is transmission slot location information of the PDSCH scheduled in DCI format 1_0 or 1_1. Specifically, for the above-described HARQ-ACK information transmission, the terminal determines the PDSCH-to-HARQ_feedback timing based on the DAI included in the DCI indicating the PDSCH or SPS PDSCH release and the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by K0.

[0552] DAI consists of Counter DAI and Total DAI. Counter DAI is information that indicates the location of HARQ-ACK information corresponding to the PDSCH scheduled in DCI format 1_0 or DCI format 1_1 within the HARQ-ACK codebook. Specifically, the value of counter DAI in DCI format 1_0 or 1_1 indicates the accumulated value of PDSCH reception or SPS PDSCH release scheduled by DCI format 1_0 or DCI format 1_1 in a specific cell c. The aforementioned accumulated value is set based on the PDCCH monitoring occasion and serving cell where the scheduled DCI exists.

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

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

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

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

[0557] [Structure of a Satellite Communication System]

[0558] The following description describes the characteristics of a satellite communications (or Non-Terrestrial Network, NTN) system. In the present disclosure, an NTN satellite may be a communication satellite that transmits a signal for a terminal to connect to a base station. In addition, in the present disclosure, a GNSS satellite may be a satellite that transmits a signal of a satellite navigation system. The terminal may receive a signal from each of one or more GNSS satellites and calculate its own location based on the received signal. In addition, the terminal may identify a reference time for each of one or more GNSS satellites. If the terminal can calculate its own location multiple times based on signals received from multiple GNSS satellites, the terminal may calculate its own actual location based on an average of the multiple locations, a location corresponding to a received signal with the strongest strength among the multiple locations, or an average of multiple locations based on signal strength (for example, a method of applying a weight to a location corresponding to a signal with a strong signal strength). Here, the method by which the terminal calculates its own location based on signals received from multiple GNSS satellites can be implemented in various forms, and a detailed description thereof will be omitted.

[0559] The terminal can calculate the time required for a signal to be transmitted from an NTN satellite to the terminal based on its own location and the location of the NTN satellite received from the NTN satellite, and can determine the TA value based on this. When determining the TA value, the terminal can also consider the distance from the NTN satellite to a ground base station, or the distance from one NTN satellite to another NTN satellite if the signal is transmitted to a ground base station via another NTN satellite.

[0560] In addition, the terminal can obtain reference time information from information transmitted by the GNSS satellite, compare the time information transmitted by the NTN satellite with the reference time information obtained from the GNSS satellite, and calculate the time required from the NTN satellite to the terminal (propagation delay) based on the comparison result.

[0561] The location and time information of NTN satellites can be transmitted from base stations to terminals via SIB. This may be transmitted directly by the NTN satellites.

[0562] The terminal of the present disclosure can operate while connected to a TN (Terrestrial Network) network or a satellite communication network (i.e., an NTN network). The terminal can determine whether the connected network is a terrestrial network or an NTN network based on upper level signal configuration information (e.g., SIB or RRC) or terminal location information (e.g., GPS (Global Positioning System) information).

[0563] 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 present invention is not limited to the above examples. According to one embodiment of the present disclosure, the Earth orbital period varies depending on each altitude. For GEO, the Earth orbital period is approximately 24 hours, for MEO, it is approximately 6 hours, and for LEO, it is approximately 90 to 120 minutes.

[0564] Low Earth orbit (~2,000 km) satellites orbit at a relatively low altitude, so they may have an advantage over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time it takes for a signal transmitted from a transmitter to reach a receiver) and loss.

[0565] FIG. 21 is a diagram illustrating the distance between a terminal and a satellite of a communication satellite according to the elevation angle between the satellite and the terminal according to one embodiment of the present disclosure. The distance between the terminal and the satellite may vary depending on the elevation angle between the satellite and the terminal. For example, when a terminal communicates with a satellite located at an altitude of 1200 km, 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 is approximately 3135 km. Therefore, in a satellite communication system, even if the terminal is fixed, the distance between the satellite and the terminal may vary due to the satellite's periodic orbit, such as a low-orbit satellite.

[0566] Additionally, since the distance between a terminal and a satellite in a satellite communication system is much longer 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 in the form of data with a low code rate or repeated transmission.

[0567] [Timing advance related]

[0568] Since terminals are typically located far from the base station, signals transmitted from the terminal are received by the base station after a propagation delay. Propagation delay is the distance a radio wave travels from the terminal to the base station divided by the speed of light, and is typically calculated as the distance from the terminal to the base station divided by the speed of light. For example, for a terminal located 100 km away from a base station, a signal transmitted by the terminal is received by the base station approximately 0.34 msec later. Conversely, a signal transmitted from the base station is also received by the terminal approximately 0.34 msec later.

[0569] Depending on the distance between the terminal and the base station, the time it takes for a signal transmitted from the terminal to arrive at the base station can vary. Therefore, if multiple terminals in different locations transmit signals simultaneously, the arrival times at the base station may vary. To ensure that signals from multiple terminals arrive at the base station simultaneously, each terminal can transmit its uplink signal at different times depending on its location. In 5G, NR, and LTE systems, this is called timing advance (TA).

[0570] FIG. 24 is a diagram illustrating a processing time of a terminal according to timing advance when the terminal receives a first signal and transmits a second signal corresponding thereto in a 5G or NR system according to an embodiment of the present disclosure.

[0571] When the base station transmits a first signal (uplink scheduling grant (UL grant) or downlink control signal and data (DL grant and DL data)) to the terminal in slot n (2402), the terminal can receive the first signal in slot n (2404). At this time, the terminal can receive the signal later by a transmission delay time (Tp, 2410) than the time at which the base station transmitted the signal.

[0572] According to one embodiment, when the terminal receives the first signal in slot n (2404), the terminal can transmit the corresponding second signal (HARQ-ACK / NACK for uplink data or downlink data) in slot n+4 (2406). Even when the terminal transmits the signal to the base station, in order to ensure that the signal arrives at the base station at a specific time, the terminal can transmit the second signal at a timing (2406) that is earlier than slot n+4 of the signal received by the terminal by a timing advance (TA, 2412). Therefore, in the present embodiment, the time that the terminal can receive uplink scheduling approval and transmit uplink data or receive downlink data and prepare to transmit HARQ ACK or NACK may be the time corresponding to three slots minus the TA (2414).

[0573] To determine the aforementioned timing, the base station can calculate the absolute value of the TA of the corresponding terminal. The base station can calculate the absolute value of the TA by adding or subtracting the amount of change in the TA value transmitted through upper signaling thereafter to the TA value initially transmitted to the terminal during the random access phase when the terminal initially connects. In the present disclosure, the absolute value of the TA can be a value obtained by subtracting the start time of the nth TTI received by the terminal from the start time of the nth TTI transmitted by the terminal.

[0574] Meanwhile, one of the key performance criteria of cellular wireless communication systems is packet data latency. To achieve this, LTE systems can transmit and receive signals in subframe units with a 1ms transmission time interval (TTI). LTE systems can support short-TTI UEs (terminals with transmission times shorter than 1ms). Meanwhile, in 5G or NR systems, transmission times can be shorter than 1ms. Short-TTI UEs are suitable for latency-critical services such as Voice over LTE (VoLTE) and remote control. Furthermore, short-TTI UEs can be a means of realizing the mission-critical Internet of Things (IoT) on a cellular basis.

[0575] In a 5G or NR system, when a base station transmits a PDSCH including downlink data, the DCI that schedules the PDSCH indicates a K1 value, which is a value corresponding to timing information for a terminal to transmit HARQ-ACK information of the PDSCH. The HARQ-ACK information may be transmitted from the terminal to the base station unless it is instructed to be transmitted before symbol L1, including a timing advance. That is, the HARQ-ACK information may be transmitted from the terminal to the base station at a time equal to or later than symbol L1, including a timing advance. If the HARQ-ACK information is instructed to be transmitted before symbol L1, including a timing advance, the HARQ-ACK information may not be valid HARQ-ACK information in HARQ-ACK transmission from the terminal to the base station.

[0576] [Half-duplex FDD related]

[0577] Below, we describe how Half-duplex (HD) terminals operate in FDD. Half-duplex (HD) terminals are capable of performing only one of two modes: transmitting or receiving at a given time. TDD is typically considered a half-duplex terminal, but unlike TDD, FDD has separate uplink and downlink frequency resources, allowing simultaneous transmission and reception. However, due to limitations of half-duplex terminals, HD operation can occur even in FDD. Compared to Full-duplex (FD), HD does not require devices such as duplexers, making it more usable by low-end terminals. For example, smart watches and wearable devices are smaller than smartphones, requiring a more streamlined design for their communication equipment. Therefore, base stations need to consider HD and communicate in FDD to communicate with terminals.

[0578] In FDD, a half-duplex terminal cannot fundamentally transmit and receive simultaneously in the serving cell. This can be applied to communication of a half-duplex terminal on a serving cell with FDD. A half-duplex terminal detects a DCI format that schedules reception in a specific symbol set and does not expect to detect a DCI format that schedules transmission in any symbol within the symbol set. In other words, the base station transmits a DCI format that schedules reception by the terminal in a specific symbol set and does not transmit a DCI format that schedules transmission by the terminal in any symbol within the symbol set.

[0579] When PDCCH reception by two PDCCH candidates by a terminal is included from a corresponding search space set, the termination of PDCCH reception is the termination of the PDCCH candidate that ends later. When a half-duplex terminal is configured by a higher layer to receive a PDCCH or a PDSCH or a CSI-RS or a DL PRS in a specific symbol set, the half-duplex terminal receives the PDCCH or PDSCH or a CSI-RS or a DL PRS unless it detects a DCI format instructing to transmit a PUSCH or a PUCCH or a PRACH or an SRS in any symbol of at least one symbol set. Otherwise, the half-duplex terminal does not receive the PDCCH or the PDSCH or the CSI-RS or the DL PRS in the symbol set.

[0580] When a half-duplex terminal is configured by a higher layer to transmit SRS or PUCCH or PUSCH in a specific symbol set and detects a DCI format that instructs the terminal to receive CSI-RS or PDSCH in a subset of the symbol set, the following applies.

[0581] - A half-duplex terminal does not cancel a PUCCH or PUSCH transmission within a symbol set if the last symbol of a PDCCH reception occurs within Tproc,2 of the last symbol of a PDCCH reception by a half-duplex terminal that detects the DCI format. Otherwise, the half-duplex terminal cancels a PUCCH or PUSCH transmission provided in an upper layer signal or L1 signal information, or an actual PUSCH repetition transmission.

[0582] FIG. 22 is a diagram showing a situation in which a half-duplex terminal receives uplink and downlink scheduling according to an embodiment of the present disclosure. As an example, FIG. 22 illustrates that after the terminal has previously set PUSCH transmission resource information through an upper layer signal, the terminal schedules a PDSCH on a PDCCH, and if the PDSCH overlaps with the PUSCH, the terminal does not receive the PDSCH and transmits the PUSCH because the time between the last symbol of the PDCCH and the first symbol of the PUSCH is within Tproc,2. If the half-duplex terminal is preparing for PUSCH transmission in a situation in which it does not know when and at what point it will receive the PDCCH scheduling the PDSCH, it needs time to cancel it. Therefore, if it is within Tproc,2, the half-duplex terminal has difficulty canceling the PUSCH it was preparing to transmit, so it may be possible to transmit the PUSCH and cancel PDSCH reception.

[0583] - A half-duplex terminal does not expect to cancel SRS transmissions from symbols in the subset occurring within Tproc,2 for the last symbol of PDCCH reception. The half-duplex terminal cancels SRS transmissions from symbols in the remaining subset.

[0584] FIG. 23 is a diagram illustrating a situation in which a half-duplex terminal receives uplink and downlink scheduling according to an embodiment of the present disclosure. As an example, FIG. 23 illustrates that after the terminal has previously set PUSCH transmission resource information through an upper layer signal, the terminal schedules a PDSCH on a PDCCH, and if the PDSCH overlaps with the PUSCH, the terminal receives the PDSCH and does not transmit the PUSCH because the time between the last symbol of the PDCCH and the first symbol of the PUSCH is greater than or equal to Tproc,2. If the half-duplex terminal is preparing for PUSCH transmission in a situation in which it does not know when and at what point it will receive the PDCCH scheduling the PDSCH, it needs time to cancel it. Therefore, if Tproc,2 is greater than, the half-duplex terminal can cancel the PUSCH it was preparing to transmit, and thus it may be possible to perform PDSCH reception without transmitting the PUSCH.

[0585] - Tproc,2 is the PUSCH preparation time, which is the preparation time required for the terminal to receive DCI and prepare to transmit PUSCH. In the above content, it may be possible to view it as the minimum requirement for canceling PUSCH transmission.

[0586] A half-duplex terminal receives upper-layer parameter settings for transmission in a specific symbol set, and does not receive all upper-layer parameters for reception in that symbol set. In other words, if at least one symbol overlaps between transmission-related upper-layer signal settings and reception-related upper-layer signal settings information, the terminal does not expect this, and the base station must take this into account and provide upper-layer signal settings information to the half-duplex terminal.

[0587] A half-duplex terminal receives a dedicated upper layer parameter configuration of a type-0 / 0A / 1 / 2-PDCCH CSS set for PDCCH reception in a specific symbol set, and does not expect to receive a setting indicating transmission as an upper signal within that symbol set, and the base station shall take this into account and provide the setting information to the half-duplex terminal.

[0588] If a half-duplex terminal transmits PUSCH or PUCCH or SRS based on configuration by upper layer and indicates the presence of SS / PBCH block in active DL BWP by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon or by non-cell defined SSB, the half-duplex terminal does not transmit:

[0589] - If the PUSCH or PUCCH transmission is less than NTx-RxTc[4, TS 38.211] before the first symbol of the SS / PBCH block where the last symbol of the PUSCH or PUCCH transmission is the earliest

[0590] - If the first symbol of a PUSCH or PUCCH transmission is less than NRx-TxTc[4, TS 38.211] after the last symbol of the previous latest SS / PBCH block, the PUSCH or PUCCH

[0591] - SRS in symbols less than NTx-RxTc before the first symbol of the fastest SS / PBCH block.

[0592] - SRS in symbols less than NRx-TxTc until the last symbol of the previous latest SS / PBCH block.

[0593] When a half-duplex terminal transmits PRACH or PUSCH or PUCCH or SRS according to a detected DCI format, or transmits MsgA PUSCH triggered by a higher layer, and an SS / PBCH block is set to a specific symbol set within an active DL BWP, the half-duplex terminal does not transmit PUSCH or PUCCH or PRACH if the transmission overlaps some symbols in the set. In addition, the half-duplex terminal does not transmit SRS in the overlapped symbols in the symbol set. That is, the half-duplex terminal can transmit SRS in non-overlapping symbols.

[0594] When a half-duplex terminal transmits a PRACH or MsgA PUSCH triggered by a higher layer and receives a PDCCH or PDSCH or CSI-RS or DL ​​PRS triggered by a higher layer, or receives a SS / PBCH block including any symbol from a symbol set, the half-duplex terminal may choose to transmit the PRACH or MsgA PUSCH or receive the PDSCH or CSI-RS or DL ​​PRS or PDCCH or SS / PBCH block depending on the implementation.

[0595] When a half-duplex terminal receives a PDCCH or a PDSCH or a CSI-RS or a DL PRS based on a configuration by a higher layer, or indicates the presence of a SS / PBCH block within an active DL BWP by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon or by a non-cell-defined SSB, the half-duplex terminal may choose to transmit a PRACH or a MsgA PUSCH or to receive a PDSCH or a CSI-RS or a DL PRS or a PDCCH or a SS / PBCH block, depending on the implementation, if the symbol at which the half-duplex terminal starts or ends transmitting a PRACH or a MsgA PUSCH is earlier or later than NRx-TxTc or NTx-RxTc from the last or first symbol of the symbol set.

[0596] A terminal that is not capable of full-duplex communication will not transmit on the uplink before a specific time interval following the end of the last downlink symbol received in the same cell. A terminal that is not capable of full-duplex communication will not receive on the downlink before a specific time interval following the end of the last uplink symbol transmitted in the same cell.

[0597] [Introduction to the Example]

[0598] Satellite communication systems typically operate on FDD, where downlink and uplink frequencies are separated. However, low-end terminals (e.g., half-duplex terminals) that cannot perform full-duplex communication may also need to perform satellite communications. For example, half-duplex terminals may be able to connect to the satellite network and transmit and receive data via wearable devices rather than smartphones. Below, we describe methods for supporting satellite communication technology for half-duplex terminals.

[0599] [Example 1]

[0600] The basic structure of a satellite communication system may include a terminal, a satellite, as illustrated in FIG. 21, and may also include a ground station (base station). TA may be introduced to reduce the complexity of the base station receiver. As illustrated in FIG. 24, in a typical terrestrial network, a base station individually transmits a signal for TA value correction (adjustment) to terminals, and the terminal can apply a TA value determined based on the signal for TA value correction. On the other hand, in a satellite communication network, the satellite covers a wide radius, and especially in the case of low-orbit satellites, the distance to the terminal (e.g., the distance between the satellite and the terminal in FIG. 21) changes over time due to the satellite orbiting the Earth, making it difficult to correct the TA value of the terminal in real time. Therefore, in a satellite communication system, the TA value that compensates for the delay time between the ground station and the satellite is provided to the terminal as SIB information, and the TA value that compensates for the delay time between the satellite and the terminal is considered to be calculated by the terminal itself.

[0601] Since the delay time between the ground station and the satellite provided with SIB information also varies over time, the delay time information according to time is provided to the terminal in the form of a quadratic or cubic function, and the terminal can receive this and determine the delay time between the ground station and the satellite at a specific point in time through the information. Specifically, the satellite-terminal delay time is provided to the terminal as an SIB in the form of a quadratic or cubic function with the satellite's location information as a variable with time. Through this, the terminal can estimate the distance using the terminal's location information calculated through the GNSS (Global Navigation Satellite System) and the satellite's location information at a specific point in time, and by dividing this by the speed of light, the phase-terminal propagation delay time can be derived.

[0602] In other words, in a satellite communication system, the TA value to be applied by the terminal can be determined based on at least one of a TA value that compensates for the delay time between the ground station and the satellite at a specific point in time or a TA value that compensates for the delay time between the satellite and the terminal at a specific point in time.

[0603] According to one embodiment, a terminal may determine a ground station-satellite delay time at a specific point in time based on a SIB, and determine a TA value that compensates for the ground station-satellite delay time. The terminal may receive the SIB, and the SIB may include information for determining the ground station-satellite delay time at a specific point in time. Since the ground station-satellite delay time varies over time, the information for determining the ground station-satellite delay time at a specific point in time may include information in the form of a quadratic or cubic function with respect to time. The terminal may receive the information included in the SIB, and determine the ground station-satellite delay time at a specific point in time based on the information included in the SIB. For example, the terminal may determine the ground station-satellite delay time at a specific point in time based on a quadratic or cubic time function. The terminal may determine a TA value that compensates for the ground station-satellite delay time based on the ground station-satellite delay time.

[0604] According to one embodiment, a terminal may determine a satellite-to-terminal delay time at a specific point in time and determine a TA value that compensates for the satellite-to-terminal delay time. The satellite-to-terminal delay time at a specific point in time may be determined based on the satellite-to-terminal distance at the specific point in time, and the satellite-to-terminal distance at the specific point in time may be determined based on the terminal's location information and the satellite's location information at the specific point in time.

[0605] Specifically, the location information of a satellite at a specific point in time can be determined based on the SIB received by the terminal. The SIB may include information for determining the location information of the satellite at a specific point in time. Since the location of a satellite changes over time, the SIB may include location information in the form of a quadratic or cubic function with time as a variable. The location information of the satellite at a specific point in time can be determined based on the information included in the SIB. For example, the terminal may obtain or determine the location information of the satellite at a specific point in time based on the location information in the form of a quadratic or cubic time function. Meanwhile, the location information of the terminal may be determined based on, for example, a Global Navigation Satellite System (GNSS). Here, the navigation satellite may be different from an NTN satellite. Of course, obtaining the location information of the terminal is not limited to the GNSS method, and the terminal may also receive its location from another entity.

[0606] The terminal can determine or calculate the satellite-to-terminal distance at a specific point in time based on the terminal's location information and the satellite's location information at a specific point in time, and divide this distance by the speed of light to determine or calculate the phase-to-terminal propagation delay time at a specific point in time. The terminal can determine the TA value that compensates for the satellite-to-terminal delay time based on the satellite-to-terminal delay time. In a satellite communication system, the TA value of the terminal can be corrected (adjusted) in this way. Therefore, in a satellite communication system, the base station may not transmit a signal to the terminal for correcting the TA value, and it is necessary to receive TA reporting to know the TA value applied by the terminal.

[0607] According to one embodiment, a base station may receive, from a terminal, TA reporting, which reports a TA value applied by the terminal. The TA reporting may be transmitted or received via a MAC CE.

[0608] According to one embodiment, a terminal may report the TA value applied to the base station in units of the length of one slot (1 ms) based on a 15 kHz subcarrier spacing. If the TA value actually applied by the terminal is not a natural number, the terminal may report the TA value by rounding it up. For example, if the TA actually applied by the terminal is 1.1 ms, the TA value reported to the base station may be 2 ms.

[0609] FIG. 27 is a diagram illustrating the structure of a TA reporting MAC CE that a terminal reports to a base station according to one embodiment. The timing advance reporting MAC CE can be identified by a MAC subheader using a Logical Channel ID (LCID). The size of the TA reporting MAC CE can be fixed, and the TA reporting MAC CE can be composed of two octets, as defined below.

[0610] - R: Set the reserved bit to 0.

[0611] - Timing Advance: In FR1, the Timing Advance field can indicate the minimum integer number of slots using a subcarrier spacing of 15 kHz that is greater than or equal to the Timing Advance value. The field length can be 14 bits.

[0612] In such situations, terminals supporting half-duplex communication cannot perform downlink reception and uplink transmission simultaneously, as explained above. Therefore, the base station must consider this and schedule accordingly. Failure to do so could result in unnecessary resource waste. This is illustrated in Figure 25.

[0613] FIG. 25 is a diagram illustrating a situation in which a half-duplex terminal is scheduled in a satellite communication system according to one embodiment of the present disclosure. Referring to FIG. 25, a first terminal (UE1) and a second terminal (UE2) each reported a TA value of 2 ms to the base station. The TA actually applied by the first terminal is 1.01 ms, and the TA actually applied by the second terminal is 2 ms.

[0614] The base station may provide DCI information for scheduling PUSCH (2506) at n+3 to the first terminal and the second terminal, respectively. Thereafter, the DL slot overlapping with UL slot n+3 may be, for example, n+1 (2502) (for the second terminal) or n+2 (2504) (for the first terminal), and the base station may not perform PDCCH scheduling in the overlapping DL slot. According to the FDD scheduling constraint for a half-duplex terminal (hereinafter referred to as “scheduling constraint A”) that “If a half-duplex terminal is configured by a higher layer to receive a PDCCH or a PDSCH or a CSI-RS or a DL PRS in a specific symbol set, the half-duplex terminal receives the PDCCH or the PDSCH or the CSI-RS or the DL PRS unless it detects a DCI format instructing to transmit a PUSCH or a PUCCH or a PRACH or an SRS in any symbol of at least one symbol set. Otherwise, the half-duplex terminal does not receive the PDCCH or the PDSCH or the CSI-RS or the DL PRS in the symbol set.”, if the PDCCH and the PUSCH overlap, the terminal may not receive the PDCCH. Therefore, from the base station's perspective, it may be common to know in advance that PUSCH is transmitted in UL slot n+3 and not transmit PDCCH in DL slot n+1 or n+2, which may potentially overlap with UL slot n+3.

[0615] Meanwhile, since the minimum unit of the TA value is 2 ms, it is difficult for the base station to distinguish whether the terminal is actually applying a TA closer to 1 ms than the TA value of 2 ms reported by the first terminal in FIG. 25, or is actually applying a TA closer to 2 ms, like the second terminal. Therefore, a method to resolve this may be necessary. Specifically, if the base station can know the exact value of the TA actually applied by the terminal from the terminal, the downlink resources can be managed more efficiently under the scheduling constraint A. Referring to FIG. 25, if the TA value reported by the terminal is 1.01 ms, the base station can transmit the PDCCH in DL slot n+1 because it can know in advance that the PDCCH resource transmitted in DL slot n+1 will not overlap with the PUSCH to be received in UL slot n+3. Therefore, the half-duplex terminal can apply at least one of the following methods or a combination thereof.

[0616] - Method 1-1: According to one embodiment, the minimum granularity interval for reporting TA values ​​may be set to be less than 1 ms. For example, the terminal may report the TA value to the base station in units of 0.1 ms or 0.01 ms. Alternatively, the minimum granularity interval for reporting TA values ​​may be determined as 1 slot per 30 kHz, 1 slot per 60 kHz, 1 slot per 120 kHz, 1 slot per 240 kHz, 1 slot per 480 kHz, or 1 slot per 960 kHz, rather than 1 slot per 15 kHz. Alternatively, the terminal may report in units of symbols based on a specific subcarrier interval, rather than in units of slots. In addition, the terminal may report a TA value that is equal to or closest to the actually calculated or actually applied TA value (ceiling or flooring). The terminal may report to the base station through a separate MAC CE format. In addition, the MAC CE format used for conventional TA reporting can be used in the same way, but the reported granularity can be changed. For example, if the base station instructs the terminal to report the granularity in 0.01 ms increments in advance through a higher-order signal, the terminal can report the TA value calculated (determined) considering (based on) the granularity of 0.01 ms to the base station. The terminal can report using a total of 14 bits. Alternatively, the terminal can report using 15 or 16 bits by utilizing a separate reserved bit indicated by R. In addition, the terminal can report using the MAC CE of the form described in FIG. 27. In this case, the MAC CE reported by the terminal has a fixed format regardless of the granularity, and can be determined based on the granularity that the terminal is instructed to report through the higher-order signal settings.If there is no separate granularity-related upper signal (i.e., a separate upper signal that indicates (sets) the granularity), the terminal can determine that 1 slot (i.e., 1 ms) at 15 kHz is the granularity to be applied for reporting the TA value.

[0617] - Method 1-2: Method 1-2 according to one embodiment is similar to Method 1-1 in some respects, but unlike Method 1-1, a MAC CE (first MAC CE) for reporting a TA value determined based on a granularity of 1 slot (1 ms) based on the conventional 15 kHz standard and a MAC CE (second MAC CE) for reporting a TA value determined based on a granularity smaller than 1 slot (1 ms) based on 15 kHz may be different. In addition, LCID values ​​indicating each MAC CE (or identifying each MAC CE) may also be different. Accordingly, the base station may determine whether the terminal reports the TA value using the first MAC CE or the second MAC CE depending on whether granularity-related configuration information is provided. Alternatively, the base station may directly provide the terminal with MAC CE configuration information to be reported by the terminal.

[0618] - Method 1-3: According to one embodiment, a terminal may report to a base station a MAC CE containing information on decimal points of the applied TA value in units of 1 ms or less, separately from the TA reporting in which a TA value determined based on (or based on) a granularity of 1 ms is reported through a MAC CE. For example, if a terminal calculates or determines a TA value to be reported as 2.4 ms, the terminal determines a TA value to be reported as 3 ms and reports this to the base station through the MAC CE described in FIG. 27, and may transmit an error of 0.6 ms in units of 1 ms or less through a separate MAC CE. The terminal may report up to the first decimal place, the second decimal place, or the third decimal place, for example. The base station may configure to which decimal places the terminal will report. Therefore, if the base station receives two different MAC CE information, and the values ​​of these two are 3ms and 0.6ms, the difference between them, 2.4ms, can be determined as the TA value actually applied by the terminal.

[0619] - Method 1-4: According to one embodiment, the terminal can directly determine the granularity information. For example, the base station can provide the terminal with candidate values ​​for the granularity to be applied in advance as an upper signal when reporting TA to the terminal. At this time, the terminal can inform the terminal of the granularity applied by using specific bitmap information. Referring to FIG. 27, this can be supported by using one or two R bit values. The values ​​that can be indicated as the granularity can include at least one of, or some combination of, one slot per 30 kHz, one slot per 60 kHz, one slot per 120 kHz, one slot per 240 kHz, one slot per 480 kHz, or one slot per 960 kHz, as the minimum granularity interval for reporting the TA value, rather than one slot per 15 kHz.

[0620] A half-duplex terminal may report TA values ​​with a more granularity, using at least one of the above methods or some combination thereof. The base station may configure the associated upper signal using at least one of the above methods, limited to terminals that have previously transmitted terminal capability information capable of supporting this.

[0621] [Example 2]

[0622] Even though the first embodiment allows the terminal to report more accurate TA values ​​to the base station, as previously explained, the TA values ​​actually applied by the terminal will vary over time due to changes in the satellite-to-terminal and satellite-to-ground station distances. Therefore, it may be difficult to apply the HD FDD scheduling constraints described above to satellite networks. For example, according to the FDD scheduling constraint for a half-duplex terminal described above (hereinafter referred to as "scheduling constraint B"), "If a half-duplex terminal receives upper layer parameter configuration information for transmission in a specific symbol set, it does not receive upper layer parameter configuration information for reception in the specific symbol set. In other words, the half-duplex terminal does not simultaneously receive upper layer parameter configuration information for transmission and upper layer parameter configuration information for reception in the specific symbol set. In other words, the terminal does not expect that at least one symbol overlaps due to transmission-related upper signal configuration information and reception-related upper signal configuration information, and the base station must take this into consideration when providing the upper signal configuration information to the half-duplex terminal. The half-duplex terminal does not expect to receive a Type-0 / 0A / 1 / 2-PDCCH CSS set configuration for PDCCH reception in a specific symbol set as a dedicated upper layer parameter, and to receive a configuration that instructs transmission as an upper signal within the corresponding symbol set, and the base station must take this into consideration when providing the configuration information to the half-duplex terminal.", the base station may instruct the terminal to transmit and receive in a specific symbol interval through upper signal configuration. The upper signal setting that allows simultaneous reception may not be provided. However, the transmission and reception periods set by the upper signal are typically periodic, and while the transmission and reception periods of the satellite and terminal may not overlap at certain points in time, they may overlap at other specific points in time.Therefore, from a base station perspective, it is difficult to consider all of these when setting the periodic transmission and reception intervals as upper-level signals. This is explained through Figure 26.

[0623] FIG. 26 is a diagram illustrating a situation in which downlink resources and uplink resources are periodically set in a satellite communication system according to one embodiment of the present disclosure. The base station may set PDCCH resources (2602) for DL ​​slots n+1, n+3, n+5, ..., i.e., every two slots, to a terminal (UE), and may also set PUSCH resources (2606) for UL slots n, n+3, ..., i.e., every three slots.

[0624] In Figure 26, "near" refers to a situation where the terminal is close to the satellite, and "far" refers to a situation where the terminal is farther away from the satellite. When the distance between the satellite and the ground station is fixed, propagation delay is typically smaller when the terminal is close to the satellite than when the terminal is far away, resulting in a smaller TA value. Therefore, Figure 26 can be understood as an illustration of how the actual TA value applied to a single terminal may vary over time as the satellite orbits the Earth.

[0625] In a situation where the satellite is close to the terminal (near), the PDCCH resources (2602) and the PUSCH resources (2606) do not overlap. However, in a situation where the satellite is far from the terminal (far), the PDCCH resources (2602) and the PUSCH resources (2606) may overlap. Fig. 26 is merely an example, and even in a situation where the satellite is close to the terminal (near), there may be cases where the PDCCH resources (2602) and the PUSCH resources (2606) overlap. Fig. 26 is merely an example illustrating that a situation where the uplink resources and the downlink resources may or may not overlap may occur depending on the distance between the satellite and the terminal.

[0626] According to scheduling constraint B, the base station should not provide configuration information of upper layer parameters to the terminal. However, in a satellite network, it may be difficult for the base station to comply with scheduling constraint B while considering the entire range of time-varying TA values. Therefore, rather than the base station avoiding configuring upper layer parameters, defining terminal operations when uplink and downlink resources overlap depending on the satellite-terminal distance may simplify base station operation. Therefore, scheduling constraint B does not apply to half-duplex terminals operating in a satellite network, and it may be possible to apply at least one of the following methods or some combination thereof.

[0627] - Method 2-1: If at least one symbol overlaps with the transmission-related upper signal setting information and the reception-related upper signal setting information, the terminal may perform downlink reception and not perform uplink transmission. For example, in FIG. 26, in a situation where the satellite is far from the terminal, if the PDCCH resource (2602) and the PUSCH resource (2606) overlap, the terminal may receive the PDCCH resource (2602) and transmit the PUSCH resource (2606).

[0628] - Method 2-2: If at least one symbol overlaps with the transmission-related upper signal setting information and the reception-related upper signal setting information, the terminal does not perform downlink reception but performs uplink transmission. For example, in FIG. 26, in a situation where the satellite is far from the terminal, if the PDCCH resource (2602) and the PUSCH resource (2606) overlap, the terminal can transmit the PUSCH resource (2606) without receiving the PDCCH resource (2602).

[0629] - Method 2-3: If at least one symbol overlaps due to the transmission-related upper signal setting information and the reception-related upper signal setting information, the terminal can perform transmission or reception according to the priorities as follows. For example, if priorities 1 and 2 occur (i.e., if their resources overlap), the terminal can perform priority 1 and not perform priority 2. For example, if priorities 2 and 3 occur (i.e., if their resources overlap), the terminal can perform priority 2 and not perform priority 3.

[0630] * Priority 1: Type-0 / 0A / 1 / 2 PDCCH settings

[0631] * Priority 2: Dedicated Uplink Settings

[0632] * Priority 3: Dedicated Downlink Settings

[0633] - Method 2-4: If at least one symbol overlaps according to the transmission-related upper signal setting information and the reception-related upper signal setting information, the terminal may be able to perform transmission or reception according to the priorities as follows. For example, if priorities 1 and 2 occur (i.e., if their resources overlap), the terminal may perform priority 1 and not perform priority 2. For example, if priorities 2 and 3 occur (i.e., if their resources overlap), the terminal may perform priority 2 and not perform priority 3.

[0634] * Priority 1: Dedicated Downlink configuration

[0635] * Priority 2: Dedicated Uplink Settings

[0636] * Priority 3: Type-0 / 0A / 1 / 2 PDCCH settings

[0637] - Method 2-5: One of the above methods can be set as the upper signal or L1 signal.

[0638] The above-described methods 2-1 to 2-4, if determined as one method, can always be applied when a half-duplex terminal operates in a satellite network without separate upper signal configuration information. Therefore, when a half-duplex terminal operates in a terrestrial network, it may be possible to apply scheduling constraint B, and in a satellite network, it may be possible to apply at least one of the above-described methods 2-1 to 2-5. In addition, the above-described scheduling constraint B may be replaced with 'the half-duplex terminal does not simultaneously receive DCI information for transmission and DCI information for reception in a specific symbol set', and in this situation, it may be possible to apply at least one of the methods 2-1 to 2-5. In this case, 'transmission-related upper signal configuration' may be replaced with 'transmission-related DCI information', and 'reception-related upper signal configuration' may be replaced with 'reception-related DCI information'. The physical channel (or signal) provided by the transmission-related upper signal configuration may include PUSCH, PUCCH, SRS, PRACH, etc. The physical channels (or signals) provided by transmission-related DCI may include PUSCH, PUCCH, SRS, PRACH, etc. The physical channels (or signals) provided by reception-related upper signal settings may include PDCCH, PDSCH, SS / PBCH, CSI-RS, PRS, etc. The physical channels (or signals) provided by reception-related DCI information may include PDSCH, CSI-RS, PRS, etc.

[0639] Although the first and second embodiments described above have been described for a half-duplex terminal operating in FDD, they can also be sufficiently applied to a terminal operating in TDD.

[0640] Hereinafter, in the third embodiment, when an uplink channel set by a first upper signal and a downlink channel set by a second upper signal overlap at least one symbol for a half-duplex terminal in an FDD situation, the operation of the terminal is described. The uplink channel set by the first upper signal refers to a channel that the terminal periodically transmits from a time resource perspective, and related types thereof may include, for example, a Configured grant PUSCH, a Periodic SRS, and a PUCCH including HARQ-ACK information for DL ​​SPS. The downlink channel set by the second upper signal refers to a channel that the terminal periodically receives from a time resource perspective, and related types thereof may include, for example, a PDCCH, a DL SPS, a Semi-persistent CSI-RS, and a periodic CSI-RS. If the uplink channel set by the first upper signal and the downlink channel set by the second upper signal overlap at least one symbol for a half-duplex terminal in an FDD situation, the terminal may transmit the uplink channel set by the first upper signal or receive the downlink channel set by the second upper signal. That is, if the uplink channel set by the first upper signal and the downlink channel set by the second upper signal overlap at least one symbol for a half-duplex terminal in an FDD situation, the terminal may not transmit the uplink channel set by the first upper signal or may not receive the downlink channel set by the second upper signal. Such operation of the terminal may be determined by the terminal implementation, or the terminal may operate according to specific rules set or determined by a separate upper signal.For example, if an overlap occurs between a PDCCH set as a higher-order signal and a Configured grant PUSCH, if the PDCCH is set to be given priority, the terminal may receive the PDCCH set by the second higher-order signal and not transmit the Configured grant PUSCH set by the first higher-order signal. As another example, if an overlap occurs between a Semi-persistent CSI-RS set as a higher-order signal and a Configured grant PUSCH, if the Configured grant PUSCH is set to be given priority, the terminal may transmit the Configured grant PUSCH set by the first higher-order signal and not receive the Semi-persistent CSI-RS set by the second higher-order signal. In another example, when a PUCCH and a PDCCH including HARQ-ACK information for DL ​​SPS set by a higher-order signal overlap, if the PDCCH is set to have priority, the UE may receive the PDCCH set by the second higher-order signal and not transmit the PUCCH including HARQ-ACK information for DL ​​SPS set by the first higher-order signal. According to one embodiment, priority-related configuration information may be provided to the UE through a higher-order signal as shown in [Table 45] below, and the UE may transmit or receive a channel with a higher priority according to the ascending or descending order of the configured priority values. [Table 45] is only an example, and in addition to the priority index or physical channel described in [Table 45], other downlink channels or uplink channels may be set to different priorities. Alternatively, although [Table 45] describes that it is set by a separate higher-order signal, it may also be possible for the priority order to be fixed without a separate higher-order signal.

[0641] Priority Index Physical Channel 0 PUCCH 1 PDCCH 2 with HARQ-ACK information for DL ​​SPS Configured grant PUSCH 3 DL SPS 4 Semi-persistent CSI-RS 5 Periodic SRS

[0642] Alternatively, if the uplink channel set by the first upper signal and the downlink channel set by the second upper signal overlap at least one symbol for a half-duplex terminal in an FDD situation, the terminal may give priority to reception of a PDCCH set to at least CSS (Common Search Space), and in other cases, the terminal may give priority to transmission of the uplink channel set by the first upper signal or reception of the downlink channel set by the second upper signal depending on terminal selection. The PDCCH set to CSS (Common Search Space) may mean a PDCCH for searching for DCI including a CRC scrambled with SI-RNTI (or MCCH (MBS (multicast / broadcast service) control channel)-RNTI or G (group)-RNTI or RA-RNTI or TC-RNTI or C-RNTI or CS-RNTI or P-RNTI or PEI (paging early indication)-RNTI or CellDTRX-RNTI, etc.). SI-RNTI is an RNTI for system information broadcasting, MCCH-RNTI is an RNTI for notifying multicast-related control information or changes in multicast / broadcast-related information, G-RNTI is an RNTI for groupcast transmission, RA-RNTI is an RNTI for random access response, TC-RNTI is an RNTI for contention resolution when there is no valid C-RNTI, C-RNTI is an RNTI for dynamically scheduled unicast transmission, CS-RNTI is an RNTI for configured scheduled unicast transmission, P-RNTI is an RNTI for paging transmission, PEI-RNTI is an RNTI for indicating existing paging information a little faster, and CellDTRX-RNTI is an RNTI for indicating network energy saving.

[0643] Alternatively, if an uplink channel established by a first upper signal and a downlink channel established by a second upper signal overlap at least one symbol for a half-duplex terminal in an FDD situation, the channel including control information may have priority over a channel including data information, and the channel including data information may have priority over a reference signal. The channel including the control information may include a PDCCH or a PUCCH. The channel including the data information may include a PDSCH or a PUSCH. The reference signal may include a CSI-RS or a DL PRS or an SRS. If both the downlink channel and the uplink channel are channels including control information (or data information) or are reference signals, the terminal may select one of them to receive the downlink channel or transmit the uplink channel. The above-described priority relationship is an example, and the order may be changed and applied. For example, a channel including data information may have priority over a channel including control information. Some of the above-described priority relationships may be omitted.

[0644] Hereinafter, in the fourth embodiment, when a downlink channel scheduled by a first DCI format and an uplink channel scheduled by a second DCI format overlap at least one symbol for a half-duplex terminal in an FDD situation, the operation of the terminal will be described. The downlink channel scheduled by the first DCI format is a downlink channel dynamically scheduled through DCI in a PDCCH, and may include, for example, a PDSCH, a CSI-RS, etc. The uplink channel scheduled by the second DCI format is an uplink channel dynamically scheduled through DCI in a PDCCH, and may include, for example, a PUSCH, a PUCCH, a PRACH, an SRS, etc. If a downlink channel scheduled by the first DCI format and an uplink channel scheduled by the second DCI format overlap at least one symbol for a half-duplex terminal in an FDD situation, the terminal may be able to operate by at least one of the following methods or some combination thereof. Alternatively, it may be possible for one of the following methods to be determined by a higher-order signal:

[0645] * Method 4-1: The terminal can always receive the downlink channel scheduled by the first DCI format with priority. That is, the terminal may not transmit the uplink channel scheduled by the second DCI format.

[0646] * Method 4-2: The terminal may always transmit the uplink channel scheduled by the second DCI format with priority. That is, the terminal may not receive the downlink channel scheduled by the first DCI format.

[0647] * Method 4-3: If the uplink channel scheduled by the second DCI format is a PRACH, the terminal gives priority to (i.e., performs) transmission of the corresponding PRACH. That is, the terminal does not receive the downlink channel scheduled by the first DCI format that overlaps with the PRACH. For other overlapping situations, the terminal may give priority to reception of the downlink channel scheduled by the first DCI format or to transmission of the uplink channel scheduled by the second DCI format. Generally, since PRACH transmission is used for scheduling by the base station to synchronize uplink, the terminal may give priority to PRACH transmission.

[0648] * Method 4-4: The terminal may prioritize reception of a downlink channel scheduled by the first DCI format or transmission of an uplink channel scheduled by the second DCI format. Generally, PRACH transmission is used by the base station for scheduling to synchronize uplink, so the terminal may prioritize PRACH transmission.

[0649] In the above methods 4-3 and 4-4, whether the terminal gives priority to the reception of the downlink channel scheduled by the first DCI format or the transmission of the uplink channel scheduled by the second DCI format may be determined by the terminal implementation or may be determined by specific conditions. An example of the specific conditions is that the priority is set by a higher-order signal. For example, if the PDSCH and the PUSCH overlap by a higher-order signal and the PDSCH is set to be given priority, the terminal may give priority to the reception of the PDSCH scheduled by the first DCI format. That is, the terminal may not transmit the PUSCH scheduled by the second DCI format. Similar to the embodiment described above in [Table 45], in the fourth embodiment, the priority between each uplink channel and downlink channel may be determined by a higher-order signal, and it may also be possible to determine the priority between specific channels without a separate higher-order signal.

[0650] Alternatively, if a downlink channel scheduled by the first DCI format and an uplink channel scheduled by the second DCI format overlap at least one symbol for a half-duplex terminal in an FDD situation, the PRACH may have priority over other channels, a channel including control information may have priority over a channel including data information, and a channel including data information may have priority over a reference signal. The channel including the control information may include a PUCCH. The channel including the data information may include a PDSCH or a PUSCH. The reference signal may include a CSI-RS or a DL PRS or an SRS. If both the downlink channel and the uplink channel are channels including control information (or data information) or are reference signals, the terminal may select one of them to receive the downlink channel or transmit the uplink channel. The above-described priority relationship is an example, and the order of the two may be changed and applied. For example, a channel including data information may have priority over a channel including control information. Some of the priority relationships described above may be omitted.

[0651] According to one embodiment, the third and fourth embodiments may be applied only to a satellite communication network. That is, the third and fourth embodiments may be applied only to a situation where a terminal receives a satellite network-only SIB or operates on a satellite network-only frequency. In addition, in the third and fourth embodiments, giving priority to a specific channel means that if the channel is a downlink channel, the terminal performs reception and the base station performs transmission, and if the channel is an uplink, the terminal performs transmission and the base station performs reception. In the third and fourth embodiments, giving priority to a specific channel may mean that if another channel overlapping with the specific channel is a downlink, the terminal does not perform reception (or the base station does not perform transmission), and if another channel overlapping with the specific channel is an uplink, the terminal does not perform transmission (or the base station does not perform reception).

[0652] Figure 28 is a flowchart illustrating a procedure for a half-duplex terminal to operate in a satellite network according to one embodiment of the present disclosure. After connecting to the satellite network, the half-duplex terminal transmits information regarding whether the terminal supports the first embodiment or the second embodiment through a terminal capability report. Thereafter, the base station may configure the upper signal described in the first embodiment (upper setting related to TA reporting) or provide the upper signal described in the second embodiment (upper setting related to overlapping uplink and downlink channels) to the terminal. The terminal may report a TA value based on the upper setting information received from the base station, or, if the uplink and downlink channels overlap, transmit an uplink channel or receive a downlink channel.

[0653] Alternatively, after the half-duplex terminal connects to the satellite network, it transmits information on whether the terminal supports the third embodiment or the fourth embodiment through a terminal capability report. Thereafter, the base station can configure the upper signal described in the third embodiment or provide the upper signal described in the fourth embodiment to the terminal. Then, based on the upper configuration information received from the base station, if the uplink channel and the downlink channel overlap by at least one symbol in terms of time resources, the terminal may be able to transmit the uplink channel or receive the downlink channel based on the methods described in the third or fourth embodiment. The base station may receive the uplink channel or transmit the downlink channel according to the third or fourth embodiment.

[0654] FIG. 29 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

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

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

[0660] FIG. 30 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. In a method performed by a terminal in a satellite communication system, the method comprises: A step of receiving information from a base station for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) method of the terminal, The information indicates one of a first method in which the uplink signal transmission is given priority over the downlink signal reception in the event of the collision and a second method in which the downlink signal transmission is given priority over the uplink signal transmission in the event of the collision; Based on one of the first method and the second method, including a step of performing the uplink signal transmission and the downlink signal reception with the base station, A method wherein the above uplink signal transmission and the above downlink signal reception are based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on upper layer signaling.

2. In paragraph 1, A method in which, when the first method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the downlink signal reception is dropped.

3. In paragraph 2, A method in which, when the second method is indicated, the uplink signal transmission and the downlink signal reception collide, the uplink signal transmission is dropped.

4. In paragraph 1, A step of receiving a system information block (SIB) from the base station; and A step of transmitting a TA report including a timing advance (TA) value determined based on a propagation delay time between the terminal and the base station at a specific point in time based on the SIB to the base station, A method in which the granularity of the above TA value is configured based on values less than 1 ms (mili second).

5. In a method performed by a base station in a satellite communication system, the method comprises: A step of receiving information from a terminal for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to a half duplex-frequency division duplexing (HD-FDD) method of the terminal, The information indicates one of a first method in which the uplink signal transmission is given priority over the downlink signal reception in the event of the collision and a second method in which the downlink signal transmission is given priority over the uplink signal transmission in the event of the collision; Based on one of the first method and the second method, the terminal includes a step of performing transmission for receiving the uplink signal transmission of the terminal and receiving the downlink signal of the terminal, A method wherein the uplink signal transmission of the terminal and the downlink signal reception of the terminal are based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on upper layer signaling.

6. In paragraph 5, A method in which, when the first method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the downlink signal reception is dropped.

7. In paragraph 6, A method in which, when the second method is indicated, the uplink signal transmission and the downlink signal reception collide, the uplink signal transmission is dropped.

8. In paragraph 5, A step of transmitting a system information block (SIB) to the terminal; and A step of receiving a TA report including a timing advance (TA) value determined based on a propagation delay time between the terminal and the base station at a specific point in time based on the SIB from the terminal, A method in which the granularity of the above TA value is configured based on values less than 1 ms (mili second).

9. In a satellite communication system, the terminal, transceiver; and Including a controller connected to the above transceiver, The above controller, Receive information from a base station for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to the half duplex-frequency division duplexing (HD-FDD) method of the terminal, The information indicates one of a first method in which the uplink signal transmission is given priority over the downlink signal reception in the event of the collision and a second method in which the downlink signal transmission is given priority over the uplink signal transmission in the event of the collision, Based on one of the first method and the second method, the base station is configured to perform the uplink signal transmission and the downlink signal reception, A terminal in which the above uplink signal transmission and the above downlink signal reception are based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on upper layer signaling.

10. In paragraph 9, A terminal in which, when the first method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the downlink signal reception is dropped.

11. In paragraph 10, A terminal in which, when the second method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the uplink signal transmission is dropped.

12. In paragraph 9, A step of receiving a system information block (SIB) from the base station; and A step of transmitting a TA report including a timing advance (TA) value determined based on a propagation delay time between the terminal and the base station at a specific point in time based on the SIB to the base station, The granularity of the above TA value is configured based on values less than 1ms (mili second).

13. In a satellite communication system, the base station, transceiver; and Including a controller connected to the above transceiver, The above controller, Receive information from a terminal for setting an operation method in case of collision between uplink signal transmission and downlink signal reception according to the half duplex-frequency division duplexing (HD-FDD) method of the terminal, The information indicates one of a first method in which the uplink signal transmission is given priority over the downlink signal reception in the event of the collision and a second method in which the downlink signal transmission is given priority over the uplink signal transmission in the event of the collision, Based on one of the first method and the second method, the terminal is configured to perform transmission for receiving the uplink signal transmission of the terminal and receiving the downlink signal of the terminal, A base station, wherein the uplink signal transmission of the terminal and the downlink signal reception of the terminal are based on dynamic scheduling based on downlink control information or semi-persistent scheduling based on upper layer signaling.

14. In paragraph 13, A base station in which, when the first method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the downlink signal reception is dropped.

15. In paragraph 14, A base station in which, when the second method is indicated, there is a collision between the uplink signal transmission and the downlink signal reception, the uplink signal transmission is dropped.

Images