Method and apparatus for allocating frequency resources in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In addition, the present disclosure relates to operations of a terminal and a base station in a wireless communication system and, more specifically, to an apparatus and a method by which a terminal can perform a subband non-overlapping full duplex (SBFD) operation. A method performed by a terminal of a communication system according to one embodiment of the present disclosure may comprise the steps of: identifying a control resource set (CORESET) associated with a search space; receiving downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) on the basis of the CORESET; and receiving the PDSCH on the basis of the DCI. The FDRA information indicates a physical resource block (PRB) for the PDSCH among a plurality of PRBs, and if the plurality of PRBs are associated with a subband non-overlapping full duplex (SBFD) symbol, the plurality of PRBs may be based on an offset value.

Description

Method and device for allocating frequency domain resources 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 device and method for enabling a terminal to perform subband non-overlapping full duplex (SBFD) operation.

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

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

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

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

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

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

[0008] As a result of the development of wireless communication systems and the aforementioned advancements in technology, various services have become available, and thus, methods for providing these services smoothly are required. In particular, methods for efficiently enabling terminals to perform SBFD (subband non-overlapping full duplex) operations are required.

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

[0010] A mobile communication (or wireless communication) system according to one embodiment of the present disclosure includes a method for receiving a PDSCH in a subband non-overlapping full duplex (SBFD).

[0011] A method performed by a terminal of a communication system according to an embodiment of the present disclosure may include the steps of: identifying a control resource set (CORESET) associated with a search space; receiving downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET; and receiving the PDSCH based on the DCI. The FDRA information may indicate a PRB for the PDSCH among a plurality of physical resource blocks (PRBs), and when the plurality of PRBs are associated with subband non-overlapping full duplex (SBFD) symbols, the plurality of PRBs may be characterized in that they are based on an offset value.

[0012] A method performed by a terminal of a communication system according to an embodiment of the present disclosure may include the steps of: identifying a control resource set (CORESET) associated with a search space; transmitting downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET; and transmitting the PDSCH according to the DCI. The FDRA information may indicate a PRB for the PDSCH among a plurality of physical resource blocks (PRBs), and when the plurality of PRBs are associated with subband non-overlapping full duplex (SBFD) symbols, the plurality of PRBs may be characterized in that they are based on an offset value.

[0013] A terminal of a communication system according to an embodiment of the present disclosure may include a transceiver and a control unit. The control unit may be configured to identify a control resource set (CORESET) associated with a search space, receive downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET, and receive the PDSCH based on the DCI. The FDRA information may indicate a PRB for the PDSCH among a plurality of physical resource blocks (PRBs), and when the plurality of PRBs are associated with subband non-overlapping full duplex (SBFD) symbols, the plurality of PRBs may be characterized in that they are based on an offset value.

[0014] A base station of a communication system according to an embodiment of the present disclosure may include a transceiver and a control unit. The control unit may be configured to identify a control resource set (CORESET) associated with a search space, transmit downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET, and transmit the PDSCH according to the DCI. The FDRA information may indicate a PRB for the PDSCH among a plurality of physical resource blocks (PRBs), and when the plurality of PRBs are associated with subband non-overlapping full duplex (SBFD) symbols, the plurality of PRBs may be characterized in that they are based on an offset value.

[0015] The disclosed embodiments provide devices and methods capable of effectively providing services in a mobile communication system. The effects achieved by the present disclosure are not limited to those mentioned above, and other effects not mentioned will be readily apparent to those skilled in the art from the description below.

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

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

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

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

[0020] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0021] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to an embodiment of the present disclosure.

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

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

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

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

[0026] FIG. 11 is a diagram illustrating a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0027] FIG. 12 is a diagram illustrating TDD settings and SBFD settings in a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 13 is a diagram illustrating frequency domain scheduling based on DCI format 1_0 received in a common search space according to one embodiment of the present disclosure.

[0029] FIG. 14 is a diagram illustrating a PDSCH scheduled based on DCI format 1_0 detected in a common search space according to an embodiment of the present disclosure.

[0030] FIG. 15 is a diagram showing an offset value applied to DCI format 1_0 of a common search space according to an embodiment of the present disclosure.

[0031] FIG. 16 is a flowchart illustrating an embodiment of the present disclosure.

[0032] FIG. 17 is a diagram illustrating a DCI length alignment process according to an embodiment of the present disclosure.

[0033] FIG. 18 is a diagram illustrating scheduled PRBs when the size of DCI format 1_0 monitored in a terminal-specific search space is derived from the size of DCI format 1_0 monitored in a common search space according to a DCI length alignment process.

[0034] FIG. 19 is a diagram illustrating DCI format 1_0 of a terminal-specific search space according to one embodiment of the present disclosure.

[0035] FIG. 20 is a diagram showing an offset value applied to DCI format 1_0 of a terminal-specific search space according to an embodiment of the present disclosure.

[0036] FIG. 21 is a flowchart illustrating an embodiment of the present disclosure.

[0037] FIG. 22 is a flowchart illustrating an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

[0048] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

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

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

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

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

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

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

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

[0056] [NR time-frequency resources]

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

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

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

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

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

[0062] [Table 1]

[0063]

[0064] [Bandwidth Part (BWP)]

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

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

[0067] Referring to FIG. 3, an example is shown in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set information such as Table 2 below for each bandwidth portion.

[0068] [Table 2]

[0069]

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

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

[0072] According to one embodiment of the present disclosure, the setting of the bandwidth portion supported by the 5G communication system can be used for various purposes.

[0073] In one embodiment, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth-part configuration. For example, the base station can configure the bandwidth-part frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and / or receive data at a specific frequency location within the system bandwidth.

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

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

[0076] According to one embodiment of the present disclosure, in a method for setting a bandwidth part, terminals prior to RRC connection can receive setting information for an initial bandwidth part through a Master Information Block (MIB) during an initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted from the MIB of a physical broadcast channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive a physical downlink shared channel (PDSCH) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0077] [Bandwidth Part (BWP) Change]

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

[0079] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a UE receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by DCI in the changed bandwidth part without any problems. To this end, the standard specifies the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in Table 3 below, for example.

[0080] [Table 3]

[0081]

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

[0083] According to the requirement on the bandwidth part change delay time described above, when a terminal receives a DCI including a bandwidth part change indicator in slot n, the terminal can complete the change to a new bandwidth part indicated by the bandwidth part change indicator at a time no later than slot n + TBWP, and can perform transmission and / or reception for a data channel scheduled by the DCI including the bandwidth part change indicator in the changed new bandwidth part. When the base station wants to schedule a data channel in the new bandwidth part, the base station can determine the time domain resource allocation for the data channel by considering the bandwidth part change delay time (TBWP) of the terminal. That is, when the base station schedules a data channel in the new bandwidth part, the data channel can be scheduled after the bandwidth part change delay time in the method of determining the time domain resource allocation for the data channel. Therefore, the terminal may not expect the DCI indicating the bandwidth part change to indicate a slot offset (e.g., K0 or K2) value that is smaller than the bandwidth part change delay time (TBWP).

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

[0085] [SS / PBCH block]

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

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

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

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

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

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

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

[0093] [PDCCH: DCI related]

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

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

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

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

[0098] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with the C-RNTI. DCI format 0_0 with the CRC scrambled with the C-RNTI can include, for example, the information in Table 4. Of course, the present invention is not limited to the following examples.

[0099] [Table 4]

[0100]

[0101] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in Table 5. Of course, the present invention is not limited to the following examples.

[0102] [Table 5]

[0103]

[0104] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 6. Of course, the present invention is not limited to the following examples.

[0105] [Table 6]

[0106]

[0107] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 7. Of course, the present invention is not limited to the following examples.

[0108] [Table 7]

[0109]

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

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

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

[0113] In the aforementioned 5G communication system, the control region can be set by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Setting the control region for the terminal may mean providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, the information may include the information in Table 8 below. Of course, the present invention may not be limited to the examples below.

[0114] [Table 8]

[0115]

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

[0117] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0118] Referring to FIG. 5, an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in a 5G communication system is provided. According to FIG. 5, the basic unit of time and frequency resources constituting a control channel can be referred to as a REG (Resource Element Group, 503), and a REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

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

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

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

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

[0123] [Table 9]

[0124]

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

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

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

[0128] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

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

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

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

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

[0133] In a terminal-specific search space, a combination of DCI format and RNTI can be monitored, although this is not limited to the examples below.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147] The DCI formats described above may follow the definitions in Table 10 below. Of course, they are not limited to the examples below.

[0148] [Table 10]

[0149]

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

[0151] [Mathematical Formula 1]

[0152]

[0153] - : Integration level

[0154] - : Carrier Index

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

[0156] - : slot index

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

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

[0159] - = 0, ..., -1

[0160] - , , , , ,

[0161] - : Terminal identifier

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

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

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

[0165] [PDSCH: Frequency Resource Allocation Related]

[0166] FIG. 7 is a diagram illustrating an example of frequency-axis resource allocation of a PDSCH (physical downlink shared channel) in a wireless communication system according to an embodiment of the present disclosure.

[0167] Referring to FIG. 7, it is a diagram illustrating three frequency axis resource allocation methods that can be set through an upper layer in an NR wireless communication system: type 0 (7-00), type 1 (7-05), and dynamic switch (7-10).

[0168] Referring to FIG. 7, if a terminal is configured to use only resource type 0 through upper layer signaling (7-00), some downlink control information (DCI) that allocates PDSCH to the terminal may include a bitmap consisting of NRBG bits. The conditions for this will be explained later. At this time, NRBG refers to the number of RBGs (resource block groups) determined as shown in [Table 11] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data may be transmitted to an RBG indicated as 1 by the bitmap.

[0169] [Table 11]

[0170]

[0171] If the terminal is configured to use only resource type 1 through upper layer signaling (7-05), some DCIs that allocate PDSCH to the terminal It may include frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. The base station can set the starting VRB (7-20) and the length of frequency axis resources (7-25) allocated continuously therefrom as described above.

[0172] If the terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (7-10), some DCIs that allocate PDSCH to the terminal may include frequency-axis resource allocation information consisting of bits of the larger value (7-35) among the payload (7-15) for configuring resource type 0 and the payload (7-20, 7-25) for configuring resource type 1. Conditions for this will be explained later. At this time, one bit (7-30) may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the added bit has a value of '0', it may indicate that resource type 0 is used, and if it has a value of '1', it may indicate that resource type 1 is used.

[0173] [PDSCH / PUSCH: Time Resource Allocation Related]

[0174] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0175] A base station can set up a table for time domain resource allocation information for a downlink data channel (Physical Downlink Shared Channel, PDSCH) and an uplink data channel (Physical Uplink Shared Channel, PUSCH) to a terminal through higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 12] or [Table 13] below may be transmitted from the base station to the terminal. Of course, it may not be limited to the above example.

[0176] [Table 12]

[0177]

[0178] [Table 13]

[0179]

[0180] 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 in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

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

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

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

[0184] Referring to Figure 9, when the subcarrier spacing of the data channel and the control channel are the same (9-00, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (9-05, μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0185] [PUSCH: Transmission method related]

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

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

[0188] [Table 14]

[0189]

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

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

[0192] [Table 15]

[0193]

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

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

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

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

[0198] A terminal can transmit to a base station one or more SRS resources included in an SRS resource set in which the usage value is set to 'codebook' according to upper layer signaling, and the base station can select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using transmission beam information of the selected SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and can be included in the DCI. Additionally, the base station can include in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal can perform PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the SRS resource indicated by the SRI, using the SRS resource indicated by the SRI.

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

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

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

[0202] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS within the upper layer signaling SRS-ResourceSet. For non-codebook-based transmission, the UE may not expect that the upper layer signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS within the upper layer signaling SRS-ResourceSet are configured together.

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

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

[0205] [CA / DC related]

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

[0207] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system may include NR SDAP (Service Data Adaptation Protocol 1025, 1070), NR PDCP (Packet Data Convergence Protocol 1030, 1065), NR RLC (Radio Link Control 1035, 1060), and NR MAC (Medium Access Control 1040, 1055) in the terminal and NR base station, respectively. Of course, the present invention is not limited to the examples, and may include more or fewer layers.

[0208] The main functions of NR SDAP (1025, 1070) may include some of the following functions. . Of course, the examples below are not limited thereto.

[0209] - Transfer of user plane data

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

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

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

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

[0214] The main functions of NR PDCP (S30, S65) may include some of the following functions. The main functions of NR PDCP (1030, 1065) may include some of the following functions. Of course, the examples below are not limited thereto.

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

[0216] - User data transfer function

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

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

[0219] - PDCP PDU reordering for reception

[0220] - Duplicate detection of lower layer SDUs

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

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

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

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

[0225] The main functions of NR RLC (1035, 1060) may include some of the following functions, but are not limited to the examples below.

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

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

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

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

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

[0231] - Re-segmentation of RLC data PDUs

[0232] - - Reordering of RLC data PDUs

[0233] - Duplicate detection function

[0234] - Protocol error detection

[0235] - RLC SDU discard function

[0236] - RLC re-establishment function

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

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

[0239] NR MAC (1040, 1055) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions. Of course, it is not limited to the examples below.

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

[0241] -- Multiplexing / demultiplexing of MAC SDUs

[0242] -- Scheduling information reporting function

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

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

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

[0246] -- MBMS service identification function

[0247] --Transport format selection function

[0248] --Padding function

[0249] The NR PHY layer (1045, 1050) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols, and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer. Of course, the present invention is not limited to the above examples.

[0250] The detailed structure of the wireless protocol structure can be changed in various ways depending on the carrier (or cell) operation method. For example, if a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer, as in 1000. On the other hand, if the base station transmits data to a terminal based on carrier aggregation (CA) using multiple carriers in a single transmission and reception point (TRP), the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the physical layer (PHY layer) through the MAC layer, as in 1010. For example, if a base station transmits data to a terminal based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer, as in 1020.

[0251] Referring to the above-described PDCCH and beam configuration-related descriptions, since repeated PDCCH transmission is not currently supported in Rel-15 and Rel-16 NR, it may be difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure may provide a method for repeated PDCCH transmission through multiple transmission points (TRPs). According to the present disclosure, the PDCCH reception reliability of a terminal may be improved. Specific methods are described in detail in the following embodiments.

[0252] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. One embodiment of the present disclosure can be applied, for example, to systems such as FDD (Frequency Division Duplex), TDD (Time Division Duplex), and XDD (Cross Division Duplex), but may not be limited thereto. In the present disclosure below, upper signaling (or upper layer signaling) may be a signal transmission method or signal transmitted from a base station to a terminal using a downlink data channel of a physical layer, or from a terminal to a base station using an uplink data channel of a physical layer. For example, upper signaling (or upper layer signaling) may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element; MAC CE), but may not be limited thereto.

[0253] Hereinafter, in the present disclosure, when a terminal determines whether cooperative communication is applied, various methods may be used, such as, but not limited to, the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator that indicates whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to a higher layer. For the convenience of the description below, a case in which a terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to the above may be referred to as a NC-JT (Non-Coherent Joint Transmission) case. That is, the NC-JT case in the present disclosure includes reception of a PDSCH to which cooperative communication is applied, and whether cooperative communication is applied can be identified based on at least one or a combination of at least one of the above-described conditions / methods.

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

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

[0256] In the following description of the present disclosure, the term "upper layer signaling" may refer to signaling corresponding to at least one or a combination of one or more of the following signaling. Of course, the present disclosure is not limited to the examples below.

[0257] - MIB (Master Information Block)

[0258] - SIB (System Information Block) or SIB

[0259] - RRC (Radio Resource Control)

[0260] - MAC (Medium Access Control) CE (Control Element)

[0261] Additionally, L1 signaling may be signaling corresponding to at least one or a combination of one or more of the following physical layer channels or signaling methods. Of course, it is not limited to the examples below.

[0262] - PDCCH (Physical Downlink Control Channel)

[0263] - DCI (Downlink Control Information)

[0264] - UE-specific DCI

[0265] - Group common DCI

[0266] - Common DCI

[0267] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

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

[0269] - PUCCH (Physical Uplink Control Channel)

[0270] - UCI (Uplink Control Information)

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

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

[0273] [Random Access procedure in SBFD]

[0274] Meanwhile, 3GPP introduced SBFD (Subband Non-Overlapping Full Duplex) as a new duplex method based on NR. SBFD is a technology that utilizes a portion of downlink resources as uplink resources in the TDD band (spectrum) of frequencies below 6 GHz or above 6 GHz, thereby receiving uplink transmissions from terminals equivalent to the increased uplink resources, thereby expanding the uplink coverage of the terminal, and reducing feedback delay by receiving feedback on downlink transmissions from the terminals using the expanded uplink resources. In the present disclosure, a terminal that receives information on whether SBFD is supported from a base station and can perform uplink transmissions using a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The following methods may be considered for defining the SBFD method in the standard and for an SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band). Of course, the present invention is not limited to the following examples.

[0275] First method. In addition to the existing unpaired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD) frame structure types, another frame structure type (e.g., frame structure type 2) can be introduced to define the above SBFD. Frame structure type 2 can be defined as supported in a specific frequency or frequency band, or the base station can indicate to the terminal whether SBFD is supported as system information. An SBFD terminal can receive system information including whether SBFD is supported and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0276] Second method. Whether SBFD is additionally supported on a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated without defining a new frame structure type. In this second method, whether SBFD is additionally supported on a specific frequency or frequency band of an existing unpaired spectrum can be defined, or the base station can indicate SBFD support to the terminal through system information. An SBFD terminal can determine whether SBFD is supported in a specific cell (or frequency, frequency band) by receiving system information including SBFD support.

[0277] In the first and second methods described above, information on whether SBFD is supported may be information that indirectly indicates whether SBFD is supported by additionally setting a portion of downlink resources as uplink resources in addition to the setting of TDD UL (uplink)-DL (downlink) resource configuration information indicating TDD downlink slot (or symbol) resources and uplink slot (or symbol) resources (for example, SBFD resource configuration information in FIG. 12 described below), or may be information that directly indicates whether SBFD is supported.

[0278] In the present disclosure, an SBFD terminal can acquire cell synchronization by receiving a synchronization signal block during the initial cell access for connecting to a cell (or base station). The process for acquiring cell synchronization may be the same for both the SBFD terminal and existing TDD terminals. Thereafter, the SBFD terminal can determine whether the cell supports SBFD through MIB acquisition, SIB acquisition, or a random access process.

[0279] The system information for transmitting information on whether SBFD is supported may be system information transmitted separately from the system information for terminals supporting other versions of the standard within the cell (e.g., existing TDD terminals). The SBFD terminal may determine whether SBFD is supported by obtaining all or part of the system information for existing TDD terminals and the separately transmitted system information. If the SBFD terminal obtains only the system information for existing TDD terminals or obtains system information on non-support for SBFD, the SBFD terminal may determine that the cell (or base station) only supports TDD.

[0280] If information about SBFD support is included in the system information for a terminal that supports a different version of the standard (e.g., a legacy TDD terminal), the information about SBFD support can be inserted last so as not to affect the system information acquisition of the legacy TDD terminal. If the SBFD terminal fails to acquire the information about SBFD support inserted last or acquires information indicating that SBFD is not supported, the SBFD terminal can determine that the cell (or base station) only supports TDD.

[0281] If information on whether SBFD is supported is included in system information for a terminal supporting a different version of the standard (e.g., a legacy TDD terminal), the information on whether SBFD is supported may be transmitted on a separate PDSCH so as not to affect acquisition of system information by the legacy TDD terminal. For example, a terminal that does not support SBFD may receive a first SIB (or SIB1) including legacy TDD-related system information on a first PDSCH. An SBFD-supporting terminal may receive a first SIB (or SIB) including legacy TDD-related system information on a first PDSCH, and a second SIB including SBFD-related system information on a second PDSCH. Here, the first PDSCH and the second PDSCH may be scheduled as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) of the first PDCCH and the second PDCCH may be scrambled with the same RNTI (e.g., SI-RNTI). An SBFD-supporting terminal can obtain a search space for monitoring a second PDCCH from system information of a first PDSCH, and if it fails to obtain it (i.e., if the system information of the first PDSCH does not include information about the search space), it can receive a second PDCCH in the same search space as the search space of the first PDCCH.

[0282] 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 and receive data / control signals in the same manner as a conventional TDD terminal.

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

[0284] The base station configures random access resources for TDD terminals and can additionally configure separate random access resources for SBFD terminals. Here, SBFD terminals may use the random access resources for TDD terminals, or they may not be able to use the random access resources for TDD terminals. In the latter case, SBFD terminals can only use the separate random access resources for SBFD terminals.

[0285] An SBFD terminal can be instructed by a base station whether or not it can use random access resources for a TDD terminal. Whether or not the random access resources for a TDD terminal can be instructed in the SIB. For example, a separate random access resource for an SBFD terminal can be configured in the SIB, and along with the separate random access resource configuration, the availability of the random access resources for the TDD terminal can be indicated. The availability of the random access resources for the TDD terminal can be indicated by 1 bit. If 1 bit is '0' (or FALSE), the SBFD terminal cannot use the random access resources for the TDD terminal. If 1 bit is '1' (or TRUE), the SBFD terminal can use the random access resources for the TDD terminal.

[0286] The base station can determine the type of terminal attempting to access a cell based on the random access resources used by the terminal. Hereinafter, in the present disclosure, determination by the terminal or the base station can be used with the same meaning as determine or identify. For example, an SBFD terminal can transmit a PRACH through a separate random access resource for SBFD terminals, and the base station can determine that the SBFD terminal is attempting to access a cell when receiving the PRACH. For example, a TDD terminal can transmit a PRACH through a random access resource for TDD terminals, and the base station can determine that the TDD terminal is attempting to access a cell when receiving the RPACH. Note that when an SBFD terminal is allowed 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 the terminal transmitting the PRACH is a TDD terminal or an SBFD terminal. In this case, the base station can always assume that the type of the terminal is a TDD terminal.

[0287] When the base station determines that the terminal is an SBFD terminal, the base station may schedule msg2, msg3, msg4, etc. to the terminal based on the uplink subband configuration. For example, when the base station schedules reception of msg2 and msg4 to the terminal, msg2 and msg4 may be scheduled so that they are not received on the uplink subband (when the terminal receives a PDSCH including msg2 and msg4, the PDSCH is received on frequency resources other than the uplink subband). When the base station schedules msg3 PUSCH to the terminal, msg3 PUSCH may be scheduled to be transmitted within the uplink subband.

[0288] If the base station determines that the terminal is a TDD terminal, the base station cannot use the uplink subband configuration when scheduling msg2, msg3, and msg4 to the terminal. For example, even if the uplink subband is configured in a downlink symbol or a flexible symbol, the base station can assume that the terminal cannot obtain the uplink subband configuration 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.

[0289] Alternatively, the base station may not set up separate random access resources for SBFD terminals, but may set up common random access resources for all terminals within the cell. In this case, configuration information for the random access resources may be transmitted to all terminals within the cell through system information, and the SBFD terminal that has received the system information may perform random access to the random access resources. After that, the SBFD terminal may complete the random access process and proceed to the RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive a higher layer signal or a physical signal from the base station that can determine that some frequency resources of the downlink time resources are set uplink resources, and may perform an SBFD operation (e.g., transmitting an uplink signal in the uplink resource).

[0290] When an SBFD terminal determines that a cell supports SBFD, the terminal may notify the base station that the terminal attempting to connect is an SBFD terminal by transmitting capability information to the base station, which includes at least one or more of whether the terminal supports SBFD, whether full-duplex communication or half-duplex communication is supported, and the number of transmit or receive antennas that the terminal has (or supports). Alternatively, if half-duplex communication support is a mandatory implementation for the SBFD terminal, whether half-duplex communication is supported may be omitted from the capability information. The SBFD terminal may report capability information to the base station through a random access procedure, may report to the base station after completing the random access procedure, or may report to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

[0291] SBFD terminals can support half-duplex communication, which performs only uplink transmission or downlink reception at a time, like existing TDD terminals, or they can support full-duplex communication, which performs both uplink transmission and downlink reception at a time. Therefore, the SBFD terminal can report whether it supports half-duplex or full-duplex communication to the base station through a capability report. After the report, the base station can configure the SBFD terminal to 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, since there is generally no duplexer, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD.

[0292] Typically, a terminal can establish a wireless link with a network through a random access procedure based on synchronization with the network and system information acquired during the cell search process. Random access can be either contention-based or contention-free. Contention-based random access can be used when a terminal performs cell selection and reselection during the initial cell access phase, for example, when moving from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access can be used to reestablish uplink synchronization when downlink data arrives, in the case of a handover, or in the case of position measurement.

[0293] FIG. 11 is a diagram illustrating a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0294] Referring to FIG. 11, a contention-based random access procedure is illustrated as an example. In addition, although not illustrated, the base station may transmit a synchronization signal block as described in the above-described embodiments. 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 including a PSS / SSS (synchronization signal) and a PBCH (broadcast channel) signal using up to 64 different beams for 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 having the strongest received signal strength or greater than a predetermined threshold) and transmit a preamble to the base station using a PRACH (physical random access channel) resource associated with the detected synchronization signal block. For example, as a first step (1101) of the random access procedure, the terminal may transmit a random access preamble (or message 1 (msg1)) to the base station. The base station that receives the random access preamble may measure a transmission delay value between the terminal and the base station and synchronize the uplink. Specifically, the terminal may transmit a random access preamble randomly selected from a random access preamble set given in advance by system information. In addition, the initial transmission power of the random access preamble may be determined according to the path loss between the base station and the terminal measured by the terminal. In addition, the terminal may 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.

[0295] In the second step (1102), the base station can transmit a response (random access response, RAR, or message 2 (msg2)) to the terminal for the detected random access attempt. The base station can transmit an uplink transmission timing control command to the terminal based on a transmission delay value measured from the random access preamble received in the first step. In addition, the base station can transmit an uplink resource and power control command to be used by the terminal as scheduling information. The scheduling information can include control information for the uplink transmission beam of the terminal. The RAR is transmitted via the PDSCH and can include at least one of the following information. Of course, the following examples are not limited.

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

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

[0298] -- Uplink scheduling grant

[0299] -- Timing advance value

[0300] 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 (1102), the first step (1101) may be performed again. If the first step is performed again, the terminal transmits the random access preamble by increasing the transmission power by a predetermined step (this is called power ramping), thereby increasing the probability of the base station receiving the random access preamble.

[0301] In the third step (1103), the terminal may transmit uplink information (scheduled transmission, or message 3 (msg3)) including its terminal identifier (UE contention resolution identity or, if the terminal already has a valid terminal identifier (C-RNTI) within the cell before initiating the random access procedure) to the base station through an uplink data channel (physical uplink shared channel, PUSCH) using the uplink resources allocated in the second step (1102). 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 (1102). In addition, the transmission power of the uplink data channel for transmitting message 3 may be determined in consideration of the power control command received from the base station in the second step (1102) and the power ramping value of the random access preamble. There is. The uplink data channel for transmitting message 3 may be the first uplink data signal transmitted by the terminal to the base station after the terminal transmits the random access preamble.

[0302] Finally, in the fourth step (1104), if the base station determines that the terminal has performed random access without collision with other terminals, it can transmit to the terminal a message (contention resolution message (CR message), or message 4 (message 4, msg4)) including the identifier of the terminal that transmitted the uplink data in the third step (1103). In this regard, if multiple terminals receive the same TC-RNTI in the second step (1102), each of the multiple terminals that received the same TC-RNTI includes its own terminal identifier (UE contention resolution identity) in message 3 in the third step (1103) and transmits the message 3 to the base station, and the base station can transmit message 4 (CR message) including the terminal identifier of one of the identifiers of the multiple terminals to resolve the contention. When the terminal receives message 4 (CR message) including its terminal identifier from the base station in the fourth step (1104) (or transmits message 3 including terminal identifier (C-RNTI) in the third step (1103) and receives terminal-specific control information including CRC based on the terminal identifier (C-RNTI) through PDCCH in the fourth step (1104), it can determine that random access is successful. Accordingly, among multiple terminals that have received the same TC-RNTI from the base station, a terminal that confirms that its terminal identifier is included in message 4 (CR message) can confirm that the contention is successful. In addition, the terminal can transmit HARQ-ACK / NACK indicating whether message 4 was successfully received to the base station through an uplink control channel (physical uplink control channel, PUCCH).

[0303] If the data transmitted by the terminal in step 3 (1103) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not transmit any more data to the terminal. Accordingly, if the terminal fails to receive data transmitted from the base station in step 4 (1104) for a certain period of time, the random access procedure may be determined to have failed, and the procedure may be restarted from step 1 (1101).

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

[0305] The base station can inform the terminal of the configuration information for random access resources, for example, the control information (or configuration information) indicating the time-frequency resources that can be used for PRACH, using at least one of SIB, higher layer signaling (RRC (Radio Resource Control) information), or DCI (Downlink Control Information). The frequency resource for PRACH transmission can indicate the start RB point of transmission to the terminal, and the number of RBs used can be determined according to the preamble format transmitted through PRACH and the applied subcarrier spacing. The time resource for PRACH transmission can inform the subframe index and start symbol including the preset PRACH configuration period, PRACH transmission time (PRACH occasion, which can be used interchangeably with transmission time), and the number of PRACH transmission time points in the slot, etc., through the PRACH configuration index (0 to 255), as shown in Table 16 below. The terminal can determine the validity of the PRACH transmission times indicated by the PRACH configuration index, and determine only the valid PRACH transmission times as the PRACH transmission times at which the random access preamble can be transmitted. 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 can check the time and frequency resources for transmitting the random access preamble, and transmit the selected sequence as a preamble to the base station.

[0306] [Table 16]

[0307]

[0308] Meanwhile, according to an embodiment of the present disclosure, a method of determining the validity of a PRACH transmission time point through a PRACH configuration index and SBFD settings for an SBFD terminal to perform PRACH transmission, and performing PRACH transmission through a PRACH transmission time point determined to be valid, a procedure of the SBFD terminal may be required when a valid PRACH transmission time point and downlink reception overlap.

[0309] FIG. 12 is a diagram illustrating TDD settings and SBFD settings in a wireless communication system according to an embodiment of the present disclosure.

[0310] Fig. 12(a) illustrates a case where TDD is operated in a specific frequency band. In a cell operating TDD, a base station can transmit and receive signals including data / control information in downlink slots (or symbols), uplink slots (or symbols) (1201), and flexible slots (or symbols) based on settings for TDD UL-DL resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD with an existing TDD terminal or SBFD terminal.

[0311] In Fig. 12, it can be assumed that the DDDSU slot format is set 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 not 'D' or 'U', for example, a slot that includes a downlink symbol or an uplink symbol or a flexible symbol. Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. For example, the repetition period of the TDD configuration can be configured with 5 slots (for example, 5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

[0312] Next, FIGS. 12(b), 12(c) and 12(d) illustrate cases where SBFD is operated together with TDD in a specific frequency band.

[0313] Referring to FIG. 12(b), the terminal may configure a portion of the frequency band of the cell as a frequency band (1210) capable of uplink transmission. The above-described band may be referred to as an uplink subband (UL subband). The uplink subband (UL subband) may be applied to all symbols of all slots. The terminal may transmit an uplink channel or signal scheduled for all symbols (1212) within the UL subband. However, the terminal may not transmit an uplink channel or signal in a band other than the UL subband.

[0314] Referring to Fig. 12(c), the terminal may set a portion of the frequency band of the cell as a frequency band (1220) capable of uplink transmission, and may set a time region in which the frequency band is activated. Here, the frequency band (1220) may be called an uplink subband (UL subband). In Fig. 12(c), the uplink subband (UL subband) may be 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 subband (1222) of the remaining slots. Therefore, although the uplink subband is activated on a slot-by-slot basis in Fig. 12(c), whether it is activated or not may be set on a symbol-by-symbol basis.

[0315] Referring to FIG. 12(d), a terminal may be configured with time-frequency resources capable of uplink transmission. The terminal may configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1232) of the first and second slots may be configured as time-frequency resources capable of uplink transmission. Additionally, some frequency bands (1233) of the third slot and some frequency bands (1234) of the fourth slot may be configured as time-frequency resources capable of uplink transmission.

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

[0317] <Example 1: DCI format 1_0 detected in common search space>

[0318] A terminal can receive a CORESET from a base station. The received CORESET may include CORESET0 configured through a Master Information Block (MIB) and CORESETs configured according to dedicated RRC settings. The terminal can receive a search space configured from a base station. The received search space may include search space 0 configured through a Master Information Block (MIB) and search spaces configured according to dedicated RRC settings. Each search space may be configured as a common search space (CSS) or a UE-specific search space (USS). In addition, a DCI format monitored by the terminal in the corresponding search space may be configured for each search space. In addition, an associated CORESET may be configured for each search space.

[0319] The terminal can monitor DCI format 1_0 in the common search space. Here, the common search space can include Type0-PDCCH CSS set, Type0A-PDCCH CSS set, Type0B-PDCCH CSS set, Type1-PDCCH CSS set, Type1A-PDCCH CSS set, Type2-PDCCH CSS set, Type2A-PDCCH CSS set, and Type3-PDCCH CSS set, as shown in Table 17.

[0320] [Table 17]

[0321]

[0322] The UE can monitor DCI format 1_0 in the UE-specific search space. Here, the UE-specific search space can monitor a DCI format in which the CRC is scrambled with C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI, or NCR-RNTI, as shown in Table 18.

[0323] [Table 18]

[0324]

[0325] The terminal can determine the time period during which it should monitor the PDCCH based on the search space setting. This can be called a PDCCH monitoring occasion. The terminal can blind decode the PDCCH in the CORESET associated with the search space set in the PDCCH monitoring occasion. During the blind decoding process, the terminal can successfully receive the DCI format from the PDCCH. Successful reception of the DCI format can be confirmed by comparing whether the scrambled CRC of the DCI format is identical to the CRC of the terminal. Here, the CRC of the terminal can be a value pre-set by the base station, a value derived from the cell index, or a value derived using a predefined method.

[0326] A terminal can schedule a PDSCH through the received DCI format. Here, the DCI format can include information about the time domain and frequency domain in which the PDSCH is scheduled.

[0327] Information about the time domain in which the PDSCH is scheduled can be indicated in the Time domain resource assignment (TDRA) field of the DCI format. More specifically, the terminal can receive a TDRA table set up from the base station. Each row of the TDRA table can have a unique index, and a K0 value, a SLIV value, and a PDSCH mapping type value corresponding to the index can be set. Here, the K0 value is a value that determines the slot in which the PDSCH is scheduled, and the slot in which the PDSCH is scheduled Is can be determined as, where n is the index of the slot in which the DCI format is received, and can be the subcarrier spacing of the PDSCH and the subcarrier spacing of the PDCCH. The SLIV value is the slot in which the PDSCH is scheduled. The start symbol and consecutive symbols for which the PDSCH is scheduled can be indicated. And the PDSCH mapping type can indicate the DMRS location of the PDSCH.

[0328] Information on the frequency domain in which the PDSCH is scheduled can be indicated in the Frequency domain resource assignment (FDRA) field of the DCI format. More specifically, the FDRA field can define an FDRA type for each DCI format. In the case of DCI format 1_0 monitored in the common search space, the FDRA field can indicate a Resource indicator value (RIV) value generated based on FDRA type 1. The UE can obtain information on the index (S) of the first RB in which the PDSCH is scheduled in the frequency domain and the number (L) of consecutive RBs from the RIV. Here, S=0,1,…, -1, and L=1,2,…, It could be. Here can be one of the following values:

[0329] - If CORESET 0 is set in a cell where PDSCH is scheduled, it may be the size of CORESET 0 (the number of RBs included in CORESET 0).

[0330] - If CORESET 0 is not set for a cell where a PDSCH is scheduled, it may be the size of the initial DL BWP (the number of RBs included in the initial DL BWP). The initial DL BWP may be set by the upper layer signal initialDownlinkBWP from the base station. Alternatively, the initial DL BWP may be determined from the start PRB to the last PRB in the frequency axis of the CORESET associated with the Type0-PDCCH CSS set.

[0331] In the following description, the terminal can receive the PDCCH in the CORESET set to the active DL BWP. Here, the active DL BWP is It can contain PRBs. The PRBs of the active DL BWP can be indexed in ascending order of the frequency axis. The index of the lowest PRB in the frequency axis among the PRBs of the active DL BWP is 0, and the indexes of the PRBs can increase by 1 along the frequency axis.

[0332] Unless otherwise specified in the following description, the index of a PRB refers to the index of the PRBs within the active DL BWP.

[0333] In the following description, the index of the RB that overlaps with the starting PRB of CORESET (the lowest PRB on the frequency axis) among the PRBs of the active DL BWP is It can be said that.

[0334] The terminal may receive DCI format 1_0 in the common search space and determine the index (S) of the first PRB for which the PDSCH is scheduled and the number of consecutive RBs (L). The terminal may determine the PRB corresponding to S=0. If DCI format 1_0 is received in the common search space, the terminal may determine the PRB corresponding to S=0 as the PRB with the lowest frequency axis among the PRBs occupied by the CORESET associated with the common search space. ) can be determined. That is, when DCI format 1_0 is received in a common search space, the indexing or numbering of RBs for FDRA field interpretation can be determined in ascending order of frequency from the lowest PRB on the frequency axis of the CORESET associated with the common search space.

[0335] If the terminal receives DCI format 1_0 in the common search space and obtains the start index (S) of the scheduled PRB and the number of consecutive PRBs (L), then among the PRBs included in the active DL BWP, the index is S + From PRB in, L PRBs, i.e., the index , , … , PRBs can be judged as scheduled PRBs.

[0336] FIG. 13 is a diagram illustrating frequency domain scheduling based on DCI format 1_0 received in a common search space according to one embodiment of the present disclosure.

[0337] Referring to Figure 13, the terminal PRBs, can be set to PRBs. The index of the starting PRB (the lowest PRB in the frequency axis) of the CORESET in which DCI format 1_0 is received ( )Is It can be. The DCI format 1_0 received by the terminal in the common search space can include the index (S) of the starting PRB with scheduling information, S=1, and the number of consecutive PRBs (L) with L=3. The terminal can include the active DL BWP. Among the PRBs of the dog, the index is Starting from PRB 1, L=3 PRBs, that is, PRBs with indices 2, 3, and 4 can be determined as scheduled PRBs.

[0338] Referring to Fig. 13, DCI format 1_0 received in the common search space can schedule PDSCH in some PRBs among the active DL BWPs, but cannot schedule PDSCH in other PRBs. Here, the PRBs that can be scheduled are included in the active DL BWP. Among the PRBs of dogs It can be the same as PRBs. PRBs that can be scheduled here have an index , , … , It could be.

[0339] FIG. 14 is a diagram illustrating a PDSCH scheduled based on DCI format 1_0 detected in a common search space according to an embodiment of the present disclosure.

[0340] Referring to Fig. 14, the starting PRB (the lowest PRB on the frequency axis) of the CORESET in which DCI format 1_0 is detected may overlap with the UL subband on the frequency axis. In addition, PRBs that can be scheduled from the starting PRB of the CORESET (with an index , , … , ) can all overlap with the UL subband on the frequency axis. Therefore, the terminal cannot schedule the PDSCH because all PRBs that can be scheduled from the start PRB of the CORESET overlap with the UL subband.

[0341] For reference, the terminal can receive the PDCCH in the CORESET. This is because the CORESET can be received in a downlink symbol for which the UL subband is not configured. All PRBs in the downlink symbol are PRBs capable of downlink reception. Even if the CORESET is received in an SBFD symbol (a symbol for which a DL subband or a UL subband is configured), the PDCCH can be received. This is because the terminal can receive the PDCCH if the time-frequency resource to which the PDCCH is mapped is included only in the DL subband. Here, the PRBs included in the DL subband of the SBFD symbol are PRBs capable of downlink reception.

[0342] As illustrated in Fig. 14, DCI format 1_0 detected in the common search space cannot schedule PDSCH in the SBFD symbol (a symbol configured with a DL subband or an UL subband). A method for resolving this is disclosed.

[0343] [Method 1]

[0344] When a terminal determines frequency domain allocation information based on scheduling information, it can apply an offset value.

[0345] More specifically, before the terminal applies the offset value, the PRBs that can be scheduled are the starting PRB (index) of the CORESET. )from These are the PRBs of the dog. That is, the index is , , … , These are the RBs.

[0346] Here, the terminal can apply an offset value. When the terminal applies an offset value, the PRBs that can be scheduled are PRBs (indexes) shifted by the offset value from the starting PRB of the CORESET. )from These are the PRBs of the dog. That is, the index is , , … , These are the RBs.

[0347] When a terminal receives DCI format 1_0 in a common search space, the terminal can obtain the index (S) of the start PRB of the PDSCH scheduled from the DCI format 1_0 and the number (L) of consecutive PRBs. The terminal can obtain the start PRB index (of the CORESET) ) and the offset value, the index of the starting PRB within the active DL BWP. can be determined. And, L PRBs from the above starting PRB can be determined as PRBs scheduled on the PDSCH. That is, if the index , , … , The PRBs may be PRBs scheduled on the PDSCH.

[0348] Here, the offset value can be an integer. Additionally, the offset value can be a non-negative integer. Additionally, the offset value can be a natural number.

[0349] As an example of how a terminal determines an offset value, the terminal can explicitly receive an offset value from a base station. Here, the offset value can be included in a system information block, an RRC (Radio Resource Control) signal, a MAC-CE signal, or DCI format 1_0. The terminal can determine the PRBs for which the PDSCH is scheduled based on the offset value.

[0350] When a terminal explicitly receives an offset value from a base station, the terminal can receive an offset value for each CORESET from the base station. Each CORESET can be allocated different resources in the frequency axis. Therefore, the terminal can receive an offset value corresponding to the frequency resource allocation of the CORESET. The terminal can determine a CORESET for which DCI format 1_0 has been received, and determine PRBs allocated to a PDSCH scheduled by DCI format 1_0 based on the offset value associated with the CORESET. If the terminal does not receive an offset value for a CORESET, the offset value for the CORESET can be regarded as 0.

[0351] When a terminal explicitly receives an offset value from a base station, the terminal can receive an offset value for each symbol or symbol type from the base station. That is, the terminal can set an offset value suitable for a specific symbol or a specific symbol type. For example, an appropriate offset value can be set for an SBFD symbol (a symbol for which a DL subband or an UL subband is set) based on the setting of the DL subband. If the terminal does not receive an offset value for a specific symbol or a specific symbol type, the offset value for the specific symbol or the specific symbol type can be regarded as 0.

[0352] As another example of how a terminal determines an offset value, the terminal can implicitly obtain the offset value based on the settings received from the base station. More specifically, the terminal can implicitly obtain the offset value based on the DL subband settings received from the base station.

[0353] For example, the terminal selects the index of the PRB that overlaps with the start PRB of the DL sub-band among the PRBs included in the active DL BWP. It can be said that the offset value of the terminal class can be determined based on. More specifically, the offset value is According to the present embodiment, the PRBs that can be scheduled by the DCI format 1_0 detected in the common search space have an index , , … , ) may be. That is, the index of the start PRB (the lowest PRB in the frequency axis) of PRBs that can be scheduled by the DCI format 1_0 detected in the common search space may be the same as the start PRB of the DL subband.

[0354] In one embodiment of the present disclosure, a terminal may be configured with up to two downlink DL subbands in an SBFD symbol. In this case, the terminal selects one of the two downlink DL subbands, (The index of the starting PRB of the selected DL sub-band) can be determined. Here, the method for selecting one DL sub-band can be as follows.

[0355] In one method, the terminal can select a DL subband located on the lower side of the frequency axis. When two DL subbands are configured, the terminal can distinguish between the two DL subbands on the frequency axis. This is because, in SBFD operation, the subbands are configured so as not to overlap on the frequency axis. Alternatively, the terminal can select a DL subband located on the higher side of the frequency axis.

[0356] In one method, the terminal can select a DL subband that contains more RBs among the two DL subbands.

[0357] In one method, the terminal can select a DL subband that overlaps with the CORESET for which DCI format 1_0 is received. If there is one DL subband that overlaps with the CORESET, the terminal can select the DL subband that overlaps with the CORESET. If there are two DL subbands that overlap with the CORESET, the terminal can select one of the two DL subbands. For example, if there are two DL subbands that overlap with the CORESET, the terminal can select the DL subband located on the lower side of the frequency axis. In another example, if there are two DL subbands that overlap with the CORESET, the terminal can select the DL subband located on the higher side of the frequency axis. If there is no DL subband that overlaps with the CORESET, the terminal can select one of the two configured DL subbands. For example, if there is no DL subband that overlaps with the CORESET, the terminal can select the DL subband located on the lower side of the frequency axis. As another example, if there is no DL subband overlapping with CORESET, the terminal may select a DL subband located higher on the frequency axis.

[0358] In one method, the terminal may select a DL subband that overlaps with the lowest PRB of the CORESET that received DCI format 1_0. If there is no DL subband that overlaps with the lowest PRB of the CORESET that received DCI format 1_0, the terminal may select a DL subband located lower on the frequency axis. For example, if there is no DL subband that overlaps with the lowest PRB of the CORESET that received DCI format 1_0, the terminal may select a DL subband located lower on the frequency axis. In another example, if there is no DL subband that overlaps with the lowest PRB of the CORESET that received DCI format 1_0, the terminal may select a DL subband located higher on the frequency axis.

[0359] In one method, a terminal can be instructed to select one of two DL subbands configured by a base station. The terminal must always select the indicated DL subband. Here, the base station can instruct one DL subband as follows.

[0360] A terminal can be configured with indices for two DL sub-bands from a base station. The indices can be 0 or 1. If the terminal does not configure indices of separate DL sub-bands from the base station, the terminal can determine the index of a lower DL sub-band as 0 and the index of a higher DL sub-band as 1 on the frequency axis. The base station can indicate the index 0 or 1 of the DL sub-band to the terminal. The indication can be included in a higher layer signal (RRC signal) transmitted from the base station to the terminal or an L1 signal (DCI format 1_0 for scheduling PDSCH) transmitted from the base station to the terminal. The terminal can select one DL sub-band based on the indices configured for the DL sub-bands and the indicated index.

[0361] A method for determining the offset value, the offset value is According to the present embodiment, the PRBs that can be scheduled by the DCI format 1_0 detected in the common search space have the following indices.

[0362] if, On the other hand,

[0363] if, On the other hand,

[0364] in other words, In this case, the index of the start PRB (the lowest PRB in the frequency axis) of the PRBs that can be scheduled by the DCI format 1_0 detected in the common search space may be the same as the start PRB of the DL subband. And, In this case, the index of the start PRB (the lowest PRB in the frequency axis) of PRBs that can be scheduled by the DCI format 1_0 detected in the common search space may be the same as the start PRB of the CORESET.

[0365] As a method of determining an offset value, the offset value can be selectively applied based on the presence or number of PRBs that can be scheduled. More specifically, the terminal can determine PRBs that can be scheduled by the DCI format 1_0 detected in the common search space without applying the offset value (or applying 0 as the offset value). The indexes of the PRBs are { , , … , } may be. The terminal may determine the PRBs on which the PDSCH can be scheduled among the PRBs. For example, if the PDSCH is scheduled in the SBFD symbol, the PRBs that can be scheduled may be PRBs included in the DL subband.

[0366] The terminal can decide whether to apply an offset value based on the number of PRBs that can be scheduled. For example, if the number of PRBs that can be scheduled is less than or equal to a certain number (T), the terminal can apply an offset value. Here, the offset value is PRBs that can be scheduled according to the above offset value are { , , … , } may be. If the number of PRBs that can be scheduled is greater than a certain number (T), the offset value may not be applied.

[0367] In the above embodiment, the terminal determines whether to apply an offset value variably depending on the number of PRBs that can be scheduled. Here, T can be determined as follows.

[0368] For example, T may be 0, i.e., if there is no PRB that can be scheduled, the terminal may apply an offset value.

[0369] For example, T may be a value set by the base station. The base station may set the minimum number of PRBs for which DCI format 1_0 must be scheduled. The terminal may determine whether to apply an offset value based on T.

[0370] For example, T may be a value corresponding to the size of the CORESET. For example, T may be half of the CORESET (half the number of RBs included in the CORESET). That is, the terminal may apply an offset value if the number of PRBs that can be scheduled is less than at least half of the CORESET.

[0371] In the above-described embodiment, That is, the index of the starting PRB of the DL subband set by the terminal may be 0 (the lowest PRB in the active DL subband).

[0372] FIG. 15 is a diagram showing an offset value applied to DCI format 1_0 of a common search space according to an embodiment of the present disclosure.

[0373] Referring to Figure 15, the terminal is set to an offset value. can be applied. Therefore, the starting PRB of CORESET (the lowest PRB on the frequency axis) and from the PRB Although the PRBs of the dog are PRBs for which PDSCH cannot be scheduled, to avoid this, the index From PRB PDSCH can be scheduled on the PRBs of the above The PRBs of the dog may be PRBs on which PDSCH can be scheduled.

[0374] FIG. 16 is a flowchart illustrating an embodiment of the present disclosure.

[0375] At step 1600, the terminal can receive a CORESET and common search space from the base station. The terminal can monitor and receive DCI format 1_0 in the configured CORESET and common search space. The CRC of DCI format 1_0 can be scrambled with C-RNTI, CS-RNTI, MCS-C-RNTI, SI-RNTI, P-RNTI, etc., and the DCI format 1_0 can schedule the PDSCH.

[0376] At step 1601, the terminal receives the starting PRB index ( ) of the CORESET that received DCI format 1_0. ) and the index of the starting PRB of the DL sub-band ( ) can be used to determine the offset value using the methods described above. For example, the offset value is Offset = This may be the case. If the terminal receives multiple DL subbands from the base station, the terminal may select one DL subband. For example, the lower DL subband on the frequency axis may be selected.

[0377] At step 1602, the terminal can determine schedulable PRBs based on the determined offset value. The terminal can determine the PRBs whose index is { , ,..., } can be determined as schedulable PRBs. For example, if the offset value is Offset = If so, { , ,...,} may be.

[0378] At step 1603, the terminal can determine the PRBs to be scheduled by interpreting the frequency domain resource assignment information of DCI format 1_0 based on the schedulable PRBs. In the frequency domain resource assignment of DCI format 1_0, if the index (S) of the starting PRB is 0 (S=0), it may be the PRB with the lowest index among the schedulable PRBs.

[0379] At step 1604, the terminal can receive PDSCH in scheduled PRBs.

[0380] In the above example, the terminal starts PRB (index) of CORESET. The offset value set in was applied. That is, in the example described above, the reference start PRB of the terminal has an index may be a PRB. According to the present disclosure, an offset value is an example for determining a reference start PRB, and in addition to a method of setting or determining an offset value to determine a reference start PRB, a terminal may also set a reference start PRB index (i.e., The corresponding index) can be explicitly set or implicitly determined from other setting information. For example, the offset value In this embodiment, the terminal has a reference start PRB index, It can be set explicitly or implicitly determined from SBFD setting information.

[0381] [DCI Length Alignment]

[0382] To reduce the complexity of blind decoding of NR terminals, the number of DCI formats of different lengths is fixed. For example, DCI formats scrambled with C-RNTI are allowed up to three different lengths, and a total of four DCI format lengths are allowed. For example, a terminal can monitor up to three different lengths of DCI using C-RNTI, and can additionally monitor one additional DCI (length) using a special purpose RNTI (e.g., SFI-RNTI, INT-RNTI, etc.). This can be called DCI size budget (or DCI budget 3+1).

[0383] If the number of DCI formats of different lengths monitored by an NR terminal exceeds the DCI size budget, the terminal can adjust the lengths of some DCI formats to be the same. This series of processes can be referred to as DCI size alignment. An example of the DCI length alignment process can be as follows.

[0384] Step 0:

[0385] ● Determine the DCI format 0_0 monitored in the common search space (CSS) according to section 7.3.1.1.1 of 3GPP standard document TS38.212. Here, is the size of the initial UL BWP.

[0386] ● Determine the DCI format 1_0 monitored in the common search space according to section 7.3.1.2.1 of 3GPP standard document TS38.212. Here is the size of CORESET 0 if CORESET 0 is configured in the cell, or the size of the initial DL BWP if CORESET 0 is not configured in the cell.

[0387] ● If DCI format 0_0 is monitored in the common search space and the number of information bits before padding of DCI format 0_0 is less than the length of DCI format 1_0 monitored in the common search space for scheduling of the same serving cell, some zero padding bits are generated for DCI format 0_0 to convert its length to be the same as DCI format 1_0.

[0388] ● If DCI format 0_0 is monitored in the common search space and the number of information bits before padding of DCI format 0_0 is greater than the length of DCI format 1_0 monitored in the common search space for scheduling the same serving cell, the most significant bits (MSBs) of the frequency domain resource allocation field in DCI format 0_0 are truncated so that the size of DCI format 0_0 becomes the same as the size of DCI format 1_0.

[0389] Step 1:

[0390] ● Size of Active UL BWP Determine the DCI format 0_0 monitored in the UE specific search space (USS).

[0391] ● The size of Active DL BWP Determine the DCI format 1_0 monitored in the UE-specific search space.

[0392] ● For a UE configured with supplementaryUplink in the cell's ServingCellConfig, if PUSCH is configured to be transmitted on both the SUL and non-SUL of the cell and the number of information bits of DCI format 0_0 in the UE-specific search space for SUL is not equal to the number of information bits of DCI format 0_0 in the UE-specific search space for non-SUL, some zero padding bits are generated for the smaller DCI format 0_0 until its length is equal to that of the larger DCI format 0_0.

[0393] ● If DCI format 0_0 is monitored in the UE-specific search space and the number of information bits of DCI format 0_0 before padding is less than the length of DCI format 1_0 monitored in the UE-specific search space scheduled for the same serving cell, some zero padding bits are generated for DCI format 0_0.

[0394] ● If DCI format 1_0 is monitored in the UE-specific search space and the number of information bits of DCI format 1_0 before padding is less than the length of DCI format 0_0 monitored in the UE-specific search space scheduled for the same serving cell, zeros are added to adjust the length of DCI format 1_0 until it becomes equal to DCI format 0_0.

[0395] Step 2:

[0396] ● DCI format 0_1 ​​monitored in the search space per UE is determined according to section 7.3.1.1.2 of 3GPP standard document TS38.212.

[0397] ● DCI format 1_1 monitored in the search space per UE is determined according to section 7.3.1.2.2 of 3GPP standard document TS38.212.

[0398] ● For a UE configured with supplementaryUplink in the cell's ServingCellConfig, if PUSCH is configured to be transmitted on both the SUL and non-SUL of the cell and the number of information bits in the DCI format 0_1 ​​of the SUL is not equal to the number of information bits in the DCI format 0_1 ​​of the non-SUL, the smaller DCI format 0_1 ​​is converted to the same length as the larger DCI format 0_1 ​​by adding 0 to it.

[0399] ● If the size of DCI format 0_1 ​​monitored in the search space per UE is the same as the size of DCI format 0_0 / 1_0 monitored in another search space per UE, add a 1-bit padding bit of '0' to DCI format 0_1.

[0400] ● If the size of DCI format 1_1 monitored in the search space per UE is the same as the size of DCI format 0_0 / 1_0 monitored in another search space per UE, add a 1-bit padding bit of '0' to DCI format 1_1.

[0401] Step 2A:

[0402] ● Determine the DCI format 0_2 to be monitored in the search space per UE according to section 7.3.1.1.3 of 3GPP standard document TS38.212.

[0403] ● Determine the DCI format 1_2 to be monitored in the search space per UE according to section 7.3.1.2.3 of 3GPP standard document TS38.212.

[0404] ● For UEs configured with supplementaryUplink in the cell's ServingCellConfig, if PUSCH is configured to be transmitted on both SUL and non-SUL of the cell and the number of information bits in DCI format 0_2 of SUL is not equal to the number of information bits in DCI format 0_2 of non-SUL, padding is added by adding '0' for the smaller DCI format 0_2 until its length is equal to that of the larger DCI format 0_2.

[0405] Step 3:

[0406] ● The DCI length alignment procedure is complete if both of the following conditions are met:

[0407] ○ If the total number of different DCI sizes to be monitored in the cell is 4 or less

[0408] ○ If the total number of different DCI sizes configured with C-RNTI in the cell is 3 or less

[0409] Step 4:

[0410] ● Otherwise

[0411] Step 4A:

[0412] ● Remove padding bits (if any) introduced in step 2.

[0413] ● Determine the DCI format 1_0 monitored in the terminal-specific search space according to section 7.3.1.2.1 of 3GPP standard document TS38.212. Here is the size of CORESET 0 if CORESET 0 is configured in the cell, or the size of the initial DL BWP if CORESET 0 is not configured in the cell.

[0414] ● Determine the DCI format 0_0 monitored in the terminal-specific search space according to section 7.3.1.1.1 of 3GPP standard document TS38.212. Here, is the size of the initial UL BWP.

[0415] ● If the length (before padding) of DCI format 0_0 monitored in the UE-specific search space is less than the number of information bits of DCI format 1_0 monitored in the UE-specific search space to schedule the same serving cell, add some zero padding bits in DCI format 0_0 until the length becomes the same as that monitored in DCI format 1_0.

[0416] ● If the number of information bits of DCI format 0_0 monitored in the search space per UE (before truncation) is greater than the number of information bits of DCI format 1_0 monitored in the search space per UE for scheduling the same serving cell, some bits of the MSB (Most Significant Bit) of the frequency domain resource allocation field of DCI format 0_0 are reduced. The size of DCI format 0_0 is converted to be the same as the size of DCI format 1_0 monitored in the search space per UE.

[0417] Step 4B:

[0418] ● If the total number of other DCI lengths to be monitored in the cell after applying the above steps is 4 or more, or the total number of other DCI lengths with C-RNTI configured is 3 or more,

[0419] ○ If the number of information bits of DCI format 0_2 before padding is less than the length of DCI format 1_2 for scheduling the same serving cell, a certain number of zero padding bits are added to DCI format 0_2 until the length becomes the same as that of DCI format 1_2.

[0420] ○ If the number of information bits of DCI format 1_2 before padding is less than the length of DCI format 0_2 for scheduling the same serving cell, a certain number of zero padding bits are added to DCI format 1_2 until the length becomes the same as that of DCI format 0_2.

[0421] Step 4C:

[0422] ● If the total number of other DCI lengths to be monitored in the cell is 4 or more after applying the above steps, or the total number of other DCI lengths configured with C-RNTI is 3 or more

[0423] ○ If the number of information bits of DCI format 0_1 ​​before padding is less than the length of DCI format 1_1 for scheduling the same serving cell, a certain number of zero padding bits are added to DCI format 0_1 ​​until the length becomes the same as that of DCI format 1_1.

[0424] ○ If the number of information bits of DCI format 1_1 before padding is less than the length of DCI format 0_1 ​​for scheduling the same serving cell, a certain number of zero padding bits are added to DCI format 1_1 until the length becomes the same as that of DCI format 0_1.

[0425] FIG. 17 is a diagram illustrating an example of a DCI length alignment method applicable to one embodiment of the present disclosure. The DCI length alignment method illustrated in FIG. 17 is a more specific example of an example of the DCI length alignment process described above, and more specific details can be found in the description described above. In the following description, it can be understood that the terminal having a DCI format length means that the terminal is set to monitor a DCI format of the corresponding length.

[0426] Referring to Fig. 17(a), after step 3, the lengths of different DCI formats that the terminal has are the lengths (Size A) for DCI format 0_0 and DCI format 1_0 monitored by CSS, the lengths (Size B) for DCI format 0_0 and DCI format 1_0 monitored by USS, the length of DCI format 0_1 ​​(Size C), the length of DCI format 1_1 (Size D), the length of DCI format 0_2 (Size E), and the length of DCI format 1_2 (Size F). Therefore, the terminal has the lengths of up to six different DCI formats.

[0427] Referring to FIG. 17(b), in step 4A, the length (Size B) for DCI format 0_0 and DCI format 1_0 that the terminal monitors in the USS can be adjusted to be the same as the length (Size A) for DCI format 0_0 and DCI format 1_0 that the terminal monitors in the CSS. Accordingly, Size B can be adjusted to satisfy Size A = Size B. Accordingly, after step 4A, the terminal can have up to five DCI formats with different lengths.

[0428] Referring to Fig. 17(c), in step 4B, the length (Size E) of DCI format 0_2 and the length (Size F) of DCI format 1_2 can be made identical. If the length (Size F) of DCI format 1_2 is longer, the length (Size E) of DCI format 0_2 can be converted to the length (Size F) of DCI format 1_2. That is, Size F = Size E can be satisfied. Therefore, after step 4B, the terminal can have up to four DCI formats with different lengths.

[0429] Referring to Fig. 17(d), in step 4C, the length (Size C) of DCI format 0_1 ​​and the length (Size D) of DCI format 1_1 can be made identical. If the length (Size D) of DCI format 1_1 is longer, the length (Size C) of DCI format 0_1 ​​can be converted to the length (Size D) of DCI format 1_1. That is, Size D = Size C can be satisfied. Therefore, after step 4C, the terminal can have up to three DCI formats with different lengths.

[0430] In this way, a terminal can have up to three different DCI formats (scrambled with C-RNTI).

[0431] <Example 2: DCI format 1_0 detected in terminal-specific search space>

[0432] The terminal can monitor DCI format 1_0 in a specific search space. DCI format 1_0 may have CRC scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI. The DCI format 1_0 may schedule a PDSCH and may include an FDRA field indicating PRBs allocated for the PDSCH.

[0433] Information about the frequency domain in which the PDSCH is scheduled can be indicated in the Frequency domain resource assignment (FDRA) field of the DCI format. More specifically, the FDRA field can define an FDRA type for each DCI format. In the case of DCI format 1_0 monitored in a terminal-specific search space, the FDRA field can indicate a Resource indicator value (RIV) value generated based on FDRA type 1. The terminal can obtain information about the index (S) of the first RB in which the PDSCH is scheduled in the frequency domain and the number of consecutive RBs (L) from the RIV.

[0434] Referring to FIG. 17, the terminal may perform a DCI length alignment process. According to the DCI length alignment process, if the size of the DCI format 1_0 monitored in the terminal-specific search space is not derived from the size of the DCI format 1_0 monitored in the common search space (i.e., if Step 4A is not applied), the terminal may obtain the index (S) of the first RB scheduled by the PDSCH in the frequency domain and the number of consecutive RBs (L) from the RIV value as follows. S=0,1,…, -1, and L=1,2,…, It could be. Here may be the number of PRBs included in the active DL BWP. Here, the length of the FDRA field is It could be.

[0435] According to the above DCI length alignment process, if the size of DCI format 1_0 monitored in the terminal-specific search space is derived from the size of DCI format 1_0 monitored in the common search space, the terminal can obtain the index (S) of the first RB scheduled by PDSCH in the frequency domain and the number of consecutive RBs (L) from the RIV value as follows. S=0,K,2*K,…,K*( -1) and L=K,2*K,…,K* It could be. If CORESET0 is set, it can be the size of CORESET0 (the number of PRBs included in CORESET0) or the size of the initial DL BWP (the number of PRBs included in the initial DL BWP) if CORESET0 is not set. Here, the length of the FDRA field is It could be.

[0436] According to the above DCI length alignment process, if the size of DCI format 1_0 monitored in the terminal-specific search space is derived from the size of DCI format 1_0 monitored in the common search space, RIV can be defined as in Table 19.

[0437] [Table 19]

[0438]

[0439] Here, the value of K can be defined as follows:

[0440] if, , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1.

[0441] In the present disclosure, the set of possible values ​​for the K value may be {1,2,4,8} or a set of other values ​​(e.g., {1,2,4,6,8,10,12}). FIG. 18 is a diagram illustrating scheduled PRBs when the size of DCI format 1_0 monitored in a terminal-specific search space is derived from the size of DCI format 1_0 monitored in a common search space according to a DCI length alignment process.

[0442] In the example of Fig. 18, the terminal PRBs, It can be set as PRBs. The terminal starts from DCI format 1_0. The FDRA field of bit length can be obtained. The RIV value can be obtained from the FDRA field, and the S' value (S'=1) and the L' value (L'=3) can be obtained with reference to Table 19. In addition, the terminal can obtain the K value (K=2). Based on the S' value, the L' value, and the K value, the terminal can obtain the index of the first RB (S=S'*K=2) in which the PDSCH is scheduled in the frequency domain and the number of consecutive RBs (L=L'*S=6). In Fig. 18, the terminal can determine the PRBs with indices {2,3,4,5,6,7} as PRBs in which the PDSCH is scheduled by the DCI format 1_0 detected in the terminal-specific search space.

[0443] Referring to Fig. 18, PRBs for which PDSCH can be scheduled by DCI format 1_0 detected in a terminal-specific search space may have indices {0,1,2,3,4,5,6,7,8,9,10,11}. The terminal may schedule some or all of the PRBs in units of two PRBs. In addition, the terminal cannot schedule PRBs with indices {12,13} by DCI format 1_0 detected in the terminal-specific search space.

[0444] In general, PRBs for which PDSCH can be scheduled by DCI format 1_0 detected in a terminal-specific search space have indices {0,1,…}. } may be. The terminal may schedule some or all of the PRBs in units of K PRBs. And, the terminal may schedule the PRBs in units of K PRBs with an index of { } PRBs cannot be scheduled in DCI format 1_0 detected in the terminal-specific search space.

[0445] FIG. 19 is a diagram illustrating DCI format 1_0 of a terminal-specific search space according to one embodiment of the present disclosure.

[0446] Figure 19(a) shows an example in which the terminal determines the K value as 1. Accordingly, PRBs for which PDSCH can be scheduled by DCI format 1_0 detected in the terminal-specific search space have indices {0, 1,…}. } may be. Therefore, the terminal is included in the active DL BWP. PRBs of the dog (index {0,1,…) }) in the low frequency axis PRBs of the dog (index {0,1,…) }) is used for scheduling, and is high in the frequency axis. The PRBs of the dog cannot be scheduled. In Fig. 19(a), the indices are {0,1,… } may be PRBs that cannot be used for PDSCH. For example, the PRBs may be included in UL subbands or guardbands. Therefore, the terminal cannot schedule the PDSCH according to the DCI format 1_0 detected in the terminal-specific search space.

[0447] Figure 19(b) shows an example in which the terminal determines the K value to be one greater than the value (e.g., K=2). Accordingly, PRBs for which PDSCH can be scheduled by DCI format 1_0 detected in the terminal-specific search space have indices {0,1,…}. } may be. Therefore, the terminal is included in the active DL BWP. PRBs of the dog (index {0,1,…) }) in the low frequency axis PRBs of the dog (index {0,1,…) }) is used for scheduling, and is high in the frequency axis. The PRBs of the dog cannot be scheduled. In Fig. 19(b), the indices are {0,1,… } may be PRBs that cannot be used for PDSCH. For example, the PRBs may be included in UL subbands or guardbands. Therefore, the terminal cannot schedule the PDSCH according to the DCI format 1_0 detected in the terminal-specific search space.

[0448] A method for solving the above problem is disclosed. Unless otherwise specified in the following description, the size of DCI format 1_0 of the terminal-specific search space may be derived from DCI format 1_0 of the common search space according to DCI length alignment.

[0449] [Method 2]

[0450] When a terminal determines frequency domain allocation information based on scheduling information, it can apply an offset value.

[0451] More specifically, before the terminal applies the offset value, the PRBs that can be scheduled are PRBs starting from the PRB with index 0. These are the PRBs of the dog. That is, the indices are 0, 1, ..., These are the RBs.

[0452] The terminal can apply an offset value when calculating the S value. When the terminal applies an offset value, the PRBs that can be scheduled are shifted by the offset value, starting from the PRB (index Offset). These are PRBs of dogs. That is, the indices are Offset, Offset+1, ..., Offset+ These are the RBs.

[0453] When a terminal receives DCI format 1_0 in a terminal-specific search space, the terminal can obtain an index (S=S'*K+Offset) of a start PRB of a PDSCH scheduled from the DCI format 1_0 and the number of consecutive PRBs (L=L'*K) based on an offset value. The terminal can determine an index S=S'*K+Offset of a start PRB within an active DL BWP based on the offset value. Then, L PRBs from the start PRB can be determined as PRBs scheduled for the PDSCH. That is, PRBs having indices {S, S+1, ..., S+L-1} or {S'*K+Offset, S'*K+Offset, S'*K+Offset+1, ..., S'*K+Offset+L-1} can be PRBs scheduled for the PDSCH.

[0454] Here, the offset value can be an integer. Additionally, the offset value can be a non-negative integer. Additionally, the offset value can be a natural number. Here, the offset value can be an integer multiple of K.

[0455] The terminal can apply the offset value to S' (the index of the starting RB obtained from RIV). When the terminal applies the offset value, the PRBs that can be scheduled are shifted by the offset value, starting from the PRB (index Offset). These are PRBs of dogs. That is, the indices are K*Offset, K*(Offset+1), ..., K*(Offset+ -1) These are RBs.

[0456] When a terminal receives DCI format 1_0 in a terminal-specific search space, the terminal can obtain an index (S=(S'+Offset)*K) of a start PRB of a PDSCH scheduled from the DCI format 1_0 and the number of consecutive PRBs (L=L'*K) based on an offset value. The terminal can determine an index S=(S'+Offset)*K of a start PRB within an active DL BWP based on the offset value. Then, L PRBs from the start PRB can be determined as PRBs scheduled for the PDSCH. That is, PRBs having indices {S, S+1, ..., S+L-1} or {(S'+Offset)*K, (S'+Offset+1)*K, ..., (S'+Offset+L-1)*K} can be PRBs scheduled for the PDSCH.

[0457] Here, the offset value can be an integer. Additionally, the offset value can be a non-negative integer. Additionally, the offset value can be a natural number.

[0458] As an example of how a terminal determines an offset value, the terminal can explicitly receive an offset value from a base station. Here, the offset value can be included in a system information block, an RRC (Radio Resource Control) signal, a MAC-CE signal, or DCI format 1_0. The terminal can determine the PRBs for which the PDSCH is scheduled based on the offset value.

[0459] As another example of how a terminal determines an offset value, the terminal can implicitly obtain the offset value based on the settings received from the base station. More specifically, the terminal can implicitly obtain the offset value based on the DL subband settings received from the base station.

[0460] For example, the terminal selects the index of the PRB that overlaps with the start PRB of the DL sub-band among the PRBs included in the active DL BWP. It can be said that the offset value of the terminal can be determined based on. More specifically, the offset value is Offset= According to the present embodiment, the PRBs that can be scheduled by the DCI format 1_0 detected in the terminal-specific search space have an index , , … , That is, the index of the start PRB (the lowest PRB in the frequency axis) of PRBs that can be scheduled by the DCI format 1_0 detected in the terminal-specific search space may be the same as the start PRB of the DL sub-band.

[0461] In one embodiment of the present disclosure, a terminal may be configured with up to two downlink DL subbands in an SBFD symbol. In this case, the terminal selects one of the two downlink DL subbands, (The index of the starting PRB of the selected DL sub-band) can be determined. Here, the method for selecting one DL sub-band can be as follows.

[0462] In one method, the terminal can select a DL subband located on the lower side of the frequency axis. When two DL subbands are configured, the terminal can distinguish between the two DL subbands on the frequency axis. This is because, in SBFD operation, the subbands are configured so as not to overlap on the frequency axis. Alternatively, the terminal can select a DL subband located on the higher side of the frequency axis.

[0463] In one method, the terminal can select a DL subband that contains more RBs among the two DL subbands.

[0464] A terminal can be configured with indices for two DL sub-bands from a base station. The indices can be 0 or 1. If the terminal does not configure indices of separate DL sub-bands from the base station, the terminal can determine the index of a lower DL sub-band as 0 and the index of a higher DL sub-band as 1 on the frequency axis. The base station can indicate the index 0 or 1 of the DL sub-band to the terminal. The indication can be included in a higher layer signal (RRC signal) transmitted from the base station to the terminal or an L1 signal (DCI format 1_0 for scheduling PDSCH) transmitted from the base station to the terminal. The terminal can select one DL sub-band based on the indices configured for the DL sub-bands and the indicated index.

[0465] When a terminal selects a single DL subband, it can assume that the terminal can schedule a PDSCH only on that single DL subband in DCI format 1_0 of the terminal-specific search space. To achieve this, the terminal can determine the K value as follows.

[0466] if, , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of active DL BWPs and PRBs included in the DL subbands.

[0467] When a terminal selects a DL subband, if the selected DL subband is a lower DL subband in the frequency domain, the terminal can assume that it can schedule PDSCHs across both DL subbands in DCI format 1_0 of the terminal-specific search space. To this end, the terminal can determine the K value as follows.

[0468] if, , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of active DL BWP and PRBs included in the first DL subband, is the number of PRBs included in the active DL BWP and the second DL subband.

[0469] When scheduling a PDSCH across two DL subbands, the PRB indices may be reassigned. That is, the PRBs included in the DL subbands may be indexed in ascending frequency order. The indices may be assigned sequentially, starting from 0. Furthermore, it can be assumed that the PRBs scheduled by DCI format 1_0 follow the newly assigned indices.

[0470] The terminal can determine the K value based on the determined offset value. For example, if , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of PRBs included in the active DL BWP in ascending order of the frequency axis, starting from the PRB corresponding to the offset value in the active DL BWP. That is, the index of the last PRB of the active DL BWP. If you say so, It could be.

[0471] FIG. 20 is a diagram showing an offset value applied to DCI format 1_0 of a terminal-specific search space according to an embodiment of the present disclosure.

[0472] Figure 20(a) shows an example in which the terminal determines the K value as 1. The terminal detects the PRBs for which the PDSCH can be scheduled by DCI format 1_0 detected in the terminal-specific search space and the index is You can start from, PRBs of dogs may be included.

[0473] Figure 20(b) shows an example in which the terminal determines the K value to be greater than 1 (K>1). The terminal detects the PRBs for which the PDSCH can be scheduled by DCI format 1_0 detected in the terminal-specific search space, and the index is You can start from, The PRBs of the dog may be included. Or, if If this is not a multiple of K, You can start from, PRBs of dogs may be included.

[0474] FIG. 21 is a diagram illustrating a flowchart according to one embodiment of the present disclosure.

[0475] At step 2100, the terminal can receive a terminal-specific search space and a DCI format to be monitored in the search space from the base station. Here, the DCI format to be monitored by the terminal may include DCI format 1_0. The terminal can receive DCI format 1_0 with the CRC scrambled with C-RNTI, MSC-C-RNTI, and CS-RNTI.

[0476] At step 2101, the terminal determines the index of the starting PRB of the DL subband ( ) can be used to determine the offset using the methods described above. Here, when multiple DL sub-bands are set for a terminal, the terminal can select one of the multiple DL sub-bands.

[0477] At step 2102, the terminal can determine the schedulable PRBs based on the determined offset value. For example, with the offset value If this is determined, the terminal will have an index of { , ,..., } can be determined as schedulable PRBs. Here, the K value can be determined as in the conventional technique, regardless of the offset value. That is, if , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of PRBs included in the active DL BWP.

[0478] At step 2103, the terminal can determine the PRBs to be scheduled by interpreting the frequency domain resource assignment information of DCI format 1_0 based on the schedulable PRBs. In the frequency domain resource assignment of DCI format 1_0, if the index (S) of the starting PRB is 0 (S=0), it may be the PRB with the lowest index among the schedulable PRBs. More specifically, S=S'*K+Offset or S=(S'+Offset)*K.

[0479] At step 2104, the terminal can receive PDSCH in scheduled PRBs.

[0480] FIG. 22 is a diagram illustrating a flowchart according to one embodiment of the present disclosure.

[0481] At step 2200, the terminal can receive a terminal-specific search space and a DCI format to be monitored in the search space from the base station. The DCI format to be monitored here may include DCI format 1_0. The terminal can receive DCI format 1_0 with the CRC scrambled with C-RNTI, MSC-C-RNTI, and CS-RNTI.

[0482] In step 2201, the terminal determines the index of the starting PRB of the DL subband ( ) can be used to determine the offset using the methods described above. Here, when multiple DL sub-bands are set for a terminal, the terminal can select one of the multiple DL sub-bands. In addition, the terminal can determine the K value based on the number of PRBs included in the selected DL sub-band.

[0483] In step 2202, the terminal can determine the schedulable PRBs based on the determined offset value. The terminal can determine the K value based on the determined offset value. For example, as the offset value If this is determined, the terminal will have an index of { , ,..., } can be determined as schedulable PRBs. Here, the value K may be determined based on the number of PRBs included in the selected DL subband. For example, if , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of PRBs included in the active DL BWP and DL subband. Alternatively, the K value can be determined based on the number of PRBs included in the DL BWP starting from the offset value. For example, if , K is a set of possible values ​​(e.g., {1,2,4,8}). is the maximum value that satisfies , otherwise, K=1. Here, is the number of PRBs included in the active DL BWP in ascending order of the frequency axis starting from the PRB corresponding to the offset value in the active DL BWP. That is, the index of the last PRB of the active DL BWP. If you say so, It could be.

[0484] At step 2203, the terminal can determine the PRBs to be scheduled by interpreting the frequency domain resource assignment information of DCI format 1_0 based on the schedulable PRBs. In the frequency domain resource assignment of DCI format 1_0, if the index (S) of the starting PRB is 0 (S=0), it may be the PRB with the lowest index among the schedulable PRBs. More specifically, S=S'*K+Offset or S=(S'+Offset)*K.

[0485] At step 2204, the terminal can receive PDSCH in scheduled PRBs.

[0486] In Embodiment 2 of the present disclosure, a method for interpreting frequency domain allocation information of DCI format 1_0 detected in a terminal-specific search space is provided. The contents described for DCI format 1_0 in the present disclosure can also be applied to DCI format 4_0 to DCI format 4_1. Here, DCI format 4_0 to DCI format 4_1 may be DCI formats that can schedule a PDSCH that a base station multicasts or broadcasts to multiple terminals. The DCI format 4_0 to DCI format 4_1 may have a CRC scrambled with G-RNTI, G-CS-RNTI, MCCH-RNTI, or multicast-MCCH-RNTI.

[0487] DCI format 4_0 to DCI format 4_1 may include RIV indicating frequency domain allocation information, like DCI format 1_0. The terminal may obtain the index (S) of the first RB where the PDSCH is scheduled in the frequency domain and the number of consecutive RBs (L) from the RIV value as follows. S=0,K,2*K,…,K*( ) and L=K,2*K,…,K* It could be. If CORESET0 is set, it can be the size of CORESET0 (the number of PRBs included in CORESET0) or the size of the initial DL BWP (the number of PRBs included in the initial DL BWP) if CORESET0 is not set. Here, the length of the FDRA field is It could be.

[0488] The RIV indicated in DCI format 4_0 or DCI format 4_1 can be defined as shown in Table 19. Here, the K value can be defined as follows.

[0489] if, , K is a set of possible values ​​(e.g., {1,2,4,6,8,10,12}). is the maximum value that satisfies , otherwise, K=1. Here, can be set from the base station to the terminal. is the number of PRBs included in the set of PRBs (Common frequency resource, CFR) for which a terminal can schedule PDSCH for multicast or broadcast purposes within an active DL BWP.

[0490] Embodiment 2 of the present disclosure can be applied to DCI formats 4_0 to 4_1. In this case, the active DL BWP can be replaced with CFR, Is can be replaced with

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

[0492] Referring to FIG. 23, the terminal may include a transceiver, which refers to a terminal receiving unit (2300) and a terminal transmitting unit (2310), a memory (not shown), and a terminal processing unit (2305, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2300, 2310), the memory, and the terminal processing unit (2305) of the terminal may operate. The terminal processing unit (2305, or processor) may control the operation of the terminal according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the terminal are not limited to the above-described examples. For example, the terminal may include more or fewer components than the above-described components. In addition, the terminal processing unit (2305), the terminal transmitting unit (2310), the terminal receiving unit (2300), and the memory may be implemented in the form of a single chip.

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

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

[0495] The memory can store programs and data necessary for the operation of the terminal. Furthermore, the memory can store control information or data included in signals transmitted and received by the terminal. The memory can be configured as a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories, and they can also store commands for performing the aforementioned communication method.

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

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

[0498] Referring to FIG. 24, the base station may include a transceiver, which refers to a base station receiver (2400) and a base station transmitter (2410), a memory (not shown), and a base station processor (2405, or a base station control unit or processor). According to the communication method of the base station described above, the transceiver units (2400, 2410), the memory, and the base station processor (2405) of the base station may operate. The base station processor (2405, or processor) may control the operation of the base station according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the base station are not limited to the above-described examples. For example, the base station may include more or fewer components than the above-described components. In addition, the base station receiver (2400), the base station transmitter (2410), the base station processor (2405), and the memory may be implemented in the form of a single chip.

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

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

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

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

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

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

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

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

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

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

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

[0510] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0511] 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 harm the essence of the invention.

Claims

1. In a method performed by a terminal of a communication system, A step of identifying a control resource set (CORESET) associated with a search space; A step of receiving downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET; Including a step of receiving the PDSCH based on the DCI, The above FDRA information indicates a PRB for the PDSCH among multiple physical resource blocks (PRBs), A method characterized in that when the plurality of PRBs are associated with SBFD (subband non-overlapping full duplex) symbols, the plurality of PRBs are based on an offset value.

2. In paragraph 1, The above search space is a common search space (CSS), The above offset value is determined based on the start PRB index of the CORESET and the start PRB index of the downlink subband of the SBFD symbol, A method characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

3. In paragraph 1, The above search space is a UE-specific search space (USS), The above offset value is determined based on the starting PRB index of the downlink subband of the SBFD symbol, A method characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

4. In paragraph 3, If the size of the DCI monitored in the USS is determined according to the size of the DCI monitored in the common search space (CSS), the starting PRB index and the number of PRBs for the PDSCH are indicated based on the offset value and the K value, A method characterized in that the above K value is determined based on the number of PRBs in an active downlink (DL) bandwidth part (BWP).

5. In paragraph 3, If the size of the DCI monitored in the USS is determined according to the size of the DCI monitored in the common search space (CSS), the starting PRB index and the number of PRBs for the PDSCH are indicated based on the offset value and the K value, A method characterized in that the above K value is determined based on the number of PRBs included in the downlink sub-band or the number of PRBs included in the active DL BWP from PRBs corresponding to the offset value.

6. In a method performed by a base station of a communication system, A step of identifying a control resource set (CORESET) associated with a search space; A step of transmitting downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the CORESET; Including a step of transmitting the PDSCH according to the DCI, The above FDRA information indicates a PRB for the PDSCH among multiple physical resource blocks (PRBs), A method characterized in that when the plurality of PRBs are associated with SBFD (subband non-overlapping full duplex) symbols, the plurality of PRBs are based on an offset value.

7. In paragraph 6, The above search space is a common search space (CSS), The above offset value is determined based on the start PRB index of the CORESET and the start PRB index of the downlink subband of the SBFD symbol, A method characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

8. In paragraph 6, The above search space is a UE-specific search space (USS), The above offset value is determined based on the starting PRB index of the downlink subband of the SBFD symbol, A method characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

9. In paragraph 8, If the size of the DCI monitored in the USS is determined according to the size of the DCI monitored in the common search space (CSS), the starting PRB index and the number of PRBs for the PDSCH are indicated based on the offset value and the K value, A method characterized in that the above K value is determined based on the number of PRBs in an active downlink (DL) bandwidth part (BWP).

10. In paragraph 8, If the size of the DCI monitored in the USS is determined according to the size of the DCI monitored in the common search space (CSS), the starting PRB index and the number of PRBs for the PDSCH are indicated based on the offset value and the K value, A method characterized in that the above K value is determined based on the number of PRBs included in the downlink sub-band or the number of PRBs included in the active DL BWP from PRBs corresponding to the offset value.

11. In the terminal of the communication system, Includes a transmitter / receiver and a control unit, The above control unit, Identify a control resource set (CORESET) associated with the search space, Receive downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the above CORESET, It is configured to receive the PDSCH based on the DCI, The above FDRA information indicates a PRB for the PDSCH among multiple physical resource blocks (PRBs), A terminal characterized in that, when the plurality of PRBs are associated with SBFD (subband non-overlapping full duplex) symbols, the plurality of PRBs are based on an offset value.

12. In paragraph 11, The above search space is a common search space (CSS), The above offset value is determined based on the start PRB index of the CORESET and the start PRB index of the downlink subband of the SBFD symbol, A terminal characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

13. In paragraph 11, The above search space is a UE-specific search space (USS), The above offset value is determined based on the starting PRB index of the downlink subband of the SBFD symbol, A method characterized in that the FDRA information indicates a start PRB index and the number of PRBs for the PDSCH among the plurality of PRBs determined based on the offset value.

14. In paragraph 13, If the size of the DCI monitored in the USS is determined according to the size of the DCI monitored in the common search space (CSS), the starting PRB index and the number of PRBs for the PDSCH are indicated based on the offset value and the K value, The above K value is determined based on the number of PRBs in the active downlink (DL) bandwidth part (BWP), or A terminal characterized in that the above K value is determined based on the number of PRBs included in the downlink subband or the number of PRBs included in the active DL BWP from the PRBs corresponding to the offset value.

15. In the base station of the communication system, Includes a transmitter / receiver and a control unit, The above control unit, Identify a control resource set (CORESET) associated with the search space, Transmit downlink control information (DCI) including frequency domain resource assignment (FDRA) information related to a physical downlink shared channel (PDSCH) based on the above CORESET, It is configured to transmit the PDSCH according to the above DCI, The above FDRA information indicates a PRB for the PDSCH among multiple physical resource blocks (PRBs), A base station characterized in that, when the plurality of PRBs are associated with SBFD (subband non-overlapping full duplex) symbols, the plurality of PRBs are based on an offset value.

Images