Method and apparatus for transmitting or receiving synchronization signal in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate, and discloses a method and apparatus characterized in that a resource for a narrowband primary synchronization signal (NPSS) and a resource for a narrowband secondary synchronization signal (NSSS) are identified, the NPSS is received on the basis of the resource for the NPSS, and the NSSS is received on the basis of the resource for the NSSS, wherein a time resource of the NPSS includes 14 symbols and a time resource of the NSSS includes 14 symbols.

Description

Method and device for transmitting and receiving synchronous signals 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 a synchronization signal in a satellite communication system and an apparatus capable of performing the same.

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

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

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

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

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

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

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

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

[0010] The technical problems to be solved in the various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned may be considered by those skilled in the art from the various embodiments of the present disclosure described below.

[0011] A method for processing a control signal in a wireless communication system according to one embodiment of the present disclosure for solving the above-mentioned problems comprises: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0012] The various embodiments of the present disclosure described above are merely some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by those skilled in the art based on the detailed description to be described below.

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

[0014] The effects obtainable from the various embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art based on the following detailed description.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0036] FIG. 22 is a diagram showing a situation in which beam groups are activated at specific times in a satellite communication system according to one embodiment of the present disclosure.

[0037] FIG. 23 is a diagram showing the TDD structure of a satellite communication supporting NB-IoT according to one embodiment of the present disclosure.

[0038] FIG. 24 is a diagram showing resources allocated to NPSS, NSSS, and NPBCH according to one embodiment of the present disclosure.

[0039] FIG. 25 is a diagram showing resources in which a synchronization signal and NBPCH are transmitted and received according to one embodiment of the present disclosure.

[0040] FIG. 26 is a diagram showing resources allocated to NPSS, NSSS, and NPBCH according to one embodiment of the present disclosure.

[0041] FIG. 27 is a flowchart showing a method for determining the transmission period of a terminal according to a frequency band according to one embodiment of the present disclosure.

[0042] FIG. 28 is a drawing showing resources allocated to NPSS according to one embodiment of the present disclosure.

[0043] FIG. 29 is a diagram showing the resource structure of an improved NPSS according to one embodiment of the present disclosure.

[0044] FIG. 30 is a flowchart showing a method for determining NPSS transmission resources of a terminal according to a frequency band according to one embodiment of the present disclosure.

[0045] FIG. 31 is a drawing showing resources allocated to an NSSS according to one embodiment of the present disclosure.

[0046] FIG. 32 is a diagram showing the resource structure of an improved NSSS according to one embodiment of the present disclosure.

[0047] FIG. 33 is a flowchart showing a method for determining NPSS transmission resources of a terminal according to a frequency band according to one embodiment of the present disclosure.

[0048] FIG. 34 is a diagram showing a situation in which NPBCH resources are mapped according to one embodiment of the present disclosure.

[0049] FIG. 35 is a diagram showing a situation in which the payloads of NPBCH according to one embodiment of the present disclosure are each divided and repeatedly transmitted.

[0050] FIG. 36 is a diagram showing an improved NPBCH transmission resource according to one embodiment of the present disclosure.

[0051] FIG. 37 is a diagram showing an improved NPBCH transmission resource according to one embodiment of the present disclosure.

[0052] FIG. 38 is a diagram showing an improved NPBCH transmission resource according to one embodiment of the present disclosure.

[0053] FIG. 39 is a diagram showing an improved NPBCH transmission resource according to one embodiment of the present disclosure.

[0054] FIG. 40 is a diagram showing a situation in which the payloads of NPBCH are each divided and repeatedly transmitted according to one embodiment of the present disclosure.

[0055] FIG. 41 is a flowchart showing a method for determining NPBCH transmission resources of a terminal according to a frequency band according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] [NR Time-Frequency Resources]

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

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

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

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

[0078] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus 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). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by Table 1 below.

[0079] [Table 1]

[0080]

[0081] [Bandwidth Section (BWP)]

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

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

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

[0085] [Table 2]

[0086]

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

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

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

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

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

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

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

[0094] [Bandwidth Section (BWP) Change]

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

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

[0097] [Table 3]

[0098]

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

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

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

[0102] [SS / PBCH Block]

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

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

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

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

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

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

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

[0110] [PDCCH: DCI related]

[0111] Next, Downlink Control Information (DCI) in 5G systems will be explained in detail.

[0112] 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 the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

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

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

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

[0116] [Table 4]

[0117]

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

[0119] [Table 5]

[0120]

[0121]

[0122]

[0123]

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

[0125] [Table 6]

[0126]

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

[0128] [Table 7]

[0129]

[0130]

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

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

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

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

[0135] [Table 8]

[0136]

[0137] 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 area.

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

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

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

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

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

[0143] [Table 9]

[0144]

[0145]

[0146]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0170] [Table 10]

[0171]

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

[0173]

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

[0175] [PDCCH: span]

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

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

[0178] [PDCCH: Terminal Capability Report]

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

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

[0181] [Table 11]

[0182]

[0183]

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

[0185] [Table 12]

[0186]

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

[0188] [Table 13]

[0189]

[0190]

[0191]

[0192]

[0193]

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

[0195] [QCL, TCI state]

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

[0197] [Table 14]

[0198]

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

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

[0201] [Table 15]

[0202]

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

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

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

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

[0207]

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

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

[0210]

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

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

[0213]

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

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

[0216]

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

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

[0219]

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

[0221] [PDCCH: TCI state related]

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

[0223] [Table 21]

[0224]

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

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

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

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

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

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

[0231] [PDCCH: QCL prioritization rule related]

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

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

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

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

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

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

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

[0239] [Regarding Rate Matching / Puncturing]

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

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

[0242] Rate Matching Operation

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

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

[0245] Puncturing action

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

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

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

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

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

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

[0252] In 5G, the granularity of "RB symbol level" and "RE level" is supported by setting the aforementioned rate matching resources to the terminal. More specifically, the following setting method may be followed.

[0253] RB symbol level

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

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

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

[0257] RE level

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

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

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

[0261] [Regarding LTE CRS rate match]

[0262] Next, the rate match process for the LTE CRS described above will be explained in detail. For the coexistence of LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), 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 may be provided by RRC signaling that includes at least one parameter within the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the above parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

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

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

[0265] ServingCellConfig ::= SEQUENCE {tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDDinitialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need MdownlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need NdownlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need NfirstActiveDownlinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAddbwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500,ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8,spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need RdefaultDownlinkBWP-Id BWP-Id OPTIONAL, -- Need SuplinkConfig UplinkConfig OPTIONAL, -- Need MsupplementaryUplink UplinkConfig OPTIONAL, -- Need Mpdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig} OPTIONAL, -- Need Mpdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig} OPTIONAL,-- Need Mcsi-MeasConfig SetupRelease { CSI-MeasConfig} OPTIONAL, -- Need MsCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240,ms320, ms400, ms480, ms520, ms640, ms720,ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCHcrossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, -- Need Mtag-Id TAG-Id,dummy ENUMERATED {enabled} OPTIONAL, -- Need RpathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnlyservingCellMO MeasObjectId OPTIONAL, -- Cond MeasObject...,[[lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS} OPTIONAL, -- Need MrateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need NdownlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S]],[[supplementaryUplinkRelease ENUMERATED {true} OPTIONAL, -- Need Ntdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IABdormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16} OPTIONAL, -- Need Mca-SlotOffset-r16 CHOICE {refSCS15kHz INTEGER (-2..2),refSCS30KHz INTEGER (-5..5),refSCS60KHz INTEGER (-10..10),refSCS120KHz INTEGER (-20..20)} OPTIONAL, -- Cond AsyncCAchannelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16} OPTIONAL, -- Need MintraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need SintraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need Scsi-RS-ValidationWith-DCI-r16 ENUMERATED {enabled} OPTIONAL, -- Need Rlte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16} OPTIONAL, -- Need Mlte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16} OPTIONAL,-- Need Mcrs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, -- Need Rcbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need Rcbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL -- Need R]]},

[0266] -RateMatchPatternLTE-CRSThe IERateMatchPatternLTE-CRSis used to configure a pattern to rate match around LTE CRS. See TS 38.214

[0019] , clause 5.1.4.2.RateMatchPatternLTE-CRS information element-- ASN1START-- TAG-RATEMATCHPATTERNLTE-CRS-STARTRateMatchPatternLTE-CRS ::= SEQUENCE {carrierFreqDL INTEGER (0..16383),carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need MnrofCRS-Ports ENUMERATED {n1, n2, n4},v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}}LTE-CRS-PatternList-r16 ::= SEQUENCE (SIZE (1..maxLTE-CRS-Patterns-r16)) OF RateMatchPatternLTE-CRS-- TAG-RATEMATCHPATTERNLTE-CRS-STOP-- ASN1STOP

[0267] [PDSCH: 프로세싱 시간]

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

[0269] [Mathematical Formula 2]

[0270]

[0271] The aforementioned T in mathematical formula 2 proc,1 In this, each variable can have the following meanings.

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

[0273] [Table 24] PDSCH processing time when PDSCH processing capability is 1

[0274]

[0275] [Table 25] PDSCH processing time when PDSCH processing capability is 2

[0276]

[0277] - : 64

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

[0279] - If l1, which represents the PDSCH DMRS position value, is 12, then N1,0 of [Table x2-2] above has a value of 14, otherwise it has a value of 13.

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

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

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

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

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

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

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

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

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

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

[0290] - When L = 2,

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

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

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

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

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

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

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

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

[0299] [Table 25] N according to scheduled PDCCH subcarrier interval pdsch

[0300]

[0301] [Regarding SRS]

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

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

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

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

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

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

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

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

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

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

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

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

[0314] SRS-Resource ::= SEQUENCE {srs-ResourceId SRS-ResourceId,nrofSRS-Ports ENUMERATED {port1, ports2, ports4},ptrs-PortIndex ENUMERATED {n0, n1} OPTIONAL, -- Need RtransmissionComb CHOICE {n2 SEQUENCE {combOffset-n2 INTEGER (0..1),cyclicShift-n2 INTEGER (0..7)},n4 SEQUENCE {combOffset-n4 INTEGER (0..3),cyclicShift-n4 INTEGER (0..11)}},resourceMapping SEQUENCE {startPosition INTEGER (0..5),nrofSymbols ENUMERATED {n1, n2, n4},repetitionFactor ENUMERATED {n1, n2, n4}},freqDomainPosition INTEGER (0..67),freqDomainShift INTEGER (0..268),freqHopping SEQUENCE {c-SRS INTEGER (0..63),b-SRS INTEGER (0..3),b-hop INTEGER (0..3)},groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping},resourceType CHOICE {aperiodic SEQUENCE {...},semi-persistent SEQUENCE {periodicityAndOffset-sp SRS-PeriodicityAndOffset,...},periodic SEQUENCE {periodicityAndOffset-p SRS-PeriodicityAndOffset,...}},sequenceId INTEGER (0..1023),spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R...}

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

[0316] SRS-SpatialRelationInfo ::= SEQUENCE {servingCellId ServCellIndex OPTIONAL, -- Need SreferenceSignal CHOICE {ssb-Index SSB-Index,csi-RS-Index NZP-CSI-RS-ResourceId,srs SEQUENCE {resourceId SRS-ResourceId,uplinkBWP BWP-Id}}}

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

[0318] [PUSCH: Regarding transmission method]

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

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

[0321] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

[0322] 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 and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config in [Table x2-4], the upper signaling, is 'codebook' or 'nonCodebook'.

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

[0324] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

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

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

[0327] 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 signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0328] A terminal may receive one SRS resource set in which the value of usage in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set may be indicated via SRI. If multiple SRS resources are set in the SRS resource set in which the value of usage 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 will be set to the same value for all SRS resources.

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

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

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

[0332] 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. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the corresponding DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

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

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

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

[0336] [PUSCH: Preparation Process Time]

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

[0338] [Mathematical Formula 3]

[0339]

[0340] The aforementioned T in mathematical formula 3 proc,2 In this, each variable can have the following meanings.

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

[0342] [Table 30]

[0343]

[0344] [Table 31]

[0345]

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

[0347] - : 64

[0348] - μ: or Middle, T proc,2 It follows the value that becomes larger. represents the numerology of the downlink through which a PDCCH containing a DCI that schedules the PUSCH is transmitted, and represents the numerology of the uplink through which PUSCH is transmitted.

[0349] - T c : has.

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

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

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

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

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

[0355] [PUSCH: Repetitive transmission related]

[0356] 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 receive either PUSCH repetitive transmission type A or B as a setting for upper layer signaling.

[0357] PUSCH Repeated Transmission Type A

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

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

[0360] PUSCH Repeated Transmission Type B

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

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

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

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

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

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

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

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

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

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

[0371] The repetitive transmission described above may be applicable 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 the DCI, while CG PUSCH refers to a method in which PUSCH scheduling information is provided only by the upper signal or by some DCI. Additionally, DG PUSCH is a method in which the terminal transmits PUSCH only within the scheduling area provided by the DCI, and CG PUSCH is a method in which the terminal periodically transmits PUSCH without receiving a separate DCI in accordance with the period set by the upper signal.

[0372] [PUSCH: Frequency Hopping Process]

[0373] The following describes frequency hopping of the Physical Uplink Shared Channel (PUSCH) in a 5G system in detail.

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

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

[0376] [Mathematical Formula 4]

[0377]

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

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

[0380] [Mathematical Formula 5]

[0381]

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

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

[0384] [Mathematical Formula 6]

[0385]

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

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

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

[0389] For the aforementioned CSI measurement and reporting, the terminal is N( Setting information for ) CSI reports (CSI-ReportConfig), M( Setting information for ) RS transmission resources (CSI-ResourceConfig) and one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) can be set through upper-level signaling. The setting information for the aforementioned CSI measurement and reporting may be more specifically as described in [Table 32] to [Table 38] as follows.

[0390] [Table 32] CSI-ReportConfig

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

[0019] , clause 5.2.1.

[0392] CSI-ReportConfig information element

[0393] -- ASN1START

[0394] -- TAG-CSI-REPORTCONFIG-START

[0395]

[0396] CSI-ReportConfig ::= SEQUENCE {

[0397] reportConfigId CSI-ReportConfigId,

[0398] carrier ServCellIndex OPTIONAL, -- Need S

[0399] resourcesForChannelMeasurement CSI-ResourceConfigId,

[0400] csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R

[0401] nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R

[0402] reportConfigType CHOICE {

[0403] periodic SEQUENCE {

[0404] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0405] pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0406] },

[0407] semiPersistentOnPUCCH SEQUENCE {

[0408] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0409] pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0410] },

[0411] semiPersistentOnPUSCH SEQUENCE {

[0412] reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},

[0413] reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),

[0414] p0alpha P0-PUSCH-AlphaSetId

[0415] },

[0416] aperiodic SEQUENCE {

[0417] reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)

[0418] }

[0419] },

[0420] reportQuantity CHOICE {

[0421] none NULL,

[0422] cri-RI-PMI-CQI NULL,

[0423] cri-RI-i1 NULL,

[0424] cri-RI-i1-CQI SEQUENCE {

[0425] pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S

[0426] },

[0427] cri-RI-CQI NULL,

[0428] cri-RSRP NULL,

[0429] ssb-Index-RSRP NULL,

[0430] cri-RI-LI-PMI-CQI NULL

[0431] },

[0432] reportFreqConfiguration SEQUENCE {

[0433] cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI} OPTIONAL, -- Need R

[0434] pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI} OPTIONAL, -- Need R

[0435] csi-ReportingBand CHOICE {

[0436] subbands3 BIT STRING(SIZE(3)),

[0437] subbands4 BIT STRING(SIZE(4)),

[0438] subbands5 BIT STRING(SIZE(5)),

[0439] subbands6 BIT STRING(SIZE(6)),

[0440] subbands7 BIT STRING(SIZE(7)),

[0441] subbands8 BIT STRING(SIZE(8)),

[0442] subbands9 BIT STRING(SIZE(9)),

[0443] subbands10 BIT STRING(SIZE(10)),

[0444] subbands11 BIT STRING(SIZE(11)),

[0445] subbands12 BIT STRING(SIZE(12)),

[0446] subbands13 BIT STRING(SIZE(13)),

[0447] subbands14 BIT STRING(SIZE(14)),

[0448] subbands15 BIT STRING(SIZE(15)),

[0449] subbands16 BIT STRING(SIZE(16)),

[0450] subbands17 BIT STRING(SIZE(17)),

[0451] subbands18 BIT STRING(SIZE(18)),

[0452] ...,

[0453] subbands19-v1530 BIT STRING(SIZE(19))

[0454] } OPTIONAL -- Need S

[0455]

[0456] } OPTIONAL, -- Need R

[0457] timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},

[0458] timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},

[0459] codebookConfig CodebookConfig OPTIONAL, -- Need R

[0460] dummy ENUMERATED {n1, n2} OPTIONAL, -- Need R

[0461] groupBasedBeamReporting CHOICE {

[0462] enabled NULL,

[0463] disabled SEQUENCE {

[0464] nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S

[0465] }

[0466] },

[0467] cqi-Table ENUMERATED {table1, table2, table3, spare1} OPTIONAL, -- Need R

[0468] subbandSize ENUMERATED {value1, value2},

[0469] non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R

[0470] ...,

[0471] [[

[0472] semiPersistentOnPUSCH-v1530 SEQUENCE {

[0473] reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}

[0474] } OPTIONAL -- Need R

[0475] ]],

[0476] [[

[0477] semiPersistentOnPUSCH-v1610 SEQUENCE {

[0478] reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R

[0479] reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R

[0480] } OPTIONAL, -- Need R

[0481] aperiodic-v1610 SEQUENCE {

[0482] reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R

[0483] reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R

[0484] } OPTIONAL, -- Need R

[0485] reportQuantity-r16 CHOICE {

[0486] cri-SINR-r16 NULL,

[0487] ssb-Index-SINR-r16 NULL

[0488] } OPTIONAL, -- Need R

[0489] codebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R

[0490] ]]

[0491] }

[0492] CSI-ReportPeriodicityAndOffset ::= CHOICE {

[0493] slots4 INTEGER(0..3),

[0494] slots5 INTEGER(0..4),

[0495] slots8 INTEGER(0..7),

[0496] slots10 INTEGER(0..9),

[0497] slots16 INTEGER(0..15),

[0498] slots20 INTEGER(0..19),

[0499] slots40 INTEGER(0..39),

[0500] slots80 INTEGER(0..79),

[0501] slots160 INTEGER(0..159),

[0502] slots320 INTEGER(0..319)

[0503] }

[0504] PUCCH-CSI-Resource ::= SEQUENCE {

[0505] uplinkBandwidthPartId BWP-Id,

[0506] pucch-Resource PUCCH-ResourceId

[0507] }

[0508] PortIndexFor8Ranks ::= CHOICE {

[0509] portIndex8 SEQUENCE{

[0510] rank1-8 PortIndex8 OPTIONAL, -- Need R

[0511] rank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, -- Need R

[0512] rank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, -- Need R

[0513] rank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, -- Need R

[0514] rank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, -- Need R

[0515] rank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, -- Need R

[0516] rank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, -- Need R

[0517] rank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL -- Need R

[0518] },

[0519] portIndex4 SEQUENCE{

[0520] rank1-4 PortIndex4 OPTIONAL, -- Need R

[0521] rank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, -- Need R

[0522] rank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, -- Need R

[0523] rank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL -- Need R

[0524] },

[0525] portIndex2 SEQUENCE{

[0526] rank1-2 PortIndex2 OPTIONAL, -- Need R

[0527] rank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL -- Need R

[0528] },

[0529] portIndex1 NULL

[0530] }

[0531] PortIndex8::= INTEGER (0..7)

[0532] PortIndex4::= INTEGER (0..3)

[0533] PortIndex2::= INTEGER (0..1)

[0534] -- TAG-CSI-REPORTCONFIG-STOP

[0535] -- ASN1STOP

[0536]

[0537]

[0538]

[0539]

[0540] [표 33]CSI-ResourceConfig

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

[0542] CSI-ResourceConfig information element

[0543] -- ASN1START

[0544] -- TAG-CSI-RESOURCECONFIG-START

[0545]

[0546] CSI-ResourceConfig ::= SEQUENCE {

[0547] csi-ResourceConfigId CSI-ResourceConfigId,

[0548] csi-RS-ResourceSetList CHOICE {

[0549] nzp-CSI-RS-SSB SEQUENCE {

[0550] nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId

[0551] OPTIONAL, -- Need R

[0552] csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R

[0553] },

[0554] csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId

[0555] },

[0556]

[0557] bwp-Id BWP-Id,

[0558] resourceType ENUMERATED { aperiodic, semiPersistent, periodic},

[0559] ...

[0560] }

[0561] -- TAG-CSI-RESOURCECONFIG-STOP

[0562] -- ASN1STOP

[0563]

[0564] [표 34]NZP-CSI-RS-ResourceSet

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

[0566] NZP-CSI-RS-ResourceSet information element

[0567] -- ASN1START

[0568] -- TAG-NZP-CSI-RS-RESOURCESET-START

[0569] NZP-CSI-RS-ResourceSet ::= SEQUENCE {

[0570] nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,

[0571] nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,

[0572] repetition ENUMERATED { on, off} OPTIONAL, -- Need S

[0573] aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S

[0574] trs-Info ENUMERATED {true} OPTIONAL, -- Need R

[0575] ...,

[0576] [[

[0577] aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S

[0578] ]]

[0579] }

[0580] -- TAG-NZP-CSI-RS-RESOURCESET-STOP

[0581] -- ASN1STOP

[0582]

[0583] [표 35]CSI-SSB-ResourceSet

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

[0585] CSI-SSB-ResourceSet information element

[0586] -- ASN1START

[0587] -- TAG-CSI-SSB-RESOURCESET-START

[0588]

[0589] CSI-SSB-ResourceSet ::= SEQUENCE {

[0590] csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,

[0591] csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index,

[0592] ...

[0593] }

[0594] -- TAG-CSI-SSB-RESOURCESET-STOP

[0595] -- ASN1STOP

[0596] [표 36]CSI-IM-ResourceSet

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

[0598] CSI-IM-ResourceSet information element

[0599] -- ASN1START

[0600] -- TAG-CSI-IM-RESOURCESET-START

[0601]

[0602] CSI-IM-ResourceSet ::= SEQUENCE {

[0603] csi-IM-ResourceSetId CSI-IM-ResourceSetId,

[0604] csi-IM-Resources SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId,

[0605] ...

[0606] }

[0607] -- TAG-CSI-IM-RESOURCESET-STOP

[0608] -- ASN1STOP

[0609]

[0610] [표 37]CSI-AperiodicTriggerStateList

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

[0612] CSI-AperiodicTriggerStateList information element

[0613] -- ASN1START

[0614] -- TAG-CSI-APERIODICTRIGGERSTATELIST-START

[0615]

[0616] CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState

[0617]

[0618] CSI-AperiodicTriggerState ::= SEQUENCE {

[0619] associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,

[0620] ...

[0621] }

[0622] CSI-AssociatedReportConfigInfo ::= SEQUENCE {

[0623] reportConfigId CSI-ReportConfigId,

[0624] resourcesForChannel CHOICE {

[0625] nzp-CSI-RS SEQUENCE {

[0626] resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

[0627] qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic

[0628] },

[0629] csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)

[0630] },

[0631] csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference

[0632] nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference

[0633] ...

[0634] }

[0635] -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP

[0636] -- ASN1STOP

[0637]

[0638]

[0639] [표 38]CSI-SemiPersistentOnPUSCH-TriggerStateList

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

[0019] , clause 5.2.

[0641] CSI-SemiPersistentOnPUSCH-TriggerStateList information element

[0642] -- ASN1START

[0643] -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-START

[0644] CSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState

[0645] CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE {

[0646] associatedReportConfigInfo CSI-ReportConfigId,

[0647] ...

[0648] }

[0649] -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP

[0650] -- ASN1STOP

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

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

[0653] - CSI-IM resources for interference measurement

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

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

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

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

[0658] [Table 39]

[0659] Table 5.2.1.4-1: Triggering / Activation of CSI Reporting for the possible CSI-RS Configurations.

[0660]

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

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

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

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

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

[0666] [Table 40]

[0667]

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

[0669] Figure 13 is a diagram illustrating an example of a non-periodic CSI reporting method.

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

[0671] [Table 41]

[0672]

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

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

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

[0676]

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

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

[0679] [Regarding Terminal Capability Reporting]

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

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

[0682] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. The method by which the terminal configures the UE capability in the NR system is summarized below.

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

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

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

[0686] 4. The terminal selects the BCs to be reported 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 predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

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

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

[0689] [CA / DC Related]

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

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

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

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

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

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

[0696] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

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

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

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

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

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

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

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

[0704] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0705] - Retransmission of PDCP SDUs

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

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

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

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

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

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

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

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

[0714] - Concatenation, segmentation, and reassembly functions of RLC SDUs

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

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

[0717] - Duplicate detection

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

[0719] - RLC SDU discard function

[0720] RLC re-establishment function

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

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

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

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

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

[0726] - Scheduling information reporting function

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

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

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

[0730] - MBMS service identification function

[0731] - Transport format selection function

[0732] - Padding

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

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

[0735] Referring to the descriptions regarding PDCCH and beam configuration above, PDCCH repeated transmission is not supported in current Rel-15 and Rel-16 NR, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for PDCCH repeated transmission through multiple transmission points (TRPs) to improve the PDCCH reception reliability of a terminal. The specific method is described in detail in the following examples.

[0736] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The contents of the present disclosure are applicable to FDD (frequency division duplex), TDD (time division duplex) and / or XDD (cross division duplex) (and / or SBFD (subband non-overlapping full duplex), full duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a downlink data channel of the physical layer, or from a terminal to a base station using an uplink data channel of the physical layer, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element; MAC CE).

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

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

[0739] The term "subframe" as used in the present disclosure below is a general term that may refer to a specific time unit corresponding to TTI (Transmit Time Interval), and specifically, it may refer to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

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

[0741] [Regarding NC-JT]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0759] Case #3 (N110) illustrates a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and a single control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

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

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

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

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

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

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

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

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

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

[0769] [Multi-DCI-based Multi-TRP]

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

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

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

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

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

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

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

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

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

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

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

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

[0782] [PHR]

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

[0784] [Mathematical Formula 7]

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

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

[0787] [PUSCH power control]

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

[0789] [Mathematical Formula 8]

[0790]

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

[0792] [Table 42-1]

[0793]

[0794]

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

[0796] [Table 43] TPC command

[0797]

[0798] [PUCCH power control]

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

[0800] [Mathematical Formula 9]

[0801]

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

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

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

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

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

[0807] [pseudo-code 1 start]

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

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

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

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

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

[0813] [End of pseudo-code 1]

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

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

[0816] [Table 44]

[0817]

[0818]

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

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

[0821] Step 1: Search for the PDSCH allocation value that terminates first within a slot among all rows of the PDSCH time resource allocation table. In Table 44, you can see that row index 14 terminates first. Mark this as 1 in the order column. Then, mark other row indices that overlap with row index 14 by at least one symbol as 1x in the order column.

[0822] Step 2: Then, search for the earliest ending PDSCH assignment value among the remaining row indices not displayed in the Order column. In Table 44, this corresponds to the row with row index 7 and dmrs-TypeA-Position value 3. Then, other row indices that overlap with that row index by at least one symbol are marked as 2x in the order column.

[0823] * Step 3: Repeat Step 2, incrementing the order value. For example, in Table 44, search for the earliest ending PDSCH assignment value 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. Then, other row indices that overlap with that row index by at least one symbol are marked as 3x in the order column.

[0824] * Step 4: Terminate when an order is displayed for all row indices. The size of that order is the maximum number of PDSCHs that can be scheduled without time overlap within that slot. Scheduling without time overlap means that different PDSCHs are scheduled via TDM.

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

[0826] As another example, the factors to be considered for determining a quasi-static HARQ-ACK codebook (or type 1 HARQ-ACK codebook) may be as shown in the following Table 45.

[0827]

[0828] As another example, the pseudo-code for determining the HARQ-ACK codebook may be as shown in the following Table 46.

[0829]

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

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

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

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

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

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

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

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

[0838] [Explanation of Satellite Communication Structure]

[0839] The following description explains the characteristics of satellite communication. Satellites for communication can be classified into Low Earth Orbit (LEO), Middle Earth Orbit (MEO), and Geostationary Earth Orbit (GEO) satellites depending on their orbits. Generally, GEO refers to a satellite at an altitude of approximately 36,000 km, MEO refers to a satellite at an altitude of 5,000 to 15,000 km, and LEO refers to a satellite at an altitude of 500 to 1,000 km. Of course, the above examples are not limited. According to one embodiment of the present disclosure, the Earth's orbital period varies depending on the altitude; for GEO, the Earth's orbital period is approximately 24 hours, for MEO, it is approximately 6 hours, and for LEO, it is approximately 90 to 120 minutes. Low Earth orbit (~2,000 km) satellites may have advantages over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time it takes for a signal transmitted from a transmitter to reach a receiver) and loss due to their relatively low altitude. FIG. 21 is a diagram illustrating the Earth orbital period of a communication satellite according to the altitude or height of the satellite according to one embodiment of the present disclosure. Assuming that a terminal communicates with a satellite located at an altitude of 1,200 km, the distance between the terminal and the satellite may vary depending on the elevation angle between the satellite and the terminal. For example, if the elevation angle between the satellite and the terminal is 90 degrees, the distance between the terminal and the satellite is 1,200 km, but if the elevation angle between the satellite and the terminal is 10 degrees, the distance between the terminal and the satellite is approximately 3,135 km. Therefore, in satellite communication, even if the terminal is fixed, the distance between the satellite and the terminal may vary due to the satellite orbiting periodically, such as a low Earth orbit satellite.In addition, because the distance between a terminal and a satellite in satellite communication is much greater than the distance between a terminal and a base station in a terrestrial network, it may be necessary to transmit control and data information by performing data transmission with a low code rate or by using repetitive transmission.

[0840] [LTE: NB-IoT]

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

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

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

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

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

[0846] a. OFDM and Single Carrier Method

[0847] - OFDM (Orthogonal Frequency Division Multiplexing): Used for downlink transmission by leveraging the strengths of multiple carrier modulation.

[0848] - Single Carrier FDMA (SC-FDMA): Used to reduce PAPR (Peak-to-Average Power Ratio) in uplink transmission to increase the power efficiency of IoT devices.

[0849] b. Modulation method

[0850] - QPSK and BPSK: NB-IoT primarily uses QPSK (quadrature phase shift keying) for robust communication, while BPSK (binary phase shift keying) is used in coverage extension scenarios that are more robust against noise and interference.

[0851] c. Resource Grid and Synchronization

[0852] - Resource Grid Adaptation: NB-IoT adapts the LTE resource grid to meet narrowband requirements and allocates resource elements for synchronization signals and reference signals.

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

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

[0855] [LTE: TDD operation in NB-IoT-based satellite communication]

[0856] Among the various methods supporting NB-IoT-based satellite communication, it is possible to group numerous beams covered by a single satellite into beam groups from the perspective of time resources using the TDMA (time division multiplexing access) method, and to transmit and receive signals with terminals belonging to the beam group according to specific time intervals.

[0857] FIG. 22 is a diagram showing a situation in which beam groups are activated at specific times in a satellite communication system according to one embodiment of the present disclosure.

[0858] In a situation where a single satellite can form a total of 12 beams at a specific location, it may be possible for three different beams to be activated for each time period of t1, t2, t3, and t4. Terminals belonging to the activated beams may be able to exchange signals with the satellite during the corresponding activated period. The reason for activating only some of the 12 beams is that, in the case of the downlink, there are limitations on the satellite's transmission power. Therefore, if all 12 beams are activated simultaneously to transmit downlink-related signals, the signal strength received by terminals belonging to (or receiving downlink signals through) a specific beam may be lower compared to when three beams are activated simultaneously to transmit downlink signals to that beam. Therefore, to maintain downlink link quality, it may be possible to activate only some beams at specific times using the TDM (time division multiplexing) method. In the example of Fig. 22, it may be possible for specific beams to be activated repeatedly and periodically in the sequence t1 -> t2 -> t3 -> t4 -> t1 -> t2 ... Alternatively, as in the example of FIG. 23, if the downlink transmission interval is repeated in the latter part every 90ms, it may be possible to transmit downlink signals through each of the last four DL intervals.

[0859] FIG. 23 is a diagram showing a TDD structure of satellite communication supporting NB-IoT according to one embodiment of the present disclosure. In FIG. 23, a TDD structure within a 90ms interval is exemplified.

[0860] Referring to 2300 in Fig. 23, the DL and UL intervals within the 90ms interval are 8.28ms, and the gap may have values ​​such as 1ms, 1.26ms, 0.22ms, and 0.1ms at specific locations within the 90ms interval. The gap value may be applied with some other values. The 20.32ms interval may not be used for actual DL and UL transmission and reception.

[0861] Referring to 2320 in Fig. 23, the 90ms interval is divided into 9 frames of 10ms length, and NPSS, NSSS, and NPBCH can be transmitted in the 9th frame. For example, NPBCH can be transmitted in the first subframe of the 9th frame, NPSS can be transmitted in the sixth subframe of the 9th frame, and NSSS can be transmitted in the tenth subframe of the 9th frame. This is exemplary, and a single subframe may contain all of NPBCH, NPSS, and NSSS, or some of them (e.g., NPBCH and NPSS).

[0862] In the following description of an embodiment of the present disclosure, a synchronization signal and NPBCH transmission and reception method specialized for the frame structure of 2300 in FIG. 23 is described. Specifically, the frame structure has a form that repeats every 90ms, and in the description of an embodiment of the present disclosure, a method for transmitting a synchronization signal and NPBCH and a signal design method are described in the last four DL transmission intervals consisting of 8.28ms. From the perspective of a terminal belonging to any specific beam, in the frame structure of 2300 in FIG. 23 that repeats every 90ms period, only one of the four DL transmission intervals (2302, 2304, 2306, 2308) illustrated in 2300 of FIG. 23 is allocated as the actual DL transmission interval. This is because, as previously explained in FIG. 22, it is possible for the satellite to activate only some beams at a specific moment. Therefore, every 90ms period, the terminal can receive a downlink signal during a DL transmission interval corresponding to approximately 8.28ms. In addition, an uplink signal can be transmitted during a UL transmission interval corresponding to another approximately 8.28 ms. The length of the gap or guard period described in FIG. 23 is merely an example and may be applied with different values. Accordingly, considering a frame structure such as 2300 in FIG. 23, a synchronization signal and PBCH transmission and reception method specialized therein will be described. Hereinafter, Examples 1 to 4 may be applied independently or at least partially combined.

[0863] [Example 1]

[0864] In the following embodiments, a method for setting synchronization signals and NPBCH resources and a method for transmitting them in a satellite communication system operating with TDD are described. As previously explained, in conventional NB-IoT, NPSS and NPBCH are periodically transmitted and received in a specific subframe every 10ms, and NSSS is periodically transmitted and received in a specific subframe every 20ms. Therefore, in the 2300 frame structure of FIG. 23, it is difficult to transmit them in a single DL transmission section such as 2302, 2304, 2306, and 2308. For example, assuming that NPSS, NSSS, and NPBCH are transmitted according to each subframe index in the 9th frame of 2320 of FIG. 23, which is 10ms long, NPSS and NSSS can be transmitted in accordance with the DL transmission section 2308, but there is a possibility that NPBCH will be transmitted in 2306 instead of the corresponding DL transmission section 2308. Therefore, the terminal belonging to the DL transmission section 2308 is unable to receive the NPBCH. The terminal may not receive the NPBCH in the DL transmission section 2308. Therefore, a method is required to enable the transmission of a synchronization signal and an NPBCH for each DL transmission section of 2300 in FIG. 23, and it may be possible to consider at least one of the following methods or a combination of at least one.

[0865] Method 1-1: NPSS, NSSS, and NPBCH are included only in the last four frames within a 90ms period and may be located within the last three subframes of each of the four frames. NPSS, NSSS, and NPBCH are assigned to the last four frames within a 90ms period, and NPSS, NSSS, and NPBCH may be assigned within the last three subframes of each of the four frames.

[0866] FIG. 24 is a diagram showing resources allocated to NPSS, NSSS, and NPBCH according to one embodiment of the present disclosure. Referring to 2420 in FIG. 24, for the last four frames among a total of nine frames belonging to a 90ms period, it may be possible for NPSS, NSSS, and NPBCH to belong to the last three subframes within each frame. 2420 in FIG. 24 illustrates a case where NPBCH, NPSS, and NSSS are included in the 8th, 9th, and 10th subframes, respectively, within the 9th frame. This is merely an example, and the order of NPBCH, NPSS, and NSSS can be changed. For example, NPBCH, NSSS, and NPSS may be included in the 8th, 9th, and 10th subframes, respectively. As another example, NSSS, NPBCH, and NPSS may be included in the 8th, 9th, and 10th subframes, respectively. As another example, NPSS, NSSS, and NPBCH may be included in the 8th, 9th, and 10th subframes, respectively. As another example, NPSS, NPBCH, and NSSS may be included in the 8th, 9th, and 10th subframes, respectively. As another example, NSSS, NPSS, and NPBCH may be included in the 8th, 9th, and 10th subframes, respectively.

[0867] Through this, terminals receiving downlink signals in the first DL transmission section 2402 of the 2400 frame structure of FIG. 24 can receive synchronization signals and NPBCH through NPBCH, NPSS, and NSSS belonging to the last three subframes within the 6th frame of FIG. 24. Similarly, terminals receiving downlink signals in the second DL transmission section 2404 of the 2400 frame structure of FIG. 24 can receive synchronization signals and NPBCH through NPBCH, NPSS, and NSSS belonging to the last three subframes within the 7th frame of FIG. 24. Similarly, terminals receiving downlink signals in the third DL transmission section 2406 of the 2400 frame structure of FIG. 24 can receive synchronization signals and NPBCH through NPBCH, NPSS, and NSSS belonging to the last three subframes within the 8th frame of FIG. 24. Similarly, in the 2400 frame structure of FIG. 24, terminals receiving downlink signals in the fourth DL transmission interval 2408 can receive synchronization signals and NPBCHs through NPBCHs, NPSSs, and NSSSs belonging to the last three subframes within the ninth frame of 2420. In this way, terminals belonging to each beam group may be able to receive at least synchronization signals and NPBCHs.

[0868] In the preceding explanation, it was explained that the synchronization signal and NPBCH are transmitted and received through the last four frames within the 90ms period of 2420 in Fig. 24, but the synchronization signal and NPBCH can be transmitted and received through the last three frames.

[0869] FIG. 25 is a diagram showing resources in which synchronization signals and NBPCH are transmitted and received according to an embodiment of the present disclosure. Since the DL transmission interval of 2600 in FIG. 25 is smaller than 10ms, which is the frame length of 2620, it is difficult to accurately map each DL transmission interval to a single frame. Therefore, by allocating NPSS, NSSS, and NPBCH to the last four subframes within each frame, downlink synchronization signals, PBCH, and other signals can be transmitted to different beam groups through each DL transmission interval 2602, 2604, 2606, and 2608. Specifically, in the DL transmission interval 2602, downlink synchronization signals, NPBCH, and other downlink signals can be transmitted and received through some subframes of the 6th and 7th frames in the frame structure of 2620. In this case, 2622 refers to signals composed of NPSS, NSSS, and NPBCH. 2622 may be a subframe (e.g., three subframes) mapped to NPSS, NSSS, and NPBCH. The order of NPSS, NSSS, and NPBCH may be changed. Similarly, in DL transmission segment 2604, downlink synchronization signals, NPBCH, and other downlink signals may be transmitted and received through some subframes of the 7th and 8th frames in the frame structure of 2620. Similarly, in DL transmission segment 2606, downlink synchronization signals, NPBCH, and other downlink signals may be transmitted and received through some subframes of the 8th and 9th frames in the frame structure of 2620. Similarly, in DL transmission segment 2608, downlink synchronization signals, NPBCH, and other downlink signals may be transmitted and received through some subframes of the 9th frame in the frame structure of 2620.

[0870] Method 1-2: NPSS, NSSS, and NPBCH are included only in the last four frames within a 90ms period and may be located within the first three subframes of each of the four frames. NPSS, NSSS, and NPBCH are assigned to the last four frames within a 90ms period, and NPSS, NSSS, and NPBCH may be assigned within the first three subframes of each of the four frames.

[0871] FIG. 26 is a diagram showing resources allocated to NPSS, NSSS, and NPBCH according to one embodiment of the present disclosure. Referring to 2520 in FIG. 26, for the last four frames among a total of nine frames belonging to a 90ms period, it may be possible for NPSS, NSSS, and NPBCH to belong to the first three subframes within each frame. 2520 in FIG. 26 illustrates a case where NPBCH, NPSS, and NSSS are included in the 1st, 2nd, and 3rd subframes, respectively, within the 9th frame. This is merely an example, and the order of NPBCH, NPSS, and NSSS may be changed. For example, NPBCH, NSSS, and NPSS may be included in the 1st, 2nd, and 3rd subframes, respectively. As another example, NSSS, NPBCH, and NPSS may be included in the 1st, 2nd, and 3rd subframes, respectively. As another example, NPSS, NSSS, and NPBCH may be included in the 1st, 2nd, and 3rd subframes, respectively. As another example, NPSS, NPBCH, and NSSS may be included in the 1st, 2nd, and 3rd subframes, respectively. As another example, NSSS, NPSS, and NPBCH may be included in the 1st, 2nd, and 3rd subframes, respectively.

[0872] Method 1-3: Separately, it may be possible for the transmission periods of NPSS, NSSS, and NPBCH to differ by band. For example, in the 1616 - 1626.5 MHz frequency band (1616 MHz or more and 1626.5 MHz or less. In the description of one embodiment of the present disclosure, 1616 - 1626.5 MHz is an exemplary range of frequency bands for satellite communication and its value may be changed. For example, 1616 - 1626.5 MHz may be designated as the MSS (Mobile Satellite Service) band), NPSS may be transmitted in the 6th subframe every 9 frames. In other frequency bands, it may be transmitted in the 6th subframe every frame. Additionally, in the 1616 - 1626.5 MHz frequency band, NSSS may be transmitted in the 10th subframe every 9 frames. In other frequency bands, it may be transmitted in the 10th subframe of every even-numbered frame. Also, in the 1616 - 1626.5 MHz frequency band, NPBCH may be transmitted in the 1st subframe of every 9 frames. In other frequency bands, it may be transmitted in the 1st subframe of every frame.

[0873] Method 1-4: The descriptions of the preceding methods primarily explained the locations where NPSS, NSSS, and NPBCH can be transmitted and received based on specific subframe indices. In contrast, the subframe index where NPSS is transmitted and received is determined in advance as a specific value, and it may be possible to indicate whether NSSS and NPBCH belong to a preceding subframe or the subframe immediately following the subframe in which NPSS is transmitted and received, respectively. For example, NPSS may be included in the last four frames among the nine frames of FIG. 25, and it may be possible to transmit and receive in the 8th subframe within each frame. And NSSS may be transmitted and received in the 8-xth subframe from the 8th subframe in which NPSS is transmitted and received. Here, x may be a non-zero integer value. NPBCH may be transmitted and received in the 8+yth subframe from the 8th subframe in which NPSS is transmitted and received. In this case, y can be a non-zero integer value. If a value greater than or equal to 10 is selected based on x and y values, this can be considered as the index of the next frame's subframe. For example, the 12th subframe refers to the 2nd subframe within the next frame. Generalizing this, if NPSS is transmitted and received in subframe p2 within frame p1, NSSS can be transmitted and received in subframe p2 + mod(p2-x, 10) within frame (p1 + floor((p2-x) / 10)) and NPBCH can be transmitted and received in subframe p2 + mod(p2+y, 10) within frame (p1 + floor((p2+y) / 10)).

[0874] FIG. 27 is a flowchart illustrating a method for determining the transmission period of NPSS / NSSS / NPBCH of a terminal according to a frequency band according to an embodiment of the present disclosure. The terminal first determines the frequency band in which it performs an initial connection. If the frequency band in which the terminal performs an initial connection is a first frequency band, the terminal searches for NPSS / NSSS / NPBCH based on a first period. Specifically, the transmission based on the first period is that NPSS is transmitted every 10ms, NSSS is transmitted every 20ms, and NPBCH is transmitted every 10ms. If the frequency band in which the terminal performs an initial connection is a second frequency band, the terminal searches for NPSS / NSSS / NPBCH based on a second period. Specifically, the transmission based on the second period is that NPSS is transmitted every 90ms, NSSS is transmitted every 90ms, and NPBCH is transmitted every 90ms. The second frequency band mentioned above refers to a frequency band of 1616–1626.5 MHz or may refer to a portion thereof. The first frequency band may refer to a frequency band other than 1616–1626.5 MHz. The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0875] [Example 2]

[0876] In the following embodiments, an NPSS transmission method in a satellite communication system operating with TDD is described.

[0877] FIG. 28 is a diagram showing resources allocated to an NPSS according to one embodiment of the present disclosure. FIG. 28 is an example of an NPSS structure utilized in FDD or TDD of a terrestrial network.

[0878] Referring to FIG. 28, the frequency resources of the NPSS consist of 11 RE (resource elements) (or subcarriers), and the time resources consist of 11 symbols. Of the 14 symbols within a 1ms subframe in which the NPSS is transmitted and received, the first 3 symbols are not utilized for transmitting or receiving other LTE control signals. The NPSS is used for the terminal to synchronize with the NB-IoT cell in both time and frequency. When the device (terminal) wakes up after being in deep sleep for a long period, the time reference may no longer have a reliable synchronization signal, and the frequency reference may deviate by up to 20 ppm (e.g., 18 kHz in the 900 MHz band) due to the limited accuracy of the low-power oscillator tracking time during deep sleep. Therefore, the NPSS must be designed to be detectable even at very large frequency offsets. To support low complexity, cells in all NB-IoT networks can use the same NPSS. Therefore, the terminal searches for only one NPSS sequence. On the other hand, in LTE networks, the terminal uses three different PSS sequences. The NPSS takes the form of a hierarchical sequence generated based on a base sequence p and a binary cover code c. The base sequence p is a frequency domain ZC (Zadoff-Chu) sequence of length 11 with a root index of 5, and the nth frequency domain element can be given by the following mathematical formula.

[0879] [Mathematical Formula 10]

[0880]

[0881] The binary cover code is c = (1,1,1,1,-1,-1,1,1,1,1,-1,1). Each OFDM symbol within an NPSS subframe carries a copy p or -p of the base sequence according to the binary cover code. The same NPSS sequence is repeated in all subframes designated as NPSS transmissions. The hierarchical sequence design can reduce the terminal complexity of searching for NPSS subframes. Resource mapping within an NPSS subframe is shown in Fig. 28.

[0882] In in-band mode, multiple NPSS REs may overlap with the LTE CRS (cell-specific reference signal). The NPSS resources in the corresponding REs can be punctured by the LTE CRS. That is, REs that overlap with the LTE CRS are not used for NPSS transmission. However, the terminal performing NPSS detection does not need to recognize this puncturing. For example, the terminal can simply correlate the received signal with an unpunctured NPSS. This is because, although there is a discrepancy between the NPSS transmitted from the base station and the locally generated device in in-band mode, the impact on NPSS detection performance is small.

[0883] However, for NB-IoT for satellite communication operating in the 1616 - 1626.5 MHz frequency band TDD, it may be inefficient for NPSS not to use the first three symbols within a single subframe. This is because LTE may not be used in that frequency band. Therefore, it may be possible to consider a new NPSS structure.

[0884] FIG. 29 is a diagram showing the resource structure of an improved NPSS according to one embodiment of the present disclosure. Referring to FIG. 29, the frequency resources of the NPSS consist of 11 REs (or subcarriers), and the time resources consist of 14 symbols. Basically, the hierarchical sequence form generated based on the basic sequence and binary cover code described above is the same, but it may have the characteristic that the length of the binary cover code c is increased to 14 instead of 11. Let this be c', the binary cover code c' may be composed of at least one of the following methods or at least a combination of at least one.

[0885] Method 2-1: (a1, a2, a3, 1,1,1,1,-1,-1,1,1,1,1,-1,1)

[0886] Method 2-2: (a1, a2, 1,1,1,1,-1,-1,1,1,1,-1,1, a3)

[0887] Method 2-3: (a1, 1,1,1,1,-1,-1,1,1,1,-1,1, a2, a3)

[0888] Method 2-4: (1,1,1,1,-1,-1,1,1,1,-1,1, a1, a2, a3)

[0889] For the above methods, a1, a2, and a3 may each have a value of 1 or -1. Accordingly, when a terminal connects to a satellite communication network operating in TDD in the 1616 - 1626.5 MHz frequency band, a binary cover code c' as shown in FIG. 29 may be applied as the NPSS, and in other frequency bands, a binary cover code c as shown in FIG. 28 may be applied.

[0890] FIG. 30 is a flowchart illustrating a method for determining an NPSS transmission resource of a terminal according to a frequency band according to an embodiment of the present disclosure. The terminal first determines a frequency band for performing an initial connection. If the frequency band for performing the initial connection is a first frequency band, it determines that a resource is mapped to a first NPSS structure and performs an initial connection. The structure of the first NPSS is the structure described in FIG. 28. If the frequency band for performing the initial connection is a second frequency band, it determines that a resource is mapped to a first NPSS structure and performs an initial connection. The structure of the second NPSS is the structure described in FIG. 29. The second frequency band may refer to a frequency band of 1616 - 1626.5 MHz or a portion thereof. The first frequency band may refer to a frequency band other than 1616 - 1626.5 MHz. The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0891] [Example 3]

[0892] In the following embodiments, a method for transmitting NSSS in a satellite communication system operating with TDD is described. When the terminal acquires the NSSS, it performs coarse synchronization in time and frequency, detects the cell ID, and then switches to an operation for receiving the NSSS to obtain more information about the frame structure. NB-IoT can support 504 unique physical cell IDs (PCIDs) indicated by the NSSS. The NSSS has an 80ms repeat interval, and four NSSS sequences are transmitted within this interval. Although the four NSSS sequences transmitted at the 80ms repeat interval are all different, the same set of four sequences is repeated every 80ms.

[0893] FIG. 31 is a diagram showing the resources allocated to an NSSS according to one embodiment of the present disclosure. The frequency resources of the NSSS consist of 12 REs (or subcarriers), and the time resources consist of 11 symbols. As shown in FIG. 31, basically, only the last 11 OFDM symbols in an NSSS subframe are used to transmit the NSSS. However, compared to NPSS, since the NSSS is mapped to all 12 subcarriers of the PRB, 132 REs are generated in the NSSS subframe. The frequency domain symbols for these 132 NSSS REs are determined according to the sequence of [Equation 11] below. FIG. 31 is a diagram showing the situation in which NSSS resources are mapped according to one embodiment of the present disclosure.

[0894] [Mathematical Formula 11]

[0895]

[0896] NSSS for cells with PCID k is an extended ZC (Zadoff-Chu) sequence , binary scrambling sequence and phase shift It is determined by the extended ZC sequence It can be obtained by first generating a ZC sequence of length 131 of root u as shown in [Equation 12], and then repeating the first element to extend the length to 132 as shown in [Equation 13].

[0897] [Mathematical Formula 12]

[0898]

[0899] [Mathematical Formula 13]

[0900]

[0901] The root is determined according to cell ID k as follows [Equation 14].

[0902]

[0903] [Mathematical Formula 14]

[0904]

[0905] Binary scrambling sequence It is based on a Walsh-Hadamad sequence of length 128, and the first four elements are repeated at the end to become a sequence of length 132. The sequence index q is determined according to cell ID k as follows [Equation 15].

[0906] [Mathematical Formula 15]

[0907]

[0908] Within a cell, all NSSS transmissions share the same binary scrambling sequence and extended ZC sequence, which are determined by the cell ID k. Four occurrences of NSSS within an 80ms NSSS repetition interval. (4 NSSS sequences) are phase shifts defined as follows [Equation 16] It is distinguished by.

[0909] [Mathematical Formula 16]

[0910]

[0911] NSSS can be designed so that the device can clearly identify the cell identifier k through the matching of the binary scrambling sequence and the extended ZC sequence. Additionally, it can support frame synchronization within an 80ms repeat interval by matching the phase shift term. Since the duration of a radio frame is 10ms, by identifying frame information within an 80ms repeat interval, the device essentially knows the least significant three bits (LSB) of the system frame number (SFN). Resource mapping within the NSSS subframe is shown in Fig. 29. Subcarriers 0 through 11 and symbols 3 through 13 within the NSSS subframe can be used as REs for the NSSS. In in-band mode, NSSS frequency domain symbols mapped to REs used by the LTE CRS are punctured by the CRS.

[0912] However, for NB-IoT for satellite communication operating in the 1616 - 1626.5 MHz frequency band TDD, it may be inefficient for NSSS not to use the first three symbols within a single subframe. This is because LTE may not be used in that frequency band. Therefore, it may be possible to consider a new NSSS structure.

[0913] FIG. 32 is a diagram showing the resource structure of an improved NSSS according to one embodiment of the present disclosure. Referring to FIG. 32, the frequency resources of the NSSS consist of 12 REs (or subcarriers), and the time resources consist of 14 symbols. As the number of resources in FIG. 32 increases from the conventional 132 to 168, it may be possible to consider at least one of the following methods or a combination thereof in consideration of this. For reference, unless otherwise specified, the NSSS resource generation and mapping process described above may be applied. The definitions of variables in each formula may also refer to those defined in the NSSS resource generation and mapping process described above.

[0914] Method 3-1: The terminal is an extended ZC sequence It can be obtained by first generating a ZC sequence of length 131 of root u as shown in [Equation 12], and then repeating the first 37 elements to extend the length to 168 as shown in [Equation 17].

[0915] [Mathematical Formula 17]

[0916]

[0917] Method 3-2: The terminal is an extended ZC sequence It can be obtained by first generating a ZC sequence of length 156 of root u as shown in [Equation 18], and then repeating the first 12 elements to extend the length to 168 as shown in [Equation 19].

[0918] [Mathematical Formula 18]

[0919]

[0920] [Mathematical Formula 19]

[0921]

[0922] Method 3-3: Phase shift in [Equation 11] is a value used by the terminal to distinguish the cell ID. In satellite communication, because a single beam covers a large area, the terminal uses multiple phase shifts It may not be necessary to blindly explore. Therefore, consider [Equation 20] instead of [Equation 11], or in [Equation 21] The value can always be made to have one of 0, 1, 2, or 3.

[0923] [Mathematical Formula 20]

[0924]

[0925] [Mathematical Formula 21]

[0926]

[0927] FIG. 33 is a flowchart illustrating a method for determining NPSS transmission resources of a terminal according to a frequency band according to an embodiment of the present disclosure. The terminal first determines a frequency band for performing an initial connection. If the frequency band for performing the initial connection is a first frequency band, it determines that resources are mapped to a first NSSS structure and performs an initial connection. The structure of the first NSSS is the structure described in FIG. 31. If the frequency band for performing the initial connection is a second frequency band, it determines that resources are mapped to a first NSSS structure and performs an initial connection. The structure of the second NSSS is the structure described in FIG. 32. The second frequency band may refer to a frequency band of 1616 - 1626.5 MHz or a portion thereof. The first frequency band may refer to a frequency band other than 1616 - 1626.5 MHz. The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0928] [Example 4]

[0929] Hereinafter, an NPBCH transmission method in a satellite communication system operating with TDD is described in the embodiments. The NPBCH, used to transmit the NB-IoT master information block (MIB), provides essential information for a terminal to operate in an NB-IoT network. The NPBCH uses a 640ms TTI, but only subframe 0 is used in the radio frame. An example of resource mapping is shown in FIG. 34.

[0930] FIG. 34 is a diagram showing a situation in which NPBCH resources are mapped according to one embodiment of the present disclosure. The subcarriers used for the Narrowband Reference Signal (NRS) vary depending on the NB-IoT cell ID. Therefore, the NRS RE can shift up and down in the frequency domain. Some REs are reserved because they can be used by LTE in the in-band case. The LTE CRS can use REs outside the potential LTE control domain, namely the first three OFDM symbols. These REs can also shift up and down depending on the LTE cell ID.

[0931] FIG. 34 illustrates that symbols 5, 6, 12, and 13 are used as NRS in subcarriers 2, 5, 8, and 11. In subcarrier 2, symbols 5 and 12 are used as RE for the NRS of antenna port 1, and symbols 6 and 13 are used as RE for the NRS of antenna port 2. In subcarrier 5, symbols 5 and 12 are used as RE for the NRS of antenna port 2, and symbols 6 and 13 are used as RE for the NRS of antenna port 1. In subcarrier 8, symbols 5 and 12 are used as RE for the NRS of antenna port 1, and symbols 6 and 13 are used as RE for the NRS of antenna port 2. In subcarrier 11, symbols 5 and 12 are used as REs for the NRS of antenna port 2, and symbols 6 and 13 are used as REs for the NRS of antenna port 1. NB-IoT requires the use of a cell ID that generates the NRS subcarrier set in an in-band environment. For example, subcarriers 2, 5, 8, and 11 in Fig. 34 are identical to the subcarrier set used by the CRS of the hosting LTE cell. Therefore, when the terminal knows the NB-IoT cell ID, it can determine which RE is used for the LTE CRS in in-band mode. As can be seen in Fig. 31, there are 100 REs available for the NPBCH in the subframe. Since the NPBCH uses QPSK modulation, the NPBCH subframe can contain 200 encoded bits. As mentioned above, the NPBCH is transmitted only in subframe 0 of the radio frame. The transport block size (TBS) of NPBCH is 34 bits, and a 16-bit cyclic redundancy check (CRC) is attached to the transport block (TB).These 50 bits (TBS+CRC) are encoded together using LTE Tail-Biting Convolutional Code (TBCC) and ratio-matched to generate 1,600 encoded bits. The encoded bits are divided into eight Code Sub Blocks (CSBs) or Code Block Groups (CBGs), each 200 bits long, which are mapped to 100 QPSK symbols. Symbol-level scrambling is applied to each CSB to provide robust protection against inter-cell interference, particularly when inter-cell interference is dominant due to NPBCH signals from other cells. The scrambling pattern depends on the cell ID and the system frame number. This is achieved by re-initializing the scrambling pattern at the start of each radio frame using the cell ID and a seed value determined by SFN mod 8. Consequently, each CSB is scrambled into eight unique sets of 100 QPSK symbols mapped to subframe 0 in eight consecutive radio frames. Scrambling is implemented as a symbol-level rotation that can be easily decrypted by the device, as the device knows the cell ID and frame structure within an 80 ms interval after synchronizing with the NSSS. Thus, the device knows how to descramble the NPBCH symbols and obtain the subframe symbol sequence spanning multiple iterations of the CSB. This facilitates, for example, the coherent coupling of the repeating CSBs. Correlating the repeating CSBs after descrambling is also a powerful tool for performing frequency offset estimation. The transmission of eight NPBCH subblocks in the NPBCH TTI is illustrated in Fig. 35.

[0932] FIG. 35 is a diagram illustrating a situation in which the payloads of an NPBCH according to one embodiment of the present disclosure are each divided and repeatedly transmitted. As described above, the encoded bits are divided into eight CSBs or CBGs, each 200 bits long, and assuming that each CSB or CBG is repeatedly transmitted eight times, transmission for a total of 64 NPBCH blocks may be required. Since the conventional NPBCH is basically transmitted in the first subframe of every radio frame, the time required to transmit all NPBCHs may be approximately 640 ms. Each NPBCH subframe can be decoded independently, but all NPBCH subframes can also be decoded collectively. For a specific device with good coverage, a single transmission of one CSB may be sufficient to correctly decode the NPBCH information. The CRC attached to the NPBCH TB is masked by a sequence that depends on the number of NRS antenna ports (1 or 2). This allows the device to detect the number of NRS antenna ports through blind decoding. In the case of two NRS ports, Space Frequency Block Coding (SFBC) is used. Two consecutive NPBCH REs along the frequency dimension form an SFBC pair. In these two REs, antenna port 0 transmits a QPSK symbol pair (s1, s2), while antenna port 1 transmits a QPSK symbol pair (-s2 * , s1 * Transmits ).

[0933] However, for NB-IoT for satellite communication operating in the TDD of the 1616 - 1626.5 MHz frequency band, it may be inefficient for the NSSS not to use the first three symbols within a single subframe and the RE that LTE CRS can potentially use. This is because there are no LTE terminals in that frequency band. In other words, LTE terminals do not use that frequency band. Additionally, it may not be necessary to consider two types of NRS patterns for adjacent cell interference cancellation. This is because, in satellite communication, the adjacent cell size is large, so there are not many situations where interference cancellation for adjacent cells is required, and furthermore, it may be possible for satellite communication to perform interference cancellation in advance using a polarized antenna pattern. Therefore, in that frequency band, it may be possible for the NPBCH to transmit and receive using at least one of the structures of FIGS. 36 to 39.

[0934] FIGS. 36 to 39 are drawings showing improved NPBCH transmission resources according to one embodiment of the present disclosure. In the example of FIGS. 36 to 39, a total of 8 REs are utilized for NRS purposes and the remaining 160 REs can be utilized for NPBCH transmission resources.

[0935] Specifically, FIG. 36 illustrates that symbols 5, 6, 12, and 13 in subcarriers 2, 5, 8, and 11 are used as NRS. Symbols 6 and 13 in subcarrier 2 are used as RE for the NRS of antenna port 1, symbols 5 and 12 in subcarrier 5 are used as RE for the NRS of antenna port 1, symbols 6 and 13 in subcarrier 8 are used as RE for the NRS of antenna port 1, and symbols 5 and 12 in subcarrier 11 are used as RE for the NRS of antenna port 1. 160 REs, excluding the corresponding NRS REs, can be utilized for NPBCH transmission resources.

[0936] Figure 37 illustrates that symbols 5, 6, 12, and 13 in subcarriers 2, 5, 8, and 11 are used as NRS. Symbols 5 and 12 in subcarrier 2 are used as RE for the NRS of antenna port 1, symbols 6 and 13 in subcarrier 5 are used as RE for the NRS of antenna port 1, symbols 5 and 12 in subcarrier 8 are used as RE for the NRS of antenna port 1, and symbols 6 and 13 in subcarrier 11 are used as RE for the NRS of antenna port 1. 160 REs, excluding the corresponding NRS REs, can be utilized for NPBCH transmission resources.

[0937] Figure 38 illustrates that symbols 5 and 12 in subcarriers 2, 5, 8, and 11 are used as NRS. Symbols 5 and 12 in subcarrier 2 are used as RE for the NRS of antenna port 1, symbols 5 and 12 in subcarrier 5 are used as RE for the NRS of antenna port 1, symbols 5 and 12 in subcarrier 8 are used as RE for the NRS of antenna port 1, and symbols 5 and 12 in subcarrier 11 are used as RE for the NRS of antenna port 1. 160 REs, excluding the corresponding NRS REs, can be utilized for NPBCH transmission resources.

[0938] Figure 39 illustrates that symbols 6 and 13 are used as NRS in subcarriers 2, 5, 8, and 11. Symbols 6 and 13 in subcarrier 2 are used as RE for the NRS of antenna port 1, symbols 6 and 13 in subcarrier 5 are used as RE for the NRS of antenna port 1, symbols 6 and 13 in subcarrier 8 are used as RE for the NRS of antenna port 1, and symbols 6 and 13 in subcarrier 11 are used as RE for the NRS of antenna port 1. 160 REs, excluding the corresponding NRS REs, can be utilized for NPBCH transmission resources.

[0939] As described above, in the examples of FIGS. 36 to 39, a total of 8 REs are utilized for NRS purposes, and the remaining 160 REs can be utilized for NPBCH transmission resources. Thus, 1600 encoded bits are composed of 5 CSBs (or CBGs), and each CSB has 320 encoded bits. This can be converted into 160 QPSK symbols and allocated to the NPBCH resources exemplified in FIGS. 32 to 35. If each CSB is transmitted 8 times, transmission for a total of 40 NPBCH blocks may be required. As previously explained, since the minimum transmission period of one NPBCH can be 90ms, the time required to transmit all NPBCHs may be approximately 3600ms.

[0940] FIG. 40 is a diagram showing a situation in which the payloads of an NPBCH are each divided and repeatedly transmitted according to one embodiment of the present disclosure. As described above, the encoded bits are divided into five CSBs or CBGs of 320 bits each, and assuming that each CSB or CBG is repeatedly transmitted 8 times, transmission for a total of 40 NPBCH blocks may be required. As previously explained, since the minimum transmission period of one NPBCH can be 90ms, the time required to transmit all NPBCHs may be approximately 3600ms.

[0941] FIG. 41 is a flowchart illustrating a method for determining an NPBCH transmission resource of a terminal according to a frequency band according to an embodiment of the present disclosure. The terminal first determines a frequency band for performing an initial connection. If the frequency band for performing the initial connection is a first frequency band, it determines that a resource is mapped to a first NPBCH structure and performs an initial connection. The structure of the first NPBCH is the structure described in FIG. 34 and FIG. 35. If the frequency band for performing the initial connection is a second frequency band, it determines that a resource is mapped to a first NPBCH structure and performs an initial connection. The structure of the second NPBCH is the structure described in FIG. 36 to 39 and FIG. 40. The second frequency band may refer to a frequency band of 1616 - 1626.5 MHz or a portion thereof. The first frequency band may refer to a frequency band other than 1616 - 1626.5 MHz. The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

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

[0943] Referring to FIG. 42, the terminal may include a transceiver (referring to a terminal receiver (4200) and a terminal transmitter (4210)), a memory (not shown), and a terminal processing unit (4205, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (4200, 4210), memory, and terminal processing unit (4205) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

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

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

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

[0947] In addition, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. There may be multiple processors, and the processors can perform component control operations of the terminal by executing a program stored in memory.

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

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

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

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

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

[0953] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. There may be multiple processors, and the processors can perform control operations for the components of the base station by executing a program stored in memory.

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

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

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

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

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

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

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

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

[0962] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the invention.

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

Claims

1. In the method of a terminal of a communication system, A step of identifying resources for the NPSS (narrowband primary synchronization signal) and resources for the NSSS (narrowband secondary synchronization signal); A step of receiving the NPSS based on resources for the NPSS; It includes the step of receiving the NSSS based on resources for the NSSS, and The time resource of the above NPSS includes 14 symbols, and A method characterized in that the time resource of the above NSSS includes 14 symbols.

2. In Paragraph 1, The above NPSS is received based on a first sequence generated based on a binary cover code, and A method characterized by the length of the above binary cover code being 14.

3. In Paragraph 1, The above NSSS is received based on a second sequence of length 168, and A method characterized in that the second sequence is generated by repeating the first N elements of a third sequence, which has a length shorter than 168, to extend its length.

4. In Paragraph 3, A method characterized in that the above third sequence is generated without applying a phase shift value, or by applying a predetermined phase shift value.

5. In the method of a base station of a communication system, A step of identifying resources for the NPSS (narrowband primary synchronization signal) and resources for the NSSS (narrowband secondary synchronization signal); A step of transmitting the NPSS based on resources for the NPSS; It includes the step of transmitting the NSSS based on resources for the NSSS, and The time resource of the above NPSS includes 14 symbols, and A method characterized in that the time resource of the above NSSS includes 14 symbols.

6. In Paragraph 5, The above NPSS is transmitted based on a first sequence generated based on a binary cover code, and A method characterized by the length of the above binary cover code being 14.

7. In Paragraph 5, The above NSSS is transmitted based on a second sequence of length 168, and A method characterized in that the second sequence is generated by repeating the first N elements of a third sequence, which has a length shorter than 168, to extend its length.

8. In Paragraph 7, A method characterized in that the above third sequence is generated without applying a phase shift value, or by applying a predetermined phase shift value.

9. In a terminal of a communication system, Transmitter / receiver; and Identify resources for the NPSS (narrowband primary synchronization signal) and resources for the NSSS (narrowband secondary synchronization signal), and Receive the NPSS based on resources for the NPSS, and It includes a control unit configured to receive the NSSS based on resources for the NSSS, and The time resource of the above NPSS includes 14 symbols, and A terminal characterized in that the time resource of the above NSSS includes 14 symbols.

10. In Paragraph 9, The above NPSS is transmitted based on the cover code, and A terminal characterized by having a cover code length of 14.

11. In Paragraph 9, The above NPSS is received based on a first sequence generated based on a binary cover code, and A terminal characterized by the length of the above binary cover code being 14.

12. In Paragraph 11, The above NSSS is received based on a second sequence of length 168, and The above second sequence is characterized by being generated by repeating the first N elements of a third sequence, which has a length shorter than 168, to extend its length.

13. In a base station of a communication system, Transmitter / receiver; and Identify resources for the NPSS (narrowband primary synchronization signal) and resources for the NSSS (narrowband secondary synchronization signal), and Transmit the NPSS based on resources for the NPSS, and It includes a control unit configured to transmit the NSSS based on resources for the NSSS, and The time resource of the above NPSS includes 14 symbols, and A base station characterized by the time resource of the above NSSS including 14 symbols.

14. In Paragraph 13, The above NPSS is received based on a first sequence generated based on a binary cover code, and A base station characterized by the length of the above binary cover code being 14.

15. In Paragraph 13, The above NSSS is received based on a second sequence of length 168, and A base station characterized in that the second sequence above is generated by repeating the first N elements of a third sequence, which has a length shorter than 168, to extend its length.

Images