Method and apparatus for indicating synchronization signal block in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure provides: a method for transmitting and receiving an uplink signal when synchronization signal block transmission is configured in a case where subband non-overlapping full duplex (SBFD) is applied in a wireless communication system; and an apparatus carrying out the method.

Description

Method and device for indicating a synchronization signal block in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method in which a terminal is instructed to a synchronization signal block and to an apparatus capable of receiving and transmitting a data channel according to the synchronization signal block.

[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] Embodiments of the present disclosure aim to provide an apparatus and method capable of effectively providing services in a mobile communication system. In particular, a method and apparatus for transmitting and receiving synchronization signal blocks are proposed when SBFD (subband non-overlapping full duplex) is applied.

[0010] According to one embodiment of the present disclosure, a method performed by a terminal of a communication system comprises: receiving synchronization signal block (SSB) setting information from a base station; receiving a first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station; receiving a second DCI from the base station, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not permitted; checking whether an SSB transmission symbol and a resource of the PUSCH overlap based on the SSB setting information and the information regarding the SSB symbol for which PUSCH transmission is not permitted; and transmitting the PUSCH when the SSB transmission symbol and the resource of the PUSCH do not overlap.

[0011] In addition, a method performed by a base station of a communication system comprises: receiving synchronization signal block (SB) configuration information to a terminal; receiving a first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal; transmitting a second DCI to the terminal, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not permitted; and receiving the PUSCH when the resources of the SSB transmission symbol and the PUSCH do not overlap, wherein the SSB transmission symbol is characterized by being based on the SSB configuration information and the information regarding the SSB symbol for which PUSCH transmission is not permitted.

[0012] Additionally, a terminal of a communication system comprises: at least one transceiver; at least one processor connected to the at least one transceiver so as to be able to communicate with the at least one transceiver; and a memory connected to the at least one processor so as to be able to communicate with the at least one processor and capable of executing the at least one processor individually or in any combination thereof, wherein the terminal: receives SSB (synchronization signal block) setting information from a base station, receives DCI (downlink control information) for scheduling PUSCH (physical uplink shared channel) from the base station, receives a second DCI from the base station, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not allowed, checks whether the resources of the PUSCH overlap with the SSB setting information and the SSB symbol information for which PUSCH transmission is not allowed, and stores an instruction to transmit the PUSCH if the resources of the SSB transmission symbol and the resources of the PUSCH do not overlap.

[0013] Additionally, a base station of a communication system comprises: at least one transceiver; at least one processor connected to the at least one transceiver so as to be able to communicate with the at least one transceiver; and a memory connected to the at least one processor so as to be able to communicate with the at least one processor and capable of executing the at least one processor individually or in any combination thereof, wherein the base station: receives synchronization signal block (SSB) setting information to a terminal, receives downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal, transmits a second DCI to the terminal, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not permitted, and stores a command to receive the PUSCH when the resources of the SSB transmission symbol and the PUSCH do not overlap; and wherein the SSB transmission symbol is based on the SSB setting information and the information regarding the SSB symbol for which PUSCH transmission is not permitted.

[0014] The disclosed embodiments provide an apparatus and method capable of effectively providing services in a mobile communication system. In particular, in a system where SBFD is applied, a synchronization signal block can be effectively transmitted and received.

[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 drawing 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 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.

[0021] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 10 illustrates an optional connection procedure in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 11 is a drawing illustrating TDD settings and SBFD settings according to one embodiment of the present disclosure.

[0026] Figure 12 is a diagram illustrating the first example of receiving an SSB and setting an SBFD symbol.

[0027] Figure 13 is a diagram illustrating a second example of the case where an SSB is received and an SBFD symbol is set.

[0028] FIG. 14 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on all SSB settings.

[0029] FIG. 15 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on a single SSB setting without separate instructions.

[0030] FIG. 16 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on some SSB settings.

[0031] FIG. 17 is a flowchart illustrating an example of an operation in which a terminal selects some SSB settings based on the DCI format to determine whether to transmit PUSCH.

[0032] FIG. 18 is a drawing illustrating an example of the operation of a terminal according to the present disclosure.

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

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

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

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

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

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

[0039] Hereinafter, the 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. The 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, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Although embodiments of this disclosure are described below using a 5G system as an example, embodiments of this disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included therein. Furthermore, this disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, provided that it does not deviate significantly from the scope of this disclosure. The contents of this disclosure are applicable to FDD and TDD systems.

[0040] 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 the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that 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).

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

[0042] 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 may be 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.

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

[0044] 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 (UE (user equipment) or MS (mobile station)) 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 typically ensures that the data or control information of each user is distinguished by allocating and operating time-frequency resources to be transmitted for each user so that they do not overlap, that is, so that orthogonality is established.

[0045] 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 (URLC).

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

[0047] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for the connection of a large number of terminals within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT provides communication functions by attaching to various sensors and devices, a large number of terminals within a cell (e.g., 1,000,000 terminals / km²) 2 It must be able to support mMTC. In addition, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones where cells cannot cover, such as building basements, so they may require wider coverage compared to other services provided by the 5G communication system. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace the device's battery, a very long battery life of 10 to 15 years may be required.

[0048] 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 example, services supporting URLLC must satisfy air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5It has the following packet error rate requirements. 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.

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

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

[0051] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or a control channel is transmitted in a 5G system according to one embodiment of the present disclosure.

[0052] Referring to FIG. 1, the horizontal axis 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 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 resource block (resource block, RB, 104).

[0053] Figure 2 is a diagram illustrating an example of a slot structure used in a 5G wireless communication system.

[0054] Referring to FIG. 2, an example of a frame (200), subframe (201), and slot (202) structure is illustrated. 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 an 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, depending on the setting value μ for the subcarrier spacing, 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 as shown in Table 1 below.

[0055] μ 014101114202214404314808414160165143203261464064

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

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

[0058] 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 information such as that shown in Table 2 below for each bandwidth portion.

[0059] BWP ::= SEQUENCE {bwp-Id BWP-Id,(Bandwidth Identifier)locationAndBandwidth INTEGER (1..65536),(Bandwidth Location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(Subcarrier Spacing)cyclicPrefix ENUMERATED { extended}(Cyclical Prefix)}

[0060] 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).

[0061] According to some embodiments, prior to the radio resource control (RRC) connection, the terminal may receive a configuration for an initial bandwidth portion (Initial BWP) for initial connection from the base station via a master information block (MIB) transmitted over a physical broadcast channel (PBCH). 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 physical downlink control channel (PDCCH) can be transmitted to receive system information required for initial connection (which may correspond to remaining system information, RMSI, or system information block 1, SIB1). The control resource set and the search space configured by 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 Area #0, i.e., configuration information for Search Area #0. The terminal may regard the frequency area configured as Control Area #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. Through the configured initial bandwidth portion, the terminal can receive the PDSCH (physical downlink shared channel) through which the SIB is transmitted. In addition to receiving the SIB, the initial bandwidth portion may also be utilized for other system information (OSI), paging, and random access.

[0062] Next, we will explain the SS / PBCH block (synchronization signal / physical broadcast channel block) in 5G.

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

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

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

[0066] - PBCH: Provides essential system information required for the transmission and reception of the terminal's data and control channels. 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 transmitting system information, etc.

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

[0068] 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 setting for Control Area #0 (which may correspond to a control area with a control area index of 0). The terminal can perform monitoring of Control Area #0 by assuming that the selected SS / PBCH block and the DMRS (demodulation reference signal) transmitted from Control Area #0 are quasi-co-located. The terminal can receive system information using downlink control information transmitted from Control Area #0. The terminal can obtain configuration information related to RACH (random access channel) required for initial connection from the received system information. The terminal can transmit PRACH (physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving 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.

[0069] Next, downlink control information (DCI) in 5G systems will be explained in detail.

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

[0071] DCI can be transmitted via the PDCCH, a physical downlink control channel, 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.

[0072] For example, a DCI scheduling a PDSCH for system information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for a random access response (RAR) message can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for a paging message can be scrambled to P-RNTI. A DCI notifying a slot format indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying a 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).

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

[0074] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator - 0 or 1 bit

[0075] 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 information in Table 4 below.

[0076] - Carrier indicator - 0 or 3 bits - UL / SUL indicator - 0 or 1 bit - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 or 2 bits - Frequency domain resource assignment - For resource allocation type 0, bits- For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook (when a dynamic HARQ-ACK codebook is used with a single HARQ-ACK codebook).- 2nd downlink assignment index - 0 or 2 bits ○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks (when a dynamic HARQ-ACK codebook is used with two HARQ-ACK sub-codebooks); ○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission(if PUSCH transmission is not codebook-based);○ bits for codebook-based PUSCH transmission. - Precoding information and number of layers - up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association - 0 or 2 bits - beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0 or 1 bit

[0077] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the information in Table 5 below.

[0078] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator - 3 bits- PDSCH-to-HARQ feedback timing indicator - [3] bits

[0079] 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 information in Table 6 below.

[0080] - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger - 0, 1, or 2 bits - For transport block 1: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - For transport block 2: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports 4, 5, or 6 bits - Transmission configuration indication - 0 or 3 bits - SRS request - 2 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - CBG flushing out information - 0 or 1 bit - DMRS sequence initialization - 1 bit.

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

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

[0083] The control domain in the aforementioned 5G can be configured by a base station to a terminal through upper-layer signaling (e.g., system information, MIB, 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, it may include the information in Table 7.

[0084] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID'controlResourceSetId ControlResourceSetId,(Control Domain Identifier(Identity))frequencyDomainResources BIT STRING (SIZE (45)),(Frequency Axis Resource Allocation Info)duration INTEGER (1..maxCoReSetDuration),(Time Axis Resource Allocation Info)cce-REG-MappingType CHOICE {(CCE-to-REG Mapping Type)interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},(REG Bundle Size)precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},interleaverSize ENUMERATED {n2, n3, n6}(Interleaver Size)shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL(Interleaved Shift)},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,(QCL setting information)tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}

[0085] In Table 7, the tci-StatesPDCCH (simply named TCI (transmission configuration indication) state) configuration information may include information on one or more SS / PBCH block indices or CSI-RS (channel state information reference signal) indices that are in a quasi-co-located relationship with the DMRS transmitted in the corresponding control area.

[0086] Figure 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.

[0087] Referring to FIG. 5, the basic unit of time and frequency resources constituting the control channel can be called a REG (resource element group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (physical resource block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

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

[0089] 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 on a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces on all configured aggregation levels.

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

[0091] 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 information in Table 8 may be included.

[0092] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,(Search Space Identifier)controlResourceSetId ControlResourceSetId,(Control Area Identifier)monitoringSlotPeriodicityAndOffset CHOICE {(Monitoring Slot Level Period)sl1 NULL,sl2 INTEGER (0..1),sl4 INTEGER (0..3),sl5 INTEGER (0..4),sl8 INTEGER (0..7),sl10 INTEGER (0..9),sl16 INTEGER (0..15),sl20 INTEGER (0..19)} OPTIONAL,duration(Monitoring Length) INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,(슬롘 내 나이스 심보)nrofCandidates SEQUENCE {(집성 별보 PDCCH 이리군 수)aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}},searchSpaceType CHOICE {(தமாற்க்குக்க்கு திய்தை)-- Configures this search space as common search space (CSS) and DCI formats to monitor.common SEQUENCE {(공통이이국이)}ue-Specific SEQUENCE {(단말-특정이스국)-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},...}.

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

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

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

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

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

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

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

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

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

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

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

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

[0105] C-RNTI (cell RNTI): Used for terminal-specific PDSCH scheduling

[0106] TC-RNTI (temporary cell RNTI): Used for terminal-specific PDSCH scheduling

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

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

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

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

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

[0112] TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0113] TPC-PUCCH-RNTI (transmit power control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0114] TPC-SRS-RNTI (transmit power control for SRS RNTI): Used to instruct power control commands for the SRS (sounding reference signal).

[0115] The aforementioned specified DCI formats may follow definitions such as the examples in Table 9.

[0116] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0117] In a 5G system, the search space of aggregation level L in CORESET p and search space set s can be expressed as Equation 1 below.

[0118] [Mathematical Formula 1]

[0119]

[0120] - L: Lamination Level

[0121] - nCI : Carrier Index

[0122] - n CCE,p : Total number of CCEs existing in CORESET p

[0123] - : Slot Index

[0124] - : Number of PDCCH candidates at assembly level L

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

[0126] - l = 0, ..., L -1

[0127] - , Y p,-1 = nRNTI≠0, A p = 39827 for p mod 3 = 0, A p = 39829 for p mod 3 = 1, A p = 39839 for p mod 3 = 2, D= 65537

[0128] - n RNTI : Terminal identifier

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

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

[0131] In a 5G system, as multiple sets of search spaces can be configured with different parameters (e.g., the parameters in Table 9), 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.

[0132] FIG. 6 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.

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

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

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

[0136] The rate matching of the RB symbol level is as follows.

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

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

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

[0140] The rate matching of the RE level is as follows.

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

[0142] - 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 multicast-broadcast single-frequency network (mbsfn-SubframConfigList). Based on the aforementioned information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

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

[0144] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0145] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods that can be configured through the upper layer in an NR wireless communication system: type 0 (700), type 1 (705), and dynamic switch (710).

[0146] Referring to FIG. 7, if the terminal is configured to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that assigns PDSCH to the terminal is N RBGIt includes a bitmap consisting of bits. The conditions for this will be explained later. In this case, NRBG refers to the number of RBGs (resource block groups) determined as shown in Table 10 below according to the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0147] Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616

[0148] If the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that assign PDSCH to the terminal are It includes frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (720) and the length (725) of the frequency axis resources continuously allocated therefrom.

[0149] If the terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal include frequency axis resource allocation information consisting of bits of the larger value (735) of the payload (715) for setting resource type 0 and the payload (720, 725) for setting resource type 1. The conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency axis resource allocation information within the DCI, and if the bit has a value of '0', it indicates that resource type 0 is used, and if it has a value of '1', it indicates that resource type 1 is used.

[0150] The following describes a time-domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems).

[0151] The base station may set a table for time domain resource allocation information for downlink data channels and uplink data channels for the terminal using upper layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of a maximum of maxNrofDL-Allocations = 16 entries may be set, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 16 entries may be set. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information regarding the position and length of the start symbol in which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH or PUSCH. For example, information such as that shown in Table 11 or Table 12 below may be transmitted from the base station to the terminal.

[0152] PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PDSCH timing, slot units)mappingType ENUMERATED {typeA, typeB},(PDSCH mapping type)startSymbolAndLength INTEGER (0..127)(start symbol and length of PDSCH)}

[0153] PUSCH-TimeDomainResourceAllocation information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PUSCH timing, slots)mappingType ENUMERATED {typeA, typeB},(PUSCH mapping type)startSymbolAndLength INTEGER (0..127)(start symbol and length of PUSCH)}

[0154] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

[0155] FIG. 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0156] Referring to FIG. 8, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and control channel. PDSCH , μ PDCCH The time axis position of a PDSCH resource can be indicated according to the scheduling offset (K0) value, and the OFDM symbol start position (800) and length (805) within a slot that are dynamically indicated through DCI.

[0157] FIG. 9 is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0158] Referring to FIG. 9, when the subcarrier spacing of the data channel and the control channel is the same (900, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset by aligning with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different (905, μ PDSCH ≠μ PDCCH Since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset based on the subcarrier interval of the PDCCH and in accordance with a predetermined slot offset K0.

[0159] In describing the present disclosure below, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0160] - MIB

[0161] - SIB (system information block) or SIB

[0162] - RRC

[0163] - MAC (medium access control) CE (control element)

[0164] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.

[0165] - PDCCH

[0166] - DCI

[0167] - Terminal-specific (UE-specific) DCI

[0168] - Group Common DCI

[0169] - Common DCI

[0170] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

[0171] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)

[0172] - PUCCH

[0173] - UCI (uplink control information)

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

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

[0176] Generally, a terminal can establish a wireless link with a network through a random access procedure based on network synchronization and system information acquired during the cell search process. Random access may utilize contention-based or contention-free methods. A contention-based random access method may be used when the terminal performs cell selection and re-selection during the initial connection phase of a cell, for example, when moving from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access may be used to reset uplink synchronization when downlink data arrives, in the case of a handover, or for location measurement.

[0177] FIG. 10 is a drawing illustrating an example of a random access procedure in a wireless communication system according to one embodiment of the present disclosure.

[0178] Referring to FIG. 10, a contention-based random access procedure is illustrated as an example. Additionally, although not illustrated in FIG. 10, a base station may transmit a synchronization signal block as described in the embodiments above. In this case, the base station may periodically transmit the synchronization signal block using beam sweeping. For example, the base station may transmit a synchronization signal block containing PSS / SSS and PBCH signals using up to 64 different beams over a period of 5 ms, and multiple synchronization signal blocks may be transmitted using different beams. The terminal may detect (select) a synchronization signal block having an optimal beam direction (e.g., a beam direction where the received signal strength is strongest or greater than a predetermined threshold) and transmit a preamble using the PRACH resource associated with the detected synchronization signal block. For example, as a first step (1001) of the random access procedure, the terminal may transmit a random access preamble (or message 1) to the base station. A base station that receives the above random access preamble can measure the transmission delay value between the terminal and the base station and synchronize the uplink. Specifically, the terminal can transmit a random access preamble arbitrarily selected from a set of random access preambles given in advance by system information. Furthermore, the initial transmission power of the random access preamble can be determined based on the path loss between the base station and the terminal measured by the terminal. Additionally, the terminal can determine the transmission beam direction (or transmission beam or beam) of the random access preamble based on the synchronization signal block received from the base station and transmit the random access preamble by applying the determined transmission beam direction.

[0179] In the second step (1002), the base station may transmit a response to the detected random access attempt (random access response, RAR, or message 2 (message 2, msg2)) to the terminal. The base station may transmit an uplink transmission timing control command to the terminal based on the transmission delay value measured from the random access preamble received in the first step (1001). Additionally, the base station may transmit uplink resource and power control commands to be used by the terminal as scheduling information. The scheduling information may include control information for the terminal's uplink transmission beam. The RAR is transmitted via PDSCH and may include at least one of the following information.

[0180] - Random access preamble sequence index detected by the network (or base station)

[0181] - TC-RNTI (temporary cell radio network temporary identifier)

[0182] - Uplink scheduling grant

[0183] - Timing advance value

[0184] If the terminal does not receive RAR, which is scheduling information for message 3, from the base station for a predetermined period of time in the second step (1002), the first step (1001) can be performed again. If the first step is performed again, the terminal increases the transmission power of the random access preamble by a predetermined step (this is called power ramping), thereby increasing the probability of the base station receiving the random access preamble.

[0185] In the third step (1003), the terminal may transmit uplink information (or message 3) containing its terminal identifier (which may be referred to as the UE contention resolution identity; or, if the terminal already possesses a valid terminal identifier (C-RNTI) within the cell before the start of the random access procedure, that valid terminal identifier) ​​to the base station using the uplink resources allocated in the second step (1002). The PUSCH may be referred to as message 3 PUSCH (msg3 PUSCH). The transmission timing of the uplink data channel for transmitting message 3 may follow the uplink transmission timing control command received from the base station in the second step (1002). Additionally, the transmission power of the uplink data channel for transmitting message 3 may be determined by considering the power control command received from the base station in the second step (1002) and the power ramping value of the random access preamble. The uplink data channel for transmitting message 3 is where the terminal [performs] random access It may be the first uplink data signal transmitted by the terminal to the base station after the preamble transmission.

[0186] In step 4 (1004), if the base station determines that the terminal has performed random access without collision with other terminals, it may transmit a message (contention resolution message, CR message, or message 4) containing the identifier of the terminal that transmitted uplink data in step 3 (1003) to the terminal. In this regard, if multiple terminals receive the same TC-RNTI in step 2 (1002), the multiple terminals that received the same TC-RNTI each include their own terminal identifier (UE contention resolution identity) in message 3 in step 3 (1003) and transmit it to the base station, and the base station may transmit message 4 (CR message) containing the terminal identifier of one of the multiple terminals to resolve the contention. When a terminal receives a message 4 (CR message) containing its terminal identifier from a base station in step 4 (1004) (or transmits a message 3 (message 3) containing a terminal identifier (C-RNTI) in step 3 (1003), and receives terminal-specific control information containing a CRC based on the terminal identifier (C-RNTI) via PDCCH in step 4 (1004), it can determine that random access has succeeded. Therefore, among multiple terminals that have received the same TC-RNTI from a base station, a terminal that confirms that its terminal identifier is included in message 4 (CR message) can confirm that it has succeeded in the competition. Then, the terminal can transmit a HARQ-ACK / NACK indicating successful reception of the message 4 to the base station through an uplink control channel.

[0187] If the data transmitted by the terminal in the third stage (1003) collides with the data of another terminal and the base station fails to receive the data signal from the terminal, the base station may not perform further data transmission to the terminal. Accordingly, if the terminal fails to receive the data transmitted from the base station in the fourth stage (1004) for a certain period of time, it is determined that the random access procedure has failed, and the process may be restarted from the first stage (1001).

[0188] As described above, in the first step (1001) of the random access process, the terminal can transmit a random access preamble onto PRACH. Each cell has 64 available preamble sequences, and depending on the transmission format, 4 long preamble formats and 9 short preamble formats may be used. The terminal generates 64 preamble sequences using a root sequence index and a cyclic shift value signaled as system information, and can randomly select one sequence to use as a preamble.

[0189] A base station may provide a terminal with configuration information for random access resources, such as control information (or configuration information) indicating time-frequency resources that can be used for PRACH, using at least one of SIB, upper layer signaling (RRC information), or DCI. Frequency resources for PRACH transmission may indicate to the terminal the starting RB point of transmission, and the number of RBs used may be determined according to the preamble format transmitted via PRACH and the applied subcarrier interval. Time resources for PRACH transmission may be provided through a PRACH configuration index (0 to 255), such as a pre-set PRACH setting period, a subframe index containing a PRACH transmission time (PRACH occasion, which may be used interchangeably with transmission time), a start symbol, and the number of PRACH transmission times within a slot, as shown in Table 13 below. The terminal determines the validity of the PRACH transmission timestamps indicated in the PRACH configuration index and determines only the valid PRACH transmission timestamps as PRACH transmission timestamps capable of transmitting a random access preamble. Through the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the terminal, the terminal identifies the time and frequency resources for transmitting the random access preamble and can transmit the selected sequence as a preamble to the base station.

[0190] PRACHConfigurationIndexPreamble formatn f mod x=ySubframe numberStarting symbolNumber of PRACH slots within a subframe , number of time-domain PRACH occasions within a PRACH slot ,PRACH durationxy0016110--01016140--02016170--03016190--0408110--0508140--0608170--0708190--0804110--0904140--01004170--0.................................1 04A1101,4,70262................................251C2102,70226252C2101,4,7022 6253C2100,2,4,6,80226254C2100,1,2,3,4,5,6,7,8,90226255C2101,3,5,7,90226

[0191] Meanwhile, 3GPP introduced SBFD (subband non-overlapping full duplex) as a new NR-based duplex method. SBFD is a technology that utilizes a portion of downlink resources as uplink resources in the TDD spectrum of frequencies below 6 GHz or above 6 GHz, thereby allowing the base station to receive uplink transmissions from the terminals to expand the uplink coverage of the terminals by the amount of increased uplink resources, and can reduce feedback delay by receiving feedback on downlink transmissions from the terminals in the expanded uplink resources.

[0192] In the present disclosure, a terminal capable of receiving information from a base station regarding SBFD support and performing uplink transmission on a portion of downlink resources may be referred to as an SBFD terminal (SBFD-capable UE) for convenience. The SBFD method is defined in the standard, and the following method may be considered for the SBFD terminal to determine whether the SBFD is supported in a specific cell (or frequency, frequency band).

[0193] In the first method, in addition to the existing frame structure types of unpaired spectrum (or TDD) or paired spectrum (or FDD), another frame structure type (e.g., frame structure type 2) may be introduced to define the above SBFD. The above frame structure type 2 may be defined as being supported at the specific frequency or frequency band, or the base station may indicate to the terminal whether SBFD is supported as system information. The SBFD terminal may receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0194] In a second method, whether the SBFD is additionally supported at a specific frequency or frequency band of the existing unpaired spectrum (or TDD) may be indicated without defining a new frame structure type. In the second method, whether the SBFD is additionally supported at a specific frequency or frequency band of the existing unpaired spectrum may be defined, or a base station may indicate to the terminal whether the SBFD is supported as system information. The SBFD terminal may receive system information including whether the SBFD is supported and determine whether the SBFD is supported in the specific cell (or frequency, frequency band).

[0195] In the first and second methods above, the information regarding whether SBFD is supported may be information indicating whether SBFD is supported indirectly by additionally setting a part of the downlink resource as an uplink resource in addition to the setting of TDD UL-DL resource configuration information indicating the downlink slot (or symbol) resource and uplink slot (or symbol) resource of TDD (e.g., SBFD resource configuration information in FIG. 11 described later), or it may be information indicating whether SBFD is supported directly.

[0196] In the present disclosure, the SBFD terminal may obtain cell synchronization by receiving a synchronization signal block during an initial cell connection for connecting to a cell (or base station). The process of obtaining cell synchronization may be the same for the SBFD terminal and the existing TDD terminal. Subsequently, the SBFD terminal may determine whether the cell supports SBFD through MIB acquisition, SIB acquisition, or a random access process.

[0197] The system information for transmitting information regarding SBFD support may be system information transmitted separately, distinguished from system information for a terminal supporting a different version of the standard within the cell (e.g., an existing TDD terminal). The SBFD terminal may determine whether SBFD is supported by acquiring all or part of the system information transmitted separately from the system information for the existing TDD terminal. If the SBFD terminal acquires only the system information for the existing TDD terminal or acquires system information regarding SBFD non-support, the cell (or base station) may determine that it supports only TDD.

[0198] If the information regarding SBFD support is included in the system information for a terminal that supports a different version of the standard (e.g., an existing TDD terminal), the information regarding SBFD support may be inserted at the very end so as not to affect the acquisition of system information for the existing TDD terminal. If the SBFD terminal fails to acquire the information regarding SBFD support inserted at the very end, or acquires information that SBFD is not supported, the SBFD terminal may determine that the cell (or base station) supports only TDD.

[0199] Alternatively, if the information regarding SBFD support is included in the system information for a terminal supporting a different version of the specification (e.g., an existing TDD terminal), the information regarding SBFD support may be transmitted to a separate PDSCH so as not to affect the acquisition of system information for the existing TDD terminal. That is, a terminal that does not support SBFD may receive a first SIB (or SIB1) containing existing TDD-related system information from the first PDSCH. A terminal that supports SBFD may receive a first SIB (or SIB) containing existing TDD-related system information from the first PDSCH and may receive a second SIB containing SBFD-related system information from the second PDSCH. Here, the first PDSCH and the second PDSCH may be scheduled as the first PDCCH and the second PDCCH, and the CRCs of the first PDCCH and the second PDCCH may be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if it is not obtained (i.e., if the system information of the first PDSCH does not include information about the search space), the terminal can receive the second PDCCH in the same search space as the search space of the first PDCCH.

[0200] As described above, if the SBFD terminal determines that the cell (or base station) supports only TDD, the SBFD terminal can perform random access procedures and transmit / receive data / control signals in the same way as an existing TDD terminal.

[0201] A base station may configure separate random access resources for each of the existing TDD terminals or SBFD terminals (e.g., an SBFD terminal supporting duplex communication and an SBFD terminal supporting half-duplex communication), and transmit configuration information for said random access resources (control information or configuration information indicating time-frequency resources that can be used for PRACH) to the SBFD terminals through system information. The system information for transmitting information about said random access resources may be system information transmitted separately, distinct from system information for terminals supporting different versions of specifications within the cell (e.g., existing TDD terminals).

[0202] The base station may set up random access resources for TDD terminals and additionally set up separate random access resources for SBFD terminals. Here, the SBFD terminal may use the random access resources for TDD terminals, or the SBFD terminal may not use the random access resources for TDD terminals. In the latter case, the SBFD terminal can always use only the separate random access resources for SBFD terminals.

[0203] An SBFD terminal may be instructed by the base station on whether it can use random access resources for a TDD terminal. This may be indicated by being included in the SIB. That is, a separate random access resource for the SBFD terminal may be configured in the SIB, and along with said configuration, the availability of random access resources for the TDD terminal may be indicated. This may be indicated by 1 bit. If the 1 bit is '0' (or FALSE), the SBFD terminal cannot use random access resources for the TDD terminal. If the 1 bit is '1' (or TRUE), the SBFD terminal can use random access resources for the TDD terminal.

[0204] A base station can determine the type of terminal attempting to connect to a cell based on the random access resources used by the terminal. For example, an SBFD terminal may transmit a PRACH through a separate random access resource for the SBFD terminal, and upon receiving the PRACH, the base station may determine that the SBFD terminal is attempting to connect to a cell. For example, a TDD terminal may transmit a PRACH through a random access resource for the TDD terminal, and upon receiving the PRACH, the base station may determine that the TDD terminal is attempting to connect to a cell. For reference, if it is permitted for an SBFD terminal to transmit a PRACH through the random access resource of a TDD terminal, the base station may be ambiguous as to whether the type of terminal transmitting the PRACH is a TDD terminal or an SBFD terminal. In this case, the base station may always assume that the type of the terminal is a TDD terminal.

[0205] When a base station determines that a terminal is an SBFD terminal, the base station may schedule msg2, msg3, msg4, etc. to the terminal based on uplink subband settings. That is, when the base station schedules the reception of msg2 and msg4 to the terminal, it may schedule the msg2 and msg4 so that they are not received in the uplink subband (when the terminal receives a PDSCH including msg2 and msg4, the PDSCH is received in a frequency resource excluding the uplink subband). When the base station schedules the msg3 PUSCH to the terminal, it may schedule the msg3 PUSCH so that it is transmitted within the uplink subband.

[0206] When a base station determines that a terminal is a TDD terminal, the base station cannot use uplink subband settings when scheduling msg2, msg3, and msg4 to the terminal. That is, even if an uplink subband is set in a downlink symbol or a flexible symbol, the base station can assume that the terminal cannot obtain the uplink subband setting information. When the base station schedules msg3 PUSCH to the terminal, msg3 PUSCH can be scheduled in a flexible symbol or an uplink symbol. In other words, msg3 PUSCH cannot be scheduled in an uplink subband.

[0207] Alternatively, the base station may not set a separate random access resource for the SBFD terminal, but may set a common random access resource for all terminals within the cell. In this case, configuration information regarding the random access resource may be transmitted to all terminals within the cell via system information, and the SBFD terminal that receives the system information may perform random access from the random access resource. Afterward, the SBFD terminal may complete the random access process and proceed to an RRC connection mode to transmit and receive data with the cell. After the RRC connection mode, the SBFD terminal may receive a higher-layer signal or physical signal from the base station that determines that a portion of the frequency resources of the downlink time resources is set as an uplink resource, and may transmit an uplink signal from the uplink resource as an SBFD operation.

[0208] When the SBFD terminal determines that the cell supports SBFD, it can notify the base station that the terminal attempting to connect is an SBFD terminal by transmitting capability information to the base station that includes at least one of the following: whether the terminal supports SBFD, whether it supports full-duplex or half-duplex communication, and the number of transmitting or receiving antennas it has (or supports). Alternatively, if half-duplex communication support is a mandatory implementation for the SBFD terminal, the half-duplex communication support status may be omitted from the capability information. The SBFD terminal's report regarding the capability information may be reported to the base station through a random access process, after the random access process is completed, or after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

[0209] The above SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at a time like an existing TDD terminal, or it may support full-duplex communication, which performs both uplink transmission and downlink reception at a time. Accordingly, whether the above half-duplex or full-duplex communication is supported can be reported to the base station by the SBFD terminal through a capability report, and after the report, the base station may set whether the SBFD terminal will transmit and receive using half-duplex communication or full-duplex communication. When the SBFD terminal reports the capability for half-duplex communication to the base station, a switching gap to change RF between transmission and reception may be required when operating in FDD or TDD, as a duplexer generally does not exist.

[0210] Meanwhile, a method is required for an SBFD terminal to determine the validity of a PRACH transmission time point through a PRACH configuration index and SBFD settings for performing PRACH transmission, to perform PRACH transmission through the PRACH transmission time point determined to be valid, and a procedure performed by the SBFD terminal when the valid PRACH transmission time point overlaps with downlink reception. In at least one embodiment of the present disclosure, a method for an SBFD terminal to perform PRACH transmission and an apparatus for performing said method are proposed.

[0211] FIG. 11 is a diagram illustrating an example in which an SBFD is operated in the TDD band of a wireless communication system according to one embodiment of the present disclosure.

[0212] Figure 11 (a) illustrates a case where TDD is operated in a specific frequency band. In a cell operating the TDD, the base station can transmit and receive signals containing data / control information in a downlink slot (or symbol), an uplink slot (or symbol) (1101), and a flexible slot (or symbol) based on the configuration of TDD UL-DL resource configuration information indicating the downlink slot (or symbol) resource and the uplink slot (or symbol) resource of the existing TDD terminal or SBFD terminal.

[0213] In Figure 11, it can be assumed that the DDDSU slot format is configured according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols, and 'S' is a slot that is neither 'D' nor 'U', that is, a slot containing downlink symbols, uplink symbols, or flexible symbols. For convenience, it can be assumed here that S consists of 12 downlink symbols and 2 flexible symbols. Furthermore, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is assumed to be 5 slots (5ms for 15kHz SCS, 2.5ms for 30kHz SCS, etc.).

[0214] Next, Figures 11 (b) to (d) illustrate cases where SBFD is operated together with TDD in a specific frequency band.

[0215] Referring to FIG. 11(b), the terminal may be configured to set a portion of the cell's frequency band as a frequency band (1110) capable of uplink transmission. This band may be called an uplink subband (UL subband). The uplink subband (UL subband) may be applied to all symbols in all slots. The terminal may transmit an uplink channel or signal scheduled to an uplink slot (or symbol) (1111) and all symbols (1112) within the subband (UL subband). However, the terminal may not transmit an uplink channel or signal in a band other than the subband (UL subband) in a downlink slot (or symbol) and a flexible slot (or symbol).

[0216] Referring to FIG. 11(c), the terminal may be configured to set a portion of the cell's frequency band as a frequency band (1120) capable of uplink transmission, and may be configured to set a time range in which the frequency band is activated. Here, this frequency band may be referred to as the uplink subband (UL subband). In FIG. 11(c), the uplink subband (UL subband) is deactivated in the first slot, and the uplink subband (UL subband) may be activated in the remaining slots. Accordingly, the terminal may transmit an uplink channel or signal in the uplink slot (or symbol) (1121) and the uplink subband (UL subband) (1122) of the remaining slots. Therefore, although the uplink subband (UL subband) is activated on a slot basis here, the activation status may be configured on a symbol basis.

[0217] Referring to FIG. 11 (d), the terminal may be configured with a time-frequency resource capable of uplink transmission. The terminal may be configured with one or more time-frequency resources capable of uplink transmission. For example, a portion of the frequency band (1132) of the first slot and the second slot may be configured with a time-frequency resource capable of uplink transmission. Additionally, a portion of the frequency band (1133) of the third slot and a portion of the frequency band (1134) of the fourth slot may be configured with a time-frequency resource capable of uplink transmission. The terminal may transmit an uplink channel or signal in the uplink slot (or symbol) (1131), a portion of the frequency band (1132) of the first slot and the second slot, a portion of the frequency band (1133) of the third slot, and a portion of the frequency band (1134) of the fourth slot.

[0218] In the following description, the time-frequency resources capable of uplink transmission in downlink symbols or flexible symbols may be referred to as SBFD resources / UL subbands.

[0219] The present disclosure discloses a method for a terminal to determine an SBFD symbol. The terminal may receive a plurality of configuration information through an upper layer signal from a base station. For example, the plurality of configuration information may include the following.

[0220] As the first upper layer configuration information, TDD DL / UL configuration information may be included. The TDD DL / UL configuration information may include up to two TDD patterns. If the period of the TDD DL / UL configuration is P (ms), the first TDD pattern may include a base station-perspective symbol type for the preceding P1 (ms) within P (ms), and the second TDD pattern may include a base station-perspective symbol type for the subsequent P2 (ms) within the period P (ms). That is, P can be represented as P1+P2. Each TDD pattern may include downlink symbols, uplink symbols, or flexible symbols. The TDD DL / UL configuration may be a configuration applied commonly to the cell. The TDD DL / UL configuration may be included in SIB1.

[0221] As second upper layer configuration information, SSB configuration information may be included. The SSB configuration information may include an SSB period. The SSB period may have one of the values ​​5ms, 10ms, 20ms, 40ms, 80ms, or 160ms. If the terminal does not receive the above SSB configuration information (e.g., in the case of an initial cell connection terminal), the SSB may be received by assuming the SSB period is a specific value (e.g., 20ms). An SSB block consists of four consecutive symbols, and the symbols included in the SSB block may be called SSB symbols. The position of the first symbol of the SSB block within a 5ms-length half frame may be as shown in Table 14. Here, index 0 may correspond to the first symbol of the first slot of the half frame. The terminal may not expect the SSB symbols determined according to the above configuration to be uplink symbols according to the TDD DL / UL configuration. That is, the terminal can expect the SSB symbols to be downlink symbols or flexible symbols according to the TDD DL / UL setting. The above SSB setting may be a setting applied commonly to the cell. The above SSB setting may be included in SIB1. The above SSB setting may be a cell-defining SSB setting. The above SSB setting may be a setting for SSBs including PBCH.

[0222] - Case A - 15 kHz SCS: the first symbols of the candidate SS / PBCH blocks have indexes of . For carrier frequencies smaller than or equal to 3 GHz, n=0, 1. For carrier frequencies within FR1 larger than 3 GHz, n=0, 1, 2, 3.- Case B - 30 kHz SCS: the first symbols of the candidate SS / PBCH blocks have indexes . For carrier frequencies smaller than or equal to 3 GHz, n=0. For carrier frequencies within FR1 larger than 3 GHz, n=0, 1.- Case C - 30 kHz SCS: the first symbols of the candidate SS / PBCH blocks have indexes .○ For paired spectrum operation● For carrier frequencies smaller than or equal to 3 GHz, n=0, 1. For carrier frequencies within FR1 larger than 3 GHz, n=0, 1, 2, 3.○ For unpaired spectrum operation● For carrier frequencies smaller than 1.88 GHz, n=0, 1. For carrier frequencies within FR1 equal to or larger than 1.88 GHz, n=0, 1, 2, 3.- Case D - 120 kHz SCS: the first symbols of the candidate SS / PBCH blocks have indexes . For carrier frequencies within FR2, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.- Case E - 240 kHz SCS: the first symbols of the candidate SS / PBCH blocks have indexes . For carrier frequencies within FR2, n=0, 1, 2, 3, 5, 6, 7, 8.

[0223] As third upper layer configuration information, SBFD configuration information may be included. The SBFD configuration information may configure SBFD symbols in downlink symbols or flexible symbols configured in the TDD DL / UL configuration. If the TDD DL / UL configuration has a single TDD pattern, the SBFD configuration may include an index for the starting symbol and an index for the last symbol (or the index for the starting symbol and the number of consecutive symbols) among the symbols within the single TDD pattern. And the period of the SBFD configuration may be the same as the period (P) of the TDD DL / UL configuration. That is, the SBFD symbols determined by the SBFD configuration may be repeated for each single TDD pattern.

[0224] When the TDD DL / UL setting has two TDD patterns, the SBFD setting may include an index for a starting symbol and an index for an ending symbol (or the number of consecutive symbols with the index for the starting symbol) among the symbols in the first TDD pattern, and an index for a starting symbol and an index for an ending symbol (or the number of consecutive symbols with the index for the starting symbol) among the symbols in the second TDD pattern. The period of the SBFD setting may be the same as the period of the TDD DL / UL setting (P=P1+P2). Here, P1 may be the period of the first TDD pattern, and P2 may be the period of the second TDD pattern.

[0225] A downlink subband and an uplink subband may be configured in the SBFD symbol determined by the SBFD configuration. The terminal can perform downlink reception in the downlink subband but cannot perform uplink transmission, and can perform uplink transmission in the uplink subband but cannot perform downlink reception.

[0226] Depending on the SBFD setting, symbols that are not SBFD symbols may be called non-SBFD symbols. Non-SBFD symbols may include downlink symbols, flexible symbols, and uplink symbols depending on the TDD DL / UL setting. In downlink symbols, the terminal can perform downlink reception in all frequency bands but cannot perform uplink transmission, and in uplink symbols, the terminal can perform uplink transmission in all frequency bands but cannot perform downlink reception. In flexible symbols, the terminal can perform either downlink reception or uplink transmission.

[0227] The SSB symbol and SBFD symbol determined by the terminal may overlap. In this case, the terminal must receive the SSB at the SBFD symbol. According to the SBFD operation, since the terminal still supports only Half-duplex mode, the terminal cannot perform uplink transmission while receiving the SSB. Therefore, the terminal cannot transmit an uplink channel or signal in the UL subband to receive the SSB at the said symbol. Alternatively, the terminal may always determine the SSB symbol as a non-SBFD symbol and receive a downlink channel or signal in all PRBs.

[0228] FIGS. 12 and 13 illustrate an example of frame structures and an SSB reception operation of a terminal according to an embodiment of the present disclosure. In FIGS. 12 and 13, a frame (SF#0) with a system frame index of 0 and a frame (SF#1) with a system frame index of 1 are illustrated. The subcarrier spacing is 30 kHz, and one frame may contain 20 slots.

[0229] In an example of FIGS. 12 and 13, according to the first upper layer configuration information, a TDD pattern (DDDSU) may be configured in each of the five slots of the terminal. Among the five slots, the first three slots may include downlink symbols, the fourth slot may include 12 downlink symbols and 2 flexible symbols, and the fifth slot may include uplink symbols.

[0230] According to the second upper layer configuration information, the terminal can receive SSB at a 20ms interval. Here, the half frame (5ms) in which the SSB is transmitted may be the third 5ms interval out of 20ms. Also, only 4 of the 8 SSB blocks may be used. More specifically, SSB#0 may be received at symbols {2, 3, 4, 5} in slot 10, SSB#1 may be received at symbols {8, 9, 10, 11}, SSB#2 may be received at symbols {2, 3, 4, 5} in slot 13, and SSB#3 may be received at symbols {8, 9, 10, 11}.

[0231] According to the third upper layer configuration information, the terminal can set all symbols in the first four slots of the five slots where the TDD pattern is set as SBFD symbols. That is, downlink subbands and uplink subbands can be set for all symbols in the first four slots.

[0232] The symbols for which SSB reception is configured (symbols 2, 3, 4, 5, 8, 9, 10, and 11 in slot 10 and symbols 2, 3, 4, 5, 8, 9, 10, and 11 in slot 12) may be configured as SBFD symbols. The terminal must receive SSB from the said symbols. That is, the terminal cannot transmit the uplink channel or signal.

[0233] FIG. 12 illustrates a first example of a case where SSB reception and SBFD symbols are set. In the first method, the terminal may receive a downlink channel or signal in the downlink subband of the SBFD symbol where SSB reception is set. However, the terminal may not transmit an uplink channel or signal in the uplink subband of the SBFD symbol where SSB reception is set. Referring to FIG. 12, in the symbols where SSB reception is set (symbols 2, 3, 4, 5, 8, 9, 10, and 11 of slot 10 and symbols 2, 3, 4, 5, 8, 9, 10, and 11 of slot 12), the terminal may only be able to receive a downlink channel or signal in the downlink subband. That is, if an uplink channel or signal overlaps with the symbol, the uplink channel or signal may not be transmitted in the symbol. For example, if the channel is PUSCH or PUCCH, the terminal may cancel / skip the transmission of PUCCH and PUSCH. For example, if the channel is SRS, the terminal may cancel / skip the transmission of the SRS corresponding to the symbol. The SRS may still be transmitted in other symbols.

[0234] FIG. 13 illustrates a second example of the case where SSB reception and SBFD symbols are set. In the second method, the terminal may not apply the SBFD settings set according to the third upper layer setting information to the slot where SSB reception is set. That is, all symbols in the slot where SSB reception is set may be determined to be non-SBFD symbols. According to FIG. 13, the slots where SSB reception is set (slot 10 and slot 12) may contain only non-SBFD symbols. That is, the SBFD settings set according to the third upper layer setting information may not be applied.

[0235] With the fourth upper layer configuration information, the terminal can receive instructions from the base station regarding the terminal's transmission and reception direction in the SBFD symbol. For example, if the terminal is instructed to transmit and receive in the SBFD symbol as a downlink, the terminal can receive downlink signals in the downlink subband and cannot transmit uplink signals in the uplink subband. If the terminal is instructed to transmit and receive in the SBFD symbol as an uplink, the terminal cannot receive downlink signals in the downlink subband and can transmit uplink signals in the uplink subband. The transmission and reception direction of the terminal according to the fourth upper layer configuration information may have the same period as the TDD pattern according to the first upper layer configuration information. That is, if the TDD pattern has a period of 5 slots, the terminal's reception direction instruction may also be applied repeatedly with the said 5 slot periods.

[0236] When an SBFD symbol overlaps with an SSB, the terminal can interpret the fourth upper layer configuration information based on the following method.

[0237] In the first method, if the SBFD symbol overlaps with the SSB, the terminal may ignore instructions according to the fourth upper layer configuration information. For example, even if the terminal's transmission and reception direction for the symbol is set as an uplink according to the fourth upper layer configuration information, the terminal may ignore the indicated transmission and reception direction and receive a downlink from the symbol. That is, the terminal's transmission and reception direction according to the fourth upper layer configuration information may be overridden as a downlink due to the SSB.

[0238] In the second method, if the SBFD symbol overlaps with the SSB, the terminal may apply instructions according to the fourth upper layer configuration information. For example, if the terminal's transmission and reception direction for the symbol is set to uplink according to the fourth upper layer configuration information, the terminal may not perform downlink reception on the symbol. Additionally, since the symbol is an SSB symbol, the terminal may not perform uplink transmission. That is, the terminal may not perform uplink transmission and downlink reception on the symbol. If the terminal's transmission and reception direction for the symbol is set to downlink according to the fourth upper layer configuration information, the terminal may perform downlink reception on the symbol.

[0239] In the third method, if an SBFD symbol overlaps with an SSB, the terminal may prioritize instructions according to the fourth upper layer configuration information. For example, if the terminal's transmission and reception direction for the symbol is set to uplink according to the fourth upper layer configuration information, the terminal may not perform downlink reception on the symbol. Furthermore, even if the symbol is an SSB symbol, uplink transmission may be performed. That is, even if it is an SSB symbol, uplink transmission may be performed in the uplink subband. If the terminal's transmission and reception direction for the symbol is set to downlink according to the fourth upper layer configuration information, the terminal may perform downlink reception on the symbol.

[0240] The terminal may selectively perform the first to third methods according to the type of the SSB setting. For example, if the SSB setting is a CD (cell-defining)-SSB, the terminal may perform transmission and reception based on the first method. This is because the reception of the CD-SSB can be prioritized to obtain downlink synchronization information and perform radio link monitoring. If the type of the SSB setting is an SSB for measuring another cell, the terminal may perform transmission and reception based on the second or third methods. That is, since the terminal can operate even without receiving the SSB for measuring another cell, the terminal's transmission and reception direction according to the fourth upper layer setting information may be applied (second method) or the fourth upper layer setting information may be prioritized (third method). The SSB for measuring another cell may be an SSB having a physical cell ID different from the SSB of the serving cell.

[0241] In the example described above, the terminal may receive multiple SSB settings. Additionally, the base station may provide SSB settings specifically for the terminal. Therefore, there may be cases where the terminal does not receive information regarding all SSB settings used by the network. Consequently, although the network uses a symbol to transmit an SSB, the terminal may not be aware that said symbol is used for SSB transmission.

[0242] As an example of resolving this, the base station may provide the terminal with all SSB settings used in the network. This can be transmitted as a higher-layer signal. The terminal may determine whether to transmit an uplink based on all or some of the SSB settings.

[0243] FIG. 14 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on all SSB settings.

[0244] Referring to FIG. 14, a terminal can receive multiple SSB settings from a base station (1400). The multiple SSB settings may include CD-SSB, NCD-SSB, or SSB settings for measuring other cells. The terminal can determine whether to transmit a PUSCH based on all the received SSBs (1410). The terminal can determine that uplink transmission is impossible for all SSB symbols corresponding to the received SSB settings. Transmission of a PUSCH that overlaps with all SSB symbols may be canceled.

[0245] According to the method described above, the terminal may not require separate signaling. However, since not all SSB symbols can always be used for uplink transmission, the terminal's uplink transmission opportunities may be reduced.

[0246] FIG. 15 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on a single SSB setting without separate instructions.

[0247] Referring to FIG. 15, a terminal can receive multiple SSB settings from a base station (1500). The multiple SSB settings may include CD-SSB, NCD-SSB, or SSB settings for measuring other cells. The terminal can select one of the received SSB settings (1510). Here, one SSB may be selected based on the period. For example, the SSB setting with the shortest period may be selected. Here, one SSB may be selected based on the type of SSB. For example, CD-SSB may be selected. The terminal can determine whether to transmit PUSCH based on the selected SSB setting (1520). The terminal may determine that uplink transmission is impossible for all SSB symbols corresponding to the selected SSB settings. And the transmission of PUSCH that overlaps with the SSB symbol may be canceled.

[0248] According to the method described above, the terminal can determine whether to transmit a PUSCH based on a single SSB setting. Here, the single SSB setting may be the SSB with the shortest period on the time axis. This can guarantee the opportunity for the terminal to receive the SSB. However, the base station may not always use the SSB with the shortest period. For example, a base station in normal mode uses a short-period SSB, while a base station in low-power mode may use a long-period SSB. Therefore, if the determination of whether to transmit an uplink signal is based solely on the short-period SSB, the opportunity for uplink transmission may be reduced.

[0249] According to the method described above, the terminal can determine whether to transmit PUSCH based on a single SSB setting. Here, the single SSB setting may be CD-SSB. This can guarantee the opportunity for the terminal to receive CD-SSB. However, since the base station can transmit various SSBs other than CD-SSB, such as NCD-SSB, if the terminal transmits an uplink signal at the said SSB symbol, the SSB reception performance may be degraded due to interference between terminals.

[0250] Each base station can change its SSB settings. For example, a base station operating in low-power mode may send fewer SSBs. This may be achieved by increasing the SSB period or reducing the number of SSBs within the same period. Additionally, a base station operating in low-power mode may transmit SSBs based on an SSB transmission request from a terminal. This can be referred to as on-demand SSB (OD-SSB). The base station may not transmit SSBs if there is no SSB transmission request from the terminal, but may transmit SSBs only within a specific time interval if there is a transmission request. Therefore, while the base station provides all SSB settings used by the network to the upper layer, the actual location of the SSB used by the base station may differ. Consequently, the terminal may be ambiguously concerned with which symbol the SSB is being transmitted. Methods to resolve this are disclosed.

[0251] FIG. 16 is a flowchart illustrating an example of an operation in which a terminal determines whether to transmit PUSCH based on some SSB settings.

[0252] Referring to FIG. 16, a terminal may receive multiple SSB settings from a base station (1600). The multiple SSB settings may include CD-SSB, NCD-SSB, or SSB settings for measuring other cells. The terminal may be instructed to some of the SSB settings among all the received SSB settings (1610). The instruction may be given in MAC-CE signal or DCI format. The terminal may determine whether to transmit PUSCH based on the instructed SSB settings (1620). The terminal may determine that uplink transmission is impossible for all SSB symbols corresponding to the instructed SSB settings. And the transmission of PUSCH that overlaps with the SSB symbols may be canceled.

[0253] Here, if the instruction is in DCI format (or DCI), the terminal can dynamically determine the SSB settings and the location of the SSB symbols. Therefore, even if the base station changes the SSB transmission method based on various SSB settings, the terminal can determine which symbol was used as the SSB. By not indicating some SSBs through the DCI format, the base station can cause the terminal to transmit PUSCH at symbols that overlap with the said SSB. In other words, if the terminal does not need to receive an SSB or if there is no issue with the reception performance of other terminals' SSBs, the base station can cause the terminal to perform uplink transmission by not indicating it in the DCI format, even if it is an SSB symbol.

[0254] FIG. 17 is a flowchart illustrating an example of an operation in which a terminal selects some SSB settings based on the DCI format to determine whether to transmit PUSCH.

[0255] Referring to FIG. 17, the terminal can determine the SSB setting and the location of the SSB symbol specified from the DCI format (1700). The terminal can determine whether to transmit PUSCH based on the specified SSB setting (1710). Here, if the PUSCH scheduled by the DCI format overlaps with the specified SSB symbol, the transmission of PUSCH may be canceled or postponed. If the PUSCH scheduled by the DCI format does not overlap with the specified SSB symbol, the PUSCH may be transmitted.

[0256] FIG. 18 is a drawing illustrating an example of the operation of a terminal according to the present disclosure.

[0257] Referring to FIG. 18, the terminal may receive a DCI format for scheduling PUSCH. The DCI format may be a DCI format for scheduling repeated transmission of PUSCH, multiple PUSCH transmission, CG (configured grant) PUSCH activation, or TBoMS (transport block over multiple slots) transmission. The symbols for which PUSCH is transmitted may be determined according to the DCI format. For example, the DCI format may be received in slot 2, and PUSCH may be transmitted in slots 3, 4, 6, 7, and 8.

[0258] The terminal can determine the SSB settings and the symbol positions of the SSBs included in the settings based on the DCI format. If PUSCH overlaps with the symbols of the SSBs, the terminal can cancel the transmission of the PUSCH. For example, the DCI format may indicate the SSB (SSB#2) of slot 6 and the SSB (SSB#4) of slot 7 among the eight SSBs of slots 5, 6, 7, and 8. The remaining six SSBs (SSB#0, SSB#1, SSB#3, SSB#5, SSB#6, SSB#7) may not be indicated. The SSBs (SSB#2, SSB#4) indicated in slots 6 and 7 and the PUSCH may overlap in the time domain, and therefore, the PUSCH may not be transmitted in slots 6 and 7.

[0259] In the above-described embodiment, the terminal described an SSB indication method in DCI format. More specific embodiments are described below.

[0260] The following describes a method for indicating an SSB through a DCI format. According to one embodiment of the present disclosure, a terminal may be indicated by the location of an SSB symbol from a DCI format. The DCI format may be a DCI format for scheduling a PUSCH. When transmitting a PUSCH scheduled by the DCI format, the terminal may consider the location of the SSB symbol.

[0261] An SSB indication field may be included to indicate the location of an SSB symbol in the DCI format. The field may be 1 bit or composed of multiple bits.

[0262] If the above field is 1 bit and the value of the field is '0', the terminal may indicate through an upper layer signal that the locations of potential SSB symbols are not actually used. That is, the terminal may not consider the SSB symbols when transmitting PUSCH. If the above field is 1 bit and the value of the field is '1', the use of SSB symbols set by the upper layer (e.g., RRC signal) may be indicated. That is, the locations of potential SSB symbols may be set through an upper layer signal, and it may be indicated that the SSB symbols cannot be used for PUSCH transmission. That is, the terminal must consider the SSB symbols when transmitting PUSCH.

[0263] The terminal can receive from the base station an association relationship between the aforementioned SSB symbols and the value 1.

[0264] If the above field is 1 bit and the value of the above field is '0', the use of a first set of SSB symbols set by an upper layer (e.g., an RRC signal) may be indicated. That is, the location of potential first SSB symbols and the location of second symbols may be set through an upper layer signal, and the value '0' may indicate that SSB symbols included in the first set among the sets of SSB symbols cannot be used for PUSCH transmission. That is, when transmitting PUSCH, the terminal must consider the SSB symbols included in the first set. If the above field is 1 bit and the value of the above field is '1', the use of a second set of SSB symbols set by an upper layer (e.g., an RRC signal) may be indicated. That is, the location of potential first SSB symbols and the location of second symbols may be set through an upper layer signal, and the value '1' may indicate that SSB symbols included in the second set among the sets of SSB symbols cannot be used for PUSCH transmission. That is, when transmitting PUSCH, the terminal must consider the SSB symbols included in the second set.

[0265] The terminal can receive from the base station an association relationship between the first and second sets described above and the values ​​0 and 1.

[0266] If the above field is 2 bits and the value of the field is '0', it may be indicated via an upper layer signal that the locations of potential SSB symbols are not actually used. That is, the terminal may not consider the SSB symbols when transmitting PUSCH. If the above field is 2 bits and the value of the field is '1', it may be indicated that the first set of SSB symbols set by the upper layer (e.g., RRC signal) is used. That is, a first set including the locations of potential first SSB symbols, a second set including the locations of second symbols, and a set including the locations of third SSB symbols may be set via an upper layer signal. A value of '1' may indicate that the SSB symbols included in the first set among the sets of SSB symbols cannot be used for PUSCH transmission. That is, the terminal must consider the SSB symbols included in the first set when transmitting PUSCH.

[0267] If the above field is 2 bits and the value of the field is '2', the use of a second set of SSB symbols set by an upper layer (e.g., an RRC signal) may be indicated. The value '2' may indicate that SSB symbols included in the second set among the sets of SSB symbols cannot be used for PUSCH transmission. That is, the terminal must take into account the SSB symbols included in the second set when transmitting PUSCH. If the above field is 2 bits and the value of the field is '3', the use of a third set of SSB symbols set by an upper layer (e.g., an RRC signal) may be indicated. The value '3' may indicate that SSB symbols included in the third set among the sets of SSB symbols cannot be used for PUSCH transmission. That is, the terminal must take into account the SSB symbols included in the third set when transmitting PUSCH.

[0268] The association relationship between the aforementioned first set, second set to third set and the values ​​0, 1, 2 and 3 can be established from the base station.

[0269] Or, if the above field is 2 bits, the MSB 1 bit and the LSB 1 bit may each correspond to different sets of SSBs. And the MSB 1 bit and the LSB 1 bit may each indicate whether the corresponding set of SSBs is actually used for transmission.

[0270] More specifically, if the value of the MSB 1 bit is '0', it may be indicated via an upper layer signal that the first set, including the locations of potential SSB symbols, is not actually used. That is, when transmitting PUSCH, the terminal may not consider the SSB symbols of the first set. If the value of the MSB 1 bit is '1', it may be indicated via an upper layer signal that the first set, including the locations of potential SSB symbols, is actually used. That is, when the terminal transmits PUSCH, the SSB symbols of the first set may be considered.

[0271] If the value of the LSB 1 bit is '0', it may be indicated via an upper layer signal that the second set, which includes the locations of potential SSB symbols, is not actually used. That is, when transmitting PUSCH, the terminal may not consider the SSB symbols of the second set. If the value of the LSB 1 bit is '2', it may be indicated via an upper layer signal that the second set, which includes the locations of potential SSB symbols, is actually used. That is, when transmitting PUSCH, the SSB symbols of the second set may be considered.

[0272] The terminal can receive from the base station the association relationship between the first set and the MSB bit and the association relationship between the second set and the LSB bit described above.

[0273] The above field is 2 bits, and the MSB 1 bit and LSB 1 bit can each indicate the set of SSBs to be used. That is, two sets of SSBs can correspond to the MSB 1 bit, and the set of SSBs to be used can be selected according to the MSB 1 bit. Another two sets of SSBs can correspond to the LSB 1 bit, and the set of SSBs to be used can be selected according to the LSB 1 bit.

[0274] More specifically, if the value of the MSB 1 bit is '0', the bit may indicate the use of a first set of SSB symbols set by an upper layer (e.g., an RRC signal). That is, the locations of potential first SSB symbols and second symbols may be set through the upper layer signal, and it may be indicated that SSB symbols included in the first set among the sets of SSB symbols cannot be used for PUSCH transmission. In other words, the terminal must consider the SSB symbols included in the first set when transmitting PUSCH. If the value of the MSB 1 bit is '1', the bit may indicate the use of a second set of SSB symbols set by an upper layer (e.g., an RRC signal). It may be indicated that SSB symbols included in the second set among the sets of SSB symbols cannot be used for PUSCH transmission. In other words, the terminal must consider the SSB symbols included in the second set when transmitting PUSCH.

[0275] If the value of the LSB 1 bit is '0', the bit may indicate the use of a third set of SSB symbols set by an upper layer (e.g., an RRC signal). That is, the locations of potential third SSB symbols and fourth symbols may be set through the upper layer signal, and it may be indicated that SSB symbols included in the third set among the sets of SSB symbols cannot be used for PUSCH transmission. In other words, the terminal must take into account the SSB symbols included in the third set when transmitting PUSCH. If the value of the LSB 1 bit is '1', the bit may indicate the use of a fourth set of SSB symbols set by an upper layer (e.g., an RRC signal). It may be indicated that SSB symbols included in the fourth set among the sets of SSB symbols cannot be used for PUSCH transmission. In other words, the terminal must take into account the SSB symbols included in the fourth set when transmitting PUSCH.

[0276] The terminal can receive from the base station an association relationship between the aforementioned first set, second set, third set to fourth set and MSB bit or LSB bit.

[0277] The aforementioned DCI format may be a DCI format that does not schedule PUSCH or a DCI format that does not schedule data channels (PDSCH, PUSCH). For example, the DCI format may be a group-common DCI format.

[0278] After receiving the aforementioned DCI format, the SSB symbol set can be applied as follows.

[0279] If the DCI format is a DCI format that schedules a PUSCH, the terminal may apply the set of SSB symbols specified by the DCI format to the scheduled PUSCH. If the DCI format schedules a Type-A PUSCH iteration, the terminal may apply the specified set of SSB symbols to all Type-A PUSCH iterations. That is, if at least one of the symbols included in the specified set of SSB symbols overlaps with a Type-A PUSCH iteration, the Type-A PUSCH may not be transmitted. This may be performed for each Type-A PUSCH iteration.

[0280] If the DCI format schedules Type-B PUSCH repetitions, the terminal may determine that symbols included in the specified set of SSB symbols are invalid symbols for which the Type-B PUSCH repetition cannot be transmitted. That is, the terminal may determine nominal repetitions based on the scheduling of Type-B PUSCH repetitions, and determine actual repetitions by grouping consecutive symbols excluding the invalid symbols.

[0281] If the DCI format schedules multiple PUSCHs, the terminal may apply a specified set of SSB symbols to all PUSCHs. That is, if at least one of the symbols included in the specified set of SSB symbols overlaps with a PUSCH, the PUSCH may not be transmitted. This can be performed for each PUSCH.

[0282] If the DCI format schedules Configured grant (CG) PUSCHs, the terminal may apply the specified set of SSB symbols to all CG PUSCHs. That is, if at least one of the symbols included in the specified set of SSB symbols overlaps with the CG PUSCH, the CG PUSCH may not be transmitted. This may be performed for each CG PUSCH occasion.

[0283] If the DCI format is a DCI format that does not schedule a PUSCH, the time at which the SSB symbol set is applied can be determined based on the time at which the DCI format is received. For example, the SSB symbol set may be applied to PUSCHs scheduled in slots or symbols that occur after a certain time from the received symbol (the last symbol in the case of multiple symbols) of the DCI format. For example, if the DCI format received in slots or symbols that occur after a certain time from the received symbol (the last symbol in the case of multiple symbols) of the DCI format schedules a PUSCH, the terminal may apply the SSB symbol set to the PUSCH.

[0284] If the DCI format is a DCI format that schedules a PDSCH, the time at which an SSB symbol set is applied can be determined based on the transmission time of the HARQ-ACK corresponding to the said DCI format and the PDSCH. For example, an SSB symbol set may be applied to a PUSCH scheduled in a slot or for symbols that occur after a certain time from the symbol in which the HARQ-ACK was transmitted (or the last symbol in the case of multiple symbols). For example, if a DCI format received in a slot or for symbols that occur after a certain time from the symbol in which the HARQ-ACK was transmitted (or the last symbol in the case of multiple symbols) schedules a PUSCH, the terminal may apply an SSB symbol set to the said PUSCH.

[0285] In the example described above, the fixed time may be at least one of N1 (PDSCH precessing time), N2 (PUSCH preparation time), and N3 to 3ms. Here, N1, N2, and N3 may be expressed in units of the number of OFDM symbols. For subcarrier intervals of 15kHz, 30kHz, 60kHz, and 120kHz, N1 = 8, 10, 17, 20, N2 = 10, 12, 23, 36, and N3 = 10, 12, 22, 25.

[0286] In the example described above, the SSB symbol set is described as being designated as DCI, but the SSB symbol set may be designated as MAC-CE. In this case, DCI in the example described above may be replaced with MAC-CE.

[0287] The following describes a method for setting an SSB symbol set using upper layer signaling (e.g., RRC signaling). A terminal can receive an SSB symbol set from a base station using an upper layer signal. The present disclosure discloses methods for a terminal to receive an SSB symbol set using an upper layer signal.

[0288] [Method 1]

[0289] The terminal can receive SSB symbol set configuration information from a base station. The SSB symbol set configuration information may include at least the following information.

[0290] - Index of the SSB symbol set configuration (SSBConfiguarationId). The above index can be used to distinguish and indicate the SSB symbol set.

[0291] - A bitmap indicating the position of an SSB within an SSB burst (half frame, 5ms) interval. The bitmap may include one of a 4-bit length (shortBitmap), an 8-bit length (mediumBitmap), or a 64-bit length (longBitmap). Here, a 4-bit length bitmap (shortBitmap) is used when the maximum number of SSBs within the half frame is 4, an 8-bit length bitmap (mediumBitmap) is used when the maximum number of SSBs within the half frame is 8, and a 64-bit length bitmap (longBitmap) is used when the maximum number of SSBs within the half frame is 64. If a bitmap indicating the position of an SSB within an SSB burst interval is not set, it can be determined that all SSBs are indicated. That is, it can be considered that all bits of the bitmap are set to a value of '1'.

[0292] - ssb-Frequency can indicate the center frequency of an SSB. ARFCN-ValueNR can represent the center frequency of an SSB block as an ARFCN value.

[0293] - subcarrierSpacing can indicate the subcarrier spacing of the SSB. If subcarrierSpacing is not set, the subcarrier spacing of the SSB can be considered to be the same as the subcarrier spacing of the active DL or active UL BWP.

[0294] - ssb-Periodicity can indicate the period of the SSB. If ssb-Periodicity is not set, the terminal can determine the period of the SSB to be 5ms. Or, if ssb-Periodicity is not set, the terminal can determine the period of the SSB to be 20ms.

[0295] - halfFrameIndex can indicate the index of a half frame containing an SSB within the frame. If halfFrameIndex is not set, the terminal can assume the index of the half frame is 0.

[0296] The RRC signal configuration according to Method 1 may be as shown in Table 15, for example.

[0297] SSB-Configuration ::= SEQUENCE {SSBConfigurationId {0, 1, 2, 3} ssb-PositionsInBurst CHOICE {shortBitmap BIT STRING (SIZE (4)),mediumBitmap BIT STRING (SIZE (8)),longBitmap BIT STRING (SIZE (64))}ssb-Frequency ARFCN-ValueNR,subcarrierSpacing SubcarrierSpacing,ssb-Periodicity ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1}halfFrameIndex-r16 ENUMERATED {zero, one},}

[0298] [Method 2]

[0299] The terminal can receive SSB symbol set configuration information from the base station. The SSB symbol set configuration information may include an SSB ID. Here, the SSB configuration corresponding to the SSB ID may be as follows.

[0300] - The first ID may indicate a CD-SSB (cell-defining SSB). Here, the CD-SSB may indicate an SSB configured in SIB1.

[0301] - The second ID may indicate an NCD-SSB (non-cell-defining SSB). Here, the NCD-SSB may be an SSB included in the initial DL BWP for a RedCap terminal or an SSB set in a terminal-specific DL BWP. The NCD-SSB may be located at a different frequency or time than the CD-SSB. If multiple NCD-SSBs are set, each NCD-SSB may be assigned a unique index.

[0302] - The third ID may be an SSB defined for low-power operation of the base station. The said SSB may have a longer period than a CD-SSB. The base station may use a CD-SSB or select and use one of the low-power SSBs.

[0303] - The 4th ID may be an on-demand SSB. An on-demand SSB may be an SSB that the base station transmits to the terminal upon the terminal's request. If the terminal does not request an on-demand SSB, the base station may not transmit the on-demand SSB. If the terminal requests an on-demand SSB, the terminal may transmit the on-demand SSB for a certain period.

[0304] - The 5th ID may be an SSB for inter-cell measurement. The terminal can monitor the SSB of surrounding cells. Through the above monitoring, radio resource management (RRM) can be performed.

[0305] - The 6th ID may be an SSB for lower-layer triggered mobility. The terminal may require a handover to another cell due to mobility. An SSB for lower-layer triggered mobility may be configured, and the terminal may monitor said SSB.

[0306] - The 7th ID may be an SSB configured for inter-cell multi-TRP transmission and reception. The terminal may be capable of downlink reception or uplink transmission through multiple TRPs. In this case, the TRP may be a transmission unit of another cell. The said TRP may transmit an SSB of another cell. The physical cell ID of the SSB of another cell may be different from the physical cell ID of the SSB of the serving cell.

[0307] For example, the above ID may be replaced with a different ID or a different order. The SSB symbol set configuration information may include one or multiple of the above IDs. The terminal can determine the SSBs included in the SSB symbol set based on the IDs included in the SSB symbol set configuration information. Additionally, the base station can set a corresponding ID when configuring the SSB.

[0308] The RRC signal configuration according to Method 2 may be as shown in Table 16, for example.

[0309] SSB-Configuration ::= SEQUENCE {SSBConfigurationId {0, 1, 2, 3}rmr-SSB-config-r19 SSB_ID}

[0310] [Method 3]

[0311] The terminal can receive SSB symbol set configuration information from the base station. The SSB symbol set configuration information may include starting symbol indices of the SSB. An SSB symbol may start at a specific symbol within a slot.

[0312] Table 17 is a table showing an example of the starting position of an SSB symbol within a slot according to the SSB setting.

[0313] Referring to Table 17, for Case A (15 kHz subcarrier spacing) and Case C (30 kHz subcarrier spacing), the index of the starting symbol of the SSB in the slot may be 2 or 8. For Case B (30 kHz subcarrier spacing) or Case D (120 kHz subcarrier spacing), the index of the starting symbol of the SSB in the slot may be 2, 4, 6, or 8. For Case E (240 kHz subcarrier spacing), the index of the starting symbol of the SSB in the slot may be 2, 4, 6, 8, or 12.

[0314] CasesSSB position in a half frameSSB position in a slot (with respect to a slot boundary)Case A: 15kHz SCS{2,8}+14nn=0,1 f c ≤3GHzn=0,1,2,3 f c >3GHzn=0,1,2,3,4 for shared spectrum2 positions{2,3,4,5},{8,9,10,11}Case B: 30kHz SCS{4,8,16,20}+28nn=0 f c ≤3GHz n=0,1 f c >3GHz4 positions{2,3,4,5},{4,5,6,7},{6,7,8,9},{8,9,10,11}Case C: 30kHz SCS{2,8}+14nPaired spectrum:n=0,1 f c ≤3GHzn=0,1,2,3 f c >3GHzUnpaired spectrum:n=0,1 f c <1.88GHzn=0,1,2,3 f c≥3GHz2 positions{2,3,4,5},{8,9,10,11}Case D: 120kHz SCS{4,8,16,20}+28nn=0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,184 positions{2,3,4,5},{4,5,6,7},{6,7,8,9},{8,9,10,11}Case E: 240kHz SCS{8,12,16,20,32,36,40,44}+56n n=0,1,2,3,5,6,7,85 positions{2,3,4,5},{4,5,6,7},{6,7,8,9},{8,9,10,11},{12,13,0,1}

[0315] The SSB symbol set setting information may include the index value of the starting symbol of the SSB. For example, n2 may indicate an SSB starting from symbol 2 in a slot. The SSB block may be an SSB transmitted from symbols 2, 3, 4, and 5. n4 may indicate an SSB starting from symbol 4 in a slot. The SSB block may be an SSB transmitted from symbols 4, 5, 6, and 7. n6 may indicate an SSB starting from symbol 6 in a slot. The SSB block may be an SSB transmitted from symbols 6, 7, 8, and 9. n8 may indicate an SSB starting from symbol 8 in a slot. The SSB block may be an SSB transmitted from symbols 8, 9, 10, and 11. n12 may indicate an SSB starting from symbol 12 in a slot. The above SSB block may be an SSB transmitted from symbols 12 and 13 of the slot and symbols 0 and 1 of the next slot.

[0316] The SSB symbol set configuration information may include one or more indices of the SSB's start symbol.

[0317] In Method 3, the index of the starting symbol of the SSB is described as the index of a symbol within a slot, but it can be extended to the index of a symbol within two slots or the index of a symbol within multiple slots. In this case, the RRC signal configuration according to Method 3 may be as shown in Table 18, for example.

[0318] SSB-Configuration ::= SEQUENCE {SSBConfigurationId {0, 1, 2, 3}ssb-PositionInSlot ENUMERATED {n2, n4, n6, n8, n12}}

[0319] [Method 4]

[0320] The terminal can receive SSB symbol set configuration information from a base station. The SSB symbol set configuration information may include information regarding the location of an SSB within a slot. A single slot may contain up to two SSBs.

[0321] Referring to Table 17, according to Case A (15 kHz subcarrier spacing) and Case C (30 kHz subcarrier spacing), a maximum of 2 SSBs may be included in one slot, and said SSBs may be located at symbols {2, 3, 4, 5} or symbols {8, 9, 10, 11}. According to Case B (30 kHz subcarrier spacing) and Case D (120 kHz subcarrier spacing), a maximum of 2 SSBs may be included in one slot, and in one slot, said SSBs may be located at symbols {4, 5, 6, 7} or symbols {8, 9, 10, 11}, and in the other slot, said SSBs may be located at symbols {2, 3, 4, 5} or symbols {6, 7, 8, 9}.

[0322] The SSB symbol set setting information may include values ​​corresponding to the relative positions of the SSBs in the slot. For example, 'first' may indicate an SSB located at a symbol relatively ahead in the slot. 'Second' may indicate an SSB located at a symbol relatively behind in the slot. 'Both' may indicate two SSBs within the slot. The RRC signal configuration according to Method 4 may be as shown in Table 19, for example.

[0323] SSB-Configuration ::= SEQUENCE {SSBConfigurationId {0, 1, 2, 3}ssb-PositionInSlot ENUMERATED {first, second, both}}

[0324] In the above-described embodiment, the SSB may include an SSB used by the terminal's general modem (or main radio) for downlink sinking, cell indexing, RLF (radio link failure) measurement and determination, and RRM (radio resource management) measurement and determination.

[0325] In the above-described embodiment, the SSB may include a low-power (LP) SSB used by the terminal's low-power modem for downlink sinking, cell indexing, RLF measurement and determination, and RRM measurement and determination. The base station may set the symbol location of the LP-SSB to the terminal. For example, the base station may set the symbol location of the LP-SSB to the terminal as shown in Table 20.

[0326] lpss-PeriodicityAndOffset-r19 CHOICE {ms160 INTEGER (0..159),ms320 INTEGER (0..319)} OPTIONAL, -- Cond FFS[OOK-only]lpss-StartSymbol-r19 SEQUENCE {startSymbol1-r19 INTEGER (0..10),startSymbol2-r19 INTEGER (0..10) OPTIONAL}

[0327] In Table 20, lpss-PeriodicityAndOffset-r19 may represent the period and offset values ​​of LP-SSB. Here, if ms160 is selected, the period is 160 ms, and the value can be one of 0 to 159, which is an offset value in units of 1 ms within the period. If ms320 is selected, the period is 320 ms, and the value can be one of 0 to 319, which is an offset value in units of 1 ms within the period.

[0328] In Table 20, lpss-StartSymbol-r19 may represent the index of the start symbol of an LP-SSB within a slot. If a slot contains one LP-SSB, only startSymbol1-r19 may be set, and if a slot contains two LP-SSBs, startSymbol2-r19 may be additionally set. The number of LP-SSBs that can be set is not limited to two.

[0329] In the above-described embodiment, the SSB may include a low-power wake-up (LP-WUS) signal that is received by the terminal's low-power modem and wakes up the general modem (or Main Radio).

[0330] The names and values ​​of the information or fields described above are merely examples, and it is fully possible to replace them with information or fields of different names or apply different values.

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

[0332] Referring to FIG. 19, the terminal may include a transceiver (referring to a terminal receiver unit (1900) and a terminal transmitter unit (1910)), a memory (not shown), and a terminal processing unit (1905, or a terminal control unit or processor). According to the communication method of the terminal described above, the transceiver (1900, 1910), the memory, and the terminal processing unit (1905) of the terminal may operate. The terminal processing unit (1905, or processor) may control the operation of the terminal according to each of the embodiments described above, as well as a combination of at least one embodiment. 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, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

[0336] Additionally, the processor may control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor may control the components of the terminal to perform the embodiments and / or methods of the present disclosure (e.g., the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, etc.). There may be multiple processors, and the processors may perform the operation of controlling the components of the terminal by executing a program stored in memory.

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

[0338] Referring to FIG. 20, the base station may include a transceiver unit (referring to a base station receiver unit (2000) and a base station transmitter unit (2010)), a memory (not shown), and a base station processing unit (2005, or a base station control unit or processor). According to the communication method of the base station described above, the transceiver unit (2000, 2010), the memory, and the base station processing unit (2005) of the base station may operate. The base station processing unit (2005, or processor) may control the operation of the base station according to each of the embodiments described above, as well as a combination of at least one embodiment. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. Furthermore, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

[0342] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to perform the embodiments and / or methods of the present disclosure (e.g., the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, etc.). There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.

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

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

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

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

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

[0348] 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 at least two of the first, second, third, or fourth embodiments 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 a TDD LTE system, 5G, or NR system.

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

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

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

Claims

1. In a method performed by a terminal of a communication system, A step of receiving SSB (synchronization signal block) configuration information from a base station; A step of receiving a first DCI (downlink control information) for scheduling a PUSCH (physical uplink shared channel) from the base station; A step of receiving a second DCI from the base station, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not allowed; A method characterized by comprising: a step of checking whether an SSB transmission symbol and a resource of the PUSCH overlap based on the above SSB setting information and the above SSB symbol information for which PUSCH transmission is not allowed; and a step of transmitting the PUSCH if the above SSB transmission symbol and the resource of the PUSCH do not overlap.

2. In Paragraph 1, A method characterized in that the SSB symbol information for which the above PUSCH transmission is not allowed indicates an on-demand SSB.

3. In Paragraph 1, A method characterized by the above-mentioned SSB setting information including the period of the SSB, a bitmap indicating whether the SSB exists in the SSB burst, or the number of SSB bursts.

4. In Paragraph 1, A method characterized by information regarding SSB symbols for which PUSCH transmission is not allowed indicating a set of SSB symbols set to upper layer signaling.

5. In the method performed by a base station of a communication system, A step of receiving SSB (synchronization signal block) configuration information to a terminal; A step of receiving a first DCI (downlink control information) that schedules a PUSCH (physical uplink shared channel) to the terminal; A step of transmitting a second DCI to the terminal, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not allowed; and If the SSB transmission symbol and the resource of the PUSCH do not overlap, the method includes the step of receiving the PUSCH. A method characterized in that the above SSB transmission symbol is based on the above SSB setting information and information regarding the above PUSCH transmission-is-not-allowed SSB symbol.

6. In Paragraph 5, A method characterized in that the SSB symbol information for which the above PUSCH transmission is not allowed indicates an on-demand SSB.

7. In Paragraph 5, A method characterized by the above-mentioned SSB setting information including the period of the SSB, a bitmap indicating whether the SSB exists in the SSB burst, or the number of SSB bursts.

8. In Paragraph 5, A method characterized by information regarding SSB symbols for which PUSCH transmission is not allowed indicating a set of SSB symbols set to upper layer signaling.

9. In a terminal of a communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and Connected to communicate with at least one processor and capable of executing individually or in any combination of the at least one processor, the terminal: Receive SSB (synchronization signal block) configuration information from the base station, and Receive DCI (downlink control information) for scheduling PUSCH (physical uplink shared channel) from the above base station, and A second DCI is received from the base station, and the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not allowed, and Check whether the above SSB configuration information and the above SSB symbol information for which PUSCH transmission is not allowed overlap with the above PUSCH resources, and A terminal characterized by including: a memory storing a command to transmit the PUSCH when the above SSB transmission symbol and the above PUSCH resource do not overlap.

10. In Paragraph 9, A terminal characterized in that the SSB symbol information for which the above PUSCH transmission is not allowed indicates an on-demand SSB.

11. In Paragraph 9, A terminal characterized by the above-mentioned SSB setting information including a bitmap indicating the period of the SSB, whether the SSB exists in an SSB burst, or the number of SSB bursts.

12. In Paragraph 9, A terminal characterized by information regarding SSB symbols for which PUSCH transmission is not allowed, indicating a set of SSB symbols set to upper layer signaling.

13. In a base station of a communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and Connected to communicate with at least one processor and capable of executing individually or in any combination of the at least one processor, the base station: The terminal receives SSB (synchronization signal block) configuration information, and The above terminal receives DCI (downlink control information) for scheduling PUSCH (physical uplink shared channel), and Transmit a second DCI to the above terminal, wherein the second DCI includes information regarding an SSB symbol for which PUSCH transmission is not allowed, and A memory storing an instruction to receive the PUSCH when the SSB transmission symbol and the resource of the PUSCH do not overlap; A base station characterized in that the above SSB transmission symbol is based on the above SSB setting information and information regarding the above PUSCH transmission-not-allowed SSB symbol.

14. In Paragraph 13, A base station characterized by the fact that the SSB symbol information for which the above PUSCH transmission is not allowed indicates an on-demand SSB.

15. In Paragraph 13, A base station characterized by the above-mentioned SSB setting information including a bitmap indicating the period of the SSB, whether the SSB exists in an SSB burst, or the number of SSB bursts.

Images