Method and apparatus for configuring frequency resources for full duplex communication in wireless communication system

Abstract

The present disclosure relates to a method and apparatus for efficiently configuring frequency resources for full duplex communication in a wireless communication system. According to an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system supporting full duplex communication comprises the steps of: receiving configuration information including information on a maximum frequency bandwidth and / or a minimum frequency bandwidth of an uplink (UL) sub-band of sub-band non-overlapping full duplex (SBFD) communication from a base station; checking an index of at least one resource block (RB) corresponding to an available UL sub-band in a downlink bandwidth portion (BWP) based on the configuration information; and transmitting the UL signal by using an available UL sub-band in the downlink BWP based on the checked index of the at least one RB.

Description

Technical Field

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a communication method and device for full-duplex communication in a wireless communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making high transmission rates and new services possible. This technology can be implemented not only in "below 6GHz" frequency bands such as 3.5GHz, but also in "above 6GHz" frequency bands (known as millimeter waves) including 28GHz and 39GHz. In addition, 6G mobile communication technology (known as a beyond 5G system) is also being considered in terahertz frequency bands (such as 95GHz to 3THz bands) to achieve a transmission rate 50 times faster than 5G mobile communication technology and ultra-low latency of one-tenth of 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet the relevant performance requirements of enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) and massive machine type communications (mMTC), standardization work has been ongoing, including the following aspects: beamforming and massive multiple-input multiple-output (MIMO) for alleviating radio wave path loss in millimeter waves and increasing radio wave transmission distance; support for multiple parameter sets (for example, operating multiple subcarrier spacings) to effectively utilize millimeter wave resources and dynamically operate time slot formats; initial access technology to support multi-beam transmission and broadband; definition and operation of bandwidth parts (BWPs); new channel coding methods, such as low-density parity-check (LDPC) codes for large amounts of data transmission, and polar codes for high-reliability transmission of control information; L2 preprocessing; and network slicing for dedicated networks that provide specific services.

[0004] Currently, discussions are underway on how to improve and enhance the performance of initial 5G mobile communications technologies for the services that 5G mobile communications technologies will support, and physical layer standardization has been carried out for technologies such as: vehicle-to-everything (V2X) for assisting autonomous vehicles in driving decisions and improving user convenience based on information sent by vehicles about their location and status; New Radio for Unlicensed Bands (NR-U) for enabling system operation to comply with various regulatory requirements for unlicensed bands; New Radio User Equipment (NR UE) power saving; Non-terrestrial Network (NTN) for direct UE satellite communication to provide coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, the standardization of air interface architecture / protocols for technologies such as: Industrial Internet of Things (IIOT) for supporting new services through interworking and integration with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; Mobility enhancement including conditional switching and dual active protocol stack (DAPS) switching; and two-step random access for simplifying the random access process (two-step random access channel (RACH) for NR). At the same time, the standardization of system architecture / services for technologies such as: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies; and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponentially growing number of connected devices will be connected to the communication network, and it is therefore expected that enhanced functions and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is planned on: extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; improving 5G performance and reducing its complexity by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, such developments in 5G mobile communication systems will serve as the basis for the development of not only new waveforms that provide coverage in the terahertz band for 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional multiple-input multiple-output (FD-MIMO); array antennas and massive antennas; metamaterial-based lenses and antennas for improving signal coverage in the terahertz band; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS), but will also serve as the basis for the development of full-duplex technologies for increasing the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies that leverage satellites and AI from the design stage and internalize end-to-end AI support functions for system optimization; and next-generation distributed computing technologies that enable services whose complexity exceeds the limits of UE operating capabilities by leveraging ultra-high-performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Based on the above discussion, the present disclosure provides an apparatus and method capable of effectively providing services in a mobile communication system.

[0010] The present disclosure provides a method and apparatus for effectively configuring / allocating frequency resources for full-duplex communication in a wireless communication system.

[0011] The present disclosure provides a method and apparatus for allocating Sub-Band Non-Overlapping Full-Duplex (SBFD) sub-band resources in a wireless communication system supporting SBFD communication.

[0012] Technical Solution

[0013] According to an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system supporting full-duplex communication includes: receiving configuration information from a base station, the configuration information including information related to at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink (UL) subband for subband non-overlapping full-duplex (SBFD) communication; based on the configuration information, identifying an index of at least one resource block (RB) corresponding to an available uplink band in a downlink bandwidth part (BWP); and sending an uplink signal by using an available uplink subband in the downlink BWP based on the identified index of at least one RB.

[0014] In addition, according to an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system supporting full-duplex communication includes: receiving configuration information of a downlink bandwidth part (BWP) and an uplink BWP; based on the configuration information and the subcarrier spacing, identifying a nominal downlink (DL) subband in the downlink BWP and a nominal downlink (DL) subband in the uplink BWP; and identifying an actual DL subband available in the nominal downlink subband and an actual UL subband available in the nominal uplink subband.

[0015] In addition, according to an embodiment of the present disclosure, a terminal in a wireless communication system supporting full-duplex communication includes: a transceiver; and a processor, configured to: receive configuration information from a base station through the transceiver, the configuration information including information related to at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink (UL) subband for subband non-overlapping full-duplex (SBFD) communication; based on the configuration information, identify an index of at least one resource block (RB) corresponding to an available uplink subband in a downlink bandwidth part (BWP); and based on the identified index of at least one RB, send an uplink signal through the transceiver by using an available uplink subband in the downlink BWP.

[0016] In addition, according to an embodiment of the present disclosure, a terminal in a wireless communication system supporting full-duplex communication includes: a transceiver; and a processor, configured to: receive configuration information of a downlink bandwidth part (BWP) and an uplink BWP through the transceiver; identify a nominal downlink (DL) subband in the downlink BWP and a nominal downlink (DL) subband in the uplink BWP based on the configuration information and the subcarrier spacing; and identify an actual DL subband available in the nominal downlink subband and an actual UL subband available in the nominal uplink subband.

[0017] According to an embodiment of the present disclosure, a method performed by a base station in a wireless communication system supporting full-duplex communication includes: sending configuration information, the configuration information including information related to at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink (UL) subband for subband non-overlapping full-duplex (SBFD) communication; based on the configuration information, identifying an index of at least one resource block (RB) corresponding to an available uplink subband in a downlink bandwidth part (BWP); and receiving an uplink signal from a terminal by using an available uplink subband in the downlink BWP based on the identified index of at least one RB.

[0018] In addition, according to an embodiment of the present disclosure, a base station in a wireless communication system supporting full-duplex communication includes: a transceiver; and a processor, configured to: send configuration information through the transceiver, the configuration information including information related to at least one of the maximum frequency bandwidth and the minimum frequency bandwidth of an uplink (UL) subband for subband non-overlapping full-duplex (SBFD) communication; based on the configuration information, identify the index of at least one resource block (RB) corresponding to an available uplink subband in a downlink bandwidth part (BWP); and based on the identified index of at least one RB, receive an uplink signal from a terminal through the transceiver by using the available uplink subband in the downlink BWP. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown;

[0020] Figure 2 The structure of a frame, a subframe and a time slot in a wireless communication system according to an embodiment of the present disclosure is shown;

[0021] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown;

[0022] Figure 4 An example of a control resource set configuration of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0023] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0024] Figure 6 A method for transmitting / receiving data by a base station and a UE in consideration of a downlink data channel and rate matching resources in a wireless communication system according to an embodiment of the present disclosure is shown;

[0025] Figure 7 An example of frequency domain resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown;

[0026] Figure 8 An example of time domain resource allocation related to PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown;

[0027] Fig. 9 An example of allocating time domain resources according to subcarrier spacing related to a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0028] Fig.10 The wireless protocol structure of the base station and the UE in the case of a single cell, carrier aggregation and dual connectivity in a wireless communication system according to an embodiment of the present disclosure is shown;

[0029] Fig.11 An example of allocating PUCCH resources through PDCCH according to an embodiment of the present disclosure is shown;

[0030] Fig.12 An example of TDD UL-DL resource allocation according to SBFD resource configuration information according to an embodiment of the present disclosure is shown;

[0031] Fig.13 An example of allocating UL and DL frequency resources for SBFD communication in a wireless communication system according to an embodiment of the present disclosure is shown;

[0032] Fig.14 An example of allocating a nominal UL subband and a nominal DL subband in a wireless communication system according to an embodiment of the present disclosure is shown;

[0033] Fig.15A and Fig. 15B An example of allocating an actual UL subband and an actual DL subband in a wireless communication system according to an embodiment of the present disclosure is shown;

[0034] Fig.16A and Fig. 16BA method for determining an actual UL subband and an actual DL subband by a terminal in a wireless communication system according to an embodiment of the present disclosure is shown;

[0035] Fig.17 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown; and

[0036] Fig.18 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

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

[0038] When describing the embodiments, descriptions related to technical contents well-known in the relevant technical field and not directly related to the present disclosure will be omitted. Omission of unnecessary descriptions is to prevent the main idea of ​​the present disclosure from being obscured and to convey the main idea more clearly.

[0039] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In each of the accompanying drawings, the same or corresponding elements are given the same reference numerals.

[0040] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the methods for achieving these advantages and features will be apparent. However, the present disclosure is not limited to the embodiments described below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements. In addition, when describing the present disclosure, if it is determined that a detailed description of a known function or configuration may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known function or configuration incorporated herein will be omitted. The terms to be described below are defined in view of the functions in the present disclosure and may vary according to the user, the user's intention or custom. Therefore, the definition of the term should be based on the content of the entire specification.

[0041] In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, "downlink (DL)" refers to a wireless link via which a base station transmits a signal to a terminal, and "uplink (UL)" refers to a wireless link via which a terminal transmits a signal to a base station. In addition, in the following description, an LTE system or an LTE-A system may be used only as an example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, new wireless, and NR) developed after LTE-A, and in the following description, "5G" may be a concept covering existing LTE, LTE-A, and other similar services. In addition, based on the judgment of those skilled in the art, the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0042] In this article, it is understood that each block in the flowchart diagram and the combination of blocks in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a process flow. Figure 1 The computer program instructions may also be stored in a computer usable memory or a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner so that the instructions stored in the computer usable memory or the computer readable memory produce an article of manufacture that includes an instruction device that implements the functions specified in one or more blocks of the flowchart. The computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process so that the instructions executed on the computer or other programmable device provide steps that implement the functions specified in one or more blocks of the flowchart.

[0043] In addition, each block in the flowchart illustration may represent a module, segment, or code portion, including one or more executable instructions for implementing the specified logical function. It should also be noted that in some optional implementations, the functions marked in the blocks may not occur in order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or blocks may sometimes be executed in reverse order, depending on the functions involved.

[0044] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, the meaning of a "unit" is not always limited to software or hardware. A "unit" can be configured to be stored in an addressable storage medium or to execute one or more processors. Therefore, a "unit" includes, for example, a software element, an object-oriented software element, a class element or a task element, a process, a function, an attribute, a program, a subroutine, a program code segment, a driver, a firmware, a microcode, a circuit, data, a database, a data structure, a table, an array, and a parameter. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, these elements and "units" can be implemented as reproducing one or more CPUs in a device or a secure multimedia card. In addition, a "unit" in an embodiment can include one or more processors.

[0045] As used herein, each of phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B or C" may include all possible combinations of items enumerated together in the corresponding phrase. Terms such as "first", "second", "the first", and "the second" may be used to simply distinguish one corresponding element from another element without limiting these elements in other aspects (such as importance or order).

[0046] Wireless communication systems are moving toward broadband wireless communication systems to provide high-speed and high-quality packet data services using communication standards such as 3GPP's High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE, or Evolved Universal Terrestrial Radio Access (E-UTRA)), Advanced LTE (LTE-A), LTE-Advanced (LTE-Pro), 3GPP2's High Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.16e, etc., as well as typical voice-based services.

[0047] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the wireless link through which the user equipment (UE) or mobile station (MS) transmits data or control signals to the base station (BS) or eNode B, and the downlink refers to the wireless link through which the base station transmits data or control signals to the UE. The above-mentioned multiple access scheme can separate the data or control information of each user by allocating and operating the time-frequency resources used to transmit the data or control information of each user to avoid mutual overlap, that is, to establish orthogonality.

[0048] In the following description, a base station (BS) is an entity that allocates resources to a terminal, which may be at least one of a gNode B, a gNB, an eNodeB, an eNB, a Node B, a radio access unit, a base station controller, or a node on a network. In addition, a base station may be a network entity, including at least one of the following: an integrated access and backhaul donor node (IAB-donor), which is a gNB that provides network access to a UE via a network of backhaul and access links; and an integrated access and backhaul node (IAB-node), which is a RAN node that supports an NR access link to a UE and supports an NR backhaul link to an IAB-donor or any other IAB-node. A user equipment (UE) may be at least one of a terminal, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. A terminal may perform wireless access via an IAB-node, and send / receive data to / from an IAB-donor connected to at least one IAB-node via a backhaul link.

[0049] Since the 5G communication system, as a communication system after LTE, must flexibly reflect the various requirements of users, service providers, etc., it must support services that meet various requirements. The services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc.

[0050] eMBB is designed to provide data rates higher than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink of a single base station and a peak data rate of 10Gbps in the uplink. In addition, the 5G communication system must also provide a higher user-perceived data rate as well as a maximum data rate to the UE. In order to meet these requirements, it is necessary to improve the transmission / reception technology, including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, the data rate required by the 5G communication system can be obtained using a frequency bandwidth of more than 20MHz in the 3GHz to 6GHz or 6GHz or higher frequency bands, instead of using a transmission bandwidth of up to 20MHz in the 2GHz band used in LTE to transmit signals.

[0051] In addition, in the 5G communication system, mMTC is being considered to support application services such as the Internet of Things (IoT). In order to effectively provide the IoT, mMTC has several requirements, such as supporting the connection of a large number of UEs in a cell, enhancing the coverage of UEs, improving battery life, and reducing UE costs. Since the IoT is provided to various sensors and various devices while providing communication functions, it must support a large number of UEs (e.g., 1,000,000 UE / km) in one cell. 2 ). In addition, compared with other services provided by the 5G communication system, UEs supporting mMTC may require wider coverage, because due to the nature of the service, UEs are likely to be located in shadow areas that are not covered by cells, such as basements of buildings, etc. UEs supporting mMTC must be cheap to configure and may require a long battery life, such as 10 to 15 years, because it is difficult to frequently replace the UE's battery.

[0052] Finally, URLLC is a cellular-based mission-critical wireless communication service. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC must provide ultra-low latency and ultra-high reliability communications. For example, URLLC-enabled services must meet an air interface latency of less than 0.5 milliseconds and may also require a packet error rate of less than or equal to 10 -5 Therefore, for services supporting URLLC, the 5G system must provide a shorter transmission time interval (TTI) than other services, and may also need to be designed to allocate a large amount of resources in the frequency band to ensure the reliability of the communication link.

[0053] The three services in 5G, namely eMBB, URLLC and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services to meet the different requirements of each service. Of course, 5G is not limited to the above three services.

[0054] In the following description, some terms and names defined in 3GPP standards (standards for 5G, NR, LTE or similar systems) may be used for ease of description. However, the present disclosure is not limited to these terms and names, and can be applied to systems that comply with other standards in the same manner. Therefore, the present disclosure is not limited to the terms as used herein, and other terms with equivalent technical meanings may be used to refer to the subject matter.

[0055]

NR time-frequency resources

[0056] Hereinafter, the framework structure of the 5G system will be described in more detail with reference to the accompanying drawings.

[0057] Figure 1 The basic structure of the time-frequency domain is shown, which is the wireless resource domain used to transmit data or control channels in the 5G system.

[0058] exist Figure 1 In the , the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The basic unit of resources in the time-frequency domain is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, (For example, 12) consecutive REs may constitute a resource block (RB) 104. Figure 1 middle, It is the number of OFDM symbols in each subframe 110 under the subcarrier spacing configuration (μ), and the resource structure in the 5G system can refer to (Technical Specification) TS 38 211 Section 4 standard.

[0059] Figure 2 The structure of a frame, a subframe, and a time slot in a wireless communication system according to an embodiment of the present disclosure is shown.

[0060] exist Figure 2 , an example of the structure of a frame 200, a subframe 201, and a time slot 202 is shown. A frame 200 may be defined as 10 milliseconds. A subframe 201 may be defined as 1 millisecond, so a frame 200 may include a total of ten subframes 201. A time slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols per time slot ). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 of each subframe 201 may vary according to the configured value μ of the subcarrier spacing 204 or 205. Figure 2 The example in FIG. 2 shows a case where the subcarrier spacing configuration value is μ=0 (204) and a case where μ=1 (205). In the case where μ=0 (204), one subframe 201 may include one time slot 202, and in the case where μ=1 (205), one subframe 201 may include two time slots 203. In other words, the number of time slots per subframe is The number of time slots per frame may vary depending on the subcarrier spacing configuration value μ. It can also be different accordingly. and It can be defined according to each subcarrier spacing configuration μ, as shown in Table 1 below.

[0061]

Table 1

[0062]

[0063] Bandwidth Part (BWP)

[0064] Next, a bandwidth part (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.

[0065] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0066] Figure 3 An example is shown in which UE bandwidth 300 is configured to include two bandwidth parts, namely bandwidth part #1 (BWP#1) 301 and bandwidth part #2 (BWP#2) 302. The base station can configure one or more bandwidth parts for the UE, and can configure the following information as given in Table 2 below for each bandwidth part.

[0067]

Table 2

[0068]

[0069] In Table 2, "locationAndBandwidth" refers to the location and bandwidth of the corresponding bandwidth part in the frequency domain, "subcarrierSpacing" refers to the subcarrier spacing used in the corresponding bandwidth part, and "cyclicPrefix" refers to whether ab extended cyclic prefix (CP) is used for the corresponding bandwidth part.

[0070] Obviously, the above example is not restrictive, and in addition to the above configuration information, various parameters related to the bandwidth part can also be configured for the UE. The base station can transfer the configuration information to the UE through upper layer signaling (e.g., radio resource control (RRC) signaling). One configured bandwidth part or at least one bandwidth part among multiple configured bandwidth parts can be activated. Whether the configured bandwidth part is activated can be semi-statically transferred from the base station to the UE through RRC signaling, or dynamically transferred through downlink control information (DCI).

[0071] According to an embodiment, before the radio resource control (RRC) connection, the base station may configure the initial bandwidth part (BWP) for the initial access for the UE through the master information block (MIB). More specifically, in the initial access step, the UE may receive configuration information about the control resource set (CORESET) and the search space through the MIB, which may be used to transmit the PDCCH for receiving the system information required for the initial access (which may correspond to the remaining system information (RMSI) or the system information block 1 (SIB1)). Each control resource set and search space configured through the MIB may be regarded as an identifier (ID) 0. The control resource set and search space configured through the MIB may be referred to as a common control resource set and a common search space, respectively. The base station may notify the UE of the configuration information about the control resource set #0, such as frequency allocation information, time allocation information, and parameter set, through the MIB. In addition, the base station may also notify the UE of the configuration information about the monitoring period and monitoring opportunity of the control resource set #0, i.e., the configuration information about the search space #0, through the MIB. The UE may consider the frequency domain configured by the control resource set #0 obtained from the MIB as the initial bandwidth part for the initial access. The ID of the initial bandwidth portion may be considered as 0. A set of control resources may be referred to as a control region, a control resource region, or the like.

[0072] The bandwidth-related configurations supported by 5G can be used for a variety of purposes.

[0073] According to certain embodiments, if the bandwidth supported by the UE is less than the system bandwidth, support may be achieved through bandwidth part configuration. For example, the base station may configure the frequency position of the bandwidth part for the UE so that the UE can send / receive data at a specific frequency position within the system bandwidth.

[0074] In addition, according to certain embodiments, the base station may configure multiple bandwidth parts for the UE to support different parameter sets. For example, in order to support the UE to use a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz for data transmission / reception at the same time, two bandwidth parts may be configured as subcarrier spacings of 15kHz and 30kHz, respectively. Different bandwidth parts may be frequency division multiplexed (FDM), and if data is to be transmitted / received at a specific subcarrier spacing, the bandwidth part configured as the corresponding subcarrier spacing may be activated.

[0075] In addition, according to certain embodiments, the base station can configure bandwidth parts with different bandwidth sizes for the UE to reduce the power consumed by the UE. For example, if the UE supports a large bandwidth (e.g., 100 MHz) and always sends / receives data with the corresponding bandwidth, a large power consumption may be generated. In particular, from the perspective of power consumption, it may be very inefficient to unnecessarily monitor a downlink control channel with a large bandwidth of 100 MHz in the absence of business. In order to reduce the power consumption of the UE, the base station can configure a bandwidth part with a relatively small bandwidth (e.g., a bandwidth part of 20 MHz) for the UE. The UE can perform monitoring operations in the 20 MHz bandwidth part in the absence of business, and if data appears, it can send / receive data using the 100 MHz bandwidth part according to the instructions of the base station.

[0076] Regarding the bandwidth part configuration method, before making an RRC connection, the UE may receive configuration information about the initial bandwidth part through the MIB in the initial access step. More specifically, the UE may have a control resource set (CORESET) configured for a downlink control channel (which may be used to transmit downlink control information (DCI) in order to schedule a system information block (SIB) from the MIB of the physical broadcast channel (PBCH)). The bandwidth of the control resource set configured by the MIB may be regarded as an initial bandwidth part, and the UE may receive a physical downlink shared channel (PDSCH) for transmitting the SIB through the configured initial bandwidth part. The initial bandwidth part may be used not only to receive SIBs, but also to receive other system information (OSI), paging, random access, etc.

[0077]

Bandwidth Part (BWP) Changes

[0078] If one or more bandwidth parts are configured for the UE, the base station can indicate to the UE to change (or switch or convert) the bandwidth part by using the bandwidth part indication field in the DCI. For example, if the bandwidth part currently activated by the UE is Figure 3If the bandwidth part #1 301 in the received DCI is not included, the base station may use the bandwidth part indicator inside the DCI to indicate the bandwidth part #2 302. The UE may change the bandwidth part to the bandwidth part #2 302 indicated by the bandwidth part indicator inside the received DCI.

[0079] As described above, the DCI-based bandwidth part change can be indicated by the DCI used to schedule PDSCH or PUSCH. Therefore, when receiving the bandwidth part change request, the UE needs to be able to receive or send the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part without any problems. To this end, the delay time (TBWP) required during the bandwidth part change is specified in the standard, for example, the definition can be given in Table 3 below.

[0080]

Table 3

[0081]

[0082] The bandwidth part change delay time requirement supports type 1 or type 2, depending on the UE's capabilities. The UE can report the supported bandwidth part change delay time type to the base station.

[0083] If the UE receives a DCI including a bandwidth part change indicator in time slot n, then according to the above requirements on the bandwidth part change delay time, the UE may BWP The change to the new bandwidth part indicated by the bandwidth part change indicator is completed at a time point of , and the data channel scheduled by the corresponding DCI can be sent / received in the newly changed bandwidth part. According to an embodiment, if the base station wants to schedule the data channel by using the new bandwidth part, the base station can change the bandwidth part delay time (T BWP ) to determine the time domain resource allocation of the relevant data channel. In other words, when scheduling the data channel by using the new bandwidth part, the base station can schedule the corresponding data channel after the bandwidth part change delay time in combination with the method for determining the time domain resource allocation of the data channel. Therefore, the UE may not expect that the DCI indicating the bandwidth part change will indicate a time that is less than the bandwidth part change delay time (T BWP )’s time slot offset (K0 or K2) value.

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

[0085]

SS / PBCH block

[0086] Next, the synchronization signal (SS) / PBCH block in 5G will be described.

[0087] The SS / PBCH block may refer to a physical layer channel block including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH. The details are as follows:

[0088] -PSS: A signal that becomes a reference for downlink time / frequency synchronization and provides partial information of a cell ID.

[0089] -SSS: Becomes a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. In addition, SSS can also be used as a reference signal for PBCH demodulation.

[0090] -PBCH: Provides MIB, which is mandatory system information required for UE to send / receive data channels and control channels. Mandatory system information may include search space related control information indicating radio resource mapping information of control channels, scheduling control information about independent data channels used to transmit system information, etc.

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

[0092] The UE may detect the PSS and SSS in the initial access phase and decode the PBCH. The UE may obtain the MIB from the PBCH, and the MIB may be used to configure the control resource set (CORESET) #0 (which may correspond to the control resource set with a control resource set index of 0). The UE may monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) transmitted in the selected SS / PBCH block is quasi co-located (QCL) with the control resource set #0. The UE may receive system information using the downlink control information transmitted in the control resource set #0. The UE may obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. The UE may transmit the physical RACH (PRACH) to the base station according to the selected SS / PBCH index, and the base station may obtain information about the SS / PBCH block index selected by the UE when receiving the PRACH. The base station may understand which block the UE has selected from the respective SS / PBCH blocks and the fact that the control resource set #0 associated therewith is monitored.

[0093] [PDCCH: About DCI]

[0094] Next, downlink control information (DCI) in the 5G system will be described in detail.

[0095] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is included in the DCI and transferred from the base station to the UE through the DCI. For PUSCH or PDSCH, the UE can monitor the fallback DCI format and the non-fallback DCI format. The fallback DCI format may include fixed fields predefined between the base station and the UE, and the non-fallback DCI format may include configurable fields.

[0096] The DCI may be channel coded and modulated, and then transmitted through a physical downlink control channel (PDCCH) after channel coding and modulation. A cyclic redundancy check code (CRC) may be attached to the payload of the DCI message, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used depending on the purpose of the DCI message, for example, UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI may not be transmitted explicitly, but may be transmitted while being included in the CRC calculation process. Upon receiving a DCI message transmitted via the PDCCH, the UE may identify the CRC by using the assigned RNTI, and if the CRC identification result is correct, the UE may understand that the corresponding message has been transmitted to the UE.

[0097] For example, the DCI for scheduling PDSCH regarding system information (SI) may be scrambled by SI-RNTI. The DCI for scheduling PDSCH regarding random access response (RAR) messages may be scrambled by RA-RNTI. The DCI for scheduling PDSCH regarding paging messages may be scrambled by P-RNTI. The DCI for notifying the slot format indicator (SFI) may be scrambled by SFI-RNTI. The DCI for notifying the transmission power control (TPC) may be scrambled by TPC-RNTI. The DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled by cell RNTI (C-RNTI).

[0098] DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 4 below.

[0099]

Table 4

[0100]

[0101] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI may include the following information given in Table 5 below.

[0102]

Table 5

[0103]

[0104]

[0105]

[0106] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 6 below.

[0107]

Table 6

[0108]

[0109] DCI format 1_1 may be used as a non-fallback DCI for scheduling PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include the following information given in Table 7 below.

[0110]

Table 7

[0111]

[0112]

[0113]

[0114] [PDCCH: CORESET, REG, CCE and search space]

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

[0116] Figure 4 An example of a control resource set (CORESET) for transmitting a downlink control channel in a 5G wireless communication system is shown. Figure 4 An example is shown in which a UE bandwidth portion 410 is configured along the frequency axis, and two CORESETs (CORESET#1 420 and CORESET#2 401) are configured in a time slot 402 along the time axis. The control resource sets 401 and 402 may be configured in specific frequency resources 403 within the entire UE bandwidth portion 420 along the frequency axis. The control resource sets 401 and 402 may each be configured as one or more OFDM symbols along the time domain, and the number of OFDM symbols may be defined as a control resource set duration 404. Figure 4 In the example shown in , control resource set #1 401 is configured to have a control resource set duration corresponding to two symbols, and control resource set #2 402 is configured to have a control resource set duration corresponding to one symbol.

[0117] The base station can configure the control resource set in the above 5G for the UE through upper layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). The description of configuring the control resource set for the UE refers to providing information such as the control resource set identifier, the frequency position of the control resource set, and the symbol duration of the control resource set. For example, the configuration information about the control resource set may include the following information in Table 8.

[0118]

Table 8

[0119]

[0120]

[0121] In Table 8, the tci-StatesPDCCH (referred to as transmission configuration indication (TCI) state) configuration information may include information of one or more SS / PBCH block indices or channel state information reference signal (CSI-RS) indices that are quasi-co-located (OCLed) with the DMRS transmitted in the corresponding CORESET.

[0122] Figure 5 An example of a basic unit of time resources and frequency resources constituting a downlink control channel available in a 5G system is shown. Figure 5 The basic unit of time resources and frequency resources constituting the control channel may be referred to as a resource element group (REG) 503, and the REG 503 may be defined by one OFDM symbol 501 along the time axis and one physical resource block (PRB) 502 (i.e., 12 subcarriers) along the frequency axis. The base station may configure a downlink control channel allocation unit by splicing multiple REGs 503.

[0123] If the basic unit of downlink control channel allocation in 5G is Figure 5 As shown in FIG. 5 , a CCE 504 may include multiple REGs 503. Figure 5 As an example, REG 503 shown in FIG. 5A may include 12 REs, and if one CCE 504 includes 6 REGs 503, one CCE 504 may include 72 REs. Once configured, a downlink control resource set may include multiple CCEs 504, and a specific downlink control channel may be mapped to one or more CCEs 504 and then transmitted according to an aggregation level (AL) in the control resource set. The CCEs 504 in the control resource set are distinguished by numbers, and the numbers of the CCEs 504 may be allocated according to a logical mapping scheme.

[0124] Figure 5 The basic unit of the downlink control channel shown in FIG. 5 , namely, REG 503, may include both REs mapped with DCI and an area mapped with a reference signal (DMRS 505) for decoding the DCI. Figure 5In A, three DRMS503 can be transmitted within one REG 505. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8 or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, one downlink control channel can be transmitted by L CCEs. The UE needs to detect the signal in the absence of information about the downlink control channel, so a search space indicating a set of CCEs for blind decoding has been defined. The search space is a set of downlink control channel candidates, including CCEs that the UE needs to try to decode at a given AL, and since 1, 2, 4, 8 or 16 CCEs can constitute a bundle at different ALs, the UE can have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0125] Search spaces can be classified into common search spaces and UE-specific search spaces. A group of UEs or all UEs can search the common search space of 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 SIB (including cell operator information, etc.) can be received by searching the common search space of PDCCH. In the case of a common search space, a group of UEs or all UEs need to receive PDCCH, so the common search space can be defined as a set of predetermined CCEs. Scheduling allocation information about UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of PDCCH. The UE-specific search space can be specifically defined by the UE as a function of various system parameters and UE identification.

[0126] In the 5G system, the base station can configure the parameters of the search space of the PDCCH for the UE through upper layer signaling (e.g., SIB, MIB or RRC signaling). For example, the base station can provide the UE with the following configurations: the number of PDCCH candidates at each aggregation level L, the monitoring period of the search space, the monitoring timing for each symbol in the time slot of the search space, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI format to be monitored in the corresponding search space, the control resource set index for monitoring the search space, etc. For example, the configuration information of the search space of the PDCCH may include the following information given in Table 9 below.

[0127]

Table 9

[0128]

[0129]

[0130]

[0131] According to the configuration information, the base station may configure one or more search space sets for the UE. According to an embodiment, the base station may configure search space set 1 and search space set 2 for the UE, may configure DCI format A scrambled by X-RNTI to monitor in the common search space in search space set 1, and may configure DCI format B scrambled by Y-RNTI to monitor in the UE-specific search space in search space set 2. In X-RNTI and Y-RNTI, "X" and "Y" may correspond to one of the various RNTIs described in the present disclosure.

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

[0133] The following combinations of DCI formats and RNTIs can be monitored in the common search space. Obviously, the following examples are not restrictive.

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

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

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

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

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

[0139] The following combinations of DCI formats and RNTIs can be monitored in the UE-specific search space. Obviously, the following examples are not restrictive.

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

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

[0142] The enumerated RNTI may follow the definition and usage given below.

[0143] Cell RNTI (C-RNTI): used to schedule UE-specific PDSCH

[0144] Temporary cell RNTI (TC-RNTI): used to schedule UE-specific PDSCH

[0145] Configuration Scheduling RNTI (CS-RNTI): used to schedule UE-specific PDSCH with semi-static configuration

[0146] Random Access RNTI (RA-RNTI): used to schedule PDSCH in the random access step Paging RNTI (P-RNTI): used to schedule PDSCH for transmission paging

[0147] System Information RNTI (SI-RNTI): used to schedule the PDSCH for transmitting system information

[0148] Interrupt RNTI (INT-RNTI): used to indicate whether PDSCH is punctured

[0149] Transmit Power Control for PUSCH RNTI (TPC-PUSCH-RNTI): used to indicate power control commands for PUSCH

[0150] Transmit Power Control for PUCCH RNTI (TPC-PUCCH-RNTI): used to indicate the power control command for PUCCH

[0151] Transmit Power Control for SRS RNTI (TPC-SRS-RNTI): used to indicate power control commands related to SRS

[0152] For example, the DCI formats enumerated above may follow the definition given in Table 10 below.

[0153]

Table 10

[0154]

[0155] In 5G, the search space at the aggregation level L related to the control resource set p and the search space set s can be expressed by the following formula 1.

[0156] [Formula 1]

[0157]

[0158] -L: aggregation level

[0159] -n CI : Carrier index

[0160] - The total number of CCEs in control resource set p

[0161] - Number of PDCCH candidates at aggregation level L

[0162] - PDCCH candidate index at aggregation level L

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

[0164] -

[0165] -n RNTI :UE ID

[0166] In the case of a public search space, The value may correspond to 0.

[0167] In case of UE-specific search space, The value may correspond to a value changed by the UE identification (C-RNTI or ID configured by the base station for the UE) and the time index.

[0168] In a 5G system, multiple search space sets may be configured by different parameters (e.g., the parameters in Table 9), and the group of search space sets monitored by the UE at each time point may be different accordingly. For example, if search space set #1 is configured to have an X time slot periodicity, search space set #2 is configured to have a Y time slot periodicity, and X is different from Y, the UE may monitor both search space set #1 and search space set #2 in a particular time slot, and may monitor one of search space set #1 and search space set #2 in another particular time slot.

[0169] [PDCCH: BD / CCE restriction]

[0170] If multiple search space sets are configured for the UE, the following conditions may be considered when determining the search space set that the UE is to monitor.

[0171] If the value of "monitoringCapabilityConfig-r16" (upper layer signaling) configured for the UE is "r15monitoringcapability", the UE defines the maximum number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (as used in this article, the entire search space refers to the entire CCE set corresponding to the union domain of multiple search space sets) for each time slot. If the value of "monitoringCapabilityConfig-r16" has been configured as "r16monitoringcapability", the UE defines the maximum number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (as used in this article, the entire search space refers to the entire CCE set corresponding to the union domain of multiple search space sets) for each time span.

[0172] [Condition 1: The maximum number of PDCCH candidates is limited]

[0173] According to the above upper layer signaling configuration value, if the maximum number of PDCCH candidates that the UE can monitor is M μ The reference is configured with a subcarrier spacing of 15·2 μ If the maximum number is defined by a time slot in a cell of kHz, the maximum number may follow Table 11 given below; if the maximum number is defined by reference to a time span, the maximum number may follow Table 12 given below.

[0174]

Table 11

[0175]

[0176]

Table 12

[0177]

[0178] [Condition 2: Maximum number of CCEs]

[0179] If the maximum number of CCEs constituting the entire search space (as used herein, the entire search space refers to the entire CCE set corresponding to the union domain of multiple search space sets) is μ The reference is configured with a subcarrier spacing of 15·2 μ kHz, the maximum number of CCEs is C μ Table 13 given below may be followed; if the maximum number is defined with reference to a time span, Table 14 given below may be followed.

[0180]

Table 13

[0181] μ <![CDATA[Maximum number of non - overlapping CCEs per time slot and per serving cell (C μ )]]> 0 56 1 56 2 48 3 32

[0182]

Table 14

[0183]

[0184] For ease of description, the situation where both the above conditions 1 and 2 are satisfied at a specific time point may be defined as “condition A.” Therefore, the description that condition A is not satisfied may mean that at least one of the above conditions 1 and 2 is not satisfied.

[0185] [PDCCH: Oversubscription]

[0186] According to the configuration of the search space set of the base station, it may happen that condition A is not met at a specific time point. If condition A is not met at a specific time point, the UE may select and monitor only certain search space sets configured to meet condition A at the corresponding time point, and the base station may transmit the PDCCH to the selected search space set.

[0187] The method for selecting certain search spaces from the set of all configured search spaces may follow the method given below.

[0188] If condition A regarding PDCCH is not met at a specific time point (time slot), the UE (or base station) may prioritize a search space set having a search space type configured as a common search space among the search space sets existing at the corresponding time point, rather than a search space set having a search space type configured as a UE-specific search space.

[0189] If all search space sets configured as common search spaces have been selected (i.e., condition A is satisfied even after all search spaces configured as common search spaces have been selected), the UE (or base station) may select a search space set configured as a UE-specific search space. If there are multiple search space sets configured as UE-specific search spaces, a search space set with a lower search space set index may have a higher priority. Considering the priority, a UE-specific search space set may be selected as long as condition A is satisfied.

[0190]

Regarding rate matching / puncturing

[0191] Hereinafter, the rate matching operation and the puncturing operation will be described in detail.

[0192] If the time-frequency resource A used to transmit the symbol sequence A overlaps with the time-frequency resource B, considering the resource C (the overlapping area of ​​resource A and resource B), the rate matching or puncturing operation can be regarded as the operation of sending / receiving channel A. The specific operation can follow the following description.

[0193] Rate Matching Operation

[0194] - The base station may transmit channel A after mapping channel A to the remaining resource domains except resource C (the region overlapping with resource B) in the entire resource A used to transmit the symbol sequence A to the UE. For example, if the symbol sequence A is configured as {symbol#1, symbol#2, symbol#3, symbol#4}, if resource A is {resource#1, resource#2, resource#3, resource#4}, and if resource B is {resource#3, resource#5}, the UE may receive the symbol sequence A based on the following assumption: the symbol sequence A has been sequentially mapped to the remaining resources {resource#1, resource#2, resource#4} except {resource#3} (corresponding to resource C) in resource A. Therefore, the base station may transmit the symbol sequence {symbol#1, symbol#2, symbol#3} after mapping them to {resource#1, resource#2, resource#4}, respectively.

[0195] The UE may evaluate resource A and resource B according to scheduling information about symbol sequence A from the base station, thereby evaluating resource C (the overlapping region of resource A and resource B). The UE may receive symbol sequence A based on the following assumption: symbol sequence A has been mapped and transmitted in the remaining region of the entire resource A except resource C. For example, if symbol sequence A is configured as {symbol#1, symbol#2, symbol#3, symbol#4}, if resource A is {resource#1, resource#2, resource#3, resource#4}, and if resource B is {resource#3, resource#5}, the UE may receive symbol sequence A based on the following assumption: symbol sequence A has been sequentially mapped to the remaining resources {resource#1, resource#2, resource#4} except {resource#3} (corresponding to resource C) in resource A. Therefore, the UE may perform the following series of reception operations based on the assumption that the symbol sequence {symbol#1, symbol#2, symbol#4} has been transmitted after being respectively mapped to {resource#1, resource#2, resource#4}.

[0196] Deletion Operation

[0197] If there is resource C (an area overlapping with resource B) within the entire resource A used to transmit symbol sequence A to the UE, the base station can map the symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, but only performs transmission for the remaining resource areas in resource A except resource C. For example, if symbol sequence A is configured as {symbol#1, symbol#2, symbol#3, symbol4}, if resource A is {resource#1, resource#2, resource#3, resource#4}, and if resource B is {resource#3, resource#5}, the UE can assume that symbol sequence A {symbol#1, symbol#2, symbol#3, symbol4} is mapped to resource A {resource#1, resource#2, resource#3, resource#4} respectively, but {symbol#3} mapped to {resource#3} (corresponding to resource C) is not transmitted, and based on the following assumption: the symbol sequence {symbol#1, symbol#2, symbol#4} corresponding to the remaining resources {resource#1, resource#2, resource#4} in resource A except {resource#3} (corresponding to resource C) has been mapped and transmitted, the UE can receive the symbol sequence. Therefore, the base station may transmit the symbol sequence {symbol#1, symbol#2, symbol#4} after mapping them to {resource#1, resource#2, resource#4} respectively.

[0198] The UE can evaluate resource A and resource B based on the scheduling information about symbol sequence A from the base station, thereby evaluating resource C (the overlapping region of resource A and resource B). The UE can receive symbol sequence A based on the following assumption: symbol sequence A has been mapped to the entire resource A, but is only transmitted in the remaining region of resource region A except resource C. For example, if symbol sequence A is configured as {symbol#1, symbol#2, symbol#3, symbol#4}, if resource A is {resource#1, resource#2, resource#3, resource#4}, and if resource B is {resource#3, resource#5}, the UE can assume that the symbol sequence A {symbol#1, symbol#2, symbol#3, symbol#4} has been mapped to resource A {resource#1, resource#2, resource#3, resource#4} respectively, but {symbol#3} mapped to {resource#3} (corresponding to resource C) has not been transmitted, and based on the following assumption: the symbol sequence {symbol#1, symbol#2, symbol#4} corresponding to the remaining resources {resource#1, resource#2, resource#4} in resource A except {resource#3} (corresponding to resource C) has been mapped and transmitted, the UE can receive the symbol sequence. Therefore, the UE may perform the following series of reception operations based on the assumption that the symbol sequence {symbol#1, symbol#2, symbol#4} has been transmitted after being respectively mapped to {resource#1, resource#2, resource#4}.

[0199] In the following, a method for configuring rate matching resources for the purpose of rate matching in a 5G communication system will be described. Rate matching refers to adjusting the size of a signal taking into account the amount of resources available to transmit the signal. For example, data channel rate matching may mean that the data channel is not mapped and transmitted for a specific time-frequency resource domain, and the size of the data is adjusted accordingly.

[0200] Figure 6 A method for a base station and a UE to transmit / receive data in a wireless communication system according to an embodiment of the present disclosure is shown in consideration of a downlink data channel and rate matching resources.

[0201] Figure 6A downlink data channel (PDSCH) 601 and a rate matching resource 602 are shown. The base station can configure one or more rate matching resources 602 for the UE through upper layer signaling (e.g., RRC signaling). The rate matching resource 602 configuration information may include time domain resource allocation information 603, frequency domain resource allocation information 604, and periodicity information 605. The bitmap corresponding to the frequency domain resource allocation information 604 will be referred to as the "first bitmap" hereinafter, the bitmap corresponding to the time domain resource allocation information 603 will be referred to as the "second bitmap", and the bitmap corresponding to the periodicity information 605 will be referred to as the "third bitmap". If all or part of the time-frequency resources of the scheduled PDSCH 601 overlap with the configured rate matching resources 602, the base station can rate match and transmit the PDSCH 602 in the overlapping portion of the rate matching resource 601, and the UE can perform reception and decoding after assuming that the PDSCH 602 has been rate matched in the overlapping portion of the rate matching resource 601.

[0202] The base station can dynamically inform the UE through DCI whether the PDSCH will be rate matched in the configured rate matching resource part through additional configuration (for example, corresponding to the "rate matching indicator" inside the above-mentioned DCI format). Specifically, the base station can select certain resources from the configured rate matching resources and group them into rate matching resource groups, and can indicate to the UE whether the PDSCH is rate matched for each rate matching resource group using a bitmap type through DCI. For example, if four rate matching resources RMR#1, RMR#2, RMR#3 and RMR#4 are configured, the base station can configure rate matching groups RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4}, and can use two bits inside the DCI field through a bitmap to indicate to the UE whether rate matching occurs in RMG#1 and RMG#2, respectively. For example, in the case where rate matching is to be performed, the base station can be indicated by "1", and in the case where rate matching is not to be performed, the base station can be indicated by "0".

[0203] 5G supports the use of "RB symbol level" and "RE level" granularity as a method for configuring the above rate matching resources for UE. More specifically, the following configuration method can be followed:

[0204] RB symbol level

[0205] The UE may configure up to four rate matching patterns (RateMatchPatterns) for each bandwidth part through upper layer signaling, and a rate matching pattern may include the following contents.

[0206] - May include resources related to reserved resources within a bandwidth part, having a time-frequency resource domain of the corresponding reserved resources configured as a combination of an RB level bitmap and a symbol level bitmap in the frequency domain. The reserved resources may span one or two time slots. In addition, a time domain pattern (periodityAndPattern) may be configured, in which the time domain and frequency domain including the corresponding RB level and symbol level bitmap pairs are repeated.

[0207] - may include: a resource region corresponding to a time domain pattern configured by a time domain resource region and a frequency domain resource region configured by a CORESET within a bandwidth part; and a search space configuration in which a corresponding resource region is repeated.

[0208] RE Level

[0209] The UE can configure the following contents through upper layer signaling.

[0210] - Configuration information (lte-CRS-ToMatchAround) related to RE corresponding to the LTE CRS (cell-specific reference signal or common reference signal) mode, which may include: LTE CRS port number (nrofCRS-Ports), LTE CRS shift value (v-shift), location information from the reference frequency point (e.g., reference point A) to the LTE carrier center subcarrier (carrierFreqDL), LTE carrier bandwidth size (carrierBandwidthDL) information, and subframe configuration information (mbsfn-SubframConfigList) corresponding to the multicast broadcast single frequency network (MBSFN). The UE can determine the position of the CRS inside the NR time slot corresponding to the LTE subframe based on the above information.

[0211] - May include configuration information about resource sets corresponding to one or more zero-power (ZP) CSI-RS within the bandwidth part.

[0212]

About LTE CRS rate matching

[0213] Next, the rate matching process for the above-mentioned LTE CRS will be described in detail. In NR, in order to achieve coexistence of long-term evolution (LTE) and new RAT (NR) (LTE-NR coexistence), the cell-specific reference signal (CRS) mode of LTE can be configured for NR UE. More specifically, the CRS mode can be provided by RRC signaling including at least one parameter within ServingCellConfigIE (information element) or ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0214] Rel-15 NR provides a function to configure one CRS pattern for each serving cell through the parameter lte-CRS-ToMatchAround. In Rel-16 NR, the above function has been extended to enable multiple CRS patterns to be configured for each serving cell. More specifically, a UE with a single-TRP (transmit and receive point) configuration can now configure one CRS pattern for each LTE carrier, while a UE with a multi-TRP configuration can now configure two CRS patterns for each LTE carrier. For example, a UE with a single-TRP configuration can configure up to three CRS patterns for each serving cell through the parameter lte-CRS-PatternList1-r16. For another example, a UE with a multi-TRP configuration can configure CRS for each TRP. In other words, the CRS pattern for TRP1 can be configured through the parameter lte-CRS-PatternList1-r16, and the CRS pattern for TRP2 can be configured through the parameter lte-CRS-PatternList2-r16. If two TRPs are configured as described above, whether the CRS patterns of both TRP1 and TRP2 will be applied to a specific physical downlink shared channel (PDSCH), or only the CRS pattern related to one TRP will be applied, will be determined by the parameter crs-RateMatch-PerCORESETPoolIndex-r16, where if the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is configured to "Enabled", only the CRS pattern of one TRP is applied, and in other cases both CRS patterns of the two TRPs are applied.

[0215] Table 11 shows the ServingCellConfig IE including the CRS pattern. Table 12 shows the RateMatchPatternLTE-CRS IE including at least one parameter related to the CRS pattern.

[0216]

Table 15

[0217]

[0218]

[0219]

[0220]

[0221]

[0222]

Table 16

[0223]

[0224]

[0225] [PDSCH: Frequency resource allocation]

[0226] Figure 7 An example of frequency domain resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0227] Figure 7 Three frequency domain resource allocation methods, type 0 700, type 1 705, and dynamic switch 710, are shown, which can be configured by the upper layer in the NR wireless communication system.

[0228] refer to Figure 7 In the case where the UE is configured to use only resource allocation type 0 through upper layer signaling (700), the partial downlink control information (DCI) for allocating PDSCH to the UE includes a bitmap 715, which includes N RBG bits. The conditions related to this will be described again later. As used in this article, N RBG It refers to the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, as shown in Table 17 below, and data is transmitted in the RBG whose bitmap indication is "1".

[0229]

Table 17

[0230] Bandwidth portion size Configuration 1 Configuration 2 1-36 3 4 37-72 4 8 73-144 8 16 145-275 16 16

[0231] In the case where the UE is configured to use only resource type 1 through upper layer signaling (705), the partial DCI includes frequency domain resource allocation information, which includes The conditions related to this will be described again later. The base station can thereby configure a starting virtual resource block (starting VRB) 720 and the length 725 of the frequency domain resources continuously allocated therefrom.

[0232] In the case where the UE is configured to use resource type 0 and resource type 1 at the same time through upper layer signaling (710), the partial DCI used to allocate PDSCH to the corresponding UE includes frequency domain resource allocation information, which includes the same number of bits as the larger value %n between the payload 715 configured with resource type 0 and the payloads 720 and 725 configured with resource type 1. The conditions related to this will be described again later. A bit can be added to the front part (MSB) of the frequency domain resource allocation information inside the DCI. If the value of this bit is "0", it can indicate the use of resource type 0; if the value of this bit is "1", it can indicate the use of resource type 1.

[0233] [PDSCH / PUSCH: Time resource allocation]

[0234] Hereinafter, a time domain resource allocation method for a data channel in a next-generation mobile communication system (5G or NR system) will be described.

[0235] The base station may configure a table of time domain resource allocation information about the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) for the UE through upper layer signaling (e.g., RRC signaling). A table including a maximum of maxNrofDL-Allocations=16 entries may be configured for PDSCH, and a table including a maximum of maxNrofUL-Allocations=16 entries may be configured for PUSCH. In an embodiment, the time domain resource allocation information may include PDCCH to PDSCH slot timing (e.g., corresponding to the time interval in time slots between the time point at which the PDCCH is received and the time point at which the PDSCH scheduled by the received PDCCH is sent; marked as K0), PDCCH to PUSCH slot timing (e.g., corresponding to the time interval in time slots between the time point at which the PDCCH is received and the time point at which the PUSCH scheduled by the received PDCCH is sent; marked as K2 below), information about the position and length of the starting symbol for scheduling PDSCH or PUSCH within the slot, the mapping type of PDSCH or PUSCH, etc. For example, information such as in Table 18 or Table 19 below may be transmitted from the base station to the UE.

[0236]

Table 18

[0237]

[0238]

[0239]

Table 19

[0240]

[0241] The base station may notify the UE of one of the entries in the table related to the above-mentioned time domain resource allocation information through L1 signaling (e.g., DCI) (e.g., the "time domain resource allocation" field in the DCI may indicate the time domain resource allocation). The UE may obtain the time domain resource allocation information about the PDSCH or PUSCH based on the DCI obtained from the base station.

[0242] Figure 8 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0243] refer to Figure 8 , the UE can use the subcarrier spacing (SCS) (μ PDSCH , μ PDCCH ), scheduling offset (K0) value, and the OFDM symbol starting position 800 and length 805 within a time slot dynamically indicated by DCI to indicate the time domain position of the PDSCH resource.

[0244] Fig. 9 An example of allocating time domain resources according to subcarrier spacing related to a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0245] refer to Fig. 9 , if the data channel and the control channel have the same subcarrier spacing (μ PDSCH =μ PDCCH )(900), the time slot number for data and the time slot number for control are the same, and the base station and the UE can generate a scheduling offset that conforms to the predetermined time slot offset K0 accordingly. On the other hand, if the data channel and the control channel have different subcarrier spacings (μ PDSCH ≠μ PDCCH )(905), the time slot number used for data and the time slot number used for control are different, and the base station and the UE can accordingly refer to the subcarrier spacing of the PDCCH to generate a scheduling offset that conforms to the predetermined time slot offset K0.

[0246] [PUSCH: About transmission scheme]

[0247] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmission can be dynamically scheduled through UL grants within DCI, or operated through configured grant type 1 or type 2. Dynamic scheduling indication for PUSCH transmission can be implemented through DCI format 0_0 or 0_1.

[0248] PUSCH transmissions with configured grant type 1 may be semi-statically configured via upper layer signaling by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant in Table 16, without receiving an UL grant inside the DCI. PUSCH transmissions with configured grant type 2 may be semi-persistently scheduled via upper layer signaling by receiving a configuredGrantConfig not including rrc-ConfiguredUplinkGrant in Table 16, with an UL grant inside the DCI. If the PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied via configuredGrantConfig (upper layer signaling) in Table 20, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank and scaling of UCI-OnPUSCH, which are provided by pusch-Config (upper layer signaling) in Table 21. If transformPrecoder is provided within configuredGrantConfig (upper layer signaling) in Table 20, the UE applies tp-pi2BPSK within pusch-Config in Table 21 to PUSCH transmissions operated by the configured grant.

[0249]

Table 20

[0250]

[0251]

[0252]

[0253] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the txConfig value inside the pusch-Config as the upper layer signaling in Table 21 is "codebook" or "non-codebook", PUSCH transmission can follow a codebook-based transmission method or a non-codebook-based transmission method.

[0254] As described above, PUSCH transmission may be dynamically scheduled via DCI format 0_0 or 0_1, or semi-statically configured via a configured grant. When a scheduling indication regarding PUSCH transmission is received via DCI format 0_0, the UE performs beam configuration for PUSCH transmission by using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and the PUSCH transmission is based on a single antenna port. Within a BWP where no PUCCH resources including pucch-spatialRelationInfo are configured, the UE does not expect scheduling regarding PUSCH transmission via DCI format 0_0. If the UE does not configure txConfig within the pusch-Config in Table 21, the UE does not expect scheduling via DCI format 0_1.

[0255]

Table 21

[0256]

[0257]

[0258] Next, codebook-based PUSCH transmission will be described. As described above, PUSCH transmission can be dynamically scheduled through DCI format 00 or 01, or semi-statically configured through a configured grant. If codebook-based PUSCH is dynamically scheduled through DCI format 0_1 ​​or semi-statically configured through a configured grant, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transmission precoding matrix indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

[0259] SRI can be given by SRS resource indicator (field inside DCI) or configured by srs-ResourceIndicator (upper layer signaling). During codebook-based PUSCH transmission, the UE is configured with at least one SRS resource and can be configured with up to two SRS resources. If the UE obtains SRI through DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the corresponding SRI. TPMI and transmission rank can be given by "precoding information and number of layers" (field inside DCI) or configured by precodingAndNumberOfLayers (upper layer signaling). TPMI is used to indicate the precoder to be applied to PUSCH transmission. If multiple SRS resources are configured for the UE, TPMI is used to indicate the precoder to be applied in the SRS resources indicated by SRI. If multiple SRS resources are configured for the UE, TPMI is used to indicate the precoder to be applied in the SRS resources indicated by SRI.

[0260] The precoder for PUSCH transmission is selected from an uplink codebook whose number of antenna ports is the same as the value of nrofSRS-Ports inside SRS-Config (upper layer signaling). For codebook-based PUSCH transmission, the UE determines the codebook subset based on codebookSubset and TPMI inside pusch-Config (upper layer signaling). Based on the UE capabilities reported by the UE to the base station, codebookSubset inside pusch-Config (upper layer signaling) can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent" or "noncoherent". If the UE reports "partialAndNonCoherent" as the UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullAndPartialAndNonCoherent". In addition, if the UE reports "noncoherent" as a UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If nrofSRS-Ports inside SRS-ResourceSet (upper layer signaling) indicates that there are two SRS antenna ports, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "partialAndNonCoherent".

[0261] The UE may be configured with one SRS resource set, where the usage value inside the SRS-ResourceSet (upper layer signaling) is "codebook", and one SRS resource may be indicated by the SRI inside the corresponding SRS resource set. If multiple SRS resources are configured inside the SRS resource set with the usage value inside the SRS-ResourceSet (upper layer signaling) being "codebook", the UE expects the value of nrofSRS-Ports inside the SRS-Resource (upper layer signaling) to be the same for all SRS resources.

[0262] According to the upper layer signaling, the UE transmits to the base station one or more SRS resources included in the SRS resource set whose usage value is configured as "codebook". The base station selects one from the SRS resources transmitted by the UE and instructs the UE so that PUSCH can be transmitted by using the transmission beam information of the corresponding SRS resource. Regarding codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. In addition, the base station also adds information indicating the rank and TPMI used by the UE for PUSCH transmission to the DCI. When performing PUSCH transmission, the UE uses the SRS resources indicated by the SRI to apply the precoder indicated by the rank and TPMI indicated by the transmission beam based on the corresponding SRS resource, thereby performing PUSCH transmission.

[0263] Next, non-codebook based PUSCH transmission will be described. Non-codebook based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, or semi-statically operated through configuration authorization. If at least one SRS resource is configured within the SRS resource set with a usage value of "nonCodebook" within the SRS-ResourceSet (upper layer signaling), non-codebook based PUSCH transmission can be scheduled for the UE through DCI format 0_1.

[0264] For an SRS resource set with a usage value of "nonCodebook" inside the SRS-ResourceSet (upper layer signaling), a connected non-zero power CSI-RS resource (NZP CSI-RS) can be configured for the UE. The UE can calculate the precoder for SRS transmission by measuring the NZP CSI-RS resources 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 in the UE is less than 42 symbols, the UE does not expect the information about the precoder used for SRS transmission to be updated.

[0265] If the configuration value of resourceType inside SRS-ResourceSet (upper layer signaling) is "non-periodic", the connected NZP CSI-RS is indicated by the SRS request as a field inside DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the presence of a connected NZP CSI-RS is indicated when the value of the SRS request (field inside DCI format 0_1 ​​or 1_1) is not "00". The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is positioned in the time slot used to transmit the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier is not configured as quasi-co-location type D (QCL-TypeD).

[0266] If a periodic SRS resource set or a semi-persistent SRS resource set is configured, the connected NZP CSI-RS may be indicated by the associatedCSI-RS inside the SRS-ResourceSet (upper layer signaling). For non-codebook based transmission, the UE does not expect that the spatialRelationInfo as the upper layer signaling about the SRS resource will be configured together with the associatedCSI-RS inside the SRS-ResourceSet (upper layer signaling).

[0267] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to the PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by the SRS resource indicator (field inside the DCI) or configured by the srs-ResourceIndicator (upper layer signaling). Similar to the above-mentioned codebook-based PUSCH transmission, if the UE obtains the SRI through the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within an SRS resource set and the maximum number of SRS resources are determined by the UE capabilities reported by the UE to the base station. The SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures an SRS port for each SRS resource. There may be only one configured SRS resource set, where the usage value inside the SRS-ResourceSet (upper layer signaling) is "nonCodebook", and for non-codebook based PUSCH transmission, a maximum of four SRS resources may be configured.

[0268] The base station may transmit an NZP-CSI-RS connected to an SRS resource set to the UE. The UE may calculate the precoder to be used when transmitting one or more SRS resources within the corresponding SRS resource set based on the measurement result when the corresponding NZP-CSI-RS is received. When transmitting one or more SRS resources within an SRS resource set whose configuration purpose is "nonCodebook" to the base station, the UE applies the calculated precoder. The base station selects one or more SRS resources from the received one or more SRS resources. With respect to non-codebook based PUSCH transmission, the SRI indication may represent an index of a combination of one SRS resource or multiple SRS resources, and the SRI is included in the DCI. The number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH. The UE transmits the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0269]

PUSCH: Preparation time

[0270] Next, the PUSCH preparation procedure time will be described. If the base station schedules the UE to transmit PUSCH by using DCI format 0_0, 0_1, or 0_2, the UE may need a PUSCH preparation procedure time so that the PUSCH is transmitted by applying the transmission method indicated by the DCI (SRS resource transmission precoding method, number of transmission layers, spatial domain transmission filter). In view of this, the PUSCH preparation procedure time is defined in NR. The PUSCH preparation procedure time of the UE can follow the formula 2 given below.

[0271] [Formula 2]

[0272] T proc,2 =max((N 2 +d 2,1 +d 2 )(2048+144)κ2 -μ T c +T ext +T switch ,d 2,2 )

[0273] T described in the above formula 2 proc,2 Each parameter in can have the following meanings.

[0274] -N 2 : The number of symbols determined according to the UE processing capability 1 or 2 based on the UE capability and parameter set μ. If the UE processing capability 1 is reported according to the UE capability report, then N 2It may have the values ​​in Table 22; if UE processing capability 2 is reported and the availability of UE processing capability 2 is configured through upper layer signaling, then N 2 Can have the values ​​in Table 23.

[0275]

Table 22

[0276] μ <![CDATA[PUSCH Preparation Time N 2

Symbol

[0277]

Table 23

[0278] μ <![CDATA[PUSCH preparation time N 2

Symbol

[0279] -d 2,1 : If all resource elements of the first OFDM symbol of PUSCH transmission include DM-RS, the determined number of symbols is 0; otherwise, the number of symbols is 1.

[0280] -κ:64

[0281] -μ: in μ DL and μ UL Take a value among them so that T proc,2 Larger. DL It refers to the downlink parameter set used to transmit PDCCH (including DCI scheduling PUSCH). UL Refers to the uplink parameter value used to transmit PUSCH.

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

[0283] -d 2,2 : If the DCI scheduling PUSCH indicates BWP switching, the BWP switching time is followed; otherwise it is 0.

[0284] -d 2 : If the OFDM symbols between a PUSCH with a high priority index and a PUCCH with a low priority index overlap in time, the d of the PUSCH with a high priority index is used. 2 Otherwise, d 2 is 0.

[0285] -T ext : If the UE uses a shared spectrum channel access solution, the UE can calculate T ext and apply it to the PUSCH preparation procedure time. Otherwise, assume T ext is 0.

[0286] -T switch : If the uplink switching interval has been triggered, it is assumed that T switch is the switching interval. Otherwise, assume T switch is 0.

[0287] Taking into account the impact of the timing advance between uplink and downlink, and the time domain resource mapping information of the PUSCH scheduled by DCI, if the first symbol of the PUSCH starts earlier than the following symbol, that is, the CP is after the last symbol of the PDCCH including the DCI scheduling the PUSCH through T proc,2 If the first uplink symbol starts after that, the base station and the UE determine that the PUSCH preparation procedure time is insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation procedure time is sufficient. Only if the PUSCH preparation procedure time is sufficient, the UE can transmit PUSCH; if the PUSCH preparation procedure time is insufficient, the UE can ignore the DCI scheduling PUSCH.

[0288]

About CA / DC

[0289] Fig.10 The wireless protocol structure of the base station and the UE in the case of single cell, carrier aggregation and dual connectivity according to an embodiment of the present disclosure is shown.

[0290] refer to Fig.10 The wireless protocol of the mobile communication system includes NR service data adaptation protocol (SDAP) S25 or S70, NR packet data convergence protocol (PDCP) S30 or S65, NR radio link control (RLC) S35 or S60 and NR medium access control (MAC) S40 or S55 on both the UE side and the NR base station side. In the following description, each layer of equipment can be understood as a functional block of the corresponding layer.

[0291] The main functions of NR SDAP S25 or S70 may include some of the following functions.

[0292] -Transfer of user plane data

[0293] - Mapping between QoS flows and DRBs for DL ​​and UL

[0294] -Mark QoS flow ID in DL and UL packets

[0295] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0296] For SDAP layer devices, the UE can be configured through an RRC message with whether to use the header of the SDAP layer device or the function of the SDAP layer device for each PDCP layer device, each bearer or each logical channel, and if the SDAP header is configured, the non-access layer (NAS) QoS reflection configuration 1-bit indicator (NAS reflective QoS) and AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header can be indicated so that the UE can update or reconfigure the mapping information of the QoS flow and data bearer for the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used to smoothly support data processing priority, scheduling information, etc. of the service.

[0297] The main functions of NR PDCP S30 or S65 may include the following functions.

[0298] -Header compression and decompression: Robust Header Compression (ROHC) only

[0299] - Transfer of user data

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

[0301] - Out-of-order delivery of upper layer PDUs

[0302] - Reordering of received PDCP PDUs

[0303] - Duplicate detection of lower layer SDUs

[0304] -Retransmission of PDCP SDU

[0305] -Encryption and decryption

[0306] - Timer-based SDU discard in uplink

[0307] The reordering of the above-mentioned NR PDCP device refers to the function of reordering the PDCP PDU received from the lower layer based on the PDCP sequence number (SN), and may include the function of transferring the data to the upper layer in the reordered order. Optionally, the reordering of the NR PDCP device may include the function of transferring data immediately without considering the order, may include the function of recording the PDCP PDU lost due to reordering, may include the function of reporting the status of the lost PDCP PDU to the transmitting end, and may also include the function of requesting the retransmission of the lost PDCP PDU.

[0308] The main functions of NR RLC S35 or S60 may include some of the following functions.

[0309] - Transfer of upper layer PDU

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

[0311] - Out-of-order delivery of upper layer PDUs

[0312] - Error correction via ARQ

[0313] - RLC SDU splicing, segmentation and reassembly

[0314] - Re-segmentation of RLC data PDUs

[0315] - Reordering of RLC data PDUs

[0316] - Duplicate detection

[0317] -Protocol error detection

[0318] -RLC SDU discarded

[0319] -RLC reconstruction

[0320] The in-sequence delivery of NR RLC refers to the function of delivering the RLC SDUs received from the lower layer to the upper layer in sequence. The in-sequence delivery of NR RLC may include the following functions: the function of reassembling and delivering the received multiple RLC SDUs segmented from one original RLC SDU; the function of reordering the received RLC PDUs with reference to the RLC sequence number (SN) or the PDCP sequence number (SN); the function of recording the RLC PDUs lost due to reordering; the function of reporting the status of the lost RLC PDUs to the transmitting end; and the function of requesting the retransmission of the lost RLC PDUs. The in-sequence delivery function of NR RLC may include the following functions: if there is a lost RLC SDU, only the RLC SDUs before the lost RLC SDU are delivered to the upper layer in sequence; if the predetermined timer has expired despite the existence of a lost RLC SDU, all RLC SDUs received before the timer is started are delivered to the upper layer in sequence. Optionally, the in-order delivery of the NR RLC device may include the following functions: if a predetermined timer has expired despite the existence of lost RLC SDUs, all currently received RLC SDUs are delivered to the upper layer in succession. In addition, the in-order delivery of the NR RLC device may include the following functions: processing the RLC PDU in the order of reception (regardless of the sequence number order, only the arrival order) and delivering it to the PDCP device regardless of the order (i.e., out-of-order delivery); in the case of segmentation, receiving the segments stored in the buffer area or to be received subsequently, reconfiguring them into a complete RLC PDU, processing them and delivering them to the PDCP device. The NR RLC layer may not include a splicing function, which may be performed in the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.

[0321] Out-of-order delivery of NR RLC refers to the function of delivering the RLC SDU received from the lower layer to the upper layer immediately regardless of the order. It may include the function of reassembling and delivering multiple RLC SDUs segmented from an original RLC SDU, and the function of storing the RLC SN or PDC PSN of the received RLC PDU, and the function of recording the RLC PDU lost due to reordering.

[0322] NR MAC S40 or S55 can be connected to multiple NR RLC layer devices configured in one UE, and the main functions of NR MAC may include some of the following functions.

[0323] - Mapping between logical channels and transport channels

[0324] -Multiplexing / demultiplexing of MAC SDU

[0325] -Dispatch information report

[0326] - Error correction through HARQ

[0327] - Priority handling between logical channels of a UE

[0328] - Prioritization between UEs through dynamic scheduling

[0329] -MBMS service identification

[0330] -Transmission format selection

[0331] -filling

[0332] The NR PHY layer S45 or S50 can perform channel coding and modulation operations on the upper layer data to obtain OFDM symbols, and deliver these symbols through the wireless channel; or demodulate and channel decode the OFDM symbols received through the wireless channel, and deliver these symbols to the upper layer.

[0333] The detailed structure of the wireless protocol structure can be changed in many ways according to the carrier (or cell) operation scheme. For example, assuming that the base station transmits data to the UE based on a single carrier (or a single cell), the base station and the UE use a protocol structure with a single structure for each layer, such as Fig.10 As shown in the reference number 1010. On the other hand, if the base station transmits data to the UE based on carrier aggregation (CA), that is, using multiple carriers in a single TRP, the base station and the UE can use the following protocol structure, which is a single structure in the RLC and lower layers of the RLC, but multiplexes the PHY layer through the MAC layer, such as Fig.10As shown in the reference number 1020. For another example, if the base station transmits data to the UE based on dual connectivity (DC), that is, using multiple carriers in multiple TRPs, the base station and the UE may use the following protocol structure, which is a single structure in the RLC and lower layers, but multiplexes the PHY layer through the MAC layer, such as Fig.10 As shown in reference number 1030.

[0334] Fig.11 An example of allocating PUCCH resources through PDCCH according to an embodiment of the present disclosure is shown.

[0335] exist Fig.11 In the present invention, the base station may allocate PUCCH resources 1110 by using DCI transmitted through the PDCCH 1100. The UE may receive the DCI by blind decoding a plurality of PDCCH candidates 1105 including CCEs in the search space, and may transmit the PUCCH by using the resources allocated through the DCI.

[0336] Hereinafter, embodiments of the present disclosure will be described in detail in conjunction with the accompanying drawings. The content of the present disclosure can be applied to FDD systems and TDD systems. As used herein, upper layer signaling (or upper layer signaling) is a method of transferring a signal from a base station to a UE by using a downlink data channel of a physical layer, or transferring a signal from a UE to a base station by using an uplink data channel of a physical layer, and may also be referred to as "RRC signaling", "PDCP signaling" or "Media Access Control (MAC) Control Element (MACCE)".

[0337] In the following of the present disclosure, the UE may use various methods to determine whether collaborative communication is applied, for example, the PDCCH allocated for the PDSCH to which collaborative communication is applied has a specific format; or the PDCCH allocated for the PDSCH to which collaborative communication is applied includes a specific indicator indicating whether collaborative communication is applied; or the PDCCH allocated for the PDSCH to which collaborative communication is applied is scrambled by a specific RNTI; or it is assumed that collaborative communication is applied in a specific range indicated by an upper layer. In the following, for ease of description, it will be assumed that the NC-JT situation refers to the situation in which the UE receives the PDSCH to which collaborative communication is applied based on conditions similar to those described above.

[0338] In the following, determining the priority between A and B can be described in various ways, for example, selecting an entity with a higher priority and performing a corresponding operation according to a predetermined priority rule; or omitting or abandoning the operation on an entity with a lower priority.

[0339] In the following, the above examples may be described through several implementations, but they are not independent of each other, and one or more implementations may be applied simultaneously or in combination.

[0340] In the following description of the present disclosure, upper layer signaling may refer to signaling corresponding to at least one of the following signalings, or a combination of one or more of the following signalings.

[0341] -Master Information Block (MIB)

[0342] - System Information Block (SIB) or SIB X (X=1, 2, ...)

[0343] -Radio Resource Control (RRC)

[0344] -Media Access Control (MAC) Control Element (CE)

[0345] In addition, L1 signaling may refer to signaling corresponding to at least one signaling method among the following signaling methods using physical layer channels or signaling, or signaling corresponding to a combination of one or more signaling methods.

[0346] - Physical Downlink Control Channel (PDCCH)

[0347] - Downlink Control Information (DCI)

[0348] -UE-specific DCI

[0349] -Group Common DCI

[0350] - Public DCI

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

[0352] - Non-scheduled DCI (e.g., DCI not used for scheduling downlink data or uplink data)

[0353] -Physical Uplink Control Channel (PUCCH)

[0354] - Uplink Control Information (UCI)

[0355] In the following, determining the priority between A and B may be described in various ways, for example, selecting an entity with a higher priority and performing a corresponding operation according to a predetermined priority rule; or omitting or abandoning operations on an entity with a lower priority.

[0356] In the following, the above examples may be described through several implementations, but they are not independent of each other, and one or more implementations may be applied simultaneously or in combination.

[0357]

SBFD: SBFD Overview

[0358] In 3GPP, sub-band non-overlapping full-duplex (SBFD) is being discussed as a new full-duplex scheme based on NR. SBFD is a technology that utilizes part of the downlink resources as uplink resources in a TDD band (spectrum) with a frequency equal to or lower than 6 GHz, or equal to or higher than 6 GHz. In this way, the uplink coverage of the UE can be expanded as much as the increase in uplink transmission resources, and the base station can receive feedback from the UE about downlink transmission in the expanded uplink resources, thereby reducing feedback delay. In the present disclosure, the UE can receive information about whether SBFD is supported from the base station. For convenience, a UE that can perform uplink transmission in part of the downlink resources can be referred to as an SBFD UE (SBFD-capable UE). The SBFD scheme can be defined in the standard, and the SBFD UE can consider adopting the following scheme to determine whether SBFD is supported in a specific cell (or a certain frequency / band).

[0359] First solution: In addition to the frame structure type of the conventional non-paired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD), another frame structure type (e.g., frame structure type 2) may be introduced to define SBFD. Frame structure type 2 may be defined as supported in a specific frequency or frequency band, or the base station may indicate to the UE whether SBFD is supported by using at least one of the above-mentioned system information or high-layer signaling. The SBFD UE may receive the system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or a certain frequency / frequency band).

[0360] Second solution: Without defining a new frame structure type, it is possible to indicate whether SBFD is additionally supported in a specific frequency or frequency band of a traditional non-paired spectrum (or TDD). The second solution may define whether SBFD is additionally supported in a specific frequency or frequency band of a traditional non-paired spectrum, or the base station may use at least one of the above system information or high-layer signaling to indicate to the UE whether SBFD is supported. The SBFD UE may receive system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or a certain frequency / frequency band).

[0361] Regarding the information on whether SBFD is supported in the first scheme and the second scheme, it can be information (for example, information on whether SBFD is supported) that configures part of the downlink resources as uplink resources in addition to configuring TDD uplink-downlink (UL-DL) resource configuration information indicating downlink time slot (or symbol) resources and uplink time slot (or symbol) resources in TDD. Fig.12It may be the SBFD resource configuration information in the document, or it may be the information directly indicating whether SBFD is supported.

[0362] Fig.12 An example of TDD UL-DL resource allocation according to SBFD resource configuration information according to an embodiment of the present disclosure is shown. Fig.12 In cases (a), (b), (c) and (d), reference symbol "D" refers to a DL time slot to which only DL symbols are allocated, "U" refers to a UL time slot to which only UL symbols are allocated, and "S" refers to a special time slot to which both DL symbols and UL symbols are allocated.

[0363] refer to Fig.12 , Fig.12 Case (a) shows a typical TDD resource allocation scheme. Fig.12 Cases (b), (c), and (d) show examples of SBFD resource allocation schemes according to SBFD resource configuration information 1, 2, and 3. The TDD cycle may include UL time slots 1201, 1211, 1221, and 1231, and UL subbands 1210 and 1220 may be allocated within the frequency resources of a DL time slot or a special time slot. Fig.12 As shown in the examples of cases (b), (c) and (d), UL resources within a DL time slot or a special time slot may be allocated according to various modes 1212, 1222, 1232, 1233 and 1234.

[0364] In the present disclosure, the SBFD UE may receive a synchronization signal block (SSB) in the initial cell access for accessing a cell (or base station) to obtain cell synchronization. For the SBFD UE and the existing TDD UE, the process of obtaining cell synchronization may be the same. Thereafter, the SBFD UE may determine whether the cell supports SBFD through MIB acquisition, SIB acquisition, or random access procedures.

[0365] The system information used to transmit the information about whether SBFD is supported may be system information that is distinguished from the system information of UEs supporting different versions of protocols (e.g., existing TDD UEs) in the cell and is transmitted separately, and the SBFD UE may obtain all or part of the system information transmitted separately from the system information of the existing TDD UE to determine whether SBFD is supported. When the SBFD UE obtains only the system information of the existing TDD UE or the system information indicating that SBFD is not supported, the SBFD UE may determine that the cell (or base station) only supports TDD.

[0366] When the information on whether SBFD is supported is included in the system information of a UE supporting a different version of the protocol (e.g., an existing TDD UE), the information on whether SBFD is supported can be inserted into the last part of the system information so as not to affect the acquisition of the system information of the existing TDD UE. When the SBFD UE cannot obtain the information on whether SBFD is supported inserted in the last part, or obtains information indicating that SBFD is not supported, the SBFD UE can determine that the cell (or base station) only supports TDD.

[0367] When information about whether SBFD is supported is included in the system information of a UE supporting a different version of the protocol (e.g., an existing TDD UE), the information about whether SBFD is supported can be transmitted through a separate PDSCH so as not to affect the acquisition of system information of the existing TDD UE. In other words, a UE that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information through a first PDSCH. A UE that supports SBFD can receive a first SIB (or SIB) including existing TDD-related system information through a first PDSCH, and can receive a second SIB including SBFD-related system information through a second PDSCH. The first PDSCH and the second PDSCH can be scheduled by DCI transmitted via a first PDCCH and a second PDCCH, and the cyclic redundancy check code (CRC) of the first PDCCH and the second PDCCH can be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if the same search space is not obtained (i.e., if the system information of the first PDSCH does not include information of the search space), the second PDCCH can be received in the same search space as the search space of the first PDCCH.

[0368] As described above, when the SBFD UE determines that the cell (or base station) supports only TDD, the SBFD UE may perform a random access procedure and transmit or receive data / control signals in the same manner as an existing TDD UE.

[0369] The base station may configure separate random access resources for an existing TDD UE or SBFD UE (e.g., an SBFD UE supporting full-duplex communication and an SBFD UE supporting half-duplex communication), and transmit configuration information about random access resources (e.g., control information or configuration information indicating time-frequency resources available for PRACH) to the SBFD UE through system information. The system information used to transmit information about random access resources may be system information that is distinguished from system information of UEs supporting different versions of protocols in the cell (e.g., existing TDD UEs) and is transmitted separately.

[0370] The base station configures separate random access resources for each SBFD UE and TDD UE supporting different versions of the protocol, so that it can distinguish whether the TDD UE supporting different versions of the protocol performs random access or the SBFD UE performs random access. For example, the separate random access resources configured for the SBFD UE can be resources determined as downlink time resources by the existing TDD UE, and the SBFD UE performs random access through uplink resources (or separate random access resources) configured in certain frequencies of the downlink time resources, so that the base station can determine that the UE attempting random access in the uplink resources is a SBFD UE.

[0371] Optionally, the base station may not configure a separate random access resource for the SBFD UE, but may configure a common random access resource for all UEs in the cell. In this case, the configuration information about the random access resource can be transmitted to all UEs in the cell through system information, and the SBFD UE that has received the system information can perform random access by using the random access resource. Thereafter, the SBFD UE can complete the random access procedure, thereby entering the RRC connection mode to send or receive data with the cell. After entering the RRC connection mode, the SBFD UE can receive a high-layer signal or physical signal (e.g., L1 signaling) from the base station that can determine that part of the frequency resources of the downlink time resources are configured as uplink resources, and perform SBFD operations, such as transmitting uplink signals in uplink resources.

[0372] When the SBFD UE determines that the cell supports SBFD, the SBFD UE transmits UE capability information to the base station, the UE capability information including whether the UE supports SBFD, whether the UE supports full-duplex communication or half-duplex communication, and at least one of the number of transmitting or receiving antennas included (or supported) by the UE, thereby notifying the base station that the UE attempting to access is a SBFD UE. Optionally, when support for half-duplex communication must be implemented for the SBFD UE, the information on whether half-duplex communication is supported can be omitted from the UE capability information. The report on the UE capability information of the SBFD UE can be reported to the base station through the random access process, can also be reported to the base station after the random access process is completed, and can also be reported to the base station after entering the RRC connection mode to send or receive data with the cell.

[0373] The SBFD UE may support half-duplex communication in which only uplink transmission or downlink reception is performed at a time, like an existing TDD UE, or may support full-duplex communication in which uplink transmission and downlink reception are performed at the same time. Therefore, the SBFD UE may report to the base station through a capability report whether it supports half-duplex communication or full-duplex communication, and after the report, the base station may configure the SBFD UE whether the SBFD UE uses half-duplex communication for transmission or reception or uses full-duplex communication for transmission or reception. When the SBFD UE reports its UE capability of half-duplex communication to the base station, since a duplexer is usually not present, a switching gap for switching a radio frequency (RF) between transmission and reception may be required when operating in FDD or TDD mode.

[0374] In general, the UE can establish a wireless link with the network through a random access process based on the system information obtained during the cell search process for the cell and the synchronization with the network. Random access can use a contention-based scheme or a contention-free scheme. For example, when the UE performs cell selection and reselection in the initial cell access phase of the cell, a contention-based random access scheme can be used to transition from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access can be used to reconfigure uplink synchronization in the case of handover or position measurement when downlink data has arrived.

[0375] According to the present disclosure to be described below, a subband SBFD UE may receive the configuration of a SBFD UL subband and transmit an uplink channel through the SBFD UL subband. The SBFD UL subband may exist at any position in the DL BWP, and its length may be limited to a maximum or minimum RB value specified by high-layer signaling. In this case, the UE receives frequency resource information of the subband with a maximum or minimum length limit before uplink channel transmission. The length of one RB constituting the SBFD subband may be determined according to the subcarrier spacing (SCS) of the SBFD subband, and may vary according to the frequency resource configuration. To this end, various methods for configuring the frequency resources of the SBFD UL subband are disclosed.

[0376] [SBFD: SBFD sub-band frequency resource allocation related]

[0377] The SBFD UE may receive the configuration of the SBFD UL subband from the base station and transmit a signal on an uplink channel through the SBFD UL subband.

[0378] Fig.13 An example of allocating UL and DL frequency resources for SBFD communication in a wireless communication system according to an embodiment of the present disclosure is shown.

[0379] refer to Fig.13 , the SBFD communication environment may have a UL subband 1305 and a DL subband 1310 coexisting in the same time resource. In addition, there may also be a UL area 1315 used only for UL transmission. In this case, the SBFD UL subband 1305 may exist anywhere in the DL BWP 1325, and the length of the SBFD UL subband 1305 may be limited to the maximum or minimum RB value specified / configured by the higher layer. The SBFD UE may receive information about the frequency resource of the UL subband 1305 from the base station before uplink transmission, and the maximum or minimum length of the subband 1305 is limited within the DL BWP. An example of an allocation-related indication method of the SBFD subband frequency resource is as follows.

[0380] In the following embodiments, the maximum frequency bandwidth and the minimum frequency bandwidth of the frequency resource allocation of the SBFD UL subband may be assumed as follows. For each frequency band, cell, or carrier on the UE, the maximum frequency bandwidth and / or the minimum frequency bandwidth of the UL subband may be known. The maximum frequency bandwidth and / or the minimum frequency bandwidth may be determined independently of the subcarrier spacing, such as Hertz (or Megahertz). The maximum frequency bandwidth and / or the minimum frequency bandwidth may be determined by the subcarrier spacing used and the number of RBs (or the number of subcarriers).

[0381] The base station may indicate the maximum frequency bandwidth and / or the minimum frequency bandwidth to the UE. The indication may be included in the system information block (SIB) broadcast by the base station to the UE or in high-layer signaling. When the UE receives the SIB, the UE may obtain information about the maximum frequency bandwidth and / or the minimum frequency bandwidth of the UL subband. In another method, the indication may be included in the RRC information transmitted by the base station to a specific UE. The RRC information may be obtained by the UE during its random access to the base station. For reference, the RRC information may include DL BWP information and UL BWP information. For each BWP pair, the maximum frequency bandwidth and / or the minimum frequency bandwidth of the UL subband may be configured in different ways (here, a BWP pair refers to a DL BWP and a UL BWP with the same BWP ID).

[0382] In another embodiment, the maximum frequency bandwidth and / or the minimum frequency bandwidth associated with the frequency resource allocation of the SBFD UL subband may be fixed. In other words, the UE may obtain information about the maximum frequency bandwidth and / or the minimum frequency bandwidth even without a separate indication from the base station. More specifically, the maximum frequency bandwidth and the minimum frequency bandwidth may be determined for each frequency band (e.g., the n78 frequency band). The UE may determine the frequency band used when communicating with the base station. The UE may obtain information about the maximum frequency bandwidth and / or the minimum frequency bandwidth defined for each frequency band.

[0383] RB Index

[0384] In the present disclosure, one of the following three may be used as an index of an RB in the frequency domain.

[0385] 1) Common RB index (eg, may be referred to as CRB index)

[0386] The common RB index is allocated starting from 0 and increases as the frequency increases. The UE designates the subcarrier matching "point A" as subcarrier 0, and can group 12 subcarriers in ascending order of frequency starting from this subcarrier and allocate a common RB index to them. In other words, when the subcarrier index is k, the value corresponding to floor(k / 12) is the common RB index of the RB to which the subcarrier belongs.

[0387] The common RB index is determined according to point A. Since point A is commonly configured for all UEs in the cell, all UEs may have the same common RB index.

[0388] 2) BWP-specific RB index (BWP-specific RB index) (eg, may be referred to as PRB index)

[0389] The UE may receive a configuration of a downlink BWP for receiving a DL signal (or DL ​​channel) and / or a configuration of an uplink BWP for sending an UL signal (or UL channel). The UE may assume that, as a specific BWP RB index, the index of the lowest RB of the BWP is 0. More specifically, the position of the starting RB of the BWP may be given by using a common RB index as In other words, with the public RB index The corresponding RB may be assigned a specific BWP RB index 0. In other words, it may be Here, n CRB is the public RB index, n PRB is the specific BWP RB index.

[0390] 3) Subband RB index (subband specific RB index)

[0391] The UE may receive the configuration of an uplink subband (UL subband) in a downlink symbol. Conversely, the UE may receive the configuration of a downlink subband (DL subband) in an uplink symbol. In the subband RB index, it may be assumed that the index of the lowest RB among the RBs included in the subband is 0.

[0392] More specifically, the position of the starting RB of a subband can be given by using a common RB index as In other words, the UE can receive the The value of the configuration. With the public RB index The corresponding RB may be assigned subband RB index 0. In other words, it may be Here, n CRB is the public RB index, n sub is the subband RB index. For reference, The subband that configures the position of the starting RB with the value of may be applied to the entire BWP of the UE. In other words, it is not BWP-specific.

[0393] In another method, the position of the starting RB of the subband can be given by using a specific BWP RB index as In other words, the UE can receive the The value of the configuration. The value can be configured to a specific BWP. The corresponding RB may be assigned subband RB index 0. In other words, it may be Here, n PRB is the specific BWP RB index, n sub is the subband RB index.

[0394] Use one of the above methods 1), 2) and 3) to obtain the subband RB index n. sub It can be expressed as the following [Formula 3].

[0395] [Formula 3]

[0396]

[0397] Therefore, it can be expressed as

[0398] In the following implementation, the UE may obtain the starting RB (RB in the following description) through the resource indication value (RIV). start ) index and / or RB length (L in the following description) RBs). The RB occupied by the UL subband can be determined by the RIV value. More specifically, when the UE obtains the index of the starting RB and the RB length, the RB occupied / allocated by the UL subband can be determined by the following first or second method. For reference, the subcarrier spacing used to determine the RB will be described later.

[0399] In the first method, the UE may specify the index and RB length of the RB based on the common RB index to determine the RB included in the UL subband. More specifically, the UE may determine the RB whose common RB index is 0 based on the above point A. The UE may determine the offset value 0 from the common RB index. offset Here, O offse The t value can be configured by the base station. The base station can configure the subcarrier spacing according to offset The index of the common RB at the start of the UL subband can be 0 offset +RB start In addition, the continuous L from the common RB RBs Can be included in the UL subband. For reference, the UE can receive the configuration of the UL BWP. The UL BWP may include part or all of the frequency domain of the UL subband. If the UL BWP includes the entire frequency domain of the UL subband, all RBs of the UL subband may be determined as RBs available for uplink transmission. If the UL BWP includes a partial frequency domain of the UL subband, the RBs included in the partial frequency domain may be determined as RBs available for uplink transmission. In other words, even if RBs other than the UL BWP are included in the UL subband, the UE may not perform uplink transmission in the RB. Therefore, the UE may determine only the RBs of the UL subband included in the UL BWP as the actual UL subband or the BWP-specific UL subband (here, the UL subband determined by the RIV value may be determined as the cell-common UL subband or the nominal UL subband). In other words, all UEs in the cell can equally determine the frequency domain position of the cell-common UL subband or the nominal UL subband, and can determine the actual UL subband or the BWP-specific UL subband according to the UL BWP configuration).

[0400] In a first method, the subcarrier spacing may be determined as follows.

[0401] First, it can be assumed that the subcarrier spacing is the same as the subcarrier spacing of the initial DL BWP. Here, the initial DL BWP is the BWP through which the UE obtains SIB scheduling information when it initially accesses the cell. Therefore, all UEs in the cell can obtain the same subcarrier spacing.

[0402] Secondly, it can be assumed that the subcarrier spacing is the same as the subcarrier spacing of the initial UL BWP. Here, the UE can receive the subcarrier spacing of the initial UL BWP in SIB1. The initial UL BWP is a BWP that can be used for physical random access channel (PRACH) transmission, msg3 PUSCH transmission, msg4 PDSCH HARQ-ACK transmission, etc. As is known to all, msg3 and msg4 are messages sent and received between the UE and the base station to resolve contention conflicts during the random access process.

[0403] Third, the subcarrier spacing can be determined based on the larger value between the subcarrier spacing of the initial DL BWP and the subcarrier spacing of the initial UL BWP. This means that the RB corresponding to the larger subcarrier spacing can completely include the RB corresponding to the smaller subcarrier spacing in the frequency domain. However, the RB corresponding to the smaller subcarrier spacing cannot completely include the RB corresponding to the larger subcarrier spacing in the frequency domain. Therefore, even if the nominal UL subband including the RB corresponding to the smaller subcarrier spacing has been determined, when the actual UL subband is determined based on the subcarrier spacing of the initial UL BWP, the problem of only including part of the RBs in the actual UL subband may occur. In order to solve this problem, the subcarrier spacing can be determined based on the larger value between the subcarrier spacing of the initial DL BWP and the subcarrier spacing of the initial UL BWP.

[0404] Fourth, the base station can configure the subcarrier spacing for the UE separately. In other words, the base station can configure the subcarrier spacing to determine the frequency domain position of the cell common UL subband or nominal UL subband. Here, the subcarrier spacing can be configured to meet at least one of the following conditions 1, 2 and 3.

[0405] - Condition 1: The subcarrier spacing to be configured may be determined as a value that is equal to or greater than a maximum value among a subcarrier spacing that can be configured for a DL BWP and a subcarrier spacing that can be configured for a UL BWP.

[0406] - Condition 2: The subcarrier spacing to be configured may be determined as a value that is equal to or greater than a maximum value among subcarrier spacings that may be configured for the DL BWP.

[0407] - Condition 3: The subcarrier spacing to be configured may be determined as a value that is equal to or greater than a maximum value among subcarrier spacings that may be configured for the UL BWP.

[0408] Under the above conditions, the subcarrier spacing that can be configured for UL BWP can be included in the high-level signal FrequencyInfoUL, FrequencyInfoUL-SIB in the 3GPP standard TS38.331, and the subcarrier spacing that can be configured for DL ​​BWP can be included in the high-level signal FrequencyInfoDL, FrequencyInfoDL-SIB.

[0409] Fifth, the subcarrier spacing may use the subcarrier spacing used in the TDD configuration. Here, the subcarrier spacing used in the TDD configuration has a value configured for the higher layer signal (referenceSubcarrierSpacing).

[0410] In the above description, the UE has determined the nominal UL subband. The UE may determine the subband other than the nominal UL subband in the cell as the nominal DL subband. The UE may receive the configuration of the DL BWP. The DL BWP may include part or all of the frequency domain of the DL subband. If the DL BWP includes the entire frequency domain of the DL subband, all RBs of the DL subband may be determined as RBs available for downlink reception. If the DL BWP includes a partial frequency domain of the DL subband, the RBs included in the partial frequency domain may be determined as RBs available for downlink reception. In other words, even if RBs other than the DL BWP are included in the DL subband, the UE may not perform downlink reception in RBs other than the DL BWP. Therefore, the UE may determine only the RBs of the DL subband included in the DL BWP as actual DL subbands or BWP-specific DL subbands.

[0411] Fig.14 An example of allocating a nominal UL sub-band and a nominal DL sub-band in a wireless communication system according to an embodiment of the present disclosure is shown.

[0412] refer to Fig.14 , assuming that the cell includes 16 RBs. The common RB index (CRB index) of the lowest RB in the frequency domain is 0, and the common RB index of the highest RB in the frequency domain is 15. The UE can obtain the RBs included in the nominal UL subband 1420 through RIV. For example, due to offset +RB start =6 and L RBs＝ 4, so four consecutive RBs starting from the RB with a common RB index of 6 may be included in the nominal UL sub-band 1420. In addition, RBs not included in the nominal UL sub-band 1420 may be included in the nominal DL sub-band 1410.

[0413] Fig.15A and Fig. 15BAn example of allocating an actual UL subband and an actual DL subband in a wireless communication system according to an embodiment of the present disclosure is shown.

[0414] refer to Fig.15A , the UE may determine the actual UL subband 1520 based on the UL BWP 1510 and the nominal UL subband 1530. For example, it is assumed that RBs having common RB indices of 8, 9, 10, ..., 14 are included in the UL BWP. The UE may determine that, among the RBs included in the UL BWP, RBs having common RB indices of 8 and 9 and overlapping the nominal UL subband 1530 are included in the actual UL subband 1520.

[0415] refer to Fig. 15B , the UE may determine the actual DL subband 1550 based on the DL BWP 1540 and the nominal UL subband. For example, it is assumed that RBs with common RB indices of 4, 5, 6, ..., 14 are included in the DL BWP 1540. The UE may determine that, among the RBs included in the DL BWP 1540, RBs with common RB indices of 4, 5, 10, 11, 12, 13, and 14 and overlapping with the nominal DL subband are included in the actual DL subband 1550, excluding the nominal UL subband 1560.

[0416] As a second method for determining the RBs occupied / allocated by the UL subband, a specific BWP RB index is determined based on the UL BWP configuration, and the RB index and RB length can be described based on the specific BWP RB index to determine the RBs included in the UL subband. More specifically, the RB whose specific BWP RB index is 0 is the lowest RB in the frequency domain in the UL BWP. The specific BWP RB index of the UL subband start may be the RB start In addition, continuous L from a specific BWP RB RBs It can be included in the UL subband. Here, the subcarrier spacing can be a subcarrier-specific BWP RB spacing configured for the DL BWP.

[0417] Fig.16A and Fig. 16B A method for determining an actual UL subband and an actual DL subband by a UE in a wireless communication system according to an embodiment of the present disclosure is shown. Fig.16A and Fig. 16B The example assumes that Fig.15A and Fig. 15B Example of resource allocation for .

[0418] refer to Fig.16A, for the UE, RBs with a common RB index of 8 (CRB#8) to RBs with a common RB index of 14 (CRB#14) have been configured in the UL BWP 1610. In addition, the UE can index the RBs configured in the UL BWP 1610 with a specific BWP RB index. In other words, the RB with a common RB index of 8 (CRB#8) can be an RB with a specific BWP RB index of 0 (RB#0). The UE can determine the actual UL subband 1620 within the UL BWP 1610 through RIV. Here, since the RB start =0 and L RBs =2, so two consecutive RBs starting from the RB whose specific BWP RB index is 0 can be included in the actual UL BWP 1620.

[0419] According to the second method, the UE can always receive the configuration of the actual UL subband or the BWP-specific UL subband. However, according to the second method, it is impossible to identify which RB within the DL BWP can be used for downlink reception. For example, referring to Fig.16A , it can be understood that the RBs with common RB indices 8 and 9 (CRB#8, CRB#9) are included in the actual UL subband 1620 and are therefore not available for downlink reception. However, in the RBs ( Fig.16A Among the RBs with common RB indexes of 4, 5, 6, and 7 (CBR#4, CBR#5, CBR#6, CBR#7), it is impossible to identify which RBs are not available for downlink reception. Therefore, it is necessary to separately inform which RBs are available for downlink reception and which RBs are available for downlink reception within the DL BWP.

[0420] The specific BWP RB index is determined based on the DL BWP configuration, and the RB index and RB length may be specified based on the specific BWP RB index to determine the RBs that are not available for downlink reception within the DL BWP. For reference, the RBs that are not available for downlink reception may be different from the actual UL subband. More specifically, the RB whose specific BWP RB index is 0 is the lowest RB in the frequency domain in the DL BWP. Among the RBs that are not available for downlink reception, the lowest RB in the frequency domain is the RB whose specific BWP RB index is 0. start In addition, the RBs that are not available for downlink reception may include consecutive RBs from a specific BWP RB. RBs Among the RBs included in the DLBWP, RBs excluding RBs unavailable for downlink reception may be determined as actual DL subbands. Here, the subcarrier spacing may be a subcarrier spacing configured for the DL BWP.

[0421] refer to Fig. 16B , for the UE, RBs with a common RB index of 4 (CRB#4) to RBs with a common RB index of 14 (CRB#14) have been configured in DL BWP 1630. In addition, the UE can index the RBs configured in DL BWP 1630 with a specific BWP RB index. In other words, the RB with a common RB index of 4 (CRB#4) can be an RB with a specific BWP RB index of 0 (RB#0). The UE can determine the RBs that are not available for downlink reception in DL BWP 1630 through RIV. Here, since the RB start =2 and L RBs =4, so four consecutive RBs 1640 starting from the RB with a specific BWP RB index of 2 (ie, the RB corresponding to the nominal UL subband 1560 among the RBs) may be included in the RBs unavailable for downlink reception. RBs other than the RB 1640 unavailable for downlink reception in the DL BWP 1630 may be determined as actual DL subbands.

[0422] In the first and second methods described above, a protection RB may be required at the boundary between the DL subband and the UL subband. In this case, the base station can configure the number of protection RBs for the UE. The protection RB may be an RB of a UL subband adjacent to a DL subband, or an RB of a DL subband adjacent to a UL subband.

[0423] Hereinafter, a method of indicating a frequency resource transmission position when a minimum number of RBs of a SBFD subband is given will be described.

[0424] This example describes a method for transmitting a start virtual RB (RB) by using a frequency resource of a sub-band start ) and the RB length of the subband (L RBs ), indicating that the size is The minimum number of RBs in a DL BWP of PRBs is limited to The frequency resource information of the SBFD subband. start , L RBs and The method for defining the resource indication value (RIV) is as shown in [Table 24] and [Table 25]. In this case, it is defined as

[0425]

Table 24

[0426]

[0427]

Table 25

[0428]

[0429] Hereinafter, a method of indicating a frequency resource transmission position when a maximum number of RBs of a SBFD subband is given will be described.

[0430] This example describes a method for transmitting a start virtual RB (RB) by using a frequency resource of a sub-band start ) and the RB length of the subband (L RBs ), indicating the size is The maximum number of RBs in a DL BWP of PRBs is limited to The frequency resource information of the SBFD subband. start , L RBs and The method for defining the resource indication value (RIV) is as shown in [Table 26] and [Table 27]. In this case, it is defined as

[0431]

Table 26

[0432]

[0433]

Table 27

[0434]

[0435] Hereinafter, a method of indicating the frequency resource transmission position when the maximum and minimum RB numbers of the SBFD subband are given will be described.

[0436] This example describes a method for transmitting a start virtual RB (RB) by using a frequency resource of a sub-band start ) and the RB length of the subband (L RBs ), indicating that the size is The maximum number of RBs in a DL BWP of PRBs is limited to And the minimum number of RBs is limited to The frequency resource information of the SBFD subband. start , L RBs , and The method for defining the resource indication value (RIV) is shown in Table 28. In this case, it is defined as

[0437]

Table 28

[0438]

[0439] [SBFD: SBFD subband parameter set related]

[0440] The length of one RB constituting the SBFD UL subband may be determined according to a parameter set of the SBFD UL subband. In order to prevent a resource grid alignment problem from occurring during operation of the SBFD system, it may be necessary to select a parameter set of the SBFD UL subband based on SBFD subband configuration information such as DL subband and UL region. As a method of configuring a parameter set of the SBFD UL subband, the following first and second embodiments may be given.

[0441] <First embodiment: a method for configuring an SBFD subband parameter set in a cell-specific SBFD system>

[0442] This example describes a method that enables configuration of a parameter set for an SBFD subband when a cell-specific SBFD system is operating. An SBFD UE operating in a random access manner may operate as a cell-specific SBFD system, and the SBFD UE may receive SBFD configuration information through an SIB. The reference point of the RIV may be point A, which is used as a common reference point in the 5G NR standard. A cell may have one or more BWPs, and each BWP may be configured with a different parameter set. In this case, the SBFD UL subband may prevent resource grid alignment issues by using the largest parameter set among the available parameter sets in the valid cell. In this case, it may be configured as

[0443] <Second embodiment: A method for configuring an SBFD subband parameter set in a partial bandwidth specific (BWP specific) SBFD system>.

[0444] This example describes a method that enables configuration of parameter sets for SBFD subbands when a partial bandwidth specific SBFD system is operating. An SBFD UE in RRC_CONNECTED state may operate as a partial bandwidth specific SBFD system, and the SBFD UE may receive SBFD configuration information via a dedicated RRC signal. The reference point for the RIV may be the minimum VRB value of the DL BWP. DL subbands that share the same time resources with the SBFD UL subband and UL areas used only for UL transmission may use different parameter sets. In this case, the SBFD UL subband may prevent resource grid alignment issues by using the larger of the two parameter sets used. In this case, it may be configured as the total number of RBs that constitute the DL BWP.

[0445] Fig.17 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0446] refer to Fig.17, the UE may include a transceiver (referring to the UE receiver 1700 and the UE transmitter 1710 as a whole), a memory (not shown) and a UE processor 1705 (or a UE controller or processor). The UE transceivers 1700 and 1710, the memory and the UE processor 1705 may operate according to the above-mentioned UE communication method. The UE processor 1705 may not only operate according to the above-mentioned Figures 1 to 16B The operation of the UE may be controlled according to each of the implementation modes, and the operation of the UE may also be controlled according to a combination of at least one of them.

[0447] The components of the UE are not limited to the above examples. For example, the UE may include more or fewer components than the above components. In addition, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0448] The transceiver can transmit / receive signals with the base station. The signals may include control information and data. To this end, the transceiver may include: a radio frequency transmitter configured to up-convert and amplify the frequency of the transmitted signal, a radio frequency receiver configured to low-noise amplify the received signal and down-convert its frequency, and the like. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the radio frequency transmitter and the radio frequency receiver.

[0449] In addition, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit a signal output from the processor through the wireless channel.

[0450] The memory may store programs and data required for UE operation. In addition, the memory may also store control information or data included in the signal sent / received by the UE. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM or DVD, or a combination of storage media. In addition, the memory may also include multiple memories.

[0451] In addition, the processor may also control a series of processes so that the UE can operate according to the above-mentioned embodiments. For example, the processor may control the components of the UE to receive DCI configured as two layers so as to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the processor may perform operations to control the components of the UE by executing a program stored in a memory.

[0452] Fig.18 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0453] refer to Fig.18, the base station may include a transceiver (referring to the base station receiver 1800 and the base station transmitter 1810 as a whole), a memory (not shown) and a base station processor 1805 (or a base station controller or processor). The base station transceivers 1800 and 1810, the memory and the base station processor 1805 may operate according to the above-mentioned base station communication method. The base station processor 1705 may not only operate according to the above-mentioned Figures 1 to 16B The operation of the base station may be controlled according to each of the embodiments described above, or may be controlled according to a combination of at least one of them. However, the components of the base station are not limited to the above examples. For example, the base station may include a greater or lesser number of components than the above components. In addition, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0454] The transceiver can transmit / receive signals with the UE. The signals may include control information and data. To this end, the transceiver may include: a radio frequency transmitter configured to up-convert and amplify the frequency of the transmitted signal, a radio frequency receiver configured to low-noise amplify the received signal and down-convert its frequency, and the like. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the radio frequency transmitter and the radio frequency receiver.

[0455] In addition, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit a signal output from the processor through the wireless channel.

[0456] The memory may store programs and data required for the base station operation. In addition, the memory may also store control information or data included in the signal sent / received by the base station. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM or DVD, or a combination of storage media. In addition, the memory may also include multiple memories.

[0457] The processor may also control a series of processes so that the base station can operate according to the above-mentioned embodiments of the present disclosure. For example, the processor may control the components of the base station to configure a DCI configured as two layers including allocation information about multiple PDSCHs, and send the DCI. The processor may include multiple processors, and the processor may perform operations to control the components of the base station by executing a program stored in a memory.

[0458] The methods disclosed in the claims and / or the methods according to the embodiments described in the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0459] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. The at least one program includes instructions that enable the electronic device to perform the method of various embodiments of the present disclosure defined by the attached claims and / or disclosed herein.

[0460] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage device, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices, or magnetic tape. Optionally, any combination of some or all of the memories can also constitute the memory for storing programs. In addition, multiple such memories can also be included in the electronic device.

[0461] In addition, the program can be stored in a connectable storage device that can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), and a storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. In addition, a separate storage device on a communication network can also access the portable electronic device.

[0462] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form according to the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected according to the presented situation, and the present disclosure is not limited to the elements expressed in singular or plural form. Therefore, the elements expressed in plural form may also include only a single element, or the elements expressed in singular form may also include multiple elements.

[0463] The embodiments of the present disclosure described and shown in this specification and the accompanying drawings are merely specific examples proposed to facilitate the explanation of the technical content of the embodiments of the present disclosure and to help understand the embodiments of the present disclosure, and are not intended to limit the scope of the embodiments of the present disclosure. In other words, it is obvious to those skilled in the art that other variants can be implemented based on the technical concept of the present disclosure. In addition, the above-mentioned respective embodiments can also be used in combination as needed. For example, a part of an embodiment of the present disclosure can be combined with a part of another embodiment to operate a base station and a terminal. For example, a part of the first embodiment of the present disclosure can be combined with a part of the second embodiment to operate a base station and a terminal. Moreover, although the above-mentioned embodiments are described based on an FDD LTE system, other variants of the technical concept based on these embodiments can also be implemented in other communication systems such as TDD LTE, 5G or NR systems.

[0464] In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order in which the steps of each method are executed, and the sequential relationship between the steps may be changed, or the steps may be executed in parallel.

[0465] Optionally, in the drawings describing the method of the present disclosure, certain elements may be omitted, and only certain elements may be included in the drawings without departing from the essential spirit and scope of the present disclosure.

[0466] Furthermore, in the method of the present disclosure, part or all of the content of each embodiment may be implemented in combination without departing from the essential spirit and scope of the present disclosure.

[0467] Various embodiments of the present disclosure have been described above. The above description of the present disclosure is for illustrative purposes and is not intended to limit the embodiments of the present disclosure to the embodiments described herein. Those skilled in the art will understand that other specific modifications and changes to the form of the present disclosure can be easily made without changing the technical concept or basic features of the present disclosure. The scope of the present disclosure is defined by the appended claims rather than the above detailed description, and the scope of the present disclosure should be interpreted as including all changes or modifications derived from the meaning and scope of the claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system supporting full-duplex communication, the method comprising: receiving configuration information from a base station, the configuration information comprising information about at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink UL subband for subband non-overlapping full-duplex SBFD communication; Based on the configuration information, identifying an index of at least one resource block RB corresponding to an available uplink subband in the downlink bandwidth part BWP; as well as An uplink signal is transmitted by using the available uplink subband in the downlink BWP based on the identified index of the at least one RB.

2. The method according to claim 1, wherein: The location of the uplink subband for the SBFD communication in the frequency domain is identified using one of a common RB index, a specific BWP RB index, and a subband RB index.

3. The method according to claim 1, wherein: The maximum frequency bandwidth and the minimum frequency bandwidth of the uplink subband are determined according to specific conditions of a cell.

4. The method according to claim 1, wherein: The length of resource blocks (RBs) constituting the uplink subband is determined based on a parameter set of the uplink subband, and a maximum parameter set among available parameter sets of a cell is used as the parameter set.

5. A method performed by a terminal in a wireless communication system supporting full-duplex communication, the method comprising: receiving configuration information of a downlink bandwidth part BWP and an uplink BWP; Based on the configuration information and the subcarrier spacing, identifying a nominal DL subband in the downlink DL BWP and a nominal DL subband in the uplink BWP; as well as Actual DL subbands available among the nominal downlink subbands and actual UL subbands available among the nominal uplink subbands are identified.

6. A terminal in a wireless communication system supporting full-duplex communication, the terminal comprising: Transceiver; as well as Processor, configured as: receiving, by the transceiver, configuration information from a base station, the configuration information comprising information on at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink UL subband for sub-band non-overlapping full-duplex SBFD communication; Based on the configuration information, identifying an index of at least one resource block RB corresponding to an available uplink subband in the downlink bandwidth part BWP; as well as An uplink signal is transmitted, by the transceiver, by using the available uplink subband in the downlink BWP based on the identified index of the at least one RB.

7. The terminal according to claim 6, wherein: The location of the uplink subband for the SBFD communication in the frequency domain is identified using one of a common RB index, a specific BWP RB index, and a subband RB index.

8. The terminal according to claim 6, wherein: The maximum frequency bandwidth and the minimum frequency bandwidth of the uplink subband are determined according to specific conditions of a cell.

9. The terminal according to claim 6, wherein: The length of resource blocks (RBs) constituting the uplink subband is determined based on a parameter set of the uplink subband, and a maximum parameter set among available parameter sets of a cell is used as the parameter set.

10. A terminal in a wireless communication system supporting full-duplex communication, the terminal comprising: Transceiver; as well as Processor, configured as: receiving configuration information of a downlink bandwidth part BWP and an uplink BWP; Based on the configuration information and the subcarrier spacing, identifying a nominal DL subband in the downlink DL BWP and a nominal DL subband in the uplink BWP; as well as Actual DL subbands available among the nominal downlink subbands and actual UL subbands available among the nominal uplink subbands are identified.

11. A method performed by a base station in a wireless communication system supporting full-duplex communication, the method comprising: sending configuration information, the configuration information comprising information about at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink UL subband for subband non-overlapping full-duplex SBFD communication; Based on the configuration information, identifying an index of at least one resource block RB corresponding to an available uplink subband in the downlink bandwidth part BWP; as well as An uplink signal is received from a terminal by using the available uplink subband in the downlink BWP based on the identified index of the at least one RB.

12. The method according to claim 11, wherein: The location of the uplink subband for the SBFD communication in the frequency domain is identified using one of a common RB index, a specific BWP RB index, and a subband RB index.

13. The method according to claim 11, wherein: The maximum frequency bandwidth and the minimum frequency bandwidth of the uplink subband are determined according to specific conditions of a cell.

14. The method according to claim 11, wherein: The length of resource blocks (RBs) constituting the uplink subband is determined based on a parameter set of the uplink subband, and a maximum parameter set among available parameter sets of a cell is used as the parameter set.

15. A base station in a wireless communication system supporting full-duplex communication, the base station comprising: Transceiver; as well as Processor, configured as: sending, by the transceiver, configuration information including information about at least one of a maximum frequency bandwidth and a minimum frequency bandwidth of an uplink (UL) subband for subband non-overlapping full-duplex (SBFD) communication; Based on the configuration information, identifying an index of at least one resource block RB corresponding to an available uplink subband in the downlink bandwidth part BWP; as well as An uplink signal is received, by the transceiver, from a terminal by using the available uplink subband in the downlink BWP based on the identified index of the at least one RB.

Images