Method and apparatus for transmitting physical uplink shared channel in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal in a wireless communication system comprises the steps of: receiving, from a base station, a radio resource control (RRC) message including first information for configuring muting of a physical uplink shared channel (PUSCH), second information for indicating a time location of a resource for the muting of the PUSCH, and third information for indicating a frequency location of the resource for the muting of the PUSCH; receiving, from the base station, downlink control information (DCI) for scheduling the PUSCH; and transmitting the PUSCH to the base station by muting the resource on the basis of the first information, the second information, and the third information.

Description

Method and device for transmitting a physical uplink shared channel in a wireless 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 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] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

[0009] Based on the discussion described above, the present disclosure provides a physical uplink shared channel (PUSCH) transmission device and method for a terminal supporting subband non-overlapping full duplex (SBFD) communication in a wireless communication system.

[0010] According to various embodiments of the present disclosure, a method performed by a terminal of a wireless communication system may include the steps of: receiving an RRC (Radio Resource Control) message including first information for setting muting of a PUSCH (Physical Uplink Shared Channel) from a base station, second information for indicating a time position of a resource for muting the PUSCH, and third information for indicating a frequency position of the resource for muting the PUSCH; receiving DCI (Downlink Control Information) for scheduling a PUSCH from the base station; and transmitting a PUSCH to the base station by muting the resource based on the first information, the second information, and the third information.

[0011] In addition, according to various embodiments of the present disclosure, a method performed by a base station of a wireless communication system may include a step of transmitting an RRC (Radio Resource Control) message including first information for setting muting of a PUSCH (Physical Uplink Shared Channel), second information for indicating a time position of a resource for muting of the PUSCH, and third information for indicating a frequency position of a resource for muting of the PUSCH to a terminal, a step of transmitting DCI (Downlink Control Information) for scheduling a PUSCH to the terminal, and a step of receiving a PUSCH with the resource muted based on the first information, the second information, and the third information from the terminal.

[0012] Through embodiments of the present disclosure, a device and method capable of effectively providing a service in a wireless communication system are provided.

[0013] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0014] FIG. 1 illustrates the basic structure of the time-frequency domain in a wireless communication system according to embodiments of the present disclosure.

[0015] FIG. 2 illustrates a frame, subframe, and slot structure in a wireless communication system according to embodiments of the present disclosure.

[0016] FIG. 3 illustrates an example of bandwidth portion settings in a wireless communication system according to embodiments of the present disclosure.

[0017] FIG. 4 illustrates an example of setting a control region of a downlink (DL) control channel in a wireless communication system according to embodiments of the present disclosure.

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

[0019] FIG. 6 illustrates an example of a method for a base station and a terminal to transmit and receive data in consideration of downlink data channels and rate matching resources in a wireless communication system according to embodiments of the present disclosure.

[0020] FIG. 7 illustrates an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to embodiments of the present disclosure.

[0021] FIG. 8 illustrates an example of time domain resource allocation of PDSCH in a wireless communication system according to embodiments of the present disclosure.

[0022] FIG. 9 illustrates an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to embodiments of the present disclosure.

[0023] FIG. 10 illustrates a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to embodiments of the present disclosure.

[0024] FIG. 11 illustrates an example of a random access procedure in embodiments of the present disclosure.

[0025] FIG. 12 illustrates an example of a time division duplex (TDD) configuration and a subband non-overlapping full duplex (SBFD) configuration according to embodiments of the present disclosure.

[0026] FIG. 13 illustrates a muting symbol according to embodiments of the present disclosure.

[0027] FIG. 14 illustrates a muting symbol applied to a symbol following a UCI symbol according to embodiments of the present disclosure.

[0028] FIG. 15 illustrates a muting symbol according to embodiments of the present disclosure.

[0029] FIG. 16a illustrates a muting symbol according to embodiments of the present disclosure.

[0030] FIG. 16b is a diagram illustrating a TDRA table according to embodiments of the present disclosure.

[0031] FIG. 16c is a diagram illustrating some rows of a TDRA table according to embodiments of the present disclosure.

[0032] Figure 17 shows the location of DMRS according to embodiments of the present disclosure.

[0033] FIG. 18 illustrates the structure of a terminal in a wireless communication system according to embodiments of the present disclosure.

[0034] FIG. 19 illustrates the structure of a base station in a wireless communication system according to embodiments of the present disclosure.

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

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

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

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

[0039] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, the downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology developed after LTE-A (e.g., 5G NR (new radio)) may be included here, and the 5G below may also be a concept that includes the existing LTE (long-term evolution), LTE-A (advanced), and other similar services. In addition, 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 determined by a person having skilled technical knowledge.

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

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

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

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

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

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

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

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

[0048] URLLC refers to a cellular-based wireless communication service used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of 10-5 or lower. Therefore, for services supporting URLLC, 5G systems must provide a shorter Transmit Time Interval (TTI) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

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

[0050] [NR time-frequency resources]

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

[0052] FIG. 1 illustrates the basic structure of the time-frequency domain in a wireless communication system according to embodiments of the present disclosure. More specifically, FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted in a 5G system.

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

[0054] FIG. 2 illustrates a frame, subframe, and slot structure in a wireless communication system according to embodiments of the present disclosure.

[0055] FIG. 2 illustrates an example of a structure of a frame (200), a subframe (201), and a slot (202). One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (for example, the number of symbols per slot ( )=14). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing.

[0056] Referring to FIG. 2, cases where the subcarrier spacing setting value is μ=0 (204) and μ=1 (205) are illustrated. When μ=0 (204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1 (205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per 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.

[0057]

[0058] [Bandwidth Part (BWP)]

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

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

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

[0062]

[0063] The configuration information is, of course, not limited to the examples above, and in addition to the configuration information described above, various parameters related to the bandwidth portion may be configured for the terminal. The above-described information may be transmitted from the base station to the terminal via higher-layer signaling, such as RRC (Radio Resource Control) 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).

[0064] According to some embodiments, a terminal before RRC (Radio Resource Control) connection can receive 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, through the MIB during the initial access phase, configuration information about a control region (Control Resource Set, CORESET) and a search space where a physical downlink control channel (PDCCH) for receiving system information (e.g., Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access can be transmitted. The control region and search space configured by the MIB can each be regarded as identifier (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 region #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and occasion settings for control area #0 (e.g., search space #0) via the MIB. The terminal can consider the frequency range designated as control area #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.

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

[0066] In some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, the base station can support this by configuring the bandwidth portion. For example, the base station can configure the bandwidth portion frequency position (e.g., configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency position within the system bandwidth.

[0067] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, a base station may configure two bandwidth segments with subcarrier spacings of 15 kHz and 30 kHz, respectively, to support data transmission and reception using both subcarrier spacings of 15 kHz and 30 kHz for a given terminal. 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.

[0068] Furthermore, in some embodiments, for the purpose of reducing power consumption of the terminal, the base station may set bandwidth portions with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth (e.g., 100 MHz bandwidth) and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may set a bandwidth portion with a relatively small bandwidth (e.g., 20 MHz bandwidth portion) for the terminal. In a situation where there is no traffic, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0069] In the method for setting the bandwidth part described above, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive, from the MIB of the PBCH (Physical Broadcast Channel), a control region (Control Resource Set, CORESET) for a downlink control channel on which downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted. The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0070] [Bandwidth Part (BWP) Change]

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

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

[0073]

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

[0075] According to the requirement for bandwidth part change delay time mentioned above, when a terminal receives DCI including a bandwidth part change indicator in slot n, it changes to a new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP It can be completed at a later time. In addition, the terminal can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth portion. If the base station wants to schedule a data channel in the new bandwidth portion, it should set the bandwidth portion change delay time (T) of the terminal. BWP ), time domain resource allocation for the data channel can be determined by considering the bandwidth portion change delay time. For example, when the base station schedules a data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

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

[0077] [SS / PBCH block]

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

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

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

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

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

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

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

[0085] [PDCCH: DCI related]

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

[0087] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from 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 predefined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

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

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

[0090] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include the information in Table 4 below.

[0091]

[0092] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include the information in Table 5 below.

[0093]

[0094]

[0095] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include the information in Table 6 below.

[0096]

[0097] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include the information in Table 7 below.

[0098]

[0099]

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

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

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

[0103] The base station can configure the control region for the terminal in the aforementioned 5G through higher-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring the control region for the terminal may mean providing information such as the control region identifier (Identity), frequency location of the control region, and symbol length of the control region. For example, the information configuring the control region may include the information in Table 8.

[0104]

[0105] In Table 8, the tci-StatesPDCCH (e.g., conveniently named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0106] FIG. 5 illustrates the structure of a downlink control channel in a wireless communication system according to embodiments of the present disclosure. More specifically, FIG. 5 illustrates an example of the basic units of time and frequency resources that constitute a downlink control channel that can be used in 5G.

[0107] According to FIG. 5, the basic unit of time and frequency resources constituting a control channel can be referred to as a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) (e.g., 12 subcarriers) on the frequency axis. A base station can concatenate REGs (503) to configure a downlink control channel allocation unit.

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

[0109] The basic unit of the downlink control channel illustrated in FIG. 5 (e.g., REG (503)) may include both REs to which DCI is mapped and regions to which DMRS (505), which is a reference signal for decoding the REs, is mapped. As in FIG. 5, three DMRSs (505) may be transmitted within one REG (503). The number of CCEs required to transmit a PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level, and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL = L, one downlink control channel may be transmitted through L CCEs.

[0110] A terminal must detect a signal without knowing information about the downlink control channel. For blind decoding, a search space representing a set of CCEs can be defined. The search space can refer to a set of downlink control channel candidates, which are CCEs that the terminal should attempt to decode at a given aggregation level. There can be multiple aggregation levels that create a single bundle of 1, 2, 4, 8, or 16 CCEs, and thus the terminal can have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0111] Search spaces can be classified 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 for system information or paging messages. For example, a UE can receive PDSCH scheduling allocation information for transmitting a SIB, including cell operator information, 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, need to receive the PDCCH, it can be defined as a set of pre-arranged CCEs. A UE can receive scheduling allocation information for a UE-specific PDSCH or PUSCH by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically based on the identity of the UE and a function of various system parameters.

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

[0113]

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

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

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

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

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

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

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

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

[0122] In a terminal-specific search space, the following combinations of DCI formats and RNTIs may be monitored, but these are only examples and are not limited to the examples below.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0136] The aforementioned specified DCI formats may follow the definitions as shown in the example in Table 10.

[0137]

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

[0139]

[0140] - : Integration level

[0141] - Carrier Index

[0142] - Total number of CCEs present within control region p

[0143] - Slot Index

[0144] - Number of PDCCH candidates for aggregation level L

[0145] - PDCCH candidate index for aggregation level L

[0146] -

[0147] -

[0148] - Terminal identifier

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

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

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

[0152] FIG. 6 illustrates an example of a method for a base station and a terminal to transmit and receive data in consideration of downlink data channels and rate matching resources in a wireless communication system according to embodiments of the present disclosure.

[0153] Referring to FIG. 6, a downlink data channel (PDSCH) (601) and a rate matching resource (602) are illustrated. A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information can include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). Hereinafter, a bitmap corresponding to frequency-domain resource allocation information (604) may be referred to as a “first bitmap,” a bitmap corresponding to time-domain resource allocation information (603) may be referred to as a “second bitmap,” and a bitmap corresponding to period information (605) may be referred to as a “third bitmap.” If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

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

[0155] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following configuration methods can be followed.

[0156] RB symbol level

[0157] A terminal can receive up to four RateMatchPatterns for each bandwidth segment via upper-layer signaling. A single RateMatchPattern can include the following. Of course, the examples below are not limited.

[0158] - As a reserved resource within the bandwidth section, the time and frequency resource domains of the reserved resource may be set by combining RB-level bitmaps and symbol-level bitmaps along the frequency axis. The reserved resource may span one or two slots (e.g., may be spanned). A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB-level and symbol-level bitmap pair are repeated may additionally be set.

[0159] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0160] RE level

[0161] The terminal can receive the following information via upper-layer signaling. Of course, the information may not be limited to the examples below.

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

[0163] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0164] [PDSCH: Frequency Resource Allocation Related]

[0165] FIG. 7 illustrates an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to embodiments of the present disclosure.

[0166] Figure 7 illustrates three frequency axis resource allocation methods that can be configured through an upper layer in an NR wireless communication system: resource type-0 (700), type-1 (705), and dynamic switch (710).

[0167] Referring to Fig. 7, if the terminal is set to use only type-0 resource allocation through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH to the terminal is N RBG It may contain a bitmap consisting of N bits. RBG can mean the number of RBGs (resource block groups) determined as shown in [Table 11] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data can be transmitted to the RBG indicated as 1 by the bitmap.

[0168]

[0169] If the terminal is configured to use only resource type-1 resource allocation through upper layer signaling (705), the DCI that allocates PDSCH to the terminal is It may include frequency domain resource allocation information (FDRA) consisting of bits. Through this, the base station can set the starting VRB (720) and the length (725) of frequency axis resources allocated continuously therefrom.

[0170] If a terminal is configured to use both resource type-0 resource allocation and resource type-1 resource allocation through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal may include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring resource type-0 resource allocation and the payload (720, 725) for configuring resource type-1 resource allocation. Conditions for this will be described later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that resource type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that resource type-1 resource allocation is used.

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

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

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

[0174]

[0175]

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

[0177] FIG. 8 illustrates an example of time domain resource allocation of PDSCH in a wireless communication system according to embodiments of the present disclosure.

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

[0179] FIG. 9 illustrates an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to embodiments of the present disclosure.

[0180] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel are the same (900)( ), the slot number for data and control is the same, so the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (905)( ), the slot numbers for data and control are different, so the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0181] [PUSCH: Transmission method related]

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

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

[0184]

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

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

[0187]

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

[0189] The SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives the SRI through the DCI, the SRS resource indicated by the SRI can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. When the UE is configured with one SRS resource, the TPMI can be used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI can be used to indicate the precoder to be applied in the SRS resource indicated through SRI.

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

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

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

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

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

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

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

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

[0198] A base station can transmit one NZP-CSI-RS associated with an SRS resource set to a terminal. The terminal can calculate a precoder to use when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. The terminal can apply the calculated precoder when transmitting one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station. The base station can select one or more SRS resources from the received one or more SRS resources. In non-codebook-based PUSCH transmission, the SRI can indicate an index that can express a combination of one or more SRS resources. The SRI can be included in the DCI. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of PUSCH transmission layers. The terminal can transmit the PUSCH by applying the precoder applied to the SRS resource transmission for each layer.

[0199] [CA / DC related]

[0200] FIG. 10 illustrates a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to embodiments of the present disclosure.

[0201] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system may be composed of NR SDAP (service data adaptation protocol) (1025, 1070), NR PDCP (packet data convergence protocol) (1030, 1065), NR RLC (radio link control) (1035, 1060), and NR MAC (medium access control) (1040, 1055) in the terminal and NR base station, respectively.

[0202] The main functions of NR SDAP (1025, 1070) may include some of the following functions:

[0203] - Transfer of user plane data

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

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

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

[0207] For an SDAP layer device, the terminal can be configured by an RRC message for each PDCP layer device, each bearer, or each 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 RRC message can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink using the NAS reflective QoS 1-bit indicator and the AS reflective QoS 1-bit indicator 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 a smooth service.

[0208] The main functions of NR PDCP (1030, 1065) may include some of the following functions:

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

[0210] - User data transfer function

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

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

[0213] - PDCP PDU reordering for reception

[0214] - Duplicate detection of lower layer SDUs

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

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

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

[0218] Referring to the above-described functions, 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 the PDCP SN (sequence number). The reordering function may include a function of transmitting data to an upper layer in the reordered order. The reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, and a function of recording lost PDCP PDUs by reordering the order. The reordering function may include a function of reporting a status on lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0219] The main functions of NR RLC (1035, 1060) may include some of the following functions:

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

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

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

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

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

[0225] - Re-segmentation of RLC data PDUs

[0226] - Reordering of RLC data PDUs

[0227] - Duplicate detection function

[0228] - Protocol error detection

[0229] - RLC SDU discard function

[0230] - RLC re-establishment function

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

[0232] The out-of-sequence delivery function of the NR RLC device described above 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 multiple RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs, and 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.

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

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

[0235] - Multiplexing / demultiplexing of MAC SDUs

[0236] - Scheduling information reporting function

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

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

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

[0240] - MBMS service identification function

[0241] - Transport format selection function

[0242] - Padding function

[0243] The NR PHY layer (1045, 1050) can perform operations of channel coding and modulating upper layer data, converting it into OFDM symbols, and transmitting it over a wireless channel. The NR PHY layer can perform operations of demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

[0244] The above-described wireless protocol structure may have various detailed structures depending on the carrier (or cell) operation method. According to embodiments, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer (1010). When a base station transmits data to a terminal based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer (1020). According to another embodiment, when a base station transmits data to a terminal based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer (1030).

[0245] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support repeated PDCCH transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present invention provides a method for repeated PDCCH transmission through multiple transmission and reception points (TRPs), thereby improving the reliability of PDCCH reception by a terminal. The specific method is described in detail in the embodiments below.

[0246] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD (frequency division duplex) and TDD (time division duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a downlink data channel of a physical layer of a base station is used to transmit a signal to a terminal, or an uplink data channel of a physical layer of a terminal is used to transmit a signal to a base station, and may also be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element, MAC CE).

[0247] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scramble the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied with a specific RNTI, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, a case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to the above may be referred to as an NC-JT case.

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

[0249] In the present disclosure below, the above-described 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.

[0250] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of 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. Although embodiments of the present disclosure are described below using a 5G system as an example, 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. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure are applicable to FDD and TDD systems.

[0251] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, 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.

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

[0253] - MIB (Master Information Block)

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

[0255] - RRC (Radio Resource Control)

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

[0257] Additionally, L1 signaling may include signaling corresponding to at least one or a combination of one or more of the signaling methods using the physical layer channels or signaling below.

[0258] - PDCCH (Physical Downlink Control Channel)

[0259] - DCI (Downlink Control Information)

[0260] - UE-specific DCI

[0261] - Group common DCI

[0262] - Common DCI

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

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

[0265] - PUCCH (Physical Uplink Control Channel)

[0266] - UCI (Uplink Control Information)

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

[0268] In the present disclosure below, the above-described 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.

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

[0270] - As a first method, in addition to the existing unpaired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD) frame structure types, another frame structure type (e.g., frame structure type 2) may be introduced to define the SBFD described above. Frame structure type 2 may be defined to be supported in a specific frequency or frequency band. Alternatively, the base station may indicate to the terminal whether SBFD is supported through system information. The SBFD terminal may receive the system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0271] - As a 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. According to 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 or not through system information. The SBFD terminal can receive the system information including whether SBFD is supported and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

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

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

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

[0275] In embodiments, when information on whether SBFD is supported is included in system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether 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 acquire the information on whether SBFD is supported inserted at the very end, or acquires information indicating that SBFD is not supported, the SBFD terminal may determine that the cell (or base station) only supports TDD.

[0276] In embodiments, when information on whether SBFD is supported is included in system information for a terminal supporting a different version of the standard (e.g., a legacy TDD terminal), the information on whether SBFD is supported may be transmitted through a separate PDSCH so as not to affect acquisition of system information by the legacy TDD terminal. For example, a terminal that does not support SBFD may receive a first SIB (or SIB1) including legacy TDD-related system information on a first PDSCH. An SBFD-supporting terminal may receive a first SIB (or SIB) including legacy TDD-related system information on a first PDSCH, and may receive a second SIB including SBFD-related system information on a second PDSCH. Here, the first PDSCH and the second PDSCH may be scheduled as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) of the first PDCCH and the second PDCCH may be scrambled with the same RNTI (e.g., SI-RNTI). 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 (for example, if 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.

[0277] As described above, when an SBFD terminal determines that a 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.

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

[0279] According to various embodiments of the present disclosure, a base station may configure random access resources for TDD terminals and additionally configure separate random access resources for SBFD terminals. Here, the SBFD terminal may be able to use the random access resources for TDD terminals, or may not be able to use the random access resources for TDD terminals. In the latter case, the SBFD terminal may always only use the separate random access resources for SBFD terminals.

[0280] In embodiments, an SBFD terminal may be instructed by a base station whether or not it can use random access resources for a TDD terminal. Such an instruction may be included and indicated in an SIB. For example, the SIB may configure a separate random access resource for the SBFD terminal, and along with the configuration, may also indicate whether or not the random access resource for the TDD terminal is available. Such an instruction may be indicated through 1-bit information. In embodiments, if the 1-bit information is '0' (or FALSE), the SBFD terminal cannot use the random access resource for the TDD terminal, or if the 1-bit information is '1' (or TRUE), the SBFD terminal may use the random access resource for the TDD terminal. Depending on various embodiments, this is merely an example, and the opposite case may also be included.

[0281] In embodiments, the base station may determine the type of terminal attempting to access a cell based on the random access resources used by the terminal. For example, an SBFD terminal may transmit a PRACH through a separate random access resource for SBFD terminals. The base station may receive the PRACH transmitted by the SBFD terminal and determine that the SBFD terminal is attempting to access the cell. For example, if a TDD terminal transmits a PRACH through a random access resource for TDD terminals, the base station may receive this RPACH and determine that the TDD terminal is attempting to access the cell. In this case, if the SBFD terminal is allowed to transmit the PRACH through the random access resource for the TDD terminal, the base station may be ambiguous as to whether the type of the terminal transmitting the PRACH is a TDD terminal or an SBFD terminal. In this case, the base station may always assume that the type of the above-mentioned terminal is a TDD terminal.

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

[0283] In embodiments, if the base station determines that the terminal involved is a TDD terminal, the base station may not be able to use the uplink subband configuration when scheduling msg2, msg3, msg4, etc. to the terminal. For example, even if the uplink subband is configured in a downlink symbol or a flexible symbol, the base station may assume that the terminal cannot obtain the configured uplink subband configuration information. When scheduling msg3 PUSCH to the terminal, the base station may schedule msg3 PUSCH in a flexible symbol or an uplink symbol. In other words, msg3 PUSCH cannot be scheduled in an uplink subband.

[0284] According to various embodiments of the present disclosure, a base station may configure a common random access resource for all terminals within a cell without configuring a separate random access resource for an SBFD terminal. In this case, configuration information for the random access resource may be transmitted to all terminals within the cell through system information, and an SBFD terminal that has received such system information may perform random access for the configured random access resource. Thereafter, the SBFD terminal may complete the random access process and proceed to an 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, which may determine that a portion of the frequency resource of the downlink time resource has been configured as an uplink resource, and may perform an SBFD operation (e.g., transmitting an uplink signal on the configured uplink resource) accordingly.

[0285] In embodiments, when it is determined that a cell supports SBFD, the SBFD terminal may notify the base station that the terminal attempting to connect is an SBFD terminal by transmitting capability information to the base station, the capability information including at least one of whether the terminal supports SBFD, whether it supports full-duplex communication or half-duplex communication, or the number of transmit or receive antennas that the terminal has (or supports). In embodiments, when half-duplex communication support is a mandatory implementation for the SBFD terminal, the half-duplex communication support may be omitted from the capability information. The SBFD terminal's report of the capability information may be reported to the base station through a random access procedure, may be reported separately to the base station after the random access procedure is completed, or may be reported to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

[0286] In embodiments, the SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at a specific moment, like a conventional TDD terminal, or may support full-duplex communication, which performs both uplink transmission and downlink reception at a specific moment. Accordingly, whether or not to support half-duplex communication or full-duplex communication 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 half-duplex communication to the base station, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD, since a duplexer is generally not present.

[0287] In embodiments, a terminal may generally establish a wireless link with a network through a random access procedure based on synchronization with the network and system information acquired during a cell search process. Random access may be contention-based or contention-free. Contention-based random access may be used for purposes such as when a terminal performs cell selection and reselection during the initial access phase of a cell (e.g., when moving from an RRC_IDLE state to an RRC_CONNECTED state). Contention-free random access may be used to reestablish uplink synchronization when downlink data arrives, in the case of a handover, or in the case of position measurement.

[0288] FIG. 11 illustrates an example of a random access procedure in embodiments of the present disclosure. More specifically, a random access procedure in a wireless communication system is illustrated with reference to FIG. 11.

[0289] Referring to FIG. 11, a contention-based random access procedure according to embodiments is illustrated. In addition, although not illustrated in FIG. 11, as described above, the base station may transmit a synchronization signal block. In this case, the base station may periodically transmit the synchronization signal block using beam sweeping. For example, the base station may transmit a synchronization signal block (e.g., an SS / PBCH (SSB) block) including a primary synchronization signal (PSS) / secondary synchronization signal (SSS) (synchronization signal) and a physical broadcasting channel (PBCH) (broadcast channel) signal using up to 64 different beams for 5 ms, and a plurality of synchronization signal blocks may be transmitted using different beams. The terminal can detect (select) a synchronization signal block having an optimal beam direction (e.g., the direction of the beam in which the received signal strength is the strongest or is greater than a predetermined threshold value), and transmit a preamble using a physical random access channel (PRACH) resource associated with the detected synchronization signal block. For example, as a first step (1110) of the random access procedure, the terminal can transmit a random access preamble (or message 1) to the base station. The base station receiving the random access preamble can measure a transmission delay value between the terminal and the base station and synchronize uplink. Specifically, the terminal can transmit a random access preamble selected randomly from a random access preamble set given in advance by system information. The initial transmission power of the random access preamble can be determined according to the path loss between the base station and the terminal measured by the terminal.Additionally, the terminal can determine the transmission beam direction (or transmission beam or beam) of the random access preamble based on the synchronization signal block received from the base station, and transmit the random access preamble by applying the determined transmission beam direction.

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

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

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

[0293] - Uplink scheduling grant

[0294] - Timing advance value

[0295] In embodiments, if the terminal does not receive RAR, which is scheduling information for message 3, from the base station for a predetermined period of time in the second step (1120), the first step (1110) may be performed again. If the first step is performed again, the terminal may increase the transmission power of the random access preamble by a predetermined step (e.g., power ramping) and transmit it, thereby increasing the probability of the base station receiving the random access preamble.

[0296] In the third step (1130), the UE may transmit uplink information (e.g., scheduled transmission or message 3) including its UE identifier (e.g., UE contention resolution identity) (or, if the UE already has a valid UE identifier (C-RNTI) within the cell before initiating the random access procedure, the valid UE identifier) ​​to the base station via an uplink data channel (physical uplink shared channel, PUSCH) using the uplink resources allocated in the second step (1120). The PUSCH may be referred to as message 3 PUSCH (msg3 PUSCH). The transmission timing of the uplink data channel for transmitting message 3 may follow the uplink transmission timing control command received from the base station in the second step (1120). In addition, the transmission power of the uplink data channel for transmitting message 3 may be determined in consideration of the power control command received from the base station in the second step (1120) and the power ramping value of the random access preamble. The uplink data channel for transmitting message 3 may include the first uplink data signal transmitted by the terminal to the base station after the terminal transmits the random access preamble.

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

[0298] In embodiments, if the data transmitted by the terminal in step 3 (1130) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not perform any further data transmission to the terminal. Accordingly, if the terminal fails to receive data transmitted from the base station in step 4 (1140) for a certain period of time, the random access procedure may be determined to have failed, and may be restarted from step 1 (1110).

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

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

[0301] Meanwhile, according to an embodiment of the present disclosure, a method is required in which an SBFD terminal determines the validity of a PRACH transmission time point through a PRACH configuration index and an SBFD configuration for performing PRACH transmission, and performs PRACH transmission through a PRACH transmission time point determined to be valid, or a method for a procedure performed by the SBFD terminal when a valid PRACH transmission time point and downlink reception overlap.

[0302]

[0303]

[0304]

[0305]

[0306]

[0307]

[0308]

[0309]

[0310]

[0311] FIG. 12 illustrates an example of a time division duplex (TDD) configuration and a subband non-overlapping full duplex (SBFD) configuration according to embodiments of the present disclosure. More specifically, FIG. 12 illustrates an example of SBFD operating in a TDD band of a wireless communication system to which the present disclosure is applied.

[0312] In Fig. 12 (a), 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 a downlink slot (or symbol), an uplink slot (or symbol) (1201), and a flexible slot (or symbol) based on settings according to TDD UL-DL resource configuration information indicating TDD downlink slot (or symbol) resources and uplink slot (or symbol) resources with an existing TDD terminal or an SBFD terminal.

[0313] In embodiments, it can be assumed that the DDDSU slot format is configured according to the TDD UL-DL resource configuration information in FIG. 12. Here, 'D' represents a slot composed entirely of downlink symbols, 'U' represents a slot composed entirely of uplink symbols, and 'S' may represent a slot other than 'D' or 'U' (e.g., a slot including a downlink symbol or an uplink symbol or including a flexible symbol). For convenience, it can be assumed that S comprises 12 downlink symbols and 2 flexible symbols, but this is merely an example and is not limited to the above-described example. The DDDSU slot format may be repeated according to the TDD UL-DL resource configuration information. For example, the repetition period of the TDD configuration may include 5 slots (e.g., 5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

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

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

[0316] Referring to (c) of Fig. 12, the terminal may set some of the frequency bands of the cell as frequency bands (1220) capable of uplink transmission, and may set a time region in which the frequency bands are activated. Here, the frequency bands described above may be called uplink subbands (UL subbands). Referring to (c) of Fig. 12, the uplink subband (UL subband) on the first slot may be deactivated, and the uplink subbands (UL subbands) on the remaining slots may be activated. Accordingly, the terminal may transmit an uplink channel or signal on the uplink subbands (UL subbands) (1222) of the remaining slots. That is, although (c) of Fig. 12 illustrates an example in which the uplink subband (UL subband) is activated on a slot-by-slot basis, this is merely an example, and it is of course possible to set whether or not to activate it on a symbol-by-symbol basis.

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

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

[0319] [PUSCH's Muting Symbol]

[0320] In the following description, a muting symbol of a PUSCH may indicate not allocating power to all or some REs of one or some symbols scheduled for the PUSCH. REs to which power is not allocated may be referred to as muting REs.

[0321] The base station can use the muting REs in the PUSCH to estimate the power of a signal leaked from an adjacent base station, the covariance matrix of the signal, or the channel between adjacent base stations. If there is no muting RE in the PUSCH, it may be difficult to estimate the power of a signal leaked due to a signal transmitted from a terminal, the covariance matrix of the signal, or the channel between adjacent base stations. The base station can suppress the leakage signal that affects the reception of the PUSCH using the estimated power of the leakage signal, the covariance matrix of the leakage signal, or the estimated channel between adjacent base stations.

[0322] FIG. 13 illustrates a muting symbol according to embodiments of the present disclosure.

[0323] Referring to Fig. 13(a), the muting symbol may be a comb-2 pattern. That is, PUSCH data may be allocated (power allocated) to even-numbered REs or odd-numbered REs, and the remaining REs may be muted (power not allocated).

[0324] Referring to Fig. 13(b), all REs in the muting symbol can be muted (power unallocated).

[0325] A muting symbol according to embodiments of the present disclosure may include one of the muting patterns shown in FIGS. 13(a) and 13(b). The muting pattern is, for example, a muting pattern other than the pattern shown in FIGS. 13(a) and 13(b) may also be applied.

[0326] In one embodiment, a comb-4 pattern or a comb-6 pattern may be applied. In the case of a comb-4 pattern, muting may be applied to three REs among twelve REs in the frequency axis within a PRB. Here, the indices of the three REs may include any one of {0, 4, 8}, {1, 5, 9}, {2, 6, 10}, or {3, 7, 11}, and the spacing between the REs is 4.

[0327] In one embodiment, for a Comb-6 pattern, muting may be applied to two REs among 12 REs in the frequency axis within a PRB. Here, the indices of the two REs may include any one of {0, 6}, {1, 7}, {2, 8}, {3, 9}, {4, 10}, or {5, 11}, and the interval between the REs is 6. Here, the RE with index 0 may represent the lowest RE in the frequency axis among the 12 REs included in the PRB.

[0328] In the muting symbol, the muting pattern can be applied to all PRBs where PUSCH is scheduled, or to some PRBs. If it is applied to some PRBs, the PRBs can be configured by the base station. The index of PRBs where PUSCH is scheduled is N start , N start +1, N start +2, ..., N start +N PRB If it is -1, the PRB with the PRB index 0 may be the PRB with the lowest frequency of the UL BWP. The PRB with the PRB index 0 may be the PRB with the lowest frequency of the UL subband. The PRB with the PRB index 0 may be a Common Resource Block (CRB) with the index 0. The subcarrier with the lowest frequency among the subcarriers included in the CRB with the index 0 may be the subcarrier indicated by PointA. PointA can be set by the base station to the terminal through system information. N start is the index of the first PRB for which PUSCH is scheduled. N PRB may represent the number of PRBs for which PUSCH is scheduled. The terminal may be configured by the base station to apply a muting pattern to the Kth RBs among the PRBs. Here, K may be at least one of 1, 2, 4, 8, or 16. When the terminal is instructed by the base station to have a K value, the index is N. start , N start +K, N start +2*K, N start A muting pattern can be applied to PRBs of +3*K, .... The terminal can additionally be configured with an offset value (M) of the starting PRB to which the muting pattern is to be applied. The offset value can include at least one of 0, 1, ..., or K-1. When the terminal receives K and M values ​​from the base station, the index is N. start +M+K, N start +M+2*K, Nstart The muting pattern can be applied to PRBs of +M+3*K, ...

[0329] The K value can be determined from other configuration information without requiring base station configuration. For example, the K value can be determined based on the bandwidth of the PUSCH or the number of RBs included. Furthermore, the K value can be determined based on the number of RBs included in the UL BWP. Furthermore, the K value can be determined based on the number of RBs included in the UL subband.

[0330] In one embodiment, when a muting RE and a PTRS (phase tracking reference signal) RE overlap for a muting symbol, the terminal may not determine the RE as a muting RE. That is, the PTRS may be transmitted in the RE.

[0331] In embodiments, a terminal may be configured by a base station to use a muting pattern. The configuration of the muting pattern may be included in the RRC signal of the base station. Specifically, the PUSCH configuration information of the RRC signal of the base station may include information about the muting pattern. For example, the PUSCH configuration information may include a comb-2 pattern-based muting pattern, as shown in FIG. 13(a), and information that all REs configure at least one muting pattern, as shown in FIG. 13(b).

[0332] When a terminal is instructed to use a comb-2 pattern-based muting pattern, the terminal can determine that the RE is muted for even-numbered subcarriers (0, 2, 4, 6, 8, 10) within the RB without separate signaling (or information) from the base station.

[0333] When a terminal is instructed to use a comb-2 pattern-based muting pattern, the terminal can determine that the odd-numbered (1, 3, 5, 7, 9, 11) subcarriers within an RB are REs to be muted without separate signaling (or information) from the base station.

[0334] In one embodiment, when a terminal is instructed to use a comb-2 pattern-based muting pattern, the terminal may receive signaling (or information) from the base station. Based on the information, the terminal may determine whether the RE to be muted is an even-numbered (0, 2, 4, 6, 8, 10) or an odd-numbered (1, 3, 5, 7, 9, 11) subcarrier within the RB.

[0335] Example 1. Method for determining an autonomous muting symbol without RRC configuration / DCI instruction

[0336] According to one embodiment of the present disclosure, a terminal can determine a muting symbol without an RRC configuration or DCI instruction regarding the muting symbol position. Here, whether the terminal applies the muting symbol to the PUSCH for transmission can be configured by the base station. The position of the muting symbol can be determined based on other information. Here, the other information can include the DMRS symbol position of the PUSCH, the symbol position to which the UCI is mapped, and / or frequency hopping, and the position of the muting symbol can be determined based on such information.

[0337] Method 1-1-1. Set the muting symbol based on the symbols in the slot.

[0338] The terminal may determine some symbols of a slot as muting symbols. For example, the first symbol of the slot may be determined as a muting symbol. In addition, the muting symbol may be determined based on the DMRS symbol position of PUSCH mapping type A in the slot. If the DMRS symbol position of PUSCH mapping type A is the 3rd OFDM symbol of the slot, the terminal may determine the 4th OFDM symbol as a muting symbol. If the DMRS symbol position of PUSCH mapping type A is the 4th OFDM symbol of the slot, the terminal may determine the 3rd OFDM symbol as a muting symbol. That is, the position of the muting symbol may be set to the symbol immediately before or immediately after the DMRS symbol position. For reference, the DMRS symbol position of PUSCH mapping type A may be determined as the 3rd or 4th symbol of the slot, regardless of the scheduled PUSCH.

[0339] Method 1-1-2. Setting the DMRS symbol location of PUSCH based on the muting symbol

[0340] When a PUSCH is scheduled, the UE can determine the DMRS location based on the number of symbols included in the PUSCH. The UE can determine the PUSCH muting symbol based on the DMRS location. The PUSCH muting symbol based on the DMRS location can be determined using at least one of the following methods.

[0341] In one embodiment, the symbol immediately following the DMRS may be determined as a muting symbol of the PUSCH. That is, the terminal may determine the position of the DMRS on the PUSCH and determine the symbol immediately following the DMRS as a muting symbol of the PUSCH.

[0342] In one embodiment, the symbol immediately preceding the DMRS may be determined as a muting symbol of the PUSCH. That is, the terminal may determine the position of the DMRS on the PUSCH and determine the symbol immediately preceding the DMRS as a muting symbol of the PUSCH.

[0343] DMRS can indicate the first DMRS (referring to the DMRS at the earliest position in time among the DMRSs of PUSCH).

[0344] The DMRS may include either the first DMRS and / or the additional DMRS. That is, the terminal may determine the muting symbol based on the location of the first DMRS and the muting symbol based on the location of the additional DMRS.

[0345] When frequency hopping of PUSCH is enabled, DMRS can indicate the first DMRS of each frequency hop. That is, it can indicate the DMRS that is earliest in time to the first frequency hop.

[0346] The PUSCH may be a PUSCH scheduled with PUSCH mapping type B. Here, the position of the DMRS of the PUSCH may be determined according to the symbol in which the PUSCH is scheduled.

[0347] Method 1-1-3. Setting muting symbols based on UCI mapped symbol locations

[0348] When a UE receives a PUSCH schedule, some REs of the PUSCH can be used to transmit UCI. The UCI can include HARQ-ACK, CSI part 1, and CSI part 2. The UE can determine the DMRS location based on the symbol to which the UCI RE is mapped. The muting symbol of the PUSCH determined based on the UCI symbol location can be determined by at least one of the following methods.

[0349] The terminal may determine the earliest symbol among the symbols that do not include a UCI symbol in the PUSCH as a muting symbol. That is, the terminal may determine the earliest symbol in time among the symbols that are not UCI symbols from the symbol on which the PUSCH is scheduled as a muting symbol. Here, the UCI symbol may include at least one of a symbol including HARQ-ACK, a symbol including CSI part 1, and a symbol including CSI part 2.

[0350] The terminal may determine the earliest symbol among the symbols following the UCI symbols in the PUSCH as a muting symbol. That is, the terminal may determine the earliest symbol in time among the symbols following the UCI symbol among the non-UCI symbols from the symbol for which the PUSCH is scheduled as a muting symbol. Here, the UCI symbol may include at least one of a symbol including HARQ-ACK, a symbol including CSI part 1, and / or a symbol including CSI part 2.

[0351] If PUSCH frequency hopping is enabled for the terminal, UCI can be distributed and mapped across two hops. In this case, a UCI symbol can be determined at each of the two hops, and a muting symbol can be determined at each of the two hops based on the UCI symbol.

[0352] FIG. 14 illustrates application of a muting symbol to a symbol following a UCI symbol according to embodiments of the present disclosure.

[0353] Fig. 14(a) is a diagram in which PUSCH frequency hopping is disabled, and Fig. 14(b) is a diagram in which PUSCH frequency hopping is enabled. In one embodiment, the symbol immediately following the UCI symbol may be determined as a muting symbol. In the case of Fig. 14(a), the UCI may be mapped to the 2nd, 3rd, 4th, and 5th OFDM symbols. Therefore, the muting symbol may be mapped to the 6th OFDM symbol. In the case of Fig. 14(b), the UCI of the first hop may be mapped to the 2nd and 3rd OFDM symbols. Therefore, the muting symbol of the first hop may be mapped to the 4th OFDM symbol. The UCI of the second hop may be mapped to the 9th and 10th OFDM symbols. Therefore, the muting symbol of the second hop may be mapped to the 11th OFDM symbol.

[0354] Method 1-2-1. Determining the muting symbol based on whether frequency hopping is enabled or not

[0355] The terminal can determine the muting symbol depending on whether PUSCH frequency hopping occurs.

[0356] In one embodiment, if frequency hopping of the PUSCH is disabled, the UE may determine a muting symbol. If frequency hopping of the PUSCH is enabled, the UE may not determine a muting symbol. That is, the PUSCH may not have a muting symbol.

[0357] In one embodiment, when PUSCH frequency hopping is disabled, the UE may determine a muting symbol. If PUSCH frequency hopping is enabled, the UE may determine a muting symbol for each of the two hops. In this case, the muting symbol may be determined for each hop according to the method described above.

[0358] In one embodiment, when PUSCH frequency hopping is disabled, the UE may determine a muting symbol. If PUSCH frequency hopping is enabled, the UE may determine a muting symbol for one of the two hops. No muting symbol may be determined for the remaining hops.

[0359] If a muting symbol is determined for only one hop, the location of the muting symbol can be determined as follows.

[0360] FIG. 15 illustrates a muting symbol according to embodiments of the present disclosure.

[0361] In one embodiment, PUSCH is N PUSCH If scheduled to occupy N symbols and intra-slot frequency hopping is indicated, the first hop is floor(N PUSCH / 2) consists of symbols, and the second hop is ceil(N PUSCH / 2) symbols. The terminal can determine the first symbol of the second hop as a muting symbol. That is, the first hop of PUSCH is floor(N PUSCH / 2) consists of symbols, and the second hop is ceil(N PUSCH / 2)-1 symbols. And one symbol after the last symbol of the first hop may be a muting symbol. Referring to FIG. 15, when a PUSCH occupying 14 OFDM symbols is scheduled in a slot, the first hop is 7 OFDM symbols (OFDM symbols 0, 1, 2, 3, 4, 5, 6), the symbol following the last symbol (OFDM symbol 6) of the first hop (OFDM symbol 7) is a muting symbol, and the 6 OFDM symbols thereafter (OFDM symbols 8, 9, 10, 11, 12, 13) may be the second hop. Here, the position of the DMRS of each hop may be determined based on the number of OFDM symbols actually included in each hop. That is, the DMRS position of the second hop is ceil(N PUSCH / 2)-1 symbols. Or, the position of the DMRS of each hop can be determined based on the number of OFDM symbols scheduled for each hop (excluding the muting symbol). That is, the DMRS position of the second hop is ceil(N PUSCH / 2) can be determined based on the symbols.

[0362] FIG. 16a illustrates a muting symbol according to embodiments of the present disclosure.

[0363] In one embodiment, PUSCH is N PUSCH If the slot is scheduled to occupy N symbols and inter-slot frequency hopping is indicated, the first hop is N PUSCH It consists of N symbols, and the second hop is N PUSCH- It can be composed of 1 symbol. The terminal can determine the last symbol of the second hop as a muting symbol. Referring to FIG. 16a, when repeated transmission of PUSCH occupying 14 OFDM symbols in the first slot and the second slot is scheduled, the first hop may be 14 OFDM symbols of the first slot (OFDM symbols 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13), and the second hop may be 13 OFDM symbols of the second slot (OFDM symbols 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). And the last symbol of the second slot (OFDM symbol 13) may be determined as a muting symbol. Here, the position of the DMRS of each hop can be determined based on the number of OFDM symbols actually included in each hop. That is, the DMRS position of the second hop is N PUSCH -Can be determined based on 1 symbol. Alternatively, the position of DMRS of each hop can be determined based on the number of OFDM symbols scheduled for each hop (excluding the muting symbol). That is, the DMRS position of the second hop is N PUSCH It can be determined based on the symbols of the dog.

[0364] In one embodiment, when determining a muting symbol, the terminal may determine a muting symbol from symbols excluding a specific symbol. The symbol to which the muting symbol cannot be applied may be a DMRS symbol, a symbol to which UCI is mapped, or a symbol to which PTRS (phase tracking reference signal) is mapped. The symbol to which UCI is mapped may include a symbol to which HARQ-ACK is mapped, a symbol to which CSI part 1 is mapped, or a symbol to which CSI part 2 is mapped. Alternatively, the symbol to which UCI is mapped may include at least one of a symbol to which HARQ-ACK is mapped, a symbol to which CSI part 1 is mapped, or a symbol to which CSI part 2 is mapped. For example, the symbol to which the muting symbol cannot be applied may include a symbol to which HARQ-ACK is mapped, and may not include a symbol to which CSI part 1 or CSI part 2 is mapped.

[0365] In one embodiment, when determining a muting symbol, if the determined muting symbol overlaps with a symbol to which the muting symbol cannot be applied, the terminal may not apply the muting symbol. That is, the terminal may transmit a PUSCH without muting.

[0366] In one embodiment, when determining a muting symbol, if the determined muting symbol overlaps with the symbol to which UCI is mapped, the terminal may transmit a PUCCH including UCI without transmitting a PUSCH (dropping it). That is, if REs on which UCI is transmitted overlap with REs on a PUSCH due to a muting symbol, the terminal may not mute the UCI REs, but may transmit UCI without transmitting the PUSCH (dropping it), thereby improving the reception performance of the UCI.

[0367] Example 2. Method for determining muting symbols based on RRC settings and DCI

[0368] Method 2-1. Indicating a muting symbol within a time unit interval

[0369] In one embodiment, the terminal may receive the position of the symbol to which the muting symbol is applied (the position of the muting symbol) from the base station via an RRC signal. Here, the position of the muting symbol may be indicated based on a specific time unit. Here, the time unit may include at least one of a slot, a set of slots, and a set of consecutive SBFD symbols. For example, the position of the muting symbol may be indicated based on a slot unit. Here, since a slot may include 14 symbols, the position of the muting symbol may be indicated by a bitmap with a length of 14 bits. Each bit may have a corresponding symbol in the slot. If the bit is '0', muting may not be applied to the corresponding symbol (i.e., it is not a muting symbol). If the bit is '1', muting may be applied to the corresponding symbol (i.e., it is a muting symbol).

[0370] In one embodiment, the terminal can additionally receive a periodicity setting from the base station via an RRC signal. Muting symbols designated for specific time units can be applied for each period. For example, let's say a specific time unit is a slot and a period is 4 slots. The terminal can apply a muting symbol set for one slot out of every 4 slots. The periodicity can be the same as the TDD periodicity. That is, if the TDD periodicity is 5 slots, the periodicity can be 5 slots. This can be applied without any special RRC configuration.

[0371] In one embodiment, a terminal may receive an indicator from a base station via an RRC signal, indicating whether to apply a muting symbol indicated in a specific time unit within a period. For example, let's say a specific time unit is a slot and a period is 4 slots. The terminal may receive a 4-bit bitmap indicating whether to apply a slot-based muting symbol to the 4 slots. Here, the length of the bits included in the bitmap may be equal to the number of specific time units included in the period. Here, each bit may correspond to a specific time unit within the period. That is, each bit may correspond to one of the 4 slots within the period. If the bit is '0', the muting symbol may not be applied to the corresponding slot. If the bit is '1', the muting symbol may be applied to the corresponding slot. Here, the position of the muting symbol may be determined based on information indicated in the specific time unit.

[0372] In one embodiment, if a muting symbol configured by RRC overlaps with a symbol to which a muting symbol cannot be applied, the terminal may not apply the muting symbol. That is, the terminal may transmit a PUSCH without muting.

[0373] In one embodiment, if a muting symbol configured as RRC overlaps with a symbol to which the muting symbol cannot be applied, the terminal may change the position of the muting symbol configured as RRC. For example, if OFDM symbol X is indicated as a muting symbol configured as RRC and OFDM symbol X overlaps with a symbol to which the muting symbol cannot be applied, the terminal may determine OFDM symbol X+1 as a muting symbol. If OFDM symbol X+1 is a muting symbol, the terminal may continue to determine OFDM symbol X+2 as a muting symbol. The above-described process may continue to be performed up to OFDM symbol X+K. Here, the value of K may be a specific value. That is, the terminal may determine whether muting can be applied to K+1 OFDM symbols from OFDM symbol X to OFDM symbol X+K. If muting cannot be applied from OFDM symbol X to OFDM symbol X+K, the terminal may transmit a PUSCH without muting. If muting cannot be applied from OFDM symbol X to OFDM symbol X+K, the terminal may not transmit (drop) PUSCH.

[0374] In one embodiment, a terminal may be configured with a first symbol set and a second symbol set to which muting is to be applied via RRC. The terminal may determine a muting symbol based on the first symbol set. If a muting symbol configured according to the first symbol set overlaps with a symbol to which a muting symbol cannot be applied, the terminal may determine a muting symbol based on the second symbol set. That is, a muting symbol may be determined based on a symbol configured in the second symbol set.

[0375] In one embodiment, the terminal may be configured with a first symbol set and a second symbol set to which muting will be applied via RRC. The terminal may determine a muting symbol based on the first symbol set when frequency hopping is disabled. The terminal may determine a muting symbol based on the second symbol set when frequency hopping is enabled. In other words, the terminal may be configured with a symbol set to which muting will be applied based on whether frequency hopping is enabled or disabled from the base station.

[0376] In one embodiment, the terminal can be configured with a first symbol set and a second symbol set to which muting is to be applied by RRC. When the terminal is scheduled for a PUSCH of PUSCH mapping type A, the muting symbol of the PUSCH can be determined based on the first symbol set. When the terminal is scheduled for a PUSCH of PUSCH mapping type B, the muting symbol of the PUSCH can be determined based on the second symbol set. That is, the terminal can be configured with a symbol set to which muting is to be applied according to each PUSCH mapping type from the base station.

[0377] In one embodiment, the terminal may be configured with a first symbol set and a second symbol set to which muting will be applied via RRC. When the terminal receives a PUSCH schedule that is DFT-s-OFDM, the terminal may determine a muting symbol based on the first symbol set. When the terminal receives a PUSCH schedule that is CP-OFDM, the terminal may determine a muting symbol based on the second symbol set. In other words, the terminal may receive from the base station a symbol set to which muting will be applied according to the waveform of the PUSCH.

[0378] In one embodiment, the terminal may be configured with multiple symbol sets by RRC according to the length of the PUSCH. For example, if the terminal can be scheduled with a PUSCH length of 2 symbols, 4 symbols, 7 symbols, or 14 symbols, the terminal may be configured with a symbol set including information on a muting symbol to be applied when the PUSCH length is 2 symbols, a symbol set including information on a muting symbol to be applied when the PUSCH length is 4 symbols, a symbol set including information on a muting symbol to be applied when the PUSCH length is 7 symbols, or a symbol set including information on a muting symbol to be applied when the PUSCH length is 14 symbols. The terminal may determine a muting symbol based on one of the plurality of symbol sets based on the number of scheduled symbols. If the PUSCH scheduled by the terminal has frequency hopping enabled, one of the plurality of symbol sets may be selected based on the number of symbols included in the first hop, and one of the plurality of symbol sets may be selected based on the number of symbols included in the second hop.

[0379] The above-described symbol set may include information about a muting symbol and information about a muting pattern. That is, the first symbol set may include first information about the position of the muting symbol and second information about the muting pattern. The muting pattern may include at least one of comb-2 (Fig. 13(a)), comb-4, comb-6, and a pattern in which all REs are muted (Fig. 13(b)).

[0380] Method 2-2. Indicate one of the symbol sets set by RRC in DCI.

[0381] In one embodiment, when a terminal receives a DCI scheduling a PUSCH, the DCI may include information about a muting symbol of the PUSCH. The terminal may receive an N-bit long indicator in the DCI to indicate one of a plurality of symbol sets.

[0382] For example, a terminal may be configured with multiple symbol sets from a base station via an RRC signal. For example, a terminal may be configured with four symbol sets from a base station via an RRC signal. The terminal may be instructed to select one of the four symbol sets via DCI. The terminal may determine a muting symbol based on the instructed symbol set.

[0383] For example, a terminal can receive from a base station, via an RRC signal, multiple symbol sets to be used when frequency hopping is disabled and multiple symbol sets to be used when frequency hopping is enabled. The terminal can determine whether frequency hopping is enabled or disabled for a scheduled PUSCH via DCI. If disabled, the terminal can be instructed via DCI which one of the multiple symbol sets to be used when frequency hopping is disabled. If enabled, the terminal can be instructed via DCI which one of the multiple symbol sets to be used when frequency hopping is enabled. Here, the number of multiple symbol sets to be used when frequency hopping is disabled and the number of multiple symbol sets to be used when frequency hopping is enabled may be the same. The indicator of the DCI may be N bits, and N may be equal to ceil(log2(the number of symbol sets)). Alternatively, if the number of multiple symbol sets to be used when frequency hopping is disabled (M1) and the number of multiple symbol sets to be used when frequency hopping is enabled (M2) are different, N may be determined based on the larger number of the two numbers (max{M1, M2}). For example, N could be ceil(log2(max{M1, M2})).

[0384] Method 2-3. Indicating whether to apply muting symbol in DCI

[0385] In one embodiment, a terminal may receive a DCI scheduling a PUSCH from a base station. The terminal may determine whether to apply a muting symbol based on information in the DCI. For example, the DCI may include a 1-bit indicator. The terminal may determine whether to apply a muting symbol based on the 1-bit indicator. If the 1-bit indicator is '0', the terminal may not apply the muting symbol. If the 1-bit indicator is '1', the terminal may apply the muting symbol.

[0386] In one embodiment, whether a muting symbol is applied may be indicated by the RNTI or format of the DCI. For example, for a PUSCH scheduled with DCI format 0_0, a muting symbol may not be applied. However, for a PUSCH scheduled with DCI formats 0_1, 0_2, and 0_3, a muting symbol may be applied.

[0387] For example, for a PUSCH scheduled with DCI format 0_0 received in a common search space, a muting symbol may not be applied. However, for a PUSCH scheduled with DCI format 0_0, DCI format 0_1, 0_2, 0_3 received in a UE-specific search space, a muting symbol may be applied.

[0388] Additionally, for example, for a PUSCH scheduled in a DCI format in which the CRC is scrambled with C-RNTI, CS-RNTI, or MCS-C-RNTI, a muting symbol may be applied. However, for a PUSCH scheduled in a DCI format in which the CRC is scrambled with another RNTI (e.g., TC-RNTI), a muting symbol may not be applied.

[0389] Method 2-4. Indicating a muting symbol within a scheduled PUSCH

[0390] In one embodiment, an index (S) for a muting symbol may be indicated by a higher layer signal based on a reference starting symbol (R). That is, the index of the muting symbol may be determined as R+S.

[0391] The reference starting symbol may include at least one of the first symbol of the PUSCH, the first DMRS symbol of the PUSCH, or the first symbol of the PUSCH to which the UCI is not mapped.

[0392] For Type-A PUSCH repeated transmission, the index for the muting symbol can be individually applied to the PUSCH repetitions repeated in each slot. That is, the first symbol of each PUSCH repetition repeated in each slot, the first DMRS symbol, or the first symbol that is not UCI mapped is regarded as the Reference Starting Symbol, and the index (S) for the muting symbol is applied to the Reference Starting Symbol, so that the UE can determine the index of the muting symbol in each PUSCH repetition.

[0393] For Type-B PUSCH repetitive transmission, the index for the muting symbol can be individually applied to the PUSCH repetitions repeated for each nominal repetition or actual repetition. That is, the first symbol of each nominal PUSCH repetition, the first DMRS symbol, or the first symbol that is not UCI mapped is regarded as the Reference starting symbol, and the index (S) for the muting symbol is applied to the Reference starting symbol, so that the UE can determine the index of the muting symbol within each nominal PUSCH repetition. Alternatively, the first symbol of each actual PUSCH repetition, the first DMRS symbol, or the first symbol that is not UCI mapped is regarded as the Reference starting symbol, and the index (S) for the muting symbol is applied to the Reference starting symbol, so that the UE can determine the index of the muting symbol within each actual PUSCH repetition. In the case of Type-B PUSCH repetition transmission, the terminal does not receive information about the index of the muting symbol from the base station, but can determine the number of OFDM symbols included in the nominal PUSCH repetition or the number of OFDM symbols included in the actual PUSCHS repetition as the index (S) of the muting symbol. That is, the last symbol of the nominal PUSCH repetition or the last symbol of the actual PUSCHS repetition can be a muting symbol.

[0394] In the case of a PUSCH scheduled by the Multi-PUSCH scheduling method with one DCI, an index for a muting symbol can be individually applied to each PUSCH. That is, one of the first symbol of each PUSCH, the first DMRS symbol, or the first symbol that is not mapped to UCI is regarded as a reference starting symbol, and by applying the index (S) for the muting symbol to the reference starting symbol, the UE can determine the index of the muting symbol in each PUSCH. Here, each PUSCH may be a PUSCH scheduled by the Multi-PUSCH scheduling method with one DCI. According to the Multi-PUSCH scheduling method, one DCI received by the UE includes a TDRA (time domain resource assignment) field, and a TDRA row corresponding to a code point of the TDRA field may include multiple staring and length indicator values ​​(SLIVs). In addition, a PUSCH may be transmitted by a symbol corresponding to each SLIV. PUSCHs corresponding to each SLIV symbol may correspond to different transport blocks and HARQ process numbers.

[0395] Method 2-5. TDRA row instruction-based muting symbol instruction method

[0396] In one embodiment, the terminal may configure a muting symbol corresponding to each TDRA row. Specifically, the terminal may receive a TDRA table configuration from the base station. The TDRA table may include one or more TDRA rows. The terminal may be indicated a TDRA row from the TDRA field included in the DCI format that schedules the PUSCH.

[0397] A terminal can receive multiple TDRA tables from a base station through a higher layer signal (e.g., an RRC signal). For example, the terminal can receive a first TDRA table from a higher layer signal PUSCH-ConfigCommon information element (IE) through push-TimeDomainAllocationList from the base station. Additionally, the terminal can receive a second TDRA table from a higher layer signal PUSCH-Config information element through push-TimeDomainAllocationList from the base station. The terminal can determine a TDRA table to be applied to DCI format 0_0 received in a common search space or a UE-specific search space according to [Table 17].

[0398]

[0399] The UE can receive TDRA tables for DCI format 0_1 ​​from a base station through a higher layer signal (e.g., an RRC signal). For example, the UE can receive a TDRA table from the base station through the pusch-TimeDomainAllocationListDCI-0-1 information element in the higher layer signal pusch-Config, and can also receive a TDRA table from the pusch-TimeDomainAllocationListForMultiPUSCH information element in the higher layer signal pusch-Config. The UE can determine a TDRA table to be applied to DCI format 0_1 ​​received in a UE-specific search space according to Table 18.

[0400]

[0401] The UE can receive TDRA tables for DCI format 0_2 from the base station through a higher layer signal (e.g., an RRC signal). For example, the UE can receive TDRA tables from the base station through the pusch-TimeDomainAllocationListDCI-0-2 information element in the higher layer signal pusch-Config. The UE can determine a TDRA table to be applied to DCI format 0_2 received in the UE-specific search space according to Table X3.

[0402]

[0403] Each TDRA row in the TDRA table can contain at least one of the following pieces of information:

[0404] - Information including the starting symbol index of PUSCH and the number of consecutive symbols. The starting symbol index can have one of the values ​​0, 1, ..., 13, and the number of consecutive symbols can have one of the values ​​1, 2, ..., 14. The starting symbol index and the number of consecutive symbols can be jointly coded and expressed as a starting and length indication value (SLIV).

[0405] - Information about the time interval between the slot in which the DCI to be scheduled is received and the slot in which the PUSCH is transmitted. The information can be expressed as the number of slots and can be referred to as the K2 value. That is, if the K2 value is 0, the slot in which the DCI to be scheduled is received and the slot in which the PUSCH is transmitted are the same slot. If the slot in which the DCI to be scheduled is received is slot n, the slot in which the PUSCH is transmitted can be slot K2+n.

[0406] - Information about the PUSCH mapping type. The PUSCH mapping type can be either A or B. If the PUSCH mapping type is A, the first DMRS (or front-loaded DMRS) of the scheduled PUSCH can be the Xth OFDM symbol of the slot. Here, X = one of 3 or 4, which can be determined based on information of the PBCH transmitted by the base station. If the PUSCH mapping type is A, the first DMRS (or front-loaded DMRS) of the scheduled PUSCH can be located in the first symbol of the scheduled PUSCH.

[0407] FIG. 16b is a diagram illustrating a configured TDRA table. Here, the location of the first DMRS (front-loaded DMRS) of PUSCH mapping type A may be set to the third OFDM symbol of the slot. The TDRA table may include 16 TDRA rows. Here, when the subcarrier spacing of the scheduled PUSCH is 15 kHz, 30 kHz, 60 kHz, 120 kHz, 480 kHz, and 960 kHz, respectively, j may be 1, 1, 2, 3, 11, and 21.

[0408] For example, according to the TDRA row with TDRA row index 1 in FIG. 16b, the PUSCH starts from OFDM symbol 0 of the slot and may include 14 OFDM symbols. And, since it is PUSCH mapping type A, the first DMRS (front-loaded DMRS) may be located at OFDM symbol 2 of the slot.

[0409] For example, according to a TDRA row with a TDRA row index of 5 in FIG. 16b, the PUSCH starts at OFDM symbol 4 of the slot and may include 10 OFDM symbols. And, since it is PUSCH mapping type B, the first DMRS (front-loaded DMRS) may be located at the first OFDM symbol of the scheduled PUSCH (i.e., OFDM symbol 4 of the slot).

[0410] According to the disclosure of this embodiment, a terminal can receive muting symbols corresponding to each TDRA row from a base station via a higher layer signal. The muting symbols can be up to two symbols. In the following description, the muting symbols are described as having a maximum of two symbols, but the number of muting symbols can be expanded to a different number.

[0411] FIG. 16c is a diagram illustrating some rows of a TDRA table according to embodiments of the present disclosure.

[0412] Referring to FIG. 16c, a terminal may receive a TDRA table configuration from a base station via a higher layer signal (e.g., an RRC signal). Some or all of the TDRA rows in the TDRA table may include muting symbol configurations. Note that a PUSCH corresponding to a TDRA row for which a muting symbol is not configured may not include a muting symbol.

[0413] The upper layer signal that sets the TDRA table including the muting symbol setting can be any one of pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-1, and pusch-TimeDomainAllocationListForMultiPUSCH. That is, the terminal can set the TDRA row including the muting symbol using the predefined upper layer signal.

[0414] In one embodiment, the terminal may set a first muting symbol index or a second muting symbol index in the TDRA row. Here, both the first muting symbol index and the second muting symbol index may be set, one of the two may be set, or neither may be set. Note that the first muting symbol index and the second muting symbol index may not be the same.

[0415] In one embodiment, the first muting symbol index and the second muting symbol index may be one of 0, 1, 2, ..., 13. And, the index may be interpreted based on the first OFDM symbol of the slot. That is, if the index is 0, it may correspond to the first OFDM symbol of the slot, and if the index is n, it may correspond to the (n+1)th OFDM symbol.

[0416] Referring to FIG. 16c, a TDRA row whose TDRA row index is N1 may be set to (S=0, L=14, m0=0, m1=3), a TDRA row whose TDRA row index is N2 may be set to (S=0, L=14, m0=0, m1=4), and a TDRA row whose TDRA row index is N3 may be set to (S=0, L=14, m0=5). Here, S may be the index of the start symbol of PUSCH, L may be the number of consecutive symbols included in PUSCH, m0 may be the index of the first muting symbol, and m1 may be the index of the second muting symbol.

[0417] In one embodiment, the first muting symbol index may have a first range of values, and the second muting symbol index may have a second range of values. Here, the first range of values ​​and the second range of values ​​may not overlap each other. Here, the first range of values ​​may include some values ​​from 0, 1, ..., 13, and the second range of values ​​may include some values ​​from 0, 1, ..., 13. Here, the first range of values ​​and the second range of values ​​may both include 0, 1, ..., 13.

[0418] More specifically, the range of the first value corresponding to the first muting symbol index may be 0, 1, 2, ..., S-1 (or some of the values), and the range of the second value corresponding to the second muting symbol index may be S, S+1 ..., 13 (or some of the values). That is, the terminal may set one symbol among the first S symbols among the OFDM symbols of the slot as the muting symbol, and may set one symbol among the first 14-S symbols among the OFDM symbols of the slot as the muting symbol. However, the terminal cannot set two symbols among the first S symbols among the OFDM symbols of the slot as muting symbols. The terminal cannot set two symbols among the 14-S symbols after the first S symbols among the OFDM symbols of the slot as muting symbols.

[0419] S can be either 3 or 4. S can be a symbol corresponding to the position of the first DMRS symbol in case of PUSCH mapping type A. The position can be indicated by dmrs-TypeA-Position of PBCH. If pos2 is indicated, the third symbol in the slot can be the position of the first DMRS symbol, and if pos3 is indicated, the fourth symbol in the slot can be the position of the first DMRS symbol. That is, if dmrs-TypeA-Position indicates pos2, S can be 2, and if pos3 is indicated, S can be 3.

[0420] And, the index can be interpreted based on the first OFDM symbol of the slot. That is, if the index is 0, it corresponds to the first OFDM symbol of the slot, and if the index is n, it corresponds to the (n+1)th OFDM symbol.

[0421] In the above example, the first muting symbol index and the second muting symbol index are interpreted based on the first symbol of the slot. That is, if the index is 0, the muting symbol index corresponds to the first OFDM symbol of the slot, and if the index is n, it may correspond to the (n+1)th OFDM symbol.

[0422] In one embodiment, the first muting symbol index and the second muting symbol index may be interpreted based on the first OFDM symbol of the PUSCH. That is, if the index is 0, the muting symbol index may correspond to the first OFDM symbol of the scheduled PUSCH, and if the index is n, it may correspond to the (n+1)-th OFDM symbol of the scheduled PUSCH.

[0423] In one embodiment, the first muting symbol index and the second muting symbol index may be interpreted based on the first DMRS symbol of the PUSCH. That is, if the index is 0, the muting symbol index may correspond to the first DMRS symbol of the scheduled PUSCH, and if the index is n, the muting symbol index may correspond to a symbol n symbols away from the first DMRS symbol of the scheduled PUSCH.

[0424] In one embodiment, the first muting symbol index may be interpreted using the first method, and the second muting symbol index may be interpreted using the second method. For example, the first muting symbol index may be interpreted based on the first OFDM symbol of the slot, and the second muting symbol index may be interpreted based on its correspondence to the first DMRS symbol of the scheduled PUSCH. Each of the multiple muting symbol indices may be interpreted using various methods.

[0425] In one embodiment, the first muting symbol index and the second muting symbol index may be interpreted differently depending on the PUSCH mapping type. For example, if the PUSCH mapping type is A, the first muting symbol index and the second muting symbol index may be interpreted based on the first OFDM symbol of the slot, and if the PUSCH mapping type is B, the first muting symbol index and the second muting symbol index may be interpreted based on the first symbol of the scheduled PUSCH.

[0426] [Table 20] illustrates the RRC structure according to the present embodiment. The RRC configuration for setting the TDRA row may include, in addition to the k2 value (k2), the mapping type of PUSCH (mappingType), and the start symbol and length of PUSCH (startSymbolAndLength), the first muting symbol index (firstMuting) and the second muting symbol index (secondMuting).

[0427]

[0428] In one embodiment, each TDRA row may be configured with a first muting symbol index and a second muting symbol index, respectively. In one embodiment, the terminal may configure the second muting symbol index and the first muting symbol index to be jointly coded. Specifically, the first muting symbol index is m0, the second muting symbol index is m1, and the distance between the two indices is L=m1-m0+1. Here, m0 m1 can be. If m0=m1, there can be one muting symbol in the PUSCH. The terminal can jointly code m0 and m1 based on Equation 2 below.

[0429] [Equation 2]

[0430] If (L-1)≤7, SLIV=14(L-1)+m0

[0431] else, SLIV=14(14-L+1)+(14-1-S)

[0432] where 0 <L≤14-S

[0433] In one embodiment, the base station may set a candidate set (or table) of muting symbols for the terminal and establish a relationship between the candidate set and the TDRA table. For example, the base station may set a candidate set (or table) of muting symbols for the terminal that includes the following information.

[0434] - Index of the muting symbol pattern

[0435] - Index of the first muting symbol (m0)

[0436] - Index of the second muting symbol (m1)

[0437] The terminal may include an index of a muting symbol pattern in each TDRA row. That is, the terminal may obtain an index of a muting symbol pattern from a TDRA row, and determine an index (m0) of a first muting symbol to an index (m1) of a second muting symbol corresponding to the index of the muting symbol pattern.

[0438]

[0439] Table 22 illustrates an RRC structure according to an embodiment of the present disclosure. The RRC configuration for configuring a TDRA row may include a muting symbol pattern index (MutingPatternIndex) in addition to the k2 value (k2), the PUSCH mapping type (mappingType), and the start symbol and / or length (startSymbolAndLength) of the PUSCH. The index of the muting symbol pattern may have one of the values ​​0, 1, ..., maxNrofMutingPatterns-1, and maxNrofMutingPatterns may indicate the maximum number of muting symbol patterns that can be configured. maxNrofMutingPatterns may be 4 or 8.

[0440]

[0441] In one embodiment, if the first muting symbol index or the second muting symbol index determined by the terminal is not included in the scheduled PUSCH, the first muting symbol index or the second muting symbol index may be ignored. That is, the muting symbol may not be applied.

[0442] In one embodiment, if the first muting symbol index or the second muting symbol index determined by the terminal overlaps with the DMRS symbol of the scheduled PUSCH, the first muting symbol index or the second muting symbol index may be ignored. That is, the muting symbol may not be applied.

[0443] In one embodiment, if the first muting symbol index or the second muting symbol index determined by the terminal overlaps with a symbol to which the PTRS of the scheduled PUSCH is mapped, the first muting symbol index or the second muting symbol index may be ignored. That is, the muting symbol may not be applied.

[0444] In one embodiment, a first muting pattern may be applied to a first muting symbol, and a second muting pattern may be applied to a second muting symbol. For example, the first muting pattern may be a pattern in which power is not allocated to even-numbered REs, and the second muting pattern may be a pattern in which power is not allocated to odd-numbered REs. The terminal may receive from the base station a first muting pattern corresponding to the first muting symbol, and a second muting pattern corresponding to the second muting symbol.

[0445] In one embodiment, when a terminal performs Type-A PUSCH repeated transmission, the terminal may repeatedly transmit the PUSCH in multiple slots in the instructed TDRA row. The terminal may determine the positions of the muting symbols based on the first muting symbol index and the second muting symbol index included in the TDRA row for each slot. For example, when the information included in the TDRA row is m0=0 and m1=3, the terminal may determine the first OFDM symbol (the symbol corresponding to m0=0) and the fourth OFDM symbol (the symbol corresponding to m1=3) in all slots in which the PUSCH is scheduled as muting symbols.

[0446] In one embodiment, when a terminal performs Type-A PUSCH repeated transmission, the terminal may repeatedly transmit the PUSCH in multiple slots in an instructed TDRA row. The terminal may determine the positions of muting symbols based on the first muting symbol index and the second muting symbol index included in the TDRA row only in some of the repeated slots. For example, when the information included in the TDRA row is m0=0 and m1=3, the terminal may determine that the first OFDM symbol (the symbol corresponding to m0=0) and the fourth OFDM symbol (the symbol corresponding to m1=3) in the slot that is earliest in time among the slots for which the PUSCH is scheduled are muting symbols. In addition, the terminal may determine that there are no muting symbols in slots other than the slot that is earliest in time among the slots for which the PUSCH is scheduled.

[0447] In one embodiment, when a terminal performs Type-B PUSCH repeated transmission, the terminal may repeatedly transmit the PUSCH at a repetition opportunity determined by an instructed TDRA row. The terminal may determine the positions of muting symbols based on the first muting symbol index and the second muting symbol index included in the TDRA row for each repetition opportunity. For example, if the information included in the TDRA row is m0=0 and m1=3, the terminal may determine the first OFDM symbol (the symbol corresponding to m0=0) and the fourth OFDM symbol (the symbol corresponding to m1=3) in all repetition opportunities in which the PUSCH is scheduled as muting symbols. Here, the first OFDM symbol may be the first OFDM symbol included in the repetition opportunity. Here, the first OFDM symbol may be the first OFDM symbol of the slot. Here, the repetition opportunity may be a nominal repetition determined according to Type-B PUSCH repetition or an actual repetition.

[0448] In one embodiment, when a terminal is scheduled for a PUSCH with multi-PUSCH scheduling, multiple SLIVs may be configured for a TDRA row. For example, a first SLIV and a second SLIV may be configured for a TDRA row. The terminal may receive from the base station a first muting symbol index or a second muting symbol index corresponding to the first SLIV. In addition, the terminal may receive from the base station a first muting symbol index or a second muting symbol index corresponding to the second SLIV. That is, when one TDRA row includes multiple SLIVs, the terminal may receive a first muting symbol index and a second muting symbol index for each SLIV. The first muting symbol index or the second muting symbol index corresponding to the first SLIV may be the same as or different from the first muting symbol index or the second muting symbol index corresponding to the second SLIV.

[0449] In one embodiment, when a terminal is scheduled for a PUSCH using multi-PUSCH scheduling, multiple SLIVs may be configured in a TDRA row. For example, a first SLIV and a second SLIV may be configured in a TDRA row. The terminal may receive from the base station a first muting symbol index or a second muting symbol index that is to be applied commonly to all SLIVs. That is, the first muting symbol index or the second muting symbol index may be applied equally to all SLIVs.

[0450] In one embodiment, a TDRA row may be configured with one set of (a first muting symbol index, a second muting symbol index). Furthermore, in one embodiment, a terminal may be configured with multiple sets of (a first muting symbol index, a second muting symbol index) in a TDRA row. Here, the first set may be used in a first condition, and the second set may be used in a second condition. The first condition may be when UCI is not multiplexed on PUSCH, and the second condition may be when UCI is multiplexed on PUSCH.

[0451] Example 3. Method for determining whether to apply a muting symbol

[0452] In one embodiment, a terminal may apply a muting symbol under specific conditions. Embodiments of the present disclosure illustrate specific conditions under which muting symbols are applied. When transmitting a PUSCH, the terminal may determine whether a specific condition is satisfied. If the specific condition is satisfied, the terminal may determine a muting symbol within the PUSCH. If the specific condition is not satisfied, the terminal may not apply a muting symbol within the PUSCH.

[0453] Method 3-1. Determining whether to apply a muting symbol based on the bandwidth of the scheduled PUSCH or the number of RBs.

[0454] In one embodiment, the UE may determine whether to apply a muting symbol based on the bandwidth for which the PUSCH is scheduled (i.e., the length from the lowest RB to the highest RB in the frequency domain among the RBs occupied by the PUSCH) or the number of scheduled RBs. For example, if the bandwidth for which the PUSCH is scheduled or the number of RBs is less than or equal to a predetermined value, the UE may not apply a muting symbol to the PUSCH. If the bandwidth for which the PUSCH is scheduled or the number of RBs is greater than a predetermined value, the UE may apply a muting symbol to the PUSCH. In another example, for example, if the bandwidth for which the PUSCH is scheduled or the number of RBs is less than or equal to a predetermined value, the UE may apply a muting symbol to the PUSCH. If the bandwidth for which the PUSCH is scheduled or the number of RBs is greater than a predetermined value, the UE may not apply a muting symbol to the PUSCH.

[0455] Here, the predetermined value may be a value set by the base station through an RRC signal. Alternatively, the predetermined value may be a specific number of RBs (e.g., 24 RBs). Alternatively, the predetermined value may be a value determined based on the number of RBs included in the UL subband. For example, if the number of RBs included in the UL subband is N RBs, the predetermined value may be N / 2 RBs, which is half of the N RBs. If N / 2 is not an integer, floor(N / 2), ceil(N / 2), or a rounded value of N / 2 may be used.

[0456] Method 3-2. Determining whether to apply a muting symbol based on the number of OFDM symbols of the scheduled PUSCH.

[0457] In one embodiment, the terminal may determine whether to apply a muting symbol based on the number of OFDM symbols of the scheduled PUSCH. For example, if the number of OFDM symbols for which the PUSCH is scheduled is less than or equal to a predetermined value, the terminal may not apply a muting symbol to the PUSCH. If the number of OFDM symbols for which the PUSCH is scheduled is greater than a predetermined value, the terminal may apply a muting symbol to the PUSCH. In another example, for example, if the number of OFDM symbols for which the PUSCH is scheduled is less than or equal to a predetermined value, the terminal may apply a muting symbol to the PUSCH. If the number of OFDM symbols for which the PUSCH is scheduled is greater than a predetermined value, the terminal may not apply a muting symbol to the PUSCH.

[0458] Here, the predetermined value may be a value set via an RRC signal from the base station. Alternatively, the predetermined value may be a specific value (e.g., 2 symbols).

[0459] Method 3-3. Determining whether to apply a muting symbol based on the OFDM symbol position of the scheduled PUSCH.

[0460] In one embodiment, the UE may determine whether to apply a muting symbol based on the position of the OFDM symbol of the scheduled PUSCH. If the PUSCH scheduled by the UE is included in a non-SBFD symbol (a symbol for which no DL or UL subband is configured), the UE may not apply a muting symbol to the PUSCH. If the PUSCH scheduled by the UE is included in an SBFD symbol (a symbol for which a DL or UL subband is configured), the UE may apply a muting symbol to the PUSCH.

[0461] A terminal can determine whether to apply a muting symbol based on the position of the OFDM symbol of the scheduled PUSCH. If the PUSCH scheduled by the terminal occupies a specific symbol of the slot, the terminal can apply a muting symbol. If the PUSCH scheduled by the terminal does not occupy a specific symbol of the slot, the terminal can not apply a muting symbol. Here, the specific symbol may include the last symbol of the slot. If the PUSCH scheduled by the terminal occupies the last symbol of the slot, the terminal can transmit the PUSCH by applying a muting symbol. If the PUSCH scheduled by the terminal does not occupy the last symbol of the slot, the terminal can transmit the PUSCH without applying a muting symbol.

[0462] Here, a specific symbol may be set via an RRC signal from the base station. For example, the specific symbol may include at least one of the last symbol of the slot, the first symbol of the slot, and the symbol immediately preceding or immediately following the first DMRS position of a PUSCH of PUSCH mapping type A.

[0463] Method 3-4. Decide whether to apply a muting symbol based on the UL waveform.

[0464] In one embodiment, the terminal may apply a muting symbol when scheduled with CP-OFDM. The terminal may not apply a muting symbol when scheduled with DFT-S-OFDM. That is, when transmitting a PUSCH scheduled with DFT-S-OFDM, the terminal may ignore the configured muting symbol or may not determine the muting symbol, and the PUSCH may be transmitted without a muting symbol.

[0465] When scheduled with CP-OFDM, the terminal may not apply a muting symbol. When scheduled with DFT-S-OFDM, the terminal may apply a muting symbol. That is, when transmitting a PUSCH scheduled with CP-OFDM, the terminal may ignore the configured muting symbol or may not determine the muting symbol, and the PUSCH may be transmitted without a muting symbol.

[0466] Here, the terminal can be configured by the base station to which waveform the muting symbol is to be applied. For example, depending on the configuration of the base station, the terminal can apply the muting symbol to a PUSCH scheduled with CP-OFDM, to a PUSCH scheduled with DFT-s-OFDM, or to both a PUSCH scheduled with CP-OFDM and a PUSCH scheduled with DFT-s-OFDM.

[0467] The UE can transmit the UE capability regarding whether or not a muting symbol is applicable to each waveform to the base station. For example, the UE can report as a UE capability that a muting symbol is applicable to a PUSCH that is a CP-OFDM waveform, and can report as a UE capability that a muting symbol is applicable to a PUSCH that is a DFT-s-OFDM waveform. The UE can report as a UE capability that a muting symbol is not applicable to a PUSCH that is a CP-OFDM waveform, and can report as a UE capability that a muting symbol is applicable to a PUSCH that is a DFT-s-OFDM waveform. The UE can report as a UE capability that a muting symbol is applicable to a PUSCH that is a CP-OFDM waveform and a PUSCH that is a DFT-s-OFDM waveform. The UE can apply a muting symbol to a PUSCH that is a waveform that can support a muting symbol, and not apply a muting symbol to a PUSCH that is a waveform that does not support a muting symbol.

[0468] In one embodiment, the terminal may be configured with a maximum number of muting symbols for each waveform. For example, the terminal may report to the base station that the PUSCH with CP-OFDM waveform can be applied with up to A muting symbols as a terminal capability, and that the PUSCH with DFT-s-OFDM waveform can be applied with up to B muting symbols as a terminal capability. Here, A and B may be either 1 or 2. For example, A=2 and B=1. In this case, the terminal may apply at most 1 muting symbol to the PUSCH with the DFT-s-OFDM waveform. If the terminal is configured or instructed to apply two muting symbols, the terminal cannot apply the two muting symbols to the PUSCH with the DFT-s-OFDM waveform. In this case, the operation of the terminal may be as follows.

[0469] A terminal may not transmit a PUSCH if a number of muting symbols exceeding the terminal's capability is indicated. In other words, if a number of muting symbols exceeding the terminal's capability is indicated, the terminal may determine that the PUSCH scheduling is invalid.

[0470] When a number of muting symbols exceeding the capability of the terminal is indicated, the terminal may transmit the PUSCH by applying the maximum number of muting symbols supported by the terminal to the PUSCH. For example, if the terminal can apply at most one muting symbol to the PUSCH, one of the indicated muting symbols may be applied to the PUSCH. Here, the applied muting symbol may be the muting symbol that is earliest in time (located in front of the PUSCH) among the indicated muting symbols. Alternatively, the applied muting symbol may be the muting symbol that is latest in time (located at the back of the PUSCH) among the indicated muting symbols.

[0471] In one embodiment, if a number of muting symbols exceeding the capability of the terminal is indicated, the terminal may transmit a PUSCH without applying muting. That is, if a number of muting symbols exceeding the capability of the terminal is indicated, the terminal may determine that the muting symbol indication is invalid and may not apply the indicated muting symbols to the PUSCH.

[0472] Method 3-5. Determining whether to apply a muting symbol based on the presence or absence of additional DMRS in PUSCH.

[0473] In one embodiment, a terminal may apply a muting symbol to a scheduled PUSCH based on the presence or absence of additional DMRS. At this time, at least one of the following combinations may be selected.

[0474] Combination #1

[0475] - How to not apply muting symbols when additional DMRS exists

[0476] - How to apply muting symbol when additional DMRS does not exist

[0477] Combination #2

[0478] - How to not apply muting symbols when additional DMRS exists and the additional DMRS is a comb-2 CDM pattern.

[0479] - How to apply muting symbols when additional DMRS does not exist or, even if it does exist, it is not a comb-2 CDM pattern.

[0480] Combination #3

[0481] - How to not apply muting symbols when additional DMRS exists and the additional DMRS is a comb-2 CDM pattern.

[0482] - If additional DMRS exists and it is not a comb-2 CDM pattern, how to change it to a comb-2 CDM pattern.

[0483] - If additional DMRS does not exist, how to add additional DMRS, which is a muting symbol or comb-2 CDM pattern.

[0484] Method 3-6. A method that does not apply muting symbols based on the information contained in PUSCH.

[0485] In one embodiment, the terminal may determine whether a PUSCH is a muting symbol based on what information it contains. The information may be a UL SCH, which is a logical channel containing general data, or UCI, which is physical layer control information.

[0486] For example, the terminal may not apply a muting symbol if the PUSCH does not include the UL SCH and only includes the UCI. That is, the muting symbol may be applied only when the PUSCH includes at least the UL SCH. In one embodiment, the terminal may apply a muting symbol if the PUSCH does not include the UCI and only includes the UL SCH. That is, the terminal may not apply a muting symbol if the PUSCH includes the UCI.

[0487] In one embodiment, the terminal may apply a muting symbol when the PUSCH includes UL SCH and UCI.

[0488] Method 3-7. Application of muting symbols based on PUSCH MCS.

[0489] When a UE is scheduled for a PUSCH, it can be instructed on the MCS (modulation and coding scheme) value of the PUSCH. For example, if the PUSCH is scheduled with a DCI, the UE can obtain the MCS value through the 5-bit MCS field of the DCI. For example, if the PUSCH is activated by a higher layer signal, the higher layer signal may include the MCS value.

[0490] The MCS value may include the corresponding modulation order and code rate. The modulation order is -Can include at least one of BPSK, QPSK, 16QAM, 64QAM, 256QAM, and 1024QAM.

[0491] The UE may determine whether to apply a muting symbol to the PUSCH based on the MCS value of the PUSCH. For example, if the MCS value of the PUSCH is less than or equal to a specific value (or threshold), the UE may apply a muting symbol to the PUSCH. In one embodiment, if the MCS value of the PUSCH is greater than the specific value, the UE may not apply a muting symbol to the PUSCH. In one embodiment, if the MCS value of the PUSCH is less than or equal to the specific value, the UE may not apply a muting symbol to the PUSCH. In one embodiment, if the MCS value of the PUSCH is greater than the specific value, the UE may apply a muting symbol to the PUSCH. In this case, the specific value (or threshold) may be a value set by the base station.

[0492] The terminal may determine whether to apply a muting symbol to the PUSCH based on the modulation order corresponding to the MCS value of the PUSCH. For example, if the modulation order corresponding to the MCS value of the PUSCH is less than or equal to a specific value (or threshold), the terminal may apply a muting symbol to the PUSCH. In one embodiment, if the modulation order corresponding to the MCS value of the PUSCH is greater than the specific value, the terminal may not apply a muting symbol to the PUSCH. In one embodiment, if the modulation order corresponding to the MCS value of the PUSCH is less than or equal to the specific value, the terminal may not apply a muting symbol to the PUSCH. In one embodiment, if the modulation order corresponding to the MCS value of the PUSCH is greater than the specific value, the terminal may apply a muting symbol to the PUSCH. In this case, the specific value (or threshold) may be a value set by the base station.

[0493] Method 3-8. Muting symbol application method based on the transmission block length of PUSCH.

[0494] The terminal can determine whether to apply a muting symbol based on the length of a transport block (TB) included in the PUSCH. Here, the length of the transport block can be calculated assuming that a muting symbol is not applied to the PUSCH. For example, if the transport block length of the PUSCH is less than or equal to a specific value (or threshold), the terminal can apply a muting symbol to the PUSCH. In one embodiment, if the transport block length of the PUSCH is greater than a certain value, the terminal may not apply a muting symbol to the PUSCH. In one embodiment, if the transport block length of the PUSCH is less than or equal to a specific value, the terminal may not apply a muting symbol to the PUSCH. In one embodiment, if the transport block length of the PUSCH is greater than a specific value, the terminal can apply a muting symbol to the PUSCH. In this case, the specific value (or threshold) may be a value set by the base station.

[0495] Method 3-9. Determine whether to apply a muting symbol based on the PUSCH mapping type.

[0496] In one embodiment, when a PUSCH is scheduled with PUSCH mapping type A, the UE may apply a muting symbol to the PUSCH. When a PUSCH is scheduled with PUSCH mapping type B, the UE may not apply a muting symbol to the PUSCH. That is, when a PUSCH is scheduled with PUSCH mapping type B, the UE may ignore the configured muting symbol or may not determine the muting symbol, and the PUSCH may be transmitted without a muting symbol.

[0497] When a PUSCH is scheduled with PUSCH mapping type A, the terminal may not apply a muting symbol to the PUSCH. When a PUSCH is scheduled with PUSCH mapping type B, the terminal may apply a muting symbol to the PUSCH. That is, when transmitting a PUSCH scheduled with PUSCH mapping type B, the terminal may ignore the configured muting symbol or may not determine the muting symbol, and the PUSCH may be transmitted without a muting symbol.

[0498] Here, the terminal can be configured by the base station to which waveform the muting symbol is to be applied. For example, depending on the configuration of the base station, the terminal can apply the muting symbol to a PUSCH scheduled with PUSCH mapping type A, to a PUSCH scheduled with PUSCH mapping type B, or to both a PUSCH scheduled with PUSCH mapping type A and a PUSCH scheduled with PUSCH mapping type B.

[0499] Example 4. Method of applying muting according to UCI

[0500] Method 4-1. Determining PUSCH to Multiplex UCI

[0501] In one embodiment, if a UCI RE of a PUSCH overlaps with a muting symbol, UCI multiplexing may be performed on a PUSCH other than the PUSCH. Specifically, a UE may transmit UCI through a PUCCH. If the PUCCH overlaps with the PUSCH, the UE may multiplex UCI onto the PUSCH. Here, there may be multiple PUSCHs that overlap with the PUCCH. The UE may select one of the multiple PUSCHs to multiplex UCI. When selecting a PUSCH, the UE may determine whether the selected UCI RE overlaps with the muting symbol. If the UCI RE overlaps with the muting symbol, the UE may not be able to transmit the UCI RE. Therefore, the UE may not be able to transmit UCI with high reliability. Therefore, the UE may exclude the PUSCH where the UCI RE and the muting symbol overlap from the UCI multiplexing target. That is, the terminal can multiplex and transmit UCI through another PUSCH.

[0502] In one embodiment, if the UCI RE of the PUSCH overlaps with a muting symbol, the terminal may not apply the muting symbol. That is, the PUSCH may be transmitted without a muting symbol.

[0503] In one embodiment, when the UCI RE of the PUSCH overlaps with a muting symbol, the terminal may not transmit the PUSCH (drop) and transmit the UCI through the PUCCH.

[0504] In one embodiment, UCI may be transmitted multiplexed on symbols other than the muting symbol.

[0505] Here, the case where the UCI RE overlaps with the muting symbol may include at least one of the following. For example, if an OFDM symbol including the UCI RE overlaps with a muting symbol, it may be determined that the UCI RE overlaps with the muting symbol. Here, the terminal may determine whether there is overlap on a symbol-by-symbol basis regardless of the muting pattern (Fig. 13(a) to Fig. 13(b)). In one embodiment, if the UCI RE overlaps with a muting RE (muting REs in Fig. 13(a)), it may be determined that the UCI RE overlaps with the muting symbol. That is, whether there is overlap on an RE-by-RE basis may be determined according to the muting pattern. In one embodiment, when determining the number of REs occupied by the UCI in the PUSCH, the terminal may consider the muting symbol. The following equation is an equation for determining the number of REs for transmitting HARQ-ACK. In the equation below: represents the number of symbols scheduled on PUSCH. And Indicates the number of REs that can transmit data in symbol l.

[0506] For example, in the DMRS symbol And, in symbols other than DMRS symbols, Here represents the number of REs allocated to PT-RS in symbol l.

[0507] According to the present disclosure, a terminal may not transmit data to all or some REs in a muting symbol of a PUSCH. Therefore, in a muting symbol (muting all REs in the muting symbol (Fig. 13(b))) or (muting half of the REs in the muting symbol (Fig. 13(a))) or It could be. Here may be the number of REs muted in symbol l. In one embodiment, in muting symbol l, That is, regardless of the muting pattern (Fig. 13(a) to Fig. 13(b)), It could be

[0508]

[0509] In one embodiment, when determining the transmit power of a PUSCH, a muting symbol may be considered.

[0510] When determining the transmission power of a PUSCH, the terminal may consider a muting symbol. Equation 4 is the equation for determining the transmission power of a PUSCH.

[0511] Here, (b, f, c, i indices are omitted) represents the bandwidth of the scheduled PUSCH in terms of the number of RBs. For convenience, if it is considered as the number of RBs of the PUSCH, there may not be an RE that is muted in all RBs of the PUSCH.

[0512] According to the present disclosure, a terminal can apply muting to some REs among RBs. In this case, the terminal determines the transmission power of the PUSCH. can be determined as follows. For example, It could be. Here, may be the number of data REs excluding the number of REs muted in the PUSCH. For example, if the terminal mutes half of the REs in the muting symbol, can represent half of the number of RBs of PUSCH.

[0513]

[0514] Table 23 is It shows how to determine. When the terminal calculates BPRE, N RE can indicate the number of REs that can transmit data in PUSCH. That is, (i index is omitted) can be, is the number of symbols occupied by PUSCH, can represent the number of data REs excluding subcarriers and PT-RS REs that are DMRSs in symbol j.

[0515] According to the present disclosure, a terminal can mute some REs among RBs. In this case, the transmission power of the PUSCH of the terminal is determined. can be determined as follows: can represent the number of data REs excluding subcarriers that are DMRSs and PT-RS REs and muted REs in symbol j.

[0516]

[0517] The UE can determine the EPRE (Energy per RE) from the muting symbol of the PUSCH. If the UE uses the comb-2 pattern (Fig. 13(a)) in the muting symbol, the UE determines that the EPRE of the RE that is not muted in the muting symbol is P=10*log higher than the reference EPRE. 10 (2) = It can be 3dB higher.

[0518] The UE can determine the EPRE (Energy per RE) from the muting symbol of the PUSCH. If the UE uses a comb-4 pattern in the muting symbol, the EPRE of the RE that is not muted in the muting symbol is P=10*log higher than the reference EPRE. 10 (4) = 6dB higher.

[0519] The UE can determine the EPRE (Energy per RE) from the muting symbol of the PUSCH. If the UE uses the comb-6 pattern in the muting symbol, the EPRE of the RE that is not muted in the muting symbol is P=10*log higher than the reference EPRE. 10 (6) = 7.78dB can be higher.

[0520] The reference EPRE here may be an EPRE in a symbol that is not a muting symbol (a symbol that is not a DMRS symbol).

[0521] The terminal can determine the EPRE (Energy per RE) from the muting symbol of the PUSCH. If the terminal determines the number of REs (N) that are not muted in the muting symbol, unmuted ) and the number of REs being muted (N muted ) can be calculated. Here, N unmuted + N muted is the number of REs scheduled in one symbol of PUSCH. The terminal determines that the EPRE of REs that are not muted in a muting symbol is P=10*log less than the reference EPRE. 10 ((N unmuted +N muted ) / N unmuted ) can be dB higher.

[0522] The terminal may apply one of the first EPRE and the second EPRE to an RE that is not muted in a muting symbol, depending on the configuration of the base station. Here, the first EPRE may be an EPRE identical to the reference EPRE, and the second EPRE may be an EPRE that is P dB higher than the reference EPRE. P may be determined by the method described above.

[0523] A terminal can report EPRE options supported by a terminal capability report to a base station. Here, a first EPRE option includes an EPRE of an RE that is not muted in a muting symbol that is the same as a reference EPRE, and a second EPRE option may include an EPRE of an RE that is not muted in a muting symbol that is P dB higher than the reference EPRE. When the terminal reports the first EPRE option to the base station, the EPRE of an RE that is not muted in a muting symbol may transmit a PUSCH that is the same as the reference EPRE. When the terminal reports the second EPRE option to the base station, the EPRE of an RE that is not muted in a muting symbol may transmit a PUSCH that is P dB higher than the reference EPRE. When the terminal reports the first EPRE option and the second EPRE option to the base station, the terminal may receive one of the two options from the base station.

[0524] Example 5. UCI mapping method according to muting symbol determination

[0525] In one embodiment, the UE may determine a muting symbol on the PUSCH. UCI may then be mapped to the PUSCH. The UE may determine that all REs included in the muting symbol are REs to which UCI cannot be mapped. Specifically, the UE may map symbols scheduled for the PUSCH to l=0, 1, ... -1 can be determined. Here, the symbol with l=0 represents the first OFDM symbol for which PUSCH is scheduled. represents the number of all OFDM symbols included in the PUSCH. The terminal selects a set of REs ( ) that can transmit UCI in OFDM symbol l. ) can be generated. If the OFDM symbol is a muting symbol, the terminal can be judged as an empty set.

[0526] The terminal is a set of REs capable of UL-SCH transmission in OFDM symbol l. ) can be generated. When the terminal applies a muting symbol with a comb-2 pattern (Fig. 13(a)), if the OFDM symbol l is a muting symbol, the terminal may contain REs that are not muted. If the terminal applies a muting symbol in a pattern in which all REs are muted (Fig. 13(b)), if the OFDM symbol l is a muting symbol, the terminal may be an empty set.

[0527] Example 6. Method for determining transmission block length according to muting symbol

[0528] In one embodiment, the terminal can calculate the transport block length of the PUSCH based on the muting symbol in the PUSCH. Specifically, the terminal can calculate the transport block length of the PUSCH through the following process.

[0529] The terminal has the number of REs (N) in the slot RE ) can be judged.

[0530] The terminal determines the number of REs (in one PRB of PUSCH) based on [Mathematical Formula 5] below. ) can be judged.

[0531]

[0532] Here, Indicates the number of subcarriers included in one PRB.

[0533] Indicates the number of OFDM symbols scheduled on PUSCH.

[0534] The overhead of data-less DMRS CDM (code division multiplexing) groups can be considered as the number of DMRS REs per PRB.

[0535] may represent the amount of overhead set by the base station as a higher layer signal.

[0536] can represent the number of muting REs per PRB. If multiple symbols are muting symbols, It could be. Here represents the number of muting symbols in PUSCH, can represent the number of muting REs per symbol. When using comb-2 (Fig. 13(a)) as the muting pattern, It can be, and if you use a pattern where all REs are muted with a muting pattern (Figure 13(b)), may be. In one embodiment, regardless of the muting pattern. It could be.

[0537] In one embodiment, the terminal determines the number of all REs included in the PUSCH based on [Equation 6] or [Equation 7]. ) can be judged.

[0538] For TB processing over multiple slots (TBoMS),

[0539]

[0540] In other cases,

[0541]

[0542] Here, Indicates the number of PRBs scheduled on PUSCH.

[0543] represents the number of slots.

[0544] The terminal is The length of the transmission block can be determined based on .

[0545] Example 7. Determining whether to add muting symbols and DMRS symbols based on the terminal's capabilities.

[0546] In one embodiment, a terminal can report to the base station the capabilities it supports through a capability report. Through the capability report, the terminal can report whether it supports phase continuity and power consistency between the symbols preceding and following the PUSCH muting symbol. Based on the report, the terminal can decide whether to add DMRS to the symbols following the muting symbol.

[0547] If a terminal reports support for phase continuity and power consistency as its capabilities, the terminal may only add muting symbols to the PUSCH. In this case, the terminal may not add additional DMRS symbols.

[0548] If the terminal does not report support for phase continuity and power consistency as a terminal capability (or reports non-support), the terminal may add a muting symbol to the PUSCH and may add additional DMRS symbols to the symbols preceding or following the muting symbol.

[0549] - For example, if there is a DMRS symbol in the symbols preceding the muting symbol, the terminal may not add an additional DMRS symbol. If there is no DMRS symbol in the symbols preceding the muting symbol, the terminal may add a DMRS symbol.

[0550] - For example, if there is a DMRS symbol in the symbols following the muting symbol, the terminal may not add an additional DMRS symbol. If there is no DMRS symbol in the symbols following the muting symbol, the terminal may add a DMRS symbol.

[0551] In one embodiment, a terminal may indicate to a base station, through a terminal capability report, the maximum number of muting symbols for a single PUSCH. For example, the terminal may report to the base station that a single PUSCH can include N muting symbols. The base station may configure or indicate muting symbols for the PUSCH based on the terminal report.

[0552] In one embodiment, a terminal may indicate to a base station, through a terminal capability report, the maximum number of muting symbols per time unit (e.g., a slot, a set of slots, etc.). For example, the terminal may report to the base station that a single time unit can include N muting symbols. The base station may configure or indicate muting symbols on the PUSCH based on the terminal report.

[0553] Example 8. Method for changing the location of the first DMRS of PDSCH or PUSCH

[0554] In one embodiment, the terminal may receive the positions of DMRS symbols of PDSCH mapping type A and PUSCH mapping type A from the base station as pos2 to pos3. If pos2 is set, the positions of the first DMRS of the PDSCH of PDSCH mapping type A and the first DMRS of the PUSCH of PUSCH mapping type A may be the third symbol of the slot. If pos3 is set, the positions of the first DMRS of the PDSCH of PDSCH mapping type A and the first DMRS of the PUSCH of PUSCH mapping type A may be the fourth symbol of the slot. Here, pos2 to pos3 may be indicated in the MIB and may be applied to the PDSCH and the PUSCH simultaneously. That is, the positions of the first DMRS of the PDSCH and the PUSCH may be the same.

[0555] In one embodiment, the terminal may be instructed by the base station via an RRC signal as the DMRS position of PDSCH mapping type A, pos2 or pos3. In addition, the terminal may be instructed by the base station via an RRC signal as the first DMRS position of PUSCH mapping type A, pos2 or pos3. Here, the RRC signal may individually set the first DMRS position of PDSCH mapping type A and the first DMRS position of PUSCH mapping type A. In one embodiment, when the terminal is instructed by the MIB as pos2, the first DMRS position of PDSCH mapping type A and the first DMRS position of PUSCH mapping type A may be the third symbol of the slot.

[0556] In the following description, the terminal may be instructed to receive pos2 from the MIB. This is an example; the same may be applied when pos3 is instructed from the MIB.

[0557] In one embodiment, when the terminal receives pos3 as the first DMRS position of PDSCH mapping type A from the RRC signal, the first DMRS position of PDSCH mapping type A may be the 4th symbol of the slot. That is, pos3 set as the first DMRS position of PDSCH mapping type A from the RRC signal may override information indicated in the MIB (pos2 in the above example). When the terminal does not receive pos3 as the first DMRS position of PDSCH mapping type A from the RRC signal, the terminal may determine the first DMRS position of PDSCH mapping type A based on information indicated in the MIB (pos2 in the above example). In one embodiment, the RRC signal may be applied only to the first DMRS position of PDSCH mapping type A, and the first DMRS position of PUSCH mapping type A may be determined based on information indicated in the MIB (pos2 in the above example).

[0558] In one embodiment, when the terminal receives pos3 as the first DMRS position of PUSCH mapping type A from the RRC signal, the first DMRS position of PUSCH mapping type A may be the 4th symbol of the slot. That is, pos3 set as the first DMRS position of PUSCH mapping type A from the RRC signal may override information indicated in the MIB (pos2 in the example above). When the terminal does not receive pos3 as the DMRS position of PUSCH mapping type A from the RRC signal, the terminal may determine the DMRS position of PUSCH mapping type A based on the information indicated in the MIB (pos2 in the example above). In one embodiment, the RRC signal may be applied only to the first DMRS position of PUSCH mapping type A, and the first DMRS position of PDSCH mapping type A may be determined based on information indicated in the MIB (pos2 in the example above).

[0559] The first DMRS position set by RRC can be applied only to a specific PDSCH and / or PUSCH. For example, the specific PDSCH and / or PUSCH can be a PDSCH and / or PUSCH scheduled in an SBFD symbol (a symbol for which a DL subband or an UL subband is configured). That is, the first DMRS position of a PDSCH and / or PUSCH scheduled in a non-SBFD symbol (a symbol for which a subband is not configured) can be determined based on the information indicated in the MIB (pos2 in the example above). For example, the specific PDSCH and / or PUSCH can be a PDSCH and / or PUSCH scheduled in DCI format 1_1, 1_2, 1_3, 0_1, 0_2, 0_3. That is, the PDSCH scheduled with DCI format 1_0 and / or the PUSCH scheduled with DCI format 0_0 can have the first DMRS position determined based on the information indicated in the MIB (pos2 in the example above). For example, a specific PDSCH and / or PUSCH can be applied only to a PDSCH and / or PUSCH whose CRC is scrambled with a specific RNTI. For example, a PDSCH and / or PUSCH scrambled with a C-RNTI, a CS-RNTI, or an MCS-C-RNTI can be a specific PDSCH and / or PUSCH. For PDSCH and / or PUSCH scrambled with RNTI other than C-RNTI, CS-RNTI, and MCS-C-RNTI (e.g., SI-RNTI, P-RNTI, TC-RNTI, RA-RNTI, etc.), the first DMRS position can be determined based on information indicated in the MIB (pos2 in the example above).

[0560] FIG. 17 illustrates a first DMRS location according to embodiments of the present disclosure.

[0561] Figure 17(a) is a diagram in which "pos2" indicated in the MIB is applied simultaneously to PDSCH and PUSCH. Therefore, the first DMRS of the PDSCH and the DMRS of the PUSCH may overlap in the third OFDM symbol of the slot.

[0562] FIG. 17(b) is a diagram in which, according to embodiments of the present disclosure, the position of the first DMRS symbol of the PDSCH is determined according to "pos2" indicated in the MIB, and the position of the first DMRS symbol of the PUSCH is determined according to "pos3" set in the RRC signal. Accordingly, the first DMRS of the PDSCH may be the third OFDM symbol of the slot, and the first DMRS of the PUSCH may be the fourth OFDM symbol of the slot.

[0563] FIG. 18 illustrates the structure of a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.

[0564] Referring to FIG. 18, a terminal according to one embodiment may include a transceiver (1810), a memory (1820), and a processor (1830). The transceiver (1810), the memory (1820), and the processor (1830) of the UE may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than those described above. In addition, the processor (1830), the transceiver (1810), and the memory (1820) may be implemented as a single chip. In addition, the processor (1830) may include at least one processor.

[0565] The transceiver (1810) collectively refers to the UE receiver and the UE transmitter, and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station or network entity may include control information and data. The transceiver (1810) may include an RF transmitter for upconverting and amplifying the frequency of a transmission signal, and an RF receiver for low-noise amplification and downconversion of the frequency of a reception signal. However, this is merely an example of the transceiver (1810), and the components of the transceiver (1810) are not limited to the RF transmitter and RF receiver.

[0566] In addition, the transceiver (1810) can receive a signal through a wireless channel and output it to the processor (1830), and transmit the signal output from the processor (1830) through the wireless channel. The memory (1820) can store programs and data necessary for the operation of the UE. In addition, the memory (1820) can store control information or data included in a signal acquired by the UE. The memory (1820) can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0567] The processor (1830) can control a series of processes to enable the terminal to operate. For example, the transceiver (1810) can receive a data signal including a control signal transmitted by a base station or network entity, and the processor (1830) can determine the result of receiving the control signal and data signal transmitted by the base station or network entity.

[0568] FIG. 19 illustrates the structure of a base station in a wireless communication system according to embodiments of the present disclosure.

[0569] Referring to FIG. 19, a base station according to one embodiment may include a transceiver (1910), a memory (1920), and a processor (1930). The transceiver (1910), the memory (1920), and the processor (1930) of the base station may operate according to the communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than the components described above. In addition, the processor (1930), the transceiver (1910), and the memory (1920) may be implemented as a single chip. In addition, the processor (1930) may include at least one processor.

[0570] The transceiver (1910) collectively refers to a base station receiver and a base station transmitter, and can transmit and receive signals with a terminal (UE) or a network entity. The signals transmitted and received with the terminal or network entity may include control information and data. The transceiver (1910) may include an RF transmitter for up-converting and amplifying the frequency of a transmission signal and an RF receiver for low-noise amplifying and down-converting the frequency of a reception signal. However, this is only an example of the transceiver (1910), and the components of the transceiver (1910) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1910) may receive a signal through a wireless channel and output it to the processor (1930), and transmit a signal output from the processor (1930) through the wireless channel.

[0571] The memory (1920) can store programs and data necessary for the operation of the base station. In addition, the memory (1920) can store control information or data included in signals acquired by the base station. The memory (1920) can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0572] The processor (1930) may control a series of processes so that the base station operates as described above. For example, the transceiver (1910) may receive a data signal including a control signal transmitted by a terminal, and the processor (1930) may determine the result of receiving the control signal and the data signal transmitted by the terminal.

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

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

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

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

[0577] In the specific embodiments of the present disclosure described above, components included in the invention 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.

[0578] 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, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, a 5G or NR system.

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

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

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

Claims

1. In a method performed by a terminal of a wireless communication system, A step of receiving an RRC (Radio Resource Control) message from a base station, the RRC message including first information for setting muting of a PUSCH (Physical Uplink Shared Channel), second information for indicating a time position of a resource for muting of the PUSCH, and third information for indicating a frequency position of a resource for muting of the PUSCH; A step of receiving DCI (Downlink Control Information) for scheduling the PUSCH from the base station; and A method comprising the step of transmitting the PUSCH to the base station by muting the resource based on the first information, the second information, and the third information.

2. In paragraph 1, The second information indicates one or two symbols, A method in which the time position of the above symbol is based on the first symbol of the slot.

3. In paragraph 2, A method in which the third information indicates an even-numbered subcarrier or an odd-numbered subcarrier in the frequency domain for the time position.

4. In paragraph 1, A method wherein the first information is included in TDRA information associated with transmission of the PUSCH corresponding to the Time Domain Resource Allocation (TDRA) field of the DCI.

5. In a method performed by a base station of a wireless communication system, A step of transmitting, to a terminal, an RRC (Radio Resource Control) message including first information for setting muting of a PUSCH (Physical Uplink Shared Channel), second information for indicating a time position of a resource for muting of the PUSCH, and third information for indicating a frequency position of a resource for muting of the PUSCH; A step of transmitting DCI (Downlink Control Information) for scheduling the PUSCH to the terminal; and A method comprising the step of receiving the PUSCH with the resource muted based on the first information, the second information, and the third information from the terminal.

6. In paragraph 5, The second information indicates one or two symbols, A method in which the time position of the above symbol is based on the first symbol of the slot.

7. In paragraph 6, A method in which the third information indicates an even-numbered subcarrier or an odd-numbered subcarrier in the frequency domain for the time position.

8. In paragraph 5, A method wherein the first information is included in TDRA information associated with transmission of the PUSCH corresponding to the Time Domain Resource Allocation (TDRA) field of the DCI.

9. In the terminal of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Receive an RRC (Radio Resource Control) message from a base station, including first information for setting muting of a PUSCH (Physical Uplink Shared Channel), second information for indicating a time position of a resource for muting of the PUSCH, and third information for indicating a frequency position of a resource for muting of the PUSCH, From the base station, receive DCI (Downlink Control Information) for scheduling the PUSCH, and A terminal configured to transmit the PUSCH to the base station by muting the resource based on the first information, the second information, and the third information.

10. In paragraph 9, The second information indicates one or two symbols, The time position of the above symbol is based on the first symbol of the slot.

11. In paragraph 10, The third information is a terminal that indicates an even-numbered subcarrier or an odd-numbered subcarrier in the frequency domain for the time position.

12. In paragraph 9, The terminal, wherein the first information is included in the Time Domain Resource Allocation (TDRA) information associated with the transmission of the PUSCH corresponding to the DCI's Time Domain Resource Allocation (TDRA) field.

13. In a base station of a wireless communication system, Transmitter and receiver; and Includes a control unit connected to the above transmitter and receiver, The above control unit: Transmitting an RRC (Radio Resource Control) message to a terminal, the RRC message including first information for setting muting of a PUSCH (Physical Uplink Shared Channel), second information for indicating a time position of a resource for muting of the PUSCH, and third information for indicating a frequency position of a resource for muting of the PUSCH, Transmitting DCI (Downlink Control Information) for scheduling the PUSCH to the terminal, and A base station configured to receive the PUSCH with the resource muted based on the first information, the second information, and the third information from the terminal.

14. In paragraph 13, The second information indicates one or two symbols, The time position of the above symbol is based on the first symbol of the slot, The third information is a base station that indicates an even-numbered subcarrier or an odd-numbered subcarrier in the frequency domain for the time position.

15. In paragraph 13, A base station, wherein the first information is included in TDRA information associated with transmission of the PUSCH corresponding to the Time Domain Resource Allocation (TDRA) field of the DCI.

Images