Method and device for transmitting physical uplink shared channel in communication system

Abstract

The present disclosure provides a method performed by a terminal in a wireless communication system. The method comprises the steps of: receiving configuration information through radio resource control (RRC) signaling; receiving downlink control information (DCI); identifying resources allocated to a PUSCH on the basis of at least one of the configuration information or the DCI; identifying, on the basis of at least one of the configuration information or the DCI, muting-related information for at least one resource among the resources allocated to the PUSCH; applying muting of the PUSCH to a resource determined on the basis of the muting-related information; and transmitting the PUSCH, wherein the muting-related information may include at least one of information about whether the muting is applied or information about the resource to which the muting is applied.

Description

Method and device for transmitting a physical uplink shared channel in a communication system

[0001] The present disclosure relates generally to a wireless communication system, and more particularly to a method and apparatus for transmitting a physical uplink shared channel (PUSCH) in a wireless communication system.

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

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

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

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

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

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

[0008] Various embodiments of the present disclosure may provide a method and apparatus for transmitting a physical uplink shared channel (PUSCH) in a wireless communication system.

[0009] The present disclosure relates to a method and device for transmitting a physical uplink shared channel (PUSCH) in a communication system. More specifically, the present disclosure relates to a method and device for transmitting a physical uplink shared channel (PUSCH) in a terminal configured with sub-band non-overlapping full duplex (SBFD).

[0010] The technical problems to be achieved in various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from various embodiments of the present disclosure described below.

[0011] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may be provided. The method includes the steps of receiving configuration information via radio resource control (RRC) signaling, receiving downlink control information (DCI), identifying resources allocated to a physical uplink shared channel (PUSCH) based on at least one of the configuration information or the DCI, identifying muting-related information for at least one resource among the resources allocated to the PUSCH based on at least one of the configuration information or the DCI, applying muting of the PUSCH to a resource determined based on the muting-related information, and transmitting the PUSCH, wherein the muting-related information may include at least one of information on whether muting is applied or information on a resource to which muting is applied.

[0012] According to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system may be provided. The method includes the steps of transmitting configuration information to a terminal via RRC signaling, transmitting DCI, and receiving the PUSCH from the terminal, wherein, based on at least one of the configuration information or the DCI, resources allocated to the PUSCH are configured, and based on at least one of the configuration information or the DCI, muting-related information for at least one of the resources allocated to the PUSCH is identified, and the muting-related information includes at least one of information on whether muting is applied or information on a resource to which muting is applied, and muting of the PUSCH may be applied to a resource determined based on the muting-related information.

[0013] In a wireless communication system according to one embodiment of the present disclosure, a terminal includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to receive configuration information through RRC signaling, receive DCI, and, based on at least one of the configuration information and the DCI, identify resources allocated to a PUSCH, identify muting-related information for at least one resource among the resources allocated to the PUSCH, apply muting of the PUSCH to a resource determined based on the muting-related information, and transmit the PUSCH, and the muting-related information may include at least one of information on whether muting is applied or information on a resource to which muting is applied.

[0014] In a wireless communication system according to one embodiment of the present disclosure, a base station includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to transmit configuration information to a terminal through RRC signaling, transmit DCI to the terminal, and receive a PUSCH from the terminal, and based on at least one of the configuration information or the DCI, resources allocated to the PUSCH are configured, and based on at least one of the configuration information or the DCI, muting-related information for at least one resource among the resources allocated to the PUSCH is identified, and the muting-related information includes at least one of information on whether muting is applied or information on a resource to which muting is applied, and muting of the PUSCH can be applied to a resource determined based on the muting-related information.

[0015] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0016] Various embodiments of the present disclosure can provide a method and apparatus for transmitting a physical uplink shared channel in a wireless communication system.

[0017] According to the present disclosure, a method for transmitting a physical uplink shared channel when various types of symbols or slots are used in a communication system is provided, thereby enabling more efficient data transmission and reception in various types of symbols or slots.

[0018] According to the present disclosure, a method for transmitting a physical uplink shared channel in various types of symbols or slots is provided, thereby enabling a terminal and a base station to perform smooth communication.

[0019] The effects that can be obtained from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.

[0020] The accompanying drawings are intended to aid in understanding various embodiments of the present disclosure, and provide various embodiments of the present disclosure together with detailed descriptions. However, the technical features of the various embodiments of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing represent structural elements.

[0021] FIG. 1 is a diagram illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 2 is a diagram illustrating a wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 3 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted, in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 4 is a diagram illustrating an example of a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.

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

[0026] FIG. 6 is a diagram for explaining carrier aggregation (CA) according to one embodiment of the present disclosure.

[0027] FIG. 7 is a diagram illustrating an example of a cross-carrier scheduling method according to one embodiment of the present disclosure.

[0028] FIG. 8 is a diagram illustrating an example of setting a control region (control resource set, CORESET) of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 9 is a diagram illustrating an example of downlink data channel (Physical Downlink Shared Channel) processing in a wireless communication system according to one embodiment of the present disclosure.

[0030] FIG. 10 is a diagram illustrating an example of a method for obtaining the size of a transport block in a wireless communication system according to an embodiment of the present disclosure.

[0031] FIG. 11A is a diagram illustrating an uplink-downlink resource configuration of an XDD system that flexibly divides uplink and downlink resources in the time domain and frequency domain according to one embodiment of the present disclosure.

[0032] FIG. 11b is a diagram illustrating an example of an uplink-downlink resource configuration of a full duplex communication system in which uplink and downlink resources are flexibly divided in the time domain and frequency domain, according to one embodiment of the present disclosure.

[0033] FIG. 11c is a diagram illustrating a transmission and reception structure for a duplex method according to one embodiment of the present disclosure.

[0034] FIG. 11d is a diagram illustrating an example of downlink and uplink resource settings in an XDD system.

[0035] FIG. 11e is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system to which the present disclosure is applied.

[0036] FIG. 11f is a diagram illustrating an SBFD setting according to one embodiment of the present disclosure.

[0037] FIG. 12 is a diagram illustrating an example of a non-SBFD symbol of a wireless communication system according to an embodiment of the present disclosure.

[0038] FIG. 13 is a diagram illustrating an example of an SBFD symbol of a wireless communication system according to one embodiment of the present disclosure.

[0039] FIG. 14 is a diagram illustrating an example of an SBFD symbol of a wireless communication system according to one embodiment of the present disclosure.

[0040] FIG. 15 is a diagram illustrating an example of an SBFD symbol of a wireless communication system according to one embodiment of the present disclosure.

[0041] FIG. 16 is a diagram illustrating an example of slots of a wireless communication system according to one embodiment of the present disclosure.

[0042] FIG. 17 is a diagram illustrating an example of slots of a wireless communication system according to one embodiment of the present disclosure.

[0043] FIG. 18 is a diagram illustrating a physical uplink shared channel (PUSCH) transmission according to one embodiment of the present disclosure.

[0044] FIG. 19 is a diagram illustrating downlink control information (DCI) according to one embodiment of the present disclosure.

[0045] FIG. 20 is a diagram illustrating downlink control information (DCI) including muting-related information according to one embodiment of the present disclosure.

[0046] FIG. 21 is a diagram illustrating downlink control information (DCI) including cell-specific muting-related information according to one embodiment of the present disclosure.

[0047] FIG. 22 illustrates a procedure of a terminal for physical uplink shared channel (PUSCH) transmission according to one embodiment of the present disclosure.

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

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

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

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

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

[0053] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments of the present disclosure are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

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

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

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

[0057] To meet the growing demand for wireless data traffic following the commercialization of 4G communication systems, efforts are being made to develop improved 5G or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are also referred to as "Beyond 4G Network" or "Post-LTE" systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio wave path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0058] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technologies, wired and wireless communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0059] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN, a big data processing technology described above, can also be considered an example of the convergence of 5G and IoT technologies.

[0060] Hereinafter, embodiments of the present disclosure will be described using a 5G system as an example, but embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Accordingly, embodiments of the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure as judged by a person skilled in the art. The contents of the present disclosure can be applied to FDD, TDD, and / or XDD (and / or SBFD, full duplex) systems.

[0061] The terms described below are defined based on the functions of the present disclosure, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification as a whole.

[0062] Hereinafter, a base station is an entity that performs resource allocation for a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.

[0063] For convenience of explanation below, some terms and names defined in the 3GPP LTE (3rd generation partnership project long term evolution) standard or 3GPP NR (new radio or new radio access technology) may be used. However, the present disclosure is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0064] FIG. 1 is a diagram illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0065] Referring to FIG. 1, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 5G) may be composed of a new radio node B (hereinafter referred to as NR gNB or NR base station) (110) and a new radio core network (NR CN) (105). A new radio user equipment (NR UE or terminal) (115) may access an external network through the NR gNB (110) and the NR CN (105).

[0066] In Fig. 1, the NR gNB (110) may correspond to an eNB (evolved node B) of an existing LTE system. The NR gNB is connected to an NR UE (115) via a wireless channel and may provide improved services than the existing node B. In the next-generation mobile communication system, all user traffic may be serviced through a shared channel. Therefore, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, and the NR gNB (110) may be responsible for this. One NR gNB may control multiple cells. In the next-generation mobile communication system, in order to implement ultra-high-speed data transmission compared to the current LTE, a bandwidth greater than the current maximum bandwidth may be applied. In addition, beamforming technology may be additionally grafted using orthogonal frequency division multiplexing (OFDM) as a wireless access technology. Additionally, an adaptive modulation and coding (AMC) method that determines a modulation scheme and channel coding rate according to the channel status of the terminal may be applied.

[0067] The NR CN (105) can perform functions such as mobility support, bearer setup, and QoS setup. The NR CN is a device that handles various control functions as well as mobility management functions for terminals and can be connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with the existing LTE system, and the NR CN can be connected to the MME (125) via a network interface. The MME can be connected to the existing base station, eNB (130).

[0068] FIG. 2 is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0069] Referring to FIG. 2, the wireless protocol of the next-generation mobile communication system is composed of NR service data adaptation protocol (SDAP) (201, 245), NR packet data convergence protocol (PDCP) (205, 240), NR RLC (210, 235), NR medium access control (MAC) (215, 230), and NR physical (PHY) (220, 225) in the terminal and NR base station, respectively.

[0070] The main functions of NR SDAP (201, 245) may include some of the following functions:

[0071] - Transfer of user plane data

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

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

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

[0075] For an SDAP layer device, a terminal can be configured by a radio resource control (RRC) message for each PDCP layer device, per bearer, or per logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device. When the SDAP header is configured, the terminal can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink by using a 1-bit indicator for reflecting the non-access stratum (NAS) quality of service (QoS) (NAS reflective QoS) and a 1-bit indicator for reflecting the access stratum (AS) QoS (AS reflective QoS) in the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

[0076] The main functions of NR PDCP (205, 240) may include some of the following functions:

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

[0078] - User data transfer function

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

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

[0081] - PDCP PDU reordering for reception

[0082] - Duplicate detection of lower layer SDUs

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

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

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

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

[0087] The main functions of NR RLC (210, 235) may include some of the following functions:

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

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

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

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

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

[0093] - Re-segmentation of RLC data PDUs

[0094] - Reordering of RLC data PDUs

[0095] - Duplicate detection function

[0096] - Protocol error detection

[0097] - RLC SDU discard function

[0098] - RLC re-establishment function

[0099] In the above, the in-sequence delivery function of the NR RLC device may refer to the function of sequentially delivering RLC SDUs received from the lower layer to the upper layer. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.

[0100] The in-sequence delivery function of the NR RLC device may include a function to reorder received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by reordering them, a function to report status of lost RLC PDUs to the transmitter, and a function to request retransmission of lost RLC PDUs.

[0101] The in-sequence delivery function of an NR RLC (210, 235) device may include a function to sequentially deliver to an upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU. In addition, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to an upper layer all RLC SDUs received before a predetermined timer starts if a predetermined timer has expired even if there is a lost RLC SDU. In addition, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to an upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.

[0102] The NR RLC (210, 235) device can process RLC PDUs in the order they are received (out of sequence delivery) and deliver them to the NR PDCP (205, 240) device.

[0103] When an NR RLC (210, 235) device receives a segment, it can receive segments stored in a buffer or to be received later, reconstruct them into a complete RLC PDU, and then transmit them to an NR PDCP device.

[0104] The NR RLC layer may not include concatenation functionality, and the functionality may be performed by the NR MAC layer or replaced by the multiplexing functionality of the NR MAC layer.

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

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

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

[0108] - Multiplexing / demultiplexing of MAC SDUs

[0109] - Scheduling information reporting function

[0110] - HARQ function (Error correction through HARQ (hybrid automatic repeat request))

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

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

[0113] - MBMS service identification function

[0114] - Transport format selection function

[0115] - Padding function

[0116] The NR PHY layer (220, 225) can perform an operation of channel coding and modulating upper layer data, converting it into an OFDM symbol and transmitting it through a wireless channel, or demodulating and channel decoding an OFDM symbol received through a wireless channel and transmitting it to a higher layer.

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

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

[0119] The horizontal axis of Fig. 3 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of resources is a resource element (RE) (301), which can be defined as 1 OFDM (orthogonal frequency division multiplexing) symbol (302) in the time axis and 1 subcarrier (303) in the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB) (304).

[0120] Figure 4 is a diagram illustrating an example of a slot structure considered in a 5G system.

[0121] FIG. 4 illustrates an example of a structure of a frame (400), a subframe (401), and a slot (402, 403). One frame (400) can be defined as 10 ms. One subframe (401) can be defined as 1 ms, and therefore one frame (400) can be composed of a total of 10 subframes (401). One slot (402, 403) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). 1 subframe (401) may be composed of one or more slots (402, 403), and the number of slots (402, 403) per 1 subframe (401) may vary depending on the setting value μ (404, 405) for the subcarrier spacing. In an example of FIG. 4, the cases where the subcarrier spacing setting value μ = 0 (404) and μ = 1 (405) are illustrated. When μ = 0 (404), 1 subframe (401) may be composed of 1 slot (402), and when μ = 1 (405), 1 subframe (401) may be composed of 2 slots (403). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.

[0122]

[0123] Next, the bandwidth part (BWP) setting in the 5G communication system will be described in detail with reference to Fig. 5.

[0124] Figure 5 is a diagram illustrating an example of settings for the bandwidth portion in a 5G communication system.

[0125] FIG. 5 illustrates an example in which the UE bandwidth (500) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (501) and bandwidth portion #2 (BWP#2) (502). The base station can set one or more bandwidth portions to the UE, and can set information for each bandwidth portion, such as, for example, Table 2 below. The BWP below can be referred to as BWP setting information.

[0126]

[0127] Of course, the present invention is not limited to the above examples, and in addition to the above configuration information, various parameters related to the bandwidth portion may be configured for the terminal. The above information may be transmitted from the base station to the terminal via higher layer signaling, for example, RRC signaling. At least one of the configured bandwidth portions may be activated. Whether or not the configured bandwidth portion is activated may be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (downlink control information).

[0128] According to some embodiments, a terminal before RRC connection can be configured with an initial bandwidth portion (initial BWP) for initial access from a base station through a master information block (MIB). More specifically, the terminal can receive, during the initial access phase, configuration information about a control resource set (CORESET) and a search space on which a physical downlink control channel (PDCCH) can be transmitted for receiving system information (remaining system information; which may correspond to RMSI or system Information block 1; SIB1) required for initial access, through the MIB. The control resource set and the search space configured by the MIB can each be regarded as identity (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control resource set #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and occasion settings for control resource set #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set to control resource set #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

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

[0130] In some embodiments, when the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, by the base station setting the bandwidth portion frequency location (configuration information 2) to the terminal, the terminal can transmit and receive data at a specific frequency location within the system bandwidth.

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

[0132] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data within that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a traffic-free environment may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free environment, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data in the 100 MHz bandwidth portion according to the instructions of the base station.

[0133] In the method of configuring the bandwidth part, terminals before RRC connection can receive configuration information for the initial bandwidth part through the MIB during the initial access stage. More specifically, the terminal can configure a control resource set (CORESET) for a downlink control channel on which a DCI scheduling an SIB can be transmitted from the MIB of the PBCH (physical broadcast channel). The bandwidth of the control resource set configured in the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH on which the SIB is transmitted through the configured initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (OSI), paging, and random access.

[0134] FIG. 6 is a diagram illustrating carrier aggregation (CA) according to one embodiment of the present disclosure.

[0135] Referring to Fig. 6, when CA is set (600), a PCell (primary cell) and an SCell (secondary cell) can be set in the terminal.

[0136] PCell is included in PCC (primary component carrier) and can provide RRC connection establishment / re-establishment, measurement, mobility procedures, random access procedures and selection, system information acquisition, initial random access, security key change, and non-access stratum (NAS) functions.

[0137] Since the UE performs system information monitoring through the PCell, the PCell is not deactivated, and in the UL, the PCC is carried through the PUCCH (physical uplink control channel) for control information transmission. In addition, only one RRC connection is possible between the UE and the PCell, and PDCCH / PDSCH / PUSCH (physical uplink shared channel) / PUCCH transmission is possible. In addition, in the secondary cell group, the PSCell (spcell of a secondary cell group) can be set as the PCell and operate. The operations for the PCell described below can also be performed on the PSCell.

[0138] Up to 31 SCells can be added, and when additional radio resources are required, SCells can be configured via RRC messages (e.g., dedicated signaling). RRC messages can include the physical cell ID for each cell and the DL carrier frequency (absolute radio frequency channel number: ARFCN). PDCCH / PDSCH / PUSCH transmission is possible via SCells. To conserve the UE's battery, the MAC layer supports dynamic activation and deactivation of SCells.

[0139] Cross-carrier scheduling may involve assigning all L1 control channels or at least one L2 control channel (e.g., a PDCCH) for at least one other component carrier (CC) to a single CC. A carrier indicator field (CIF) may be used to transmit data information for another CC via the PDCCH of one CC.

[0140] Resources (PDSCH, PUSCH) for data transmission of the CC or resources (PDSCH, PUSCH) for data transmission of another CC can be allocated through control information transmitted through the PDCCH of one CC.

[0141] With the application of cross-carrier scheduling, n-bit CIF is added to the DCI format, and the size of the bits may vary depending on the upper layer settings or the DCI format, and the location of the CIF within the DCI format may be fixed.

[0142] FIG. 7 is a diagram illustrating an example of a cross-carrier scheduling method according to one embodiment of the present disclosure.

[0143] Referring to 710 of FIG. 7, PDSCH or PUSCH for two CCs (e.g., CC#1, CC#2) can be scheduled through PDCCH (701) of one CC (e.g., CC#2).

[0144] Also, referring to 720 of FIG. 7, when a total of four CCs are set, the PDSCH or PUSCH of each CC can be scheduled using the PDCCHs (721, 723) of the two CCs.

[0145] Each CC can be mapped to a CI (carrier indicator) value for CIF application, which can be transmitted from the base station to the terminal via a dedicated RRC signal as a UE specific setting.

[0146] Each PDSCH / PUSCH CC can be scheduled from a single DL CC. Therefore, the UE only needs to monitor the PDCCH on the DL CC for each PDSCH / PUSCH CC. The UE can obtain PUSCH scheduling information on the linked UL carrier by monitoring the PDCCH on the DL CC. The UE can obtain PDSCH scheduling information on the linked DL carrier by monitoring the PDCCH on the DL CC.

[0147] FIG. 8 is a diagram illustrating an example of setting a control region (CORESET) of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0148] Referring to FIG. 8, FIG. 8 illustrates an example in which two control regions (control region #1 (CORESET #1) (801), control region #2 (CORESET #2) (802)) are set within a terminal bandwidth portion (810) in the frequency axis and one slot (820) in the time axis. The control regions (801, 802) may be set to a specific frequency resource (803) within the entire terminal bandwidth portion (810) in the frequency axis. The control regions (801, 802) may be set to one or more OFDM symbols in the time axis, which may be defined as a control region length (control resource set duration, 804). In the example of FIG. 8, control region #1 (801) is set to a control region length of two symbols, and control region #2 (802) is set to a control region length of one symbol.

[0149] The control region in 5G described above can be set by the base station to the terminal via higher-layer signaling (e.g., system information, MIB, RRC signaling). Setting a control region for a terminal means providing the terminal with information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, the information in Table 3 may be included.

[0150]

[0151] The number of CCEs required to transmit a PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs can be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel can be transmitted through L CCEs. The UE must detect the signal (blind decode) without knowing information about the downlink control channel, and a search space representing a set of CCEs for blind decoding is defined. The search space is a set of downlink control channel candidates consisting of CCEs that the UE must attempt to decode at a given aggregation level, and since there are various aggregation levels that create a single bundle with 1, 2, 4, 8, or 16 CCEs, 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.

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

[0153] In 5G, parameters for a search space for a PDCCH can be configured from a base station to a terminal via higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, a monitoring period for the search space, a monitoring occasion for each symbol within a slot for the search space, a search space type (common search space or terminal-specific search space), a combination of a DCI format and an RNTI (radio network temporary identifier) ​​to be monitored in the search space, a control resource set index to be monitored for the search space, etc. to the terminal. For example, parameters for a search space for a PDCCH may include at least some of the information shown in Table 4 below.

[0154]

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

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

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

[0158] DCI format 0_0 / 1_0 with CRC (cyclic redundancy check) scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0178] [Mathematical Formula 1]

[0179]

[0180] -L: Integration level

[0181] - n CI : Carrier Index

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

[0183] - : slot index

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

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

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

[0187] - , , , , ,

[0188] - n RNTI : Terminal identifier

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

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

[0191] Accordingly, the terminal can monitor the PDCCH in the control area set by the base station and transmit and receive data based on the received control information.

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

[0193] DCI can be transmitted over the physical downlink control channel (PDCCH) after going through the channel coding and modulation process. A CRC is added to the DCI message payload, and the CRC can be scrambled based on the RNTI corresponding to the terminal's identity. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the terminal receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the terminal can determine that the message was transmitted to the terminal.

[0194] For example, a DCI scheduling a PDSCH for system information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a random access response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a paging message may be scrambled with P-RNTI. A DCI notifying a slot format indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a transmit power control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (cell RNTI).

[0195] Meanwhile, NR can provide various DCI formats as shown in Table 5 below to enable efficient control information reception by terminals.

[0196]

[0197] For example, the base station may use DCI format 1_0, DCI format 1_1, or DCI format 1_2 to schedule a PDSCH for a cell to a UE. For another example, the base station may use DCI format 0_0, DCI format 0_1, or DCI format 0_2 to schedule a PUSCH for a cell to a UE. For another example, the base station may use DCI format 0_1 ​​to indicate downlink feedback information for a configured grant PUSCH.

[0198] DCI format 1_0, when transmitted with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI or new-RNTI, may contain, for example, at least the following information:

[0199]

[0200] DCI format 1_1 may include, for example, at least the information in Table 7 when transmitted with a CRC scrambled by a cell radio network temporary identifier (C-RNTI) or a configured scheduling RNTI (CS-RNTI) or an MCS-C-RNTI or a new-RNTI.

[0201]

[0202]

[0203] DCI format 1_2, when transmitted with a CRC scrambled by a cell radio network temporary identifier (C-RNTI) or a configured scheduling RNTI (CS-RNTI) or an MCS-C-RNTI or a new-RNTI, may include, for example, at least the information shown in Table 8.

[0204]

[0205]

[0206] The maximum number of DCIs of different sizes that a terminal can receive per slot in a given cell is 4. The maximum number of DCIs of different sizes scrambled with C-RNTI that a terminal can receive per slot in a given cell is 3.

[0207] A base station can set time domain resource allocation information (e.g., information in the form of a table) for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) to a terminal through higher layer signaling (e.g., RRC signaling). For PDSCH, the base station can set resource allocation information (e.g., information in the form of a table) consisting of up to maxNrofDL-Allocations=16 entries, and for PUSCH, the base station can set resource allocation information (e.g., information in the form of a table) consisting of up to maxNrofUL-Allocations=16 entries. The time domain resource allocation information may include, for example, PDCCH-to-PDSCH slot timing (the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0) or PDCCH-to-PUSCH slot timing (the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as Table 9 or Table 10 below may be notified from the base station to the terminal.

[0208]

[0209]

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

[0211] Below, a method for allocating frequency domain resources for data channels in a 5G communication system is described.

[0212] In 5G, two types of methods for indicating frequency domain resource allocation information for downlink data channel (PDSCH) and uplink data channel (PUSCH) are supported: resource allocation type 0 and resource allocation type 1.

[0213] In resource allocation type 0, RB allocation information can be notified from the base station to the terminal in the form of a bitmap for an RBG (resource block group). At this time, an RBG can be composed of a set of consecutive VRBs, and the size P of the RBG can be determined based on a value set as a higher layer parameter (rbg-Size) and the size value of the bandwidth part defined as in Table 11 below. Table 11 shows an example of a normal RBG size P.

[0214]

[0215] The size The total number of RBGs in bandwidth part i (N RBG ) can be defined as follows.

[0216] , where

[0217] The size of the first RBG is ,

[0218] The size of the last RBG is if and P otherwise,

[0219] the size of all other RBGs is P.

[0220] N RBG Each bit in the bitmap of bit size can correspond to each RBG. RBGs can be indexed in order of increasing frequency starting from the lowest frequency position in the bandwidth part. N within the bandwidth part RBG For the RBGs of the dog, from RBG#0 to RBG#(N RBG -1) can be mapped from MSB to LSB of the RBG bitmap. If a specific bit value in the bitmap is 1, the terminal can determine that the RBG corresponding to the bit value is allocated, and if a specific bit value in the bitmap is 0, the terminal can determine that the RBG corresponding to the bit value is not allocated.

[0221] In resource allocation type 1, RB allocation information can be notified from the base station to the terminal with information on the starting position and length of consecutively allocated VRBs. At this time, interleaving or non-interleaving can be additionally applied to consecutively allocated VRBs. The resource allocation field of resource allocation type 1 can be composed of a resource indication value (RIV), and the RIV can be the starting point of the VRB (RB start ) and the length of the consecutively allocated RB (L RBs ) can be composed of. More specifically, RIV within the bandwidth part of the size can be defined as follows.

[0222] if then

[0223]

[0224] else

[0225]

[0226] where L RBs ≥1 and shall not exceed

[0227] FIG. 9 is a diagram illustrating an example of downlink data channel processing in a wireless communication system according to one embodiment of the present disclosure.

[0228] Referring to Fig. 9, a scrambling process can be performed for one codeword or each of two codewords (901). Length A sequence b of codewords q having (q) (0),...,b (q) ( -1) The scrambling sequence c obtained through initialization as in mathematical expression 3 (q) (i) A scrambled sequence through a process similar to Equation 2 can be obtained. n ID is set to a value through the upper layer parameter, or if not, as the cell ID value. can be determined, n RNTI may mean an RNTI associated with a PDSCH transmission.

[0229] [Equation 2]

[0230]

[0231] [Equation 3]

[0232]

[0233] A sequence of scrambled bits and using one of the various modulation schemes supported by the wireless communication system. A modulation symbol sequence d having a length of (q) (0),...,d (q) ( -1) can be generated (902).

[0234] For each layer in v layers Each modulation symbol can be mapped (903), which can be expressed as x(i)=[x (0) (i),...,x (v-1) (i)] T The number of layers, the number of codewords, and the codeword-layer mapping relationship are as shown in Table 12.

[0235]

[0236] Modulation symbols mapped to layers can be mapped to antenna ports as in Equation 4. {p0,...,p v-1} can be determined by the information contained in the DCI format (904).

[0237] [Equation 4]

[0238]

[0239] where i=0,1,..., , .

[0240] y who completed the above process (p) (0),...,y (p) ( ) symbols can be mapped to REs that satisfy conditions that can be used for transmission of PDSCH among REs within VRBs allocated for transmission (e.g., cannot be mapped to DM-RS resources, etc.) (905).

[0241] VRBs that have completed the above process can be mapped to PRBs using either an interleaving mapping method or a non-interleaving mapping method (906). The mapping method can be indicated through the VRB-to-PRB mapping field in the DCI. If there is no indication of a mapping method, it may imply a non-interleaving mapping method.

[0242] When a non-interleaving mapping scheme is used, VRB n can be mapped to PRB n except in certain cases. For example, in the above-mentioned certain cases, VRB n of a PDSCH scheduled using DCI format 1_0 through a common search space is mapped to PRB n+. ( may include a case where the DCI is mapped to the first PRB of the CORESET transmitted.

[0243] When the interleaving mapping method is used, the RBs within the BWP are N bundle It can be divided into RB bundles and the RB bundles can be mapped in the same manner as in Table 13.

[0244] RBs within BWP N bundle An example of dividing into RB bundles might be as follows: Starting point BWP with The set of RBs of the dog is It is divided into RB bundles, and the RB bundles can be indexed in increasing order. Here, L i means the bundle size in BWP i, which can be transmitted to the terminal by the upper layer parameter vrb-ToPRB-Interleaver. And, RB bundle 0 It consists of RBs, and RB bundle N bundle -1 is If you are satisfied with It consists of RBs of dogs and otherwise L i It can be composed of RBs of L. And the remaining RB bundles are L i It can be composed of RBs.

[0245]

[0246] According to one embodiment of the present disclosure, in a 5G NR system, an MCS index for a PDSCH, i.e., a modulation order (or scheme) Qm and a target code rate R can be determined through the following process.

[0247] [How to determine the MCS index table]

[0248] For a PDSCH scheduled through a PDCCH (PDCCH with DCI format 1_0, format 1_1, or format 1_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, MSGB-RNTI, or P-RNTI) including DCI (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, MSGB-RNTI, or P-RNTI), or for a PDSCH scheduled using PDSCH configuration SPS-Config (or SPS configuration) provided by a higher layer without a corresponding PDCCH transmission,

[0249] (a) If the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 1_1 with CRC scrambled by C-RNTI, the UE determines the modulation order Qm and the target code rate R by using the MCS index I of [Table 15]. MCS You can use the value.

[0250] (b) If the condition of (a) is not satisfied, and the UE is not configured with MCS-C-RNTI, the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with a DCI format other than DCI format 1_2 in a UE-specific search space with CRC scrambled by C-RNTI, the UE determines the modulation order Qm and the target code rate R by using MCS index I of [Table 16]. MCSYou can use the value.

[0251] (c) If the conditions of (a) and (b) are not met, and the UE is configured with MCS-C-RNTI, and the PDSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI, the UE determines the modulation order Qm and the target code rate R by using MCS index I of [Table 16]. MCS You can use the value.

[0252] (d) Conditions (a), (b), and (c) are not met, and the UE is not configured with the higher layer parameter mcs-Table given by SPS-Config, and the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam256' (if the UE is not configured with the higher layer parameter mcs-Table given by SPS-Config, and the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam256'),

[0253] (d-1) if the PDSCH is scheduled by a PDCCH with DCI format 1_1 with CRC scrambled by CS-RNTI or,

[0254] (d-2) If a PDSCH is scheduled without a corresponding PDCCH transmission using SPS-Config,

[0255] The terminal determines the modulation order Qm and the target code rate R using the MCS index I of [Table 15]. MCS You can use the value.

[0256] (e) If the conditions (a), (b), (c), and (d) are not met and the UE is configured with the higher layer parameter mcs-Table given by SPS-Config set to 'qam64LowSE',

[0257] (e-1) if the PDSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or,

[0258] (e-2) If the PDSCH is scheduled without corresponding PDCCH transmission using SPS-Config,

[0259] The UE uses the MCS index I of [Table 16] to determine the modulation order Qm and the target code rate R. MCS You can use the value.

[0260] (f) If conditions (a), (b), (c), (d), and (e) do not hold, the UE uses MCS index I of [Table 14] to determine modulation order Qm and target code rate R. MCS You can use the value.

[0261]

[0262]

[0263]

[0264] FIG. 10 is a diagram illustrating an example of a method for obtaining a transport block size (TBS) in a wireless communication system according to one embodiment of the present disclosure.

[0265] Referring to Figure 10, the terminal first determines the number of REs (N) within the slot. RE ) can be obtained (determined, or calculated) (1001). The terminal can obtain N', which is the number of REs allocated to PDSCH mapping in one PRB within the allocated resources. RE can be obtained (calculated). N' RE Is can be calculated as follows: Here, is 12, can indicate the number of OFDM symbols allocated to the PDSCH. is the number of REs of DMRS of the same CDM group within one PRB. is the number of REs occupied by overhead within a PRB as long as it is set to upper signaling, and can be set to one of 0, 6, 12, or 18 (if not set to upper signaling, it can be set to 0).

[0266] And, the total number of REs allocated to PDSCH N RE can be calculated. N RE Is It is calculated based on n PRB represents the number of PRBs allocated to the terminal. N RE The value can be calculated as above. Or, N RE Information including all cases that can be set to the value of is stored (e.g., it can be organized in the form of at least one table), , , , , nPRB N from the stored information (e.g., table) through at least one parameter value RE The value can be obtained.

[0267] And, the terminal has a temporary information bit number N info can be obtained (calculated) (1002). For example, the number of temporary information bits N info is N RE *R*Q m *v can be calculated as follows. Here, R represents a code rate, Qm represents a modulation order, and the information can be determined based on MCS (modulation and coding scheme) information included in control information (e.g., DCI, RRC configuration information, etc.). Specifically, information previously agreed upon for the code rate and modulation order (e.g., MCS index tables such as Tables 14, 15, and 16) can be used, and the code rate and modulation order can be determined based on the MCS information and the previously agreed upon information. v can represent the number of allocated layers. N info The value is calculated as above, or information including all cases (for example, in the form of at least one table) is stored, and N is stored in the stored information through at least one parameter value among R, Qm, and v. info The value can be obtained.

[0268] The terminal acquires (calculates) N info The value of can be compared with the value of 3824 (1003). N info N' is calculated in different ways depending on whether the value is less than or greater than 3824. info and TBS can be obtained (calculated) (1004).

[0269] N info If ≤3824, and N' through the formula infocan be calculated. N' info The values ​​are calculated as above, or information about all cases (e.g., at least one table) is stored, N' info , N' from the stored information through at least one parameter value among n info The value can be obtained. TBS is N' in Table 17 info N' among values ​​not less than info can be determined as the closest value.

[0270]

[0271] N info If it is >3824, and N' through the formula info can be calculated. N' info The values ​​are calculated as above, or information about all cases (e.g., at least one table) is stored, N' info , N' from the above stored table through at least one parameter value among n info The value can be obtained. TBS is N' info The values ​​and pseudo codes included in Table 18 or other forms of pseudo codes that produce the same results can be determined. Alternatively, the TBS stores information on all cases (e.g., at least one table), and R, N' info , the TBS value can be obtained from the stored information through at least one parameter value among C.

[0272]

[0273] The maximum data rate supported by a terminal in an NR system can be determined using mathematical expression 6.

[0274] [Equation 6]

[0275]

[0276] In mathematical expression 6, J is the number of carriers bound by carrier aggregation, and Rmax = 948 / 1024, is the maximum number of layers, is the maximum modulation order, f (j) is a scaling factor, μ can mean the subcarrier spacing. The terminal can be f (j) can be reported by setting μ to one of the values ​​1, 0.8, 0.75, and 0.4, and μ can be given as shown in Table 19.

[0277]

[0278] is the average OFDM symbol length, Is can be calculated as, is the maximum number of RBs in BW(j). OH (j) is an overhead value, which can be given as 0.14 for downlink and 0.18 for uplink in FR1 (band below 6 GHz), and 0.08 for downlink and 0.10 for uplink in FR2 (band above 6 GHz). For example, the maximum data rate in downlink in a cell with a frequency bandwidth of 100 MHz at a subcarrier spacing of 30 kHz can be as shown in Table 20 below through Equation 6.

[0279]

[0280] Meanwhile, the actual data rate, which represents the actual data transmission efficiency, can be the value obtained by dividing the amount of transmitted data by the data transmission time. That is, for 1 TB transmission, it can be the value obtained by dividing the TBS or the sum of two TBSs for 2 TB transmissions by the TTI (transmission time interval) length. The maximum downlink actual data rate in a cell with a 30 kHz subcarrier spacing and a 100 MHz frequency bandwidth can be determined as shown in Table 21 below depending on the number of allocated PDSCH symbols.

[0281]

[0282] Referring to the maximum data rate supported by the terminal as in Table 20 and the actual data rate according to the allocated TBS as in Table 21, it can be confirmed that there are cases where the actual data rate is greater than the maximum data rate supported by the terminal depending on the scheduling information.

[0283] In wireless communication systems, such as NR systems, the data rate that a terminal can support can be determined (calculated, acquired) between the base station and the terminal using the maximum frequency band, maximum modulation order, maximum number of layers, etc. supported by the terminal. However, the data rate that a terminal can support may differ from the actual data rate calculated based on the TBS and TTI, and in some cases, the base station may transmit data to the terminal with a TBS that is higher than the terminal's supportable data rate.

[0284] According to one embodiment of the present disclosure, a base station can configure SPS configuration information to a terminal through higher layer signaling (e.g., RRC signaling). For example, the configuration information can be transmitted to the terminal through an SPS-Config IE. The configuration information can include, for example, at least information as shown in Table 22. The base station can configure at least one SPS using the configuration information as shown in Table 22, for example, according to the capability of the terminal. When multiple SPSs are configured, the multiple SPSs can be distinguished by sps-ConfigIndex of Table 22. According to the present disclosure, sps-ConfigIndex can be referred to as an SPS index. SPS configuration (or SPS configuration information) can be configured for each BWP of a serving cell, and multiple SPS configurations can be activated simultaneously within the same BWP.

[0285]

[0286] According to one embodiment of the present disclosure, a base station can configure configuration information for a ConfiguredGrant to a terminal through higher layer signaling (e.g., RRC signaling). For example, the configuration information can be delivered to the terminal through a ConfiguredGrantConfig IE. The configuration information can configure at least one ConfiguredGrant using, for example, configuration information as shown in at least Table 23. When multiple ConfiguredGrants are configured, the multiple ConfiguredGrants can be distinguished by configuredGrantConfigIndex and / or configuredGrantConfigIndexMAC of Table 23. According to the present disclosure, configuredGrantConfigIndex and / or configuredGrantConfigIndexMAC can be referred to as a ConfiguredGrant. ConfiguredGrant configuration (or ConfiguredGrant configuration information) can be configured for each BWP of a serving cell, and multiple ConfiguredGrant configurations can be activated simultaneously within the same BWP. The above ConfiguredGrant exists in two types. Type 1 allows the terminal to transmit data through resources set through Table 23 with only RRC settings, and type 2 allows the terminal to transmit data only when the terminal receives a signal activating the ConfiguredGrant set through RRC settings and a control signal (e.g., DCI or MAC CE).

[0287]

[0288]

[0289]

[0290]

[0291]

[0292] The base station can instruct the terminal to activate or release at least one SPS or ConfiguredGrant (type 2) among the SPS or ConfiguredGrant (type 2) set through a control signal (e.g., DCI or MAC CE). For example, the base station can instruct the terminal to activate or deactivate (release) the SPS or ConfiguredGrant (type 2) by setting at least one specific field in the DCI to a specific value, scrambling a CRC generated through the DCI with a specific RNTI, and transmitting the scrambled CRC to the terminal through a PDCCH. DCI format 1_0, 1_1, or 1_2 can be used as the DCI instructing the activation or deactivation of the SPS, and DCI format 0_0, 0_1, or 0_2 can be used as the DCI instructing the activation or deactivation of the ConfiguredGrant (type 2). More specifically, if the CRC is scrambled using CS-RNTI (provided to the terminal as an RRC setting), the value of the new data indicator (NDI) field in the DCI is set to 0, the DFI flag field, if present, is set to 0, and if the PDSCH-to-HARQ_feedback timing indicator field is present and the value of the field satisfies the condition that it does not provide an inapplicable value among the values ​​of dl-DataToUL-ACK, then the DCI can be interpreted as being enabled or disabled.If there is only one SPS or ConfiguredGrant (type 2) setting, when the HARQ process number field of the DCI is set to all 0 and the redundancy version field is set to all 0, the SPS or ConfiguredGrant (type 2) is activated, the HARQ process number field of the DCI is set to all 0, the redundancy version field is set to all 0, and the modulation and coding scheme field is set to all 1, and in case of FDRA (frequency domain resource assignment) type 0 or dynamicSwitch (i.e., when the resource allocation type can be changed based on the DCI), the FDRA field is set to all 0, and in case of FDRA type 1, when the FDRA field is set to all 1, the SPS is deactivated, the HARQ process number field of the DCI is set to all 0, the redundancy version field is set to all 0, and the modulation and coding scheme field is set to all 1, and in case of FDRA type 2 (μ value is 1), the FDRA field is If all are set to 0, and all other cases are set to 1, it can be interpreted as disabling ConfiguredGrant (type2).

[0293] If there are multiple SPS or ConfiguredGrant (type2) settings, the HARQ process number field in the DCI is the SPS-config. Or, if it points to sps-ConfigIndex or configuredGrantConfigIndex in the ConfiguredGrant setting, and the redundancy version field of the DCI is all set to 0, it can be interpreted as activation of the SPS or ConfiguredGrant (type 2) corresponding to the sps-ConfigIndex or configuredGrantConfigIndex, if the redundancy version field of the DCI is all set to 0 and the modulation and coding scheme fields are all set to 1, and in the case of FDRA type 0 or dynamicSwitch, if the FDRA field is all set to 0, and in the case of FDRA type 1, if the FDRA field is all set to 1, it can be interpreted as deactivation of the SPS corresponding to the sps-ConfigIndex, if the redundancy version field of the DCI is all set to 0 and the modulation and coding scheme fields are all set to 1, and in the case of FDRA type 2 (μ value is 1), if the FDRA field is all set to 0, and in other cases, if it is all set to 1, it can be interpreted as deactivation of the ConfiguredGrant (type 2).

[0294] When a terminal receives a DCI indicating SPS deactivation, it clears the configured downlink assignment of the corresponding serving cell if it exists, and if the timeAlignmentTimer associated with the TAG including the serving cell to which HARQ feedback is to be transmitted is running, it can transmit an ACK for the deactivation.

[0295] When the terminal receives a DCI indicating deactivation of ConfiguredGrant, it triggers 'configured uplink grant confirmation' and transmits a MAC CE (Configured Grant Confirmation MAC CE or Multiple Entry Configured Grant Confirmation MAC CE) confirming 'deactivation of configured uplink grant', and then clears the configured uplink grant(s).

[0296] When a terminal receives a DCI indicating SPS activation, the terminal can store the downlink assignment and associated HARQ information of the corresponding serving cell as a configured downlink assignment and (re-)initialize the configured downlink assignment of the corresponding serving cell.

[0297] When the terminal receives a DCI indicating activation of ConfiguredGrant, it triggers 'configured uplink grant confirmation', stores the uplink grant and associated HARQ information of the corresponding serving cell as the configured uplink grant, and (re-)initializes the configured uplink grant of the corresponding serving cell.

[0298] The base station can schedule retransmission for SPS PDSCH transmission or ConfiguredGrant PUSCH transmission by setting the value of the NDI field of DCI to 1 and scrambling the CRC of the DCI with CS-RNTI and transmitting it through PDCCH.

[0299] The base station can transmit the PDSCH to the resources determined according to the RRC settings and activation DCI signal. More specifically, the transmission slot of the Nth PDSCH can be determined as in Equation 7. The HARQ process ID associated with the SPS transmission can be determined as in Equation 8 when harq-ProcID-Offset is not set, and as in Equation 9 when it is set.

[0300] [Equation 7]

[0301] (numberOfSlotsPerFrame×SFN + slot number in the frame) =

[0302] [(numberOfSlotsPerFrame× SFN start time + slotstart time) + N ×periodicity×numberOfSlotsPerFrame / 10] modulo (1024 ×numberOfSlotsPerFrame)

[0303] - SFN start time and slotstart time indicate the SFN and slot of the first PDSCH transmission for which the configured downlink assignment is (re-)initialized, and numberOfSlotsPerFrame indicates the number of slots contained in the frame.

[0304] [Equation 8]

[0305] HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame×periodicity))] modulonrofHARQ-Processes

[0306] - CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame]

[0307] - CURRENT_slot points to the slot index of the first transmission point in the bundle of configured downlink assignments.

[0308] [Equation 9]

[0309] HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame×periodicity))] modulonrofHARQ-Processes+harq-ProcID-Offset

[0310] - CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame]

[0311] - CURRENT_slot points to the slot index of the first transmission point in the bundle of configured downlink assignments.

[0312] The terminal can transmit a PUSCH to a resource determined by the RRC settings (ConfiguredGrant type 1). More specifically, the location of the Nth uplink grant can be determined as shown in Equation 10.

[0313] [Equation 10]

[0314] [(SFN ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot) + (slot number in the frame ×numberOfSymbolsPerSlot) + symbol number in the slot] =

[0315] (timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+ N×periodicity) modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

[0316] The terminal can transmit a PUSCH to a resource determined (ConfiguredGrant type 1) based on the RRC configuration and activation DCI signal. More specifically, the location of the Nth uplink grant can be determined as shown in Equation 11.

[0317] [Equation 11]

[0318] [(SFN ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot) + (slot number in the frame ×numberOfSymbolsPerSlot) + symbol number in the slot] =

[0319] [(SFN start time ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+ slotstart time×numberOfSymbolsPerSlot+ symbolstart time) + N ×periodicity] modulo (1024 ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)

[0320] - SFN start time, slotstart time and symbolstart time indicate the SFN, slot and symbol of the first PUSCH transmission for which the configured uplink grant is (re-)initialized, and numberOfSlotsPerFrame indicates the number of slots included in the frame.

[0321] The HARQ process ID associated with the first symbol of ConfiguredGrant UL transmission can be determined as in Equation 12 when harq-ProcID-Offset2 and cg-RetransmissionTimer are not set, and as in Equation 13 when harq-ProcID-Offset2 is set. When cg-RetransmissionTimer is set, the terminal can select one of the available HARQ process IDs among the ConfiguredGrant settings. The terminal can prioritize retransmission over initial transmission.

[0322] [Equation 12]

[0323] HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes

[0324] - CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame × numberOfSymbolsPerSlot + symbol number in the slot)

[0325] -numberOfSlotsPerFrame represents the number of slots contained in the frame, and numberOfSymbolsPerSlot represents the number of symbols contained in the slot.

[0326] - CURRENT_symbol points to the symbol index of the first transmission point of the bundle of the configured uplink grant.

[0327] [Equation 13]

[0328] HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset2

[0329] - CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame × numberOfSymbolsPerSlot + symbol number in the slot)

[0330] -numberOfSlotsPerFrame represents the number of slots contained in the frame, and numberOfSymbolsPerSlot represents the number of symbols contained in the slot.

[0331] - CURRENT_symbol points to the symbol index of the first transmission point of the bundle of the configured uplink grant.

[0332] According to one embodiment of the present disclosure, DCI format 0_1 ​​may be set to include a DFI (downlink feedback information) field (1 bit). When the CRC of DCI format 0_1 ​​in which the value of the DFI field is 1 is scrambled with CS-RNTI, the DCI format 0_1 ​​is interpreted to include a DCI format indicator (Identifier for DCI formats, 1 bit), a carrier indicator (0 or 3 bits), a DFI flag (1 bit if set), a HARQ-ACK bitmap (16 bits), and a TPC command for a scheduled PUSCH (2 bits), and the remaining fields may all be filled with 0. The HARQ process index may be mapped in order from the MSB to the LSB of the HARQ-ACK bitmap, and a value of 1 may indicate ACK and a value of 0 may indicate NACK. If the value of the above DFI field is 0, the DCI can be used for other purposes (PUSCH scheduling or (de)activation of ConfiguredGrant). The HARQ-ACK bitmap corresponds to all HARQ process(es) of the serving cell, and the carrier indicator can indicate which serving cell it is.

[0333] For a PUSCH transmission configured by ConfiguredGrant, if the reception time of the first symbol of the PDCCH in which the DCI format 0_1 ​​is transmitted is located after the number of symbols given by cg-minDFI-Delay (configured through RRC settings such as Table 23) from the last symbol of the PUSCH transmission or any one last symbol of the PUSCH repeated transmission, the HARQ-ACK information of the corresponding HARQ process index (corresponding to the PUSCH transmission) included in the DCI format 0_1 ​​may be valid.

[0334] For a PUSCH transmission scheduled by a DCI format, if the reception time of the first symbol of the PDCCH in which the DCI format 0_1 ​​is transmitted is located after the number of symbols given by cg-minDFI-Delay (set through the RRC setting as in Table 23) from the last symbol of the PUSCH transmission, the HARQ-ACK information of the corresponding HARQ process index (corresponding to the PUSCH transmission) included in the DCI format 0_1 ​​may be valid.

[0335] In the case of PUSCH transmission in multiple slots scheduled by DCI format, the criteria for determining whether HARQ-ACK information is valid may differ depending on whether HARQ-ACK information of the corresponding HARQ process index (corresponding to the PUSCH transmission) included in the DCI format 0_1 ​​is ACK or NACK. If the HARQ-ACK information is ACK, if the reception time of the first symbol of the PDCCH in which the DCI format 0_1 ​​is transmitted is located after the number of symbols given by cg-minDFI-Delay (set through RRC settings such as Table 23) from the last symbol of the PUSCH transmission in the first slot among the PUSCH transmissions in multiple slots, the HARQ-ACK information may be determined to be valid. If the HARQ-ACK information is NACK, if the reception time of the first symbol of the PDCCH in which the DCI format 0_1 ​​is transmitted is located after the number of symbols given by cg-minDFI-Delay (set through the RRC setting as shown in Table 23) from the last symbol of the PUSCH transmission in the last slot among the PUSCH transmissions in multiple slots, the HARQ-ACK information may be determined to be valid.

[0336] A terminal may not expect different cg-minDFI-Delay values ​​for each of the multiple ConfiguredGrants included in a single BWP.

[0337] While 5G mobile communication services have introduced additional coverage expansion technologies compared to LTE, actual 5G mobile communication services will generally utilize a TDD (time division duplex) system, which is suitable for services with a high proportion of downlink traffic. Furthermore, as the center frequency increases to expand the frequency band, the coverage between base stations and terminals decreases, making coverage enhancement a key requirement for 5G mobile communication services. Specifically, to support services where the terminal transmit power is generally lower than that of the base station and the downlink traffic proportion is high, and because the downlink portion of the time domain is higher than that of the uplink, uplink channel coverage enhancement is a key requirement for 5G mobile communication services. Physical methods for improving uplink channel coverage between base stations and terminals include increasing the uplink channel's time resources, lowering the center frequency, or increasing the terminal's transmit power. However, changing the frequency may be limited because frequency bands are determined by each network operator. Additionally, because the maximum transmission power of a terminal is regulated to reduce interference, there may be restrictions on increasing the maximum transmission power of a terminal to improve coverage.

[0338] Therefore, in order to improve the coverage of base stations and terminals, in addition to dividing uplink and downlink resources in the time domain according to the traffic proportions of uplink and downlink as in a TDD system, uplink and downlink resources can also be divided in the frequency domain as in an FDD (frequency division duplex) system. In one embodiment, a system that can flexibly divide uplink resources and downlink resources in the time domain and the frequency domain may be referred to as an XDD (cross division duplex) system, a Flexible TDD system, a Hybrid TDD system, a TDD-FDD system, a Hybrid TDD-FDD system, etc., and for convenience of explanation, this will be described as an XDD system in the present disclosure. According to one embodiment, X in XDD may mean time or frequency.

[0339] FIG. 11A is a diagram illustrating an uplink-downlink resource configuration of an XDD system that flexibly divides uplink and downlink resources in the time domain and frequency domain according to one embodiment of the present disclosure.

[0340] Referring to FIG. 11a, from the base station perspective, the uplink-downlink configuration (1100a) of the entire XDD system can flexibly allocate resources to each symbol or slot (1102a) according to the traffic proportions of uplink and downlink for the entire frequency band (1101a). However, this is just an example, and the unit to which resources are allocated is not limited to a symbol or slot (1102a), and resources can also be flexibly allocated according to units such as mini slots. At this time, a guard band (1104a) can be allocated between the frequency bands of the downlink resources (1103a) and the uplink resources (1105a). This guard band (1104a) can be allocated as a measure to reduce interference applied to the uplink channel or signal reception due to out-of-band emission generated when the base station transmits a downlink channel or signal in the downlink resources (1103a). At this time, for example, terminal 1 (1110a) and terminal 2 (1120a), which have overall more downlink traffic than uplink traffic due to the base station settings, can be allocated downlink and uplink resource ratios of 4:1 in the time domain. At the same time, terminal 3 (1130a), which operates at the cell edge and has insufficient uplink coverage, can be allocated only uplink resources during a specific time interval due to the base station settings. Additionally, terminal 4 (1140a), which operates at the cell edge and has insufficient uplink coverage but relatively large amounts of downlink and uplink traffic, can be allocated more uplink resources in the time domain and more downlink resources in the frequency band for uplink coverage. As in the example described above, terminals with relatively large downlink traffic operating at the cell center can be allocated more downlink resources in the time domain, and terminals with relatively insufficient uplink coverage operating at the cell edge can be allocated more uplink resources in the time domain, which is advantageous.

[0341] FIG. 11b is a diagram illustrating an example of an uplink-downlink resource configuration of a full duplex communication system in which uplink and downlink resources are flexibly divided in the time domain and frequency domain, according to one embodiment of the present disclosure.

[0342] According to an example illustrated in FIG. 11b, all or part of downlink resources (1100b) and uplink resources (1101b) may be configured to overlap in the time and frequency domains. Downlink transmission from a base station to a terminal may be performed in an area configured as downlink resources (1100b), and uplink transmission from a terminal to a base station may be performed in an area configured as uplink resources (1101b).

[0343] In an example of FIG. 11b, the downlink resources (1110b) and uplink resources (1111b) may be configured to overlap entirely in the time resources corresponding to the symbol or slot (1102b) and the frequency resources corresponding to the bandwidth (1103b). In this case, since the downlink resources (1110b) and uplink resources (1111b) overlap in time and frequency, downlink and uplink transmission and reception of a base station or terminal can occur simultaneously in the same time and frequency resources.

[0344] In another example of FIG. 11b, a portion of the downlink resources (1120b) and uplink resources (1121b) may be configured to overlap in the time resources corresponding to symbols or slots and the frequency resources corresponding to the bandwidth (1103b). In this case, downlink and uplink transmission and reception of a base station or terminal may occur simultaneously in some areas where the downlink resources (1120b) and uplink resources (1121b) overlap.

[0345] In another example of FIG. 11b, downlink resources (1130b) and uplink resources (1131b) can be set so that they do not overlap in time resources corresponding to symbols or slots and frequency resources corresponding to bandwidth (1103b).

[0346] FIG. 11c is a diagram illustrating a transmission and reception structure for a duplex method according to one embodiment of the present disclosure.

[0347] The transmission / reception structure illustrated in FIG. 11c can be used in a base station device or a terminal device. According to the transmission / reception structure illustrated in FIG. 11c, the transmitter can be composed of blocks such as a transmission baseband block (Tx Baseband, 1110c), a digital pre-distortion block (Digital Pre-Distortion; DPD, 1111c), a digital-to-analog converter (DAC, 1112c), a pre-driver (Pre-driver, 1113c), a power amplifier (PA, 1114c), and a transmission antenna (Tx Antenna, 1115c). Each block can perform the following roles.

[0348] Transmit Baseband Block (1110c): Digital processing block for the transmit signal.

[0349] Digital Pre-Distortion Block (1111c): Pre-distortion of digital transmission signals.

[0350] Digital-to-Analog Converter (1112c): Converts digital signals to analog signals.

[0351] Pre-driver (1113c): progressive power amplification of analog transmission signals

[0352] Power amplifier (1114c): Power amplification of analog transmission signals.

[0353] Transmitting antenna (1115c): Antenna for signal transmission.

[0354] According to the transmission / reception structure illustrated in FIG. 11c, the receiving end may be composed of blocks such as a receiving antenna (Rx Antenna, 1124c), a low noise amplifier (LNA, 1123c), an analog-to-digital converter (ADC, 1122c), a successive interference canceller (Successive Interference Canceller, 1121c), and a receiving baseband block (Rx Baseband, 1120c). Each block may perform the following roles.

[0355] Receiving antenna (1124c): Antenna for receiving signals

[0356] Low-Noise Amplifier (1123c): Amplifies the power of an analog received signal while minimizing noise amplification.

[0357] Analog-to-digital converter (1122c): Converts analog signals to digital signals.

[0358] Continuous Interference Canceller (1121c): Interference canceller for digital signals

[0359] Receive Baseband Block (1120c): Digital processing block for the received signal.

[0360] According to the transmission / reception structure illustrated in Fig. 11c, a power amplifier coupler (PA Coupler, 1116c) and a coefficient update block (Coefficient Update, 1117c) may be present for additional signal processing between the transmitter and receiver. Each block may perform the following roles.

[0361] Power amplifier connector (1116c): A block for observing the waveform of an analog transmission signal that has passed through a power amplifier at the receiving end.

[0362] Constant Update Block (1117c): Updates various constants required for digital domain signal processing at the transmitter and receiver. The constants calculated here can be used to set various parameters in the DPD (1111c) block at the transmitter and the SIC (1121c) block at the receiver.

[0363] The transmission / reception structure illustrated in FIG. 11c can be utilized for the purpose of effectively controlling interference between a transmission signal and a reception signal when transmission and reception operations are performed simultaneously at a base station or a terminal device. For example, when transmission and reception occur simultaneously at a certain device, a transmission signal (1101c) transmitted through a transmission antenna (1115c) of a transmission end may be received through a reception antenna (1124c) of a reception end, and in this case, the transmission signal (1101c) received by the reception end may cause interference (1100c) with the reception signal (1102c) that the reception end originally intended to receive. The interference between the transmission signal (1101c) and the reception signal (1102c) received by the reception end is referred to as self-interference (1100c). For example, to explain specifically, if a base station device performs downlink transmission and uplink reception at the same time, the downlink signal transmitted by the base station may be received by the base station's receiving end, and as a result, interference may occur between the downlink signal transmitted by the base station and the uplink signal that the base station originally intended to receive at the receiving end. If a terminal device performs downlink reception and uplink transmission at the same time, the uplink signal transmitted by the terminal may be received by the receiving end of the terminal, and as a result, interference may occur between the uplink signal transmitted by the terminal and the downlink signal that the terminal originally intended to receive at the receiving end. Interference between links in different directions, that is, downlink signals and uplink signals, at the base station and the terminal device is also referred to as cross-link interference.

[0364] In one embodiment of the present disclosure, self-interference between a transmission signal (or downlink signal) and a reception signal (or uplink signal) may occur in a system in which transmission and reception can be performed simultaneously.

[0365] For example, magnetic interference may occur in the XDD system described above.

[0366] FIG. 11d is a diagram illustrating an example of downlink and uplink resource settings in an XDD system.

[0367] In the case of XDD, downlink (1100d) resources and uplink (1103d) resources can be distinguished in the frequency domain, and a guard band (GB, 1104d) may exist between the downlink (1100d) resources and the uplink (1101d) resources. Actual downlink transmission may be performed within the downlink bandwidth (1102d), and uplink transmission may be performed within the actual uplink bandwidth (1103d). At this time, leakage (1106d) may occur outside the uplink or downlink transmission band. In an area where downlink resources (1100d) and uplink resources (1101d) are adjacent, interference due to this leakage (which may be named Adjacent Carrier Leakage (ACL, 1105d)) may occur. FIG. 11d illustrates an example in which an ACL (1105d) occurs from a downlink (1100d) to an uplink (1101d). As the downlink bandwidth (1102d) and the uplink bandwidth (1103d) become closer together, the influence of signal interference by the ACL (1105) may increase, which may result in performance degradation. For example, as illustrated in FIG. 11d, some resource areas (1108d) within the uplink band (1103d) adjacent to the downlink band (1102d) may be significantly affected by interference by the ACL (1105d). Some resource areas (1107d) within the uplink band (1103d) relatively far from the downlink band (1102d) may be less affected by interference by the ACL (1105d). That is, within the uplink band (1103d), there may exist a resource region (1108d) that is relatively more affected by interference and a resource region (1107d) that is relatively less affected by interference. In order to reduce performance degradation due to the ACL (1105d), a guard band (1104d) may be inserted between the downlink bandwidth (1102d) and the uplink bandwidth (1103d).As the size of the guard band (1104d) increases, there is an advantage that the interference effect due to the ACL (1105d) between the downlink bandwidth (1102d) and the uplink bandwidth (1103d) may be reduced. However, there may be a disadvantage that resource efficiency may decrease because the resources available for transmission and reception decrease as the size of the guard band (1104d) increases. Conversely, as the size of the guard band (1104d) decreases, the amount of resources available for transmission and reception may increase, which has the advantage of improving resource efficiency. However, there is a disadvantage that the interference effect due to the ACL (1105d) between the downlink bandwidth (1102d) and the uplink bandwidth (1103d) may be increased. Therefore, it may be important to determine an appropriate size of the guard band (1104d) by considering the trade-offs.

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

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

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

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

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

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

[0374] If the information on whether the above SBFD is supported is included in the system information for a terminal that supports a different version of the standard (e.g., an existing TDD terminal), the information on whether the above SBFD is supported may be inserted at the very end so as not to affect the acquisition of system information by the existing TDD terminal. If the SBFD terminal does not obtain the information on whether the above SBFD is supported inserted at the very end, or obtains information that SBFD is not supported, the SBFD terminal can determine that the cell (or base station) only supports TDD.

[0375] If the information on whether the SBFD is supported is included in the system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether the SBFD is supported may be transmitted through a separate PDSCH so as not to affect the acquisition of system information by the existing TDD terminal. That is, a terminal that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information from a first PDSCH. An SBFD-supporting terminal can receive a first SIB (or SIB) including existing TDD-related system information from a first PDSCH, and a second SIB including SBFD-related system information from a second PDSCH. Here, the first PDSCH and the second PDSCH can be scheduled as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) 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 it is not obtained (i.e., the system information of the first PDSCH does not include information about the search space), the second PDCCH can be received in the same search space as the search space of the first PDCCH.

[0376] As described above, when the SBFD terminal determines that the cell (or base station) supports only TDD, the SBFD terminal can perform random access procedures and transmit and receive data / control signals in the same manner as a conventional TDD terminal.

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

[0378] The base station may be able to distinguish whether the TDD terminal supporting different versions of the standard performs random access or the SBFD terminal performs random access by setting separate random access resources for the TDD terminal and the SBFD terminal supporting different versions of the standard. For example, the separate random access resource set for the SBFD terminal may be a resource that the existing TDD terminal determines to be a downlink time resource, and the SBFD terminal performs random access through an uplink resource (or a separate random access resource) set to a part of the frequency of the downlink time resource, so that the base station may determine that the terminal attempting random access through the uplink resource is an SBFD terminal.

[0379] Alternatively, the base station may not set up separate random access resources for SBFD terminals, but may set up common random access resources for all terminals within the cell. In this case, configuration information for the random access resources may be transmitted to all terminals within the cell through system information, and the SBFD terminal that has received the system information may perform random access to the random access resources. Thereafter, the SBFD terminal may complete the random access process and proceed to RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive an upper layer or physical signal from the base station that can determine that some frequency resources of the downlink time resources are set uplink resources, and may perform SBFD operations, for example, transmit uplink signals on the uplink resources.

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

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

[0382] FIG. 11e is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system to which the present disclosure is applied.

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

[0384] In Fig. 11e, it can be assumed that the DDDSU slot format is set according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols, and 'S' is a slot that is not 'D' or 'U', that is, a slot that includes a downlink symbol or an uplink symbol or a flexible symbol. Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is 5 slots (5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

[0385] Next, in (b), (c) to (d) of FIG. 11e, a case in which SBFD is operated together with TDD in a specific frequency band is illustrated.

[0386] Referring to (b) of FIG. 11e, the terminal may set a portion of the frequency band of the cell as a frequency band (1110e) capable of uplink transmission. This band may be referred to as an uplink subband (UL subband). And the uplink subband (UL subband) may be applied to all symbols of all slots. The terminal may transmit an uplink channel or signal scheduled for all symbols (1112e) within the subband (UL subband). However, the terminal may not transmit an uplink channel or signal in a band other than the subband (UL subband).

[0387] Referring to (c) of Fig. 11e, the terminal may set a portion of the frequency band of the cell as a frequency band (1120e) capable of uplink transmission, and may set a time region in which the frequency band is activated. Here, this frequency band may be called an uplink subband (UL subband). In Fig. 11(c), the uplink subband (UL subband) is deactivated in the first slot, and the uplink subband (UL subband) may be activated in the remaining slots. Accordingly, the terminal may transmit an uplink channel or signal in the uplink subband (UL subband) (1122e) of the remaining slots. Therefore, although the uplink subband (UL subband) is activated in units of slots here, whether it is activated or not may be set in units of symbols.

[0388] Referring to (d) of FIG. 11e, the terminal can be configured with time-frequency resources capable of uplink transmission. The terminal can configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1132e) of the first and second slots can be configured as time-frequency resources capable of uplink transmission. In addition, some frequency bands (1133e) of the third slot and some frequency bands (1134e) of the fourth slot can be configured as time-frequency resources capable of uplink transmission.

[0389] In the following description, a time-frequency resource capable of uplink transmission within a downlink symbol or slot may be referred to as an SBFD resource. In addition, a symbol within a downlink symbol for which an uplink subband is configured may be referred to as an SBFD symbol. In addition, a time-frequency resource capable of downlink reception within an uplink symbol or slot may be referred to as an SBFD resource. In addition, a symbol within an uplink symbol for which a downlink subband is configured may be referred to as an SBFD symbol. An SBFD resource or SBFD symbol may refer to a resource or symbol capable of SBFD operation.

[0390] For convenience, in the present disclosure, a band in which downlink channels or signals can be received, excluding uplink sub-bands, is referred to as a downlink sub-band. A terminal can configure at most one uplink sub-band and at most two downlink sub-bands in one symbol. For example, a terminal can be configured with one of {uplink sub-band, downlink sub-band}, {downlink sub-band, uplink sub-band}, or {first downlink sub-band, uplink sub-band, second downlink sub-band} in the frequency domain.

[0391] FIG. 11f is a diagram illustrating an SBFD setting according to one embodiment of the present disclosure.

[0392] Referring to Fig. 11f, the terminal may be configured with an uplink symbol, a downlink symbol, or a flexible symbol according to the TDD configuration. Here, all symbols in the 'D' slot are downlink symbols. All symbols in the 'U' slot are uplink symbols. The 'S' slot is a slot that is not a 'D' slot or a 'U' slot. The terminal may be configured with a UL BWP (1120f). In addition, the terminal may be configured with a UL subband (1110f) in a DL symbol. In addition, the terminal may be configured with a slot or a symbol to which the UL subband (1110f) is to be applied. Referring to Fig. 11f, the UL subband may be applied only to some symbols among the DL symbols of the TDD periodicity. The UL subband may be applied to the DL symbols of the second and third slots, but the UL subband may not be applied to the other DL symbols. Here, the SBFD symbol can represent a symbol to which the UL subband is applied.

[0393] The base station can set a guard frequency interval between the DL sub-band and the UL sub-band in the terminal. When the guard frequency interval is set for the terminal, frequency resources in the frequency domain can be divided into a UL sub-band, a guard frequency interval, and a DL sub-band. For the purpose of explaining the present embodiment, it is assumed that the guard frequency interval is included in the UL sub-band. That is, in the following description, the expression 'if 'X' overlaps with the UL sub-band' can be interpreted as 'if 'X' overlaps with the UL sub-band or the guard frequency interval'. In addition, the expression 'if 'X' overlaps with the UL sub-band' can be interpreted as 'if 'X' does not overlap with the DL sub-band'.

[0394] The expression 'if 'X' does not overlap with a UL sub-band' can be interpreted as 'if 'X' does not overlap with a UL sub-band and a Guard frequency interval.' Furthermore, the expression 'if 'X' does not overlap with a UL sub-band' can be interpreted as 'if 'X' overlaps with a DL sub-band.'

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

[0396] - MIB (Master Information Block)

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

[0398] - RRC (Radio Resource Control)

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

[0400] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the physical layer channel or signaling below.

[0401] - PDCCH (Physical Downlink Control Channel)

[0402] - DCI (Downlink Control Information)

[0403] - UE-specific DCI

[0404] - Group common DCI

[0405] - Common DCI

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

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

[0408] - PUCCH (Physical Uplink Control Channel)

[0409] - UCI (Uplink Control Information)

[0410] The term slot used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a TTI (transmit time interval, transmission time interval), and specifically may mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

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

[0412] FIG. 12 is a diagram illustrating an example of a non-SBFD symbol of a wireless communication system according to an embodiment of the present disclosure.

[0413] Referring to FIG. 12, the entire RB located in the non-SBFD symbol (1201) of the carrier (1202) can be used in downlink (DL), uplink (UL), or sidelink (SL) transmission depending on the transmission direction.

[0414] According to one embodiment of the present disclosure, a terminal and a base station can perform an operation according to SBFD. An SBFD subband in which an SBFD operation is performed can be composed of at least one or more consecutive RBs, and resources belonging to an SBFD subband have the same transmission direction. That is, all resources belonging to a single SBFD subband can be used for downlink, uplink, or sidelink. The SBFD operation can be performed by utilizing some resources of a TDD carrier.

[0415] A base station can set a BWP for SBFD operation in a terminal. The BWP set by the base station can include a DL-BWP (Downlink Bandwidth Part), an UL-BWP (Uplink Bandwidth Part), and an SL-BWP (Sidelink Bandwidth Part). The base station and the terminal can communicate using SBFD symbols (symbols in which SBFD subbands are located on the time axis). At most one UL subband can be located in an SBFD symbol. One or at most two DL subbands can be located in an SBFD symbol. The UL subband located in the SBFD symbol can be located in the center part of the carrier or at one end. The location of the SBFD symbol can be set in a DL symbol or a Flexible symbol.

[0416] FIG. 13, FIG. 14 and FIG. 15 are diagrams illustrating examples of SBFD symbols of a wireless communication system according to one embodiment of the present disclosure.

[0417] Some of the RBs (one or more RBs among the RBs included in the carrier) located in the SBFD symbols (1301, 1401, 1501) of the carriers (1302, 1402, 1502) may belong to the downlink subbands and uplink subbands (1303, 1403, 1503). For example, the position of the uplink subband (1303, 1403, 1503) located in the SBFD symbol (1301, 1401, 1501) may be located at the center of the uplink carrier as in FIG. 13, at one end with a low RB index as in FIG. 14 (one or more RBs consecutive on the frequency axis from the RB with the lowest index among the RBs included in the carrier), or at one end with a high RB index as in FIG. 15 (one or more RBs consecutive on the frequency axis from the RB with the highest index among the RBs included in the carrier).

[0418] According to one embodiment of the present disclosure, the location of the SBFD symbol may be signaled to the terminal. For example, the location of the SBFD symbol may be signaled by one or a combination of one or more of an RRC message, a SIB (System Information Block) message, a MAC CE, and a DCI.

[0419] According to one embodiment of the present disclosure, the location of the SBFD subband can be signaled to the terminal. For example, the location of the SBFD subband can be signaled by one or a combination of one or more of an RRC message, an SIB message, a MAC CE, and a DCI. According to one embodiment of the present disclosure, the size (subband bandwidth) of the SBFD subband configured to the terminal can be set in units of RBs, that is, in units of multiple RBs. According to one embodiment of the present disclosure, the size of the SBFD subband configured to the terminal can be set in units of multiple RBs as one group, that is, to include multiple groups. The units can include, for example, an RB Group (RBG), a Precoding Resource Block Group (PRG), etc.

[0420] According to one embodiment of the present disclosure, a base station and a terminal can communicate using SBFD symbols. For example, the base station can transmit data to the terminal using the DL subband of the SBFD symbol, and the terminal can transmit data to the base station using the UL subband of the SBFD symbol. As another example, sidelink communication between terminals can be performed using SBFD symbols. For example, the terminal can transmit and receive a sidelink signal using the UL subband of the SBFD symbol.

[0421] According to one embodiment of the present disclosure, a base station can transmit data to a terminal using both SBFD symbols and non-SBFD symbols (symbols in which an SBFD subband is not located). For example, the base station can transmit a PDSCH to a terminal using both SBFD symbols and non-SBFD symbols. The base station can transmit data to a terminal via a PDSCH using both SBFD symbols and non-SBFD symbols included in one slot. The base station can transmit data to a terminal via a PDSCH using both a slot including an SBFD symbol and a slot including a non-SBFD symbol.

[0422] According to one embodiment of the present disclosure, a terminal can transmit data to a base station using both SBFD symbols and non-SBFD symbols. The terminal can transmit a PUSCH to the base station using both SBFD symbols and non-SBFD symbols. The terminal can transmit data to the base station via the PUSCH using both SBFD symbols and non-SBFD symbols included in one slot. The terminal can transmit data to the base station via the PUSCH using both a slot including an SBFD symbol and a slot including a non-SBFD symbol.

[0423] According to one embodiment of the present disclosure, a terminal can transmit data to another terminal using both SBFD symbols and non-SBFD symbols. The terminal can transmit a physical sidelink shared channel (PSSCH) to another terminal using both SBFD symbols and non-SBFD symbols. The terminal can transmit data to another terminal through the PSSCH using both SBFD symbols and non-SBFD symbols included in one slot. The terminal can transmit data to another terminal through the PSSCH using both slots including SBFD symbols and slots including non-SBFD symbols.

[0424] According to one embodiment of the present disclosure, one TTI may include at least one SBFD symbol and / or at least one non-SBFD symbol.

[0425] According to one embodiment of the present disclosure, when symbols used for transmission include both SBFD symbols and non-SBFD symbols, the amount of available frequency resources in SBFD symbols may be different from the amount of available frequency resources in non-SBFD symbols. For example, the number of RBs included in a DL subband located in an SBFD symbol may be less than or equal to the number of RBs included in a DL non-SBFD symbol. The number of RBs included in a UL subband located in an SBFD symbol may be less than or equal to the number of RBs included in a UL non-SBFD symbol. The sum of the number of RBs included in a DL subband located in an SBFD symbol and the number of RBs included in a UL subband located in an SBFD symbol may be less than or equal to the number of RBs included in a non-SBFD symbol.

[0426] FIG. 16 and FIG. 17 are diagrams illustrating slots of a wireless communication system according to one embodiment of the present disclosure.

[0427] Referring to FIGS. 16 and 17, slots (1601, 1701) containing only SBFD symbols and slots (1602, 1702) containing only non-SBFD symbols may be positioned consecutively. As illustrated, uplink subbands (1603, 1703) and downlink subbands (1604, 1704) may be positioned in slots (1601, 1701) containing only SBFD symbols. Downlink subbands (1605) or uplink subbands (1706) may be positioned in slots (1602, 1702) containing only non-SBFD symbols. In FIGS. 16 and 17, slots (1601, 1701) containing only SBFD symbols are shown to be ahead of slots (1602, 1702) containing only non-SBFD symbols, but conversely, slots (1601, 1701) containing only SBFD symbols may be behind slots (1602, 1702) containing only non-SBFD symbols.

[0428] Meanwhile, some uplink resources may be set as muting resources for purposes such as estimating cross-link interference (CLI) between base stations and estimating self-interference between base stations and terminals. For example, some of the resources allocated for PUSCH may be set as muting resources or may be predefined. The muting resources may include symbol(s) and / or some RE(s) included within the symbol(s).

[0429] For convenience of explanation, in this disclosure, resources allocated to PUSCH and instructed to perform muting are referred to as muting resources or PUSCH muting resources. However, these terms do not limit the scope of this disclosure.

[0430] According to one embodiment of the present disclosure, a terminal instructed to mute some resources used for PUSCH transmission may map 0 (zero) to the muting resource (PUSCH muting resource). This may also be interpreted as PUSCH not being mapped to the muting resource (PUSCH muting resource), zero-power being allocated to the muting resource (PUSCH muting resource), or zero-power PUSCH being mapped to the muting resource (PUSCH muting resource).

[0431] Below, a method for indicating / setting muting resources among the resources allocated for PUSCH is specifically described.

[0432] A base station can schedule PUSCH transmission to a terminal. At this time, the base station can instruct the terminal to mute some of the resources used for PUSCH transmission.

[0433] According to one embodiment of the present disclosure, a base station may schedule PUSCH transmission to a terminal and instruct muting of some resources in some symbol(s) used for the PUSCH transmission.

[0434] According to one embodiment of the present disclosure, if a resource on which PUSCH transmission is scheduled to a terminal is performed includes SBFD symbol(s), the base station may instruct muting of some resources in some symbol(s) of the SBFD symbol(s). In other words, if a symbol (i.e., an SBFD symbol) in which an uplink subband is set in a part of a frequency band corresponding to a downlink symbol or slot is allocated for PUSCH transmission, the base station may instruct the terminal to mute PUSCH for some resources of the symbol in which the uplink subband is set. Hereinafter, that a resource scheduled to perform PUSCH transmission includes SBFD symbol(s) may mean that a frequency band corresponding to a downlink symbol or slot includes both an uplink subband and a downlink subband, and a symbol in which the uplink subband is set is allocated for a PUSCH.

[0435] For example, the base station may instruct the terminal to mute some resources in one or two of the SBFD symbol(s). The base station may instruct the muting in some RE(s) included in some symbol(s) for which the muting is instructed. Some RE(s) for which the muting is instructed may be the same as the comb-2 type of SRS. That is, when the frequency axis index of the RE is k, PUSCH transmission may be muted in REs corresponding to an even value index k, or PUSCH transmission may be muted in REs corresponding to an odd value index k.

[0436] According to one embodiment of the present disclosure, if a resource on which a PUSCH transmission scheduled by a base station to a terminal is performed includes SBFD symbol(s), the base station may instruct the terminal to mute some REs (e.g., 'REs corresponding to an even value index k' or 'REs corresponding to an odd value index k') in some symbol(s) of the SBFD symbol(s). The base station may signal to the terminal information indicating which REs among the REs corresponding to the some symbols are to be muted. For example, the signaling may include RRC signaling, DCI transmitted via PDCCH, or a combination of RRC signaling and DCI.

[0437] According to one embodiment of the present disclosure, if a resource on which a PUSCH transmission scheduled by a base station to a terminal is performed includes SBFD symbol(s), whether to mute some REs of some symbol(s) among the SBFD symbol(s) may be indicated, and at this time, there may be no separate indication for determining the REs to be muted. That is, the PUSCH may be muted in REs that are predefined. For example, if the base station instructs the terminal to mute as described above, the terminal may mute some REs (e.g., one of the REs among the 'REs corresponding to an even value index k' or the 'REs corresponding to an odd value index k') according to the agreement (predefined).

[0438] According to one embodiment of the present disclosure, if a resource on which a PUSCH transmission scheduled by a base station to a terminal is performed includes SBFD symbol(s), the base station may instruct the terminal to mute some REs in some symbol(s) of the SBFD symbol(s). The base station may signal to the terminal information related to the symbol(s) to which the muting is applied among the SBFD symbol(s). For example, the signaling may include RRC signaling, DCI transmitted via PDCCH, or a combination of RRC signaling and DCI.

[0439] According to one embodiment of the present disclosure, the information about the muting symbol(s) may include at least some of the number of muting symbol(s) or position information of the muting symbol(s).

[0440] According to one embodiment of the present disclosure, when the number of muting symbols is 1, one piece of location information of the muting symbol may be signaled to the terminal, and when the number of muting symbols is 2, two pieces of location information of the muting symbols may be signaled. That is, the base station and the terminal may identify the number of muting symbols and the locations of the muting symbols depending on the number of 'muting symbol location information' signaled.

[0441] According to one embodiment of the present disclosure, 'muting symbol position information' may be indicated by a symbol index (e.g., 0 to 13) within a slot. For example, if 5 is given as the index of a muting symbol, the 5th symbol of a slot in which a PUSCH is transmitted may be the muting symbol. As another example, if 5 and 12 are given as the muting symbol indices, the 5th and 12th symbols of a slot in which a PUSCH is transmitted may be the muting symbols.

[0442] According to one embodiment of the present disclosure, 'muting symbol position information' is a PUSCH transmission start symbol (lstart ) from the muting symbol (l mute ) number of symbols between (d = l) mute - l start ) can be given. For example, if the index of the transmission start symbol of PUSCH is 2 and 3 is given as the 'muting symbol position information', the muting symbol can be determined as the 5th symbol in the slot. For another example, if the index of the transmission start symbol of PUSCH is 2 and 3 and 9 are given as the 'muting symbol position information', the muting symbol can be determined as the 5th and 11th symbols in the slot.

[0443] According to one embodiment of the present disclosure, 'muting symbol location information' is a DMRS symbol (l) associated with a PUSCH. dmrs ) from the muting symbol (l mute ) number of symbols between (d' = l mute - l dmrs ) can be given. The above DMRS symbol may be the first DMRS symbol linked to PUSCH.

[0444] According to one embodiment of the present disclosure, information related to the combination of the number of muting symbols and the positions of the muting symbols may be signaled. At least one piece of information related to the combination of the number of muting symbols and their positions (e.g., N pieces, where N is a natural number) may be signaled. For example, the combination-related information may be transmitted via higher layer signaling (e.g., RRC) or may be predefined. Index information indicating one combination of the combination-related information may be signaled (e.g., via log2N bits). For example, the index information may be transmitted via L1 signaling (e.g., DCI). If only one piece of information related to the combination of the number of muting symbols and their positions is transmitted via higher layer signaling (e.g., RRC), the UE may apply muting to the PUSCH according to the received information.

[0445] Table 24 shows combination-related information of 'muting symbol position information' according to one embodiment of the present disclosure. Combination-related information of 'muting symbol position information' as shown in Table 24 may be signaled to a terminal. One or two 'muting symbol position information' may be linked to one index. For example, two muting symbols are linked to index 0, and two corresponding 'muting symbol position information' (l 0,1 , l 0,2 ) can be linked. One muting symbol is linked to index 1, and one corresponding 'muting symbol location information' (l 1,1 ) can be linked.

[0446] For example, the 'muting symbol position information' included in the above combination may be indicated in the form of a symbol index within the above-described slot. As another example, the 'muting symbol position information' included in the above combination may be indicated in the form of the above-described PUSCH transmission start symbol (l start) from the muting symbol (l mute ) number of symbols between (d = l) mute - l start ) may be. For another example, the 'muting symbol location information' included in the above combination may be the DMRS symbol (l) linked to the PUSCH described above. dmrs ) from the muting symbol (l mute ) number of symbols between (d' = l mute - l dmrs ) may be.

[0447] Index 'muting symbol location information' 'muting symbol location information' 0l 0,1 l 0,2 1l 1,1 -2l 2,1 l 2,2 .........N-1l N-1,1 -

[0448] According to one embodiment of the present disclosure, the combination-related information may be in the form of a list. For example, each entity in the list may include an index and one or more 'muting symbol position information.' Additionally, information indicating one of the entities in the list (e.g., indicating an index) may be signaled.

[0449] According to one embodiment of the present disclosure, the position of the muting symbol is predefined, and the number of muting symbols can be signaled to the terminal. That is, if information indicating that the number of muting symbols is 1 is signaled, the terminal can identify the position of 1 muting symbol according to the predefined information that the number of muting symbols is 1. In addition, if information indicating that the number of muting symbols is 2 is signaled, the terminal can identify the position of 2 muting symbols according to the predefined information that the number of muting symbols is 2.

[0450] According to one embodiment of the present disclosure, the position(s) of the predefined muting symbol may be specific symbol(s) within a slot. For example, if the predefined symbol is 5, the 5th symbol of the slot in which the PUSCH is transmitted may be the muting symbol. For another example, if the predefined symbols are 5 and 12, the 5th and 12th symbols of the slot in which the PUSCH is transmitted may be muting symbols. Accordingly, for example, if one muting symbol is signaled, the terminal may mute some resources of the 5th symbol of the slot in which the PUSCH is transmitted, and if two muting symbols are signaled, the terminal may mute some resources of the 5th and 12th symbols of the slot in which the PUSCH is transmitted, respectively.

[0451] According to one embodiment of the present disclosure, the position(s) of the predefined muting symbol(s) are PUSCH transmission start symbol (l start ) from the muting symbol (l mute ) number of symbols between (d = l) mute - l start ) can be defined. For example, if the index of the PUSCH transmission start symbol is 2 and the number of the predefined symbols (d) is 3, the muting symbol can be determined as the 5th symbol in the slot. For another example, if the index of the PUSCH transmission start symbol is 2 and the number of the predefined symbols (d) are 3 and 9, the muting symbol can be determined as the 5th and 11th symbols in the slot. Accordingly, for example, if 1 is signaled as the number of muting symbols, the terminal can mute some resources of the 5th symbol of the slot in which the PUSCH is transmitted, and if 2 are signaled as the number of muting symbols, the terminal can mute some resources of the 5th and 11th symbols, respectively, of the slot in which the PUSCH is transmitted.

[0452] According to one embodiment of the present disclosure, the position(s) of the predefined muting symbol(s) are DMRS symbols (l) associated with PUSCH. dmrs ) from the muting symbol (l mute ) number of symbols between (d' = l mute - l dmrs ) can be defined. The above DMRS symbol may be the first DMRS symbol linked to PUSCH.

[0453] According to one embodiment of the present disclosure, the position(s) of the predefined muting symbol(s) may be specific symbol(s) within symbols scheduled for PUSCH transmission. For example, if there is one muting symbol, the specific symbol(s) may be the last symbol among symbols scheduled for PUSCH transmission. If there are two muting symbols, the specific symbol(s) may be the last two symbols among symbols scheduled for PUSCH transmission. For another example, if there is one muting symbol, the specific symbol(s) may be the first symbol among symbols scheduled for PUSCH transmission. If there are two muting symbols, the specific symbol(s) may be the first two symbols among symbols scheduled for PUSCH transmission.

[0454] The embodiment of the present disclosure is described mainly with an example of applying PUSCH muting to some REs of some symbol(s) among SBFD symbol(s) when the resource on which PUSCH transmission scheduled by a base station to a terminal is performed includes SBFD symbol(s); however, when the resource on which PUSCH transmission scheduled by a base station to a terminal is performed includes SBFD symbol(s), PUSCH muting may also be applied to some REs of some symbol(s) among the symbol(s) on which PUSCH transmission is performed (e.g., at least one of an uplink symbol, a flexible symbol, or an SBFD symbol).

[0455] According to one embodiment of the present disclosure, a base station may signal to a terminal at least some of information about whether muting is applied, the number of muting symbol(s), the position of the muting symbol(s), or REs to be muted within the muting symbol for muting in PUSCH transmission resources. The signaling may include RRC signaling, DCI transmitted via PDCCH, or a combination of RRC signaling and DCI.

[0456] FIG. 18 illustrates PUSCH transmission according to one embodiment of the present disclosure.

[0457] Referring to FIG. 18, a UL subband (1820) and a DL subband (1810) may be configured in a downlink slot (1830) and used for communication. Through the UL subband, the terminal may transmit PUSCH (1840, 1850, 1860). By one or a combination of the above-described embodiments, the terminal may transmit PUSCH by muting some resources of some symbols among the symbols allocated to PUSCH (1850, 1860).

[0458] For example, the position of the muting symbol may be indicated to the terminal as symbol index 5 and 12 of the slot. Alternatively, the position of the muting symbol may be preset as symbol index 5 and 12 of the slot. In this case, the terminal may determine the symbol corresponding to symbol index 5 and 12 within the slot as the muting symbol regardless of the position of the PUSCH transmission start symbol, mute some resources of the symbol, and transmit the PUSCH (1850).

[0459] For another example, the position of the muting symbol may be indicated to the terminal as relative information 3, 9 for the PUSCH transmitted by the terminal. Alternatively, the position of the muting symbol may be preset to the terminal as relative information 3, 9 for the PUSCH transmitted by the terminal. The relative distance from the first symbol of the PUSCH transmitted by the terminal, the relative distance from the last symbol, or the relative distance from the DMRS symbol associated with the PUSCH may be included in the 'relative information for the PUSCH'. The terminal may determine the muting symbol within the PUSCH based on the 'relative information for the PUSCH', mute some resources of the muting symbol, and transmit the PUSCH. For example, based on the fact that the start symbol of PUSCH is symbol 2 and 3 and 9 are indicated as the 'relative information for PUSCH', the terminal can decide to mute symbols 3 and 9 after the start symbol of PUSCH, and can mute some resources of the corresponding symbols and transmit PUSCH (1860).

[0460] According to one embodiment of the present disclosure, the configuration information for the muting can be configured via RRC signaling. The base station can provide the terminal with configuration information including at least some of the following: whether PUSCH is muted, the number of muting symbol(s), the location of the muting symbol(s), or information on REs to be muted within the muting symbol, via RRC signaling. The terminal can identify the symbols and REs to be muted when transmitting the PUSCH based on the configuration information.

[0461] For example, the above configuration information can be set to the terminal via PUSCH-config.

[0462] For example, the above configuration information can be set for each PUSCH transmission type (e.g., Type A, Type B).

[0463] For example, the location(s) of the muting symbol(s) may be predefined or configured for each time domain resource assignment (timeDomainAllocation) in which the PUSCH is transmitted.

[0464] According to one embodiment of the present disclosure, a base station may use at least one field included in a DCI scheduling a PUSCH to indicate muting of some resources used for the PUSCH transmission. The some resources may include symbol(s) and / or some RE(s) included within the symbol(s).

[0465] At least one of the above fields may be existing fields included in the DCI rather than new fields. That is, by utilizing at least some of the existing fields included in the DCI, the base station may instruct the terminal to mute some resources used for PUSCH transmission. The some resources may include symbol(s) and / or some RE(s) included within the symbol(s).

[0466] According to one embodiment of the present disclosure, the existing field may include a Frequency Domain Resource Assignment (FDRA) field. That is, through some bits of the Frequency Domain Resource Assignment field, the base station may instruct the terminal to mute some of the resources used for PUSCH transmission. That is, through reinterpretation of the Frequency Domain Resource Assignment field, the base station may instruct the terminal to mute some of the resources used for PUSCH transmission.

[0467] According to one embodiment of the present disclosure, a frequency domain resource allocation field in a DCI scheduling a PUSCH transmission may be interpreted differently depending on the time resource for which the PUSCH transmission is scheduled.

[0468] According to one embodiment of the present disclosure, a frequency domain resource allocation field in a DCI scheduling a PUSCH transmission may be interpreted differently depending on whether the time resource for which the PUSCH transmission is scheduled includes an SBFD symbol.

[0469] For example, if the time resource for which the PUSCH transmission is scheduled does not include an SBFD symbol, all bits included in the frequency domain resource allocation field in the DCI for scheduling the PUSCH transmission may be used to interpret the frequency domain resource allocation information of the PUSCH. If the time resource for which the PUSCH transmission is scheduled includes an SBFD symbol, some of the bits included in the frequency domain resource allocation field may be used to interpret the frequency domain resource allocation information of the PUSCH, and the remaining bits included in the frequency domain resource allocation field may be filled with 0.

[0470] For another example, if the time resource for which the PUSCH transmission is scheduled does not include an SBFD symbol, all bits included in a frequency domain resource allocation field in the DCI for scheduling the PUSCH transmission may be used to interpret frequency domain resource allocation information of the PUSCH. If the time resource for which the PUSCH transmission is scheduled includes an SBFD symbol, some of the bits included in the frequency domain resource allocation field may be used to interpret frequency domain resource allocation information of the PUSCH, and some of the remaining bits included in the frequency domain resource allocation field may be used to indicate muting-related information of the PUSCH, and the remaining bits may be filled with 0.

[0471] For another example, if the time resource for which the PUSCH transmission is scheduled does not include an SBFD symbol, all bits included in the frequency domain resource allocation field can be used to interpret the frequency domain resource allocation information of the PUSCH. If the time resource for which the PUSCH transmission is scheduled includes an SBFD symbol, N for resource allocation type 0 REG The bandwidth of the UL BWP used when determining the bitwidth (when resource allocation type is 0) ) as a parameter - N size Use ul_subband (bandwidth of UL subband, expressed as the number of RBs belonging to the UL subband) and for resource allocation type 1. The bandwidth of the UL BWP used when determining the bitwidth (in case of resource allocation type 1) , ) as a parameter - N size ul_subband (bandwidth of UL subband, expressed as the number of RBs belonging to the UL subband) can be used. At least one or more bits located after the bits indicating frequency resource allocation information in the frequency resource allocation field can be used to indicate muting-related information of the PUSCH. If the sum of 'the number of bits indicating frequency resource allocation information in the SBFD symbol' and 'the number of bits indicating muting-related information of the PUSCH' is less than 'the number of bits for frequency resource allocation fields in the case where the time resource for which the PUSCH transmission is scheduled does not include an SBFD symbol', the remaining bits can be filled with 0.

[0472] According to one embodiment of the present disclosure, the muting-related information of the PUSCH may include at least some of information on whether muting of the PUSCH is applied, the number of muting symbol(s), the position of the muting symbol(s), or REs to be muted within the muting symbol.

[0473] FIG. 19 illustrates DCI according to one embodiment of the present disclosure.

[0474] Referring to FIG. 19, DCI (1910) may be transmitted via PDCCH. The DCI (1910) may be a DCI format 0_0, 0_1, ..., 0_x for scheduling PUSCH. The DCI (1910) may include a frequency domain resource allocation (FDRA) field (1920). The number of bits corresponding to the FDRA field (1920) may be determined by the size of the uplink BWP configured by the terminal, the configured resource allocation type, etc. In FIG. 19, when the resource allocation type that allocates resources in units of RBG (Resource Block Group) through a bitmap is configured in the terminal, the 'number of bits of the FDRA field' is N RBG(1930), but the scope of the present disclosure is not limited thereto.

[0475] FIG. 20 illustrates DCI including muting-related information according to one embodiment of the present disclosure.

[0476] Referring to FIG. 20, DCI (2010a, 2010b) may be transmitted via PDCCH. The DCI (2010a, 2010b) may be in DCI format 0_0, 0_1, ..., 0_x for scheduling PUSCH. The DCI (2010a, 2010b) may include a frequency-axis resource allocation field (2020a, 2020b). The number of bits corresponding to FDRA (2020a, 2020b) may be determined by the size of the uplink subband configured by the terminal, the configured resource allocation type, etc. Since the size of the above uplink subband is smaller than the size of the uplink BWP, the 'number of bits corresponding to the above FDRA (2020a, 2020b)' is 'the number of bits corresponding to the above FDRA (1920) of the resource allocation type that allocates resources in RBG units (N RBG , 1930, 2030a, 2030b)' may be less than some bits (N) located after 'bits corresponding to the above FDRA (2020a, 2020b)'. mute The bits 2050a, 2050b) can be used to indicate the 'muting related information (2040a, 2040b) to the terminal' as described above. Even if the 'number of bits corresponding to the FDRA (2020a, 2020b)' and the 'number of bits (2050a, 2050b) used to indicate the muting related information (2040a, 2040b) to the terminal are allocated, the sum of them is 'the number of bits corresponding to the FDRA (1920) (N RBG , 1930, 2030a, 2030b)', the remaining bits can be treated as reserved (2060b). For example, the reserved bits can be filled with 0.

[0477] FIG. 21 illustrates DCI including cell-specific muting related information according to one embodiment of the present disclosure.

[0478] Referring to FIG. 21, DCI (2110) may be transmitted via PDCCH. The DCI (2110) may be a DCI format 0_3, ..., 0_x for scheduling PUSCH to multiple cells. Fields (2120, 2130, 2140) corresponding to cells scheduled by the DCI (2110) may be included in the DCI (2110). The field (2120) corresponding to serving cell a and the field (2130) corresponding to serving cell b may correspond to the contents described above in FIG. 20. The field (2140) corresponding to serving cell x may correspond to the contents described above in FIG. 19.

[0479] According to one embodiment of the present disclosure, when a symbol to be muted during PUSCH transmission overlaps with a DMRS associated with the PUSCH transmission, the terminal may interpret the position of the symbol to be muted during the PUSCH transmission as one of the symbols following the DMRS symbol (e.g., the symbol immediately following the DMRS symbol) and mute the PUSCH at the corresponding symbol.

[0480] According to one embodiment of the present disclosure, when a symbol to be muted during PUSCH transmission overlaps with a DMRS associated with the PUSCH transmission, the terminal may interpret the position of the symbol to be muted during the PUSCH transmission as one of the symbols preceding the DMRS symbol (e.g., the symbol immediately preceding the DMRS symbol) and mute the PUSCH at the corresponding symbol.

[0481] According to one embodiment of the present disclosure, when UCI is transmitted together with PUSCH transmission, if a symbol to be muted overlaps with a symbol to which the UCI is mapped, the terminal may interpret the position of the symbol to be muted during PUSCH transmission as one of the symbols following the symbol to which the UCI is transmitted (e.g., the symbol immediately following the symbol to which the UCI is mapped) and mute the PUSCH at the corresponding symbol.

[0482] According to one embodiment of the present disclosure, when UCI is transmitted together with PUSCH transmission, if a symbol to be muted overlaps with a symbol to which the UCI is mapped, the terminal may interpret the position of the symbol to be muted during PUSCH transmission as one of the symbols preceding the symbol to which the UCI is transmitted (e.g., the symbol immediately preceding the symbol to which the UCI is mapped) and mute the PUSCH at the corresponding symbol.

[0483] According to one embodiment of the present disclosure, when a UCI is transmitted together with a PUSCH transmission, if a symbol to be muted overlaps with a symbol to which the UCI is mapped, the UE may map the UCI excluding the RE to be muted in the muting symbol during UCI mapping. For example, when the frequency-axis index of an RE to which a certain 'modulated UCI symbol' is mapped is k, if REs corresponding to subcarrier indices ..., k-4, k-2, k, k+2, k+4, ... of the muting symbol are muted, the 'modulated UCI symbol' may be mapped to an RE corresponding to subcarrier index k+1 of the muting symbol.

[0484] According to one embodiment of the present disclosure, when a UCI is transmitted together with a PUSCH transmission, if a symbol to be muted overlaps with a symbol to which the UCI is mapped, the UE may map the UCI excluding the RE to be muted in the muting symbol during UCI mapping. For example, when the frequency-axis index of an RE to which a certain 'modulated UCI symbol' is mapped is k, if REs corresponding to subcarrier indices ..., k-4, k-2, k, k+2, k+4, ... of the muting symbol are muted, the 'modulated UCI symbol' may be mapped to an RE corresponding to a subcarrier index k-1 of the muting symbol.

[0485] According to one embodiment of the present disclosure, a terminal may receive PUSCH transmission configuration (e.g., RRC configuration) and / or PUSCH transmission scheduling information (e.g., DCI). The terminal may determine PUSCH transmission slot and symbol(s) (i.e., slot and symbol(s) allocated for PUSCH) based on the PUSCH transmission configuration (e.g., RRC configuration) and / or PUSCH transmission scheduling information (e.g., DCI). The terminal may determine PUSCH muting symbol(s) based on information transmitted via the RRC configuration and / or DCI. The terminal may determine frequency resources on which PUSCH is transmitted based on information transmitted via the above-described RRC configuration and / or DCI. The terminal may map modulated symbols to at least one layer, perform transform precoding depending on whether transform precoding is set / indicated, and perform precoding depending on whether precoding is set / indicated. The terminal may map the complex valued symbols output as a result of the precoding performed according to the setting / instruction to the remaining REs, excluding the resources used for RS (e.g. DM-RS, PT-RS, etc.) among the time-frequency resources on which the PUSCH is transmitted. At this time, the terminal may map the 'output complex valued symbols' to REs in the order of increasing RE indexes, starting from the RE with the lowest index belonging to the frequency resource, for non-muting symbol(s). The terminal may map any RE (e.g., it is first determined whether muting is performed in 'REs with even indices' or 'REs with odd indices', and the 'complex valued symbols' can be mapped starting from REs with the lowest index belonging to the frequency resource and in increasing order of RE index, excluding the 'REs subject to muting'. The value 0 can be mapped to the 'REs subject to muting'.

[0486] According to one embodiment of the present disclosure, the terminal applies a scaling factor to 'complex valued symbols'. can be mapped to REs by multiplying them. The terminal compensates for the power value due to muting for the 'complex valued symbols' mapped to the 'non-muting REs' of the 'muting symbol' by the scaling factor. Additionally, REs can be mapped by multiplying them by a value greater than 1.

[0487] According to one embodiment of the present disclosure, a terminal instructed to mute some of the resources used for PUSCH transmission may map 0 (zero) to the corresponding resources (PUSCH muting resources).

[0488] According to one embodiment of the present disclosure, muting of some of the resources used for PUSCH transmission may be applied only when the number of symbols allocated to the PUSCH is greater than or equal to a specific number. The specific number may be predefined between the terminal and the base station.

[0489] According to one embodiment of the present disclosure, muting of some of the resources used for PUSCH transmission may be applied only when the number of SFBD symbols among the time resources allocated to the PUSCH is greater than or equal to a specific number. The specific number may be predefined between the terminal and the base station.

[0490] According to one embodiment of the present disclosure, when some resources are transmitted over a PUSCH that is muted, the modulation and coding order index (MCS index, I) used MCS ) may have smaller or equal characteristics than those that do not.

[0491] FIG. 22 illustrates a procedure of a terminal for PUSCH transmission according to one embodiment of the present disclosure.

[0492] Some steps in FIG. 22 may be omitted in some cases, or two or more steps may be combined and performed as a single step. Furthermore, the order in FIG. 22 may be changed.

[0493] Referring to FIG. 22, a terminal may receive configuration information transmitted by a base station (2210). The base station may transmit the configuration information to the terminal. The configuration information may be transmitted via RRC signaling. For example, the configuration information may include configuration information for one or more cells, BWP configuration information, SBFD-related configuration information, resource allocation type configuration information, DCI format information to be monitored, and / or PUSCH muting-related configuration information.

[0494] The terminal can receive PUSCH scheduling information transmitted by the base station (2220). For example, the PUSCH scheduling information may be information included in DCI transmitted via PDCCH. The DCI may include a frequency domain resource allocation (FDRA) field. Alternatively, the PUSCH scheduling information may be PUSCH scheduling information configured via RRC. Alternatively, the PUSCH scheduling information may be PUSCH scheduling information configured via RRC and activated via PDCCH.

[0495] The terminal can determine whether the resource to which the PUSCH is mapped includes an SBFD symbol based on at least one of the configuration information or the scheduling information (2230). If not, the terminal can perform PUSCH transmission based on the configuration information and the PUSCH scheduling information (2250).

[0496] If the resource to which the PUSCH is mapped includes an SBFD symbol, the UE can determine whether to perform PUSCH muting (2240). The UE can determine whether some of the PUSCH transmission resources should be muted through the above-described muting-related configuration / indication information or the above-described preset / promised information. If PUSCH muting is not performed, the UE can perform PUSCH transmission based on the configuration information and PUSCH scheduling information (2250). If PUSCH muting is required, the UE can determine the muting resources based on the configuration information and PUSCH scheduling information (2260). The UE can determine the muting resources through the above-described muting-related configuration / indication information or the above-described preset / promised information. For example, the UE can obtain muting-related information through some bit fields included in a bit field included in the DCI (e.g., FDRA field) and determine the resources to be muted. The terminal can transmit PUSCH by muting the determined resource (2270).

[0497] For example, the muting-related information may include at least one of information on whether muting is applied or information on resources to which muting is applied. The information on resources to which muting is applied may include at least one of the number of symbols to which muting is applied, position information on symbols to which muting is applied, or information on resource elements (REs) within symbols to which muting is applied. For example, the position information on symbols to which muting is applied may be indicated in the form of a symbol index within the above-described slot. Alternatively, the position information on symbols to which muting is applied may be indicated in the form of a PUSCH transmission start symbol (l) described above. start ) from the muting symbol (l mute ) number of symbols between (d = l) mute - l start ) may be. Alternatively, the location information of the symbol to which the muting is applied may be a DMRS symbol (l) linked to the above-described PUSCH. dmrs ) from the muting symbol (l mute ) number of symbols between (d' = l mute - l dmrs ) may be.

[0498] According to one embodiment of the present disclosure, the above-described operation can be applied to PUSCH transmission scheduled via PDCCH, PUSCH transmission scheduled via RRC configuration, and PUSCH transmission configured via RRC and activated via PDCCH.

[0499] According to one embodiment of the present disclosure, the aforementioned operation can also be applied to repeated PUSCH transmissions. The aforementioned method can be applied to each repeatedly transmitted PUSCH. Alternatively, the aforementioned method can be applied to at least one of the repeatedly transmitted PUSCHs. Alternatively, the aforementioned method can be applied to the first or last PUSCH among the repeatedly transmitted PUSCHs.

[0500] The methods and / or embodiments described above in the present disclosure can be performed by the terminal of FIG. 23 and the base station of FIG. 24. FIG. 23 is a diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0501] Referring to FIG. 23, the terminal may include a transceiver (2310), a control unit (processor) (2320), and a memory (storage unit) (2330). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0502] The transceiver (2310) can transmit and receive signals with a base station. For example, the transceiver (2310) can transmit or receive a control channel or a data channel. For example, the transceiver (2310) can transmit or receive an RRC message. For example, the transceiver (2310) can receive a DCI scheduling a data channel via a PDCCH and transmit a PUSCH.

[0503] The control unit (2320) can control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (2320) can control the signal flow between each block to perform operations according to the flowchart described above. For example, the control unit (2320) can extract FDRA muting-related information, determine a muting resource, and map 0 to mute the PUSCH in the determined resource. For example, the control unit (2320) may be configured to receive configuration information through RRC signaling, receive DCI for scheduling a PUSCH, and the DCI may include a frequency domain resource allocation (FDRA) field, and determine whether a resource allocated to the PUSCH includes at least one SBFD symbol based on at least one of the configuration information and the DCI, and, if the resource allocated to the PUSCH includes the at least one SBFD symbol, determine muting-related information based on the FDRA field, apply muting of the PUSCH to a resource determined based on the muting-related information, and transmit the PUSCH.

[0504] In addition, the operation of the terminal described above can be controlled by the control unit (2320).

[0505] The memory (2330) can store at least one of information transmitted and received through the transceiver (2310) and information generated through the control unit (2320).

[0506] FIG. 24 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0507] Referring to FIG. 24, the base station may include a transceiver (2410), a control unit (processor) (2420), and a memory (2430). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0508] The transceiver (2410) can transmit and receive signals with the terminal. For example, the transceiver (2410) can transmit or receive a control channel or a data channel. For example, the transceiver (2410) can transmit or receive an RRC message. For example, the transceiver (2410) can transmit a DCI scheduling a data channel via a PDCCH, and the DCI can include determined muting-related information. For example, the transceiver (2410) can receive a PUSCH with some resources muted.

[0509] The control unit (2420) can control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (2420) can control the signal flow between each block to perform the operation according to the flowchart described above. For example, the control unit (2420) can transmit configuration information to the terminal through RRC signaling, transmit DCI for scheduling a PUSCH to the terminal, and the DCI can be configured to include a frequency domain resource allocation (FDRA) field and receive the PUSCH from the terminal. At this time, based on at least one of the configuration information or the DCI, whether the resource allocated to the PUSCH includes at least one SBFD symbol can be configured. In addition, when the resource allocated to the PUSCH includes the at least one SBFD symbol, the FDRA field includes muting-related information, and the muting-related information can include at least one of information on whether muting is applied or information on a resource to which muting is applied. Muting of the PUSCH may be applied to resources determined based on the above muting-related information.

[0510] In addition, the operation of the base station described above can be controlled by the control unit (2420).

[0511] The storage unit (2430) can store at least one of the information transmitted and received through the transmission and reception unit (2410) and the information generated through the control unit (2420).

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. In a method performed by a terminal in a wireless communication system, A step of receiving configuration information through RRC (radio resource control) signaling; A step of receiving downlink control information (DCI); A step of checking resources allocated to a physical uplink shared channel (PUSCH) based on at least one of the above configuration information or the DCI; A step of checking muting-related information for at least one resource among the resources allocated to the PUSCH based on at least one of the above setting information or the DCI; A step of applying muting of the PUSCH to a resource determined based on the muting-related information; and A step of transmitting the above PUSCH is included, A method wherein the above muting-related information includes at least one of information on whether muting is applied or information on a resource to which muting is applied.

2. In paragraph 1, A method in which information about resources to which muting is applied includes at least one of the number of symbols to which muting is applied, position information about symbols to which muting is applied, or information about resource elements (REs) within symbols to which muting is applied.

3. In paragraph 2, A method in which the location information of the symbol to which the muting is applied is indicated by a symbol index within a slot or the number of symbols between the start symbol of the PUSCH and the symbol to which the muting is applied.

4. In paragraph 1, The above configuration information includes a list of symbols to which muting is applied, and each entity of the list includes an index and position information of one or more symbols, A method wherein the frequency domain resource allocation (FDRA) field included in the DCI includes index information indicating one entity among the above lists.

5. In paragraph 1, The resource determined based on the above muting-related information includes at least one SBFD (subband non-overlapping full duplex) symbol, The step of applying muting of the PUSCH to the resource determined based on the muting-related information is: A step of identifying odd-numbered resource elements among resource elements corresponding to one of the at least one SBFD symbol based on the muting-related information; and A method comprising the step of mapping 0 to the odd-numbered resource elements identified above.

6. In paragraph 1, A method in which uplink control information (UCI) is not mapped to a resource element (RE) of a resource determined based on the above muting-related information.

7. In paragraph 1, A method in which a scaling factor for power compensation is applied to REs to which the PUSCH is mapped, excluding resource elements (REs) to which muting is applied among the resources allocated to the PUSCH.

8. In a wireless communication system, at the terminal, Transmitter and receiver; and A processor connected to the transceiver, the processor comprising: Receive configuration information through RRC (radio resource control) signaling, Receives downlink control information (DCI), Based on at least one of the above configuration information or the DCI, resources allocated to a physical uplink shared channel (PUSCH) are identified, Based on at least one of the above configuration information or the DCI, muting-related information for at least one resource among the resources allocated to the PUSCH is checked, Applying muting of the PUSCH to the resources determined based on the above muting-related information, and It is set to transmit the above PUSCH, and A terminal in which the above muting-related information includes at least one of information on whether muting is applied or information on a resource to which muting is applied.

9. In paragraph 8, The information about the resource to which the muting is applied includes at least one of the number of symbols to which the muting is applied, position information of the symbol to which the muting is applied, or information about a resource element (RE) within the symbol to which the muting is applied, and A terminal in which the position information of the symbol to which the muting is applied is indicated by a symbol index within a slot or the number of symbols between the start symbol of the PUSCH and the symbol to which the muting is applied.

10. In paragraph 8, The above configuration information includes a list of symbols to which muting is applied, and each entity of the list includes an index and position information of one or more symbols, A terminal, wherein the frequency domain resource allocation (FDRA) field included in the DCI includes index information indicating one entity among the above lists.

11. In paragraph 8, The resource determined based on the above muting-related information includes at least one SBFD (subband non-overlapping full duplex) symbol, To apply muting of the PUSCH to a resource determined based on the muting-related information, the processor: Based on the above muting-related information, odd-numbered resource elements are identified among the resource elements corresponding to one of the at least one SBFD symbols, and A terminal configured to map 0 to the odd-numbered resource elements identified above.

12. In paragraph 8, The resource element (RE) of the resource determined based on the above muting-related information is not mapped with uplink control information (UCI), and A terminal in which a scaling factor for power compensation is applied to REs to which the PUSCH is mapped, excluding resource elements (REs) to which muting is applied among the resources allocated to the PUSCH.

13. In a method performed by a base station in a wireless communication system, A step of transmitting configuration information to a terminal through RRC (radio resource control) signaling; A step of transmitting downlink control information (DCI) to the terminal; and A step of receiving a physical uplink shared channel (PUSCH) from the terminal, Based on at least one of the above configuration information or the DCI, resources allocated to the PUSCH are set, Based on at least one of the above configuration information or the DCI, muting-related information for at least one resource among the resources allocated to the PUSCH is confirmed, The above muting-related information includes at least one of information on whether muting is applied or information on the resource to which muting is applied, and A method in which muting of the PUSCH is applied to a resource determined based on the muting-related information.

14. In paragraph 13, The information about the resource to which the muting is applied includes at least one of the number of symbols to which the muting is applied, position information of the symbol to which the muting is applied, or information about a resource element (RE) within the symbol to which the muting is applied, and A method wherein the frequency domain resource allocation (FDRA) field included in the DCI includes muting-related information for multiple cells.

15. In a base station in a wireless communication system, Transmitter and receiver; and A processor connected to the transceiver, the processor comprising: Transmits configuration information to the terminal through RRC (radio resource control) signaling, Transmits downlink control information (DCI) to the terminal, and It is set to receive a physical uplink shared channel (PUSCH) from the terminal, Based on at least one of the above configuration information or the DCI, resources allocated to the PUSCH are set, Based on at least one of the above configuration information or the DCI, muting-related information for at least one resource among the resources allocated to the PUSCH is confirmed, The above muting-related information includes at least one of information on whether muting is applied or information on the resource to which muting is applied, and A base station in which muting of the PUSCH is applied to resources determined based on the above muting-related information.

Images