Method and device 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 terminal according to an embodiment of the present disclosure may receive configuration information about a muting resource from a base station through an RRC signal, identify, on the basis of the configuration information, whether muting is applied to an OFDM symbol allocated for PUSCH transmission, determine, on the basis of whether muting is applied, a set corresponding to the OFDM symbol, and perform transform precoding for the OFDM symbol on the basis of the determined set.

Description

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

[0001] The present disclosure generally relates to a wireless communication system, and more specifically, 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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] As a result of the aforementioned developments and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to facilitate the smooth provision of these services.

[0009] Based on the discussion above, the present disclosure aims to provide a device and method for transmitting a Physical Uplink Shared Channel (PUSCH) of a terminal in a wireless communication system.

[0010] A method performed by a terminal in a wireless communication system according to one embodiment of the present disclosure comprises: receiving configuration information regarding a muting resource via a radio resource control (RRC) signal from a base station; identifying, based on the configuration information, whether muting is applied to an orthogonal frequency division multiplexing (OFDM) symbol allocated for physical uplink shared channel (PUSCH) transmission; and, based on whether muting is applied, a set corresponding to the OFDM symbol A step of determining; and the above set The method includes the step of performing transform precoding for the OFDM symbol based on the above, and if the muting is not applied to the OFDM symbol, the set silver Includes values, and when the muting is applied to the OFDM symbol, the set silver It can include dog values.

[0011] Through embodiments of the present disclosure, an apparatus and method capable of effectively providing services in a wireless communication system are provided.

[0012] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

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

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

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

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

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

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

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

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

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

[0022] FIG. 10 illustrates the 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.

[0023] FIG. 11 illustrates an example of an optional connection procedure to embodiments of the present disclosure.

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

[0025] FIG. 13 shows a muting symbol according to embodiments of the present disclosure.

[0026] FIG. 14 shows a muting symbol applied to a symbol after a UCI symbol according to embodiments of the present disclosure.

[0027] FIG. 15a shows a muting symbol according to one embodiment of the present disclosure.

[0028] FIG. 15b shows a muting symbol according to one embodiment of the present disclosure.

[0029] FIG. 16a shows a muting symbol according to one embodiment of the present disclosure.

[0030] FIG. 16b shows a muting symbol according to one embodiment of the present disclosure.

[0031] FIG. 17a shows the location of the DMRS according to one embodiment of the present disclosure.

[0032] FIG. 17b shows the location of the DMRS according to one embodiment 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] A method performed by a terminal in a wireless communication system according to one embodiment of the present disclosure comprises: receiving configuration information regarding a muting resource via a radio resource control (RRC) signal from a base station; identifying, based on the configuration information, whether muting is applied to an orthogonal frequency division multiplexing (OFDM) symbol allocated for physical uplink shared channel (PUSCH) transmission; and, based on whether muting is applied, a set corresponding to the OFDM symbol A step of determining; and the above set The method includes the step of performing transform precoding for the OFDM symbol based on the above, and if the muting is not applied to the OFDM symbol, the set silver Includes values, and when the muting is applied to the OFDM symbol, the set silver It can include dog values.

[0036] A method performed by a base station in a wireless communication system according to one embodiment of the present disclosure comprises: transmitting configuration information regarding a muting resource to a terminal via an RRC signal, wherein the configuration information indicates an OFDM symbol to which muting is applied among a plurality of OFDM symbols allocated for PUSCH transmission; and a set corresponding to the OFDM symbol. The method includes the step of receiving a signal containing OFDM symbols transformed and precoded based on, and if the muting is not applied to the OFDM symbols, the set silver Includes values, and when the muting is applied to the OFDM symbol, the set silver It can include dog values.

[0037] A terminal in a wireless communication system according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor connected to the transceiver, wherein the at least one processor: receives configuration information regarding a muting resource via an RRC signal from a base station, identifies whether muting is applied to an OFDM symbol allocated for PUSCH transmission based on the configuration information, and, based on whether muting is applied, sets corresponding to the OFDM symbol Decide on, and three Transform precoding for OFDM symbols is performed based on, and if the muting is not applied to the OFDM symbols, the set silver Includes values, and when the muting is applied to the OFDM symbol, the set silver It can include dog values.

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

[0039] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0040] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0041] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0042] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies developed after LTE-A (e.g., 5G NR (new radio)) may be included therein, and the 5G below may be a concept that includes 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 made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0043] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0044] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0045] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

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

[0047] As a representative example of the broadband wireless communication system described above, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink. The uplink refers to a wireless link through 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 through which a base station transmits data or control signals to a terminal. Such multiple access methods can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0048] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0049] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0050] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0051] URLLC is a mission-critical cellular-based wireless communication service. Examples include services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and simultaneously require a packet error rate of 10⁻⁵ or less. Consequently, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and design considerations may be required to allocate wide resources within the frequency band to ensure the reliability of the communication link.

[0052] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0053] [NR Time-Frequency Resources]

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

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

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

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

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

[0059] Referring to Fig. 2, with a subcarrier interval setting value The case where =0(204) and The case where =1(205) is illustrated. If =0 (204), 1 subframe (201) can be composed of 1 slot (202), and If =1 (205), 1 subframe (201) can be composed of 2 slots (203). That is, the setting value for the subcarrier interval Number of slots per subframe according to ( ) may change, and accordingly, slots per frame ( ) may vary. Setting the interval for each subcarrier According to and It can be defined by Table 1 below.

[0060] [Table 1]

[0061]

[0062] [Bandwidth Part (BWP)]

[0063] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

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

[0065] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure information such as that shown in Table 2 below for each bandwidth portion.

[0066] [Table 2]

[0067]

[0068] The configuration information is, of course, not limited to the examples above, and various parameters related to bandwidth portions may be configured for the terminal in addition to the configuration information described above. The information described above may be transmitted by the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. Among the one or more configured bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via Downlink Control Information (DCI).

[0069] According to some embodiments, prior to the Radio Resource Control (RRC) connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a Physical Downlink Control Channel (PDCCH) can be transmitted for receiving system information required for initial connection (e.g., Remaining System Information (RMSI) or System Information Block 1 (SIB1)). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. In addition, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for control area #0 (e.g., search area #0). The terminal may consider the frequency area set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0070] The settings for the bandwidth portion supported by the aforementioned 5G can be used for various purposes.

[0071] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, the base station may support this through a bandwidth portion setting. For example, the base station may set a frequency position of the bandwidth portion (e.g., setting information 2) to the terminal so that the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0072] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, the base station may set two bandwidth portions to subcarrier intervals of 15 kHz and 30 kHz, respectively, in order to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for any terminal. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0073] In addition, according to some embodiments, for the purpose of reducing power consumption of the terminal, the base station may set a bandwidth portion having a bandwidth of different sizes for the terminal. For example, if the terminal supports a very large bandwidth (e.g., a bandwidth of 100 MHz) and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of unnecessary downlink control channels using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. For the purpose of reducing power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth (e.g., a bandwidth portion of 20 MHz) 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.

[0074] In the method for configuring the bandwidth portion described above, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part through the Master Information Block (MIB) during the initial connection phase. More specifically, the terminal can receive a Control Resource Set (CORESET) from the Physical Broadcast Channel (PBCH) MIB for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIB) can be transmitted. The bandwidth of the control set by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and Random Access.

[0075] [Bandwidth Section (BWP) Change]

[0076] When one or more bandwidth parts are configured for a terminal, the base station may instruct the terminal to change the bandwidth part (e.g., switching or transition) using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may instruct the terminal to Bandwidth Part #2 (302) using the Bandwidth Part Indicator within the DCI. The terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0077] As mentioned above, DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH. Therefore, when a terminal receives a request for a bandwidth portion change, it must be able to transmit and receive the PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth portion. To this end, the standard specifies the required delay time (T) when changing the bandwidth portion. BWP The requirements for ) have been defined, and can be defined as, for example, as shown in Table 3.

[0078] [Table 3]

[0079]

[0080] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0081] In accordance with the aforementioned requirements for the bandwidth portion change delay time, when the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be achieved at a time no later than that. Additionally, 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 intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWPThe time-domain resource allocation for a data channel can be determined by considering ). For example, when a base station schedules a data channel with a new bandwidth portion, in the method for determining the time-domain resource allocation for a data channel, the data channel may be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

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

[0083] [SS / PBCH Block]

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

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

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

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

[0088] - PBCH: Provides essential system information required for the transmission and reception of the terminal's data channel and control channel. The essential system information may include search space-related control information indicating wireless resource mapping information of the control channel, scheduling control information for a separate data channel transmitting system information, etc.

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

[0090] The terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. The terminal can obtain MIB from PBCH and receive a Control Resource Set (CORESET) #0 from it (e.g., may correspond to a control resource set with a control resource index of 0). The terminal can assume that the selected SS / PBCH block and the Demodulation Reference Signal (DMRS) transmitted from Control Resource Set #0 are Quasi-Co-Locations (QCL) and can perform monitoring of Control Resource Set #0. The terminal can receive system information using downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to Random Access Channel (RACH) required for initial connection from the received system information. The terminal can transmit a Physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information regarding the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among the respective SS / PBCH blocks and is monitoring the associated control area #0.

[0091] [PDCCH: DCI related]

[0092] Next, Downlink Control Information (DCI) in 5G systems will be explained in detail.

[0093] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields predefined between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0094] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) may be attached to the DCI message payload, and the CRC may be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Here, different RNTIs may be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control commands, or random access responses). For example, the RNTI may not be transmitted explicitly but may be included in the CRC calculation process. A terminal receiving a DCI message transmitted over the PDCCH can verify the CRC using the assigned RNTI, and if the CRC verification result is correct, the terminal can know that the message was transmitted to it.

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

[0096] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include at least one of the information in Table 4 below.

[0097] [Table 4]

[0098]

[0099] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include at least one of the information in Table 5 below.

[0100] [Table 5]

[0101]

[0102] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include at least one of the information in Table 6 below.

[0103] [Table 6]

[0104]

[0105] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include at least one of the information in Table 7 below.

[0106] [Table 7]

[0107]

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

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

[0110] FIG. 4 illustrates an example of setting control areas 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 areas (control area #1 (401), control area #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) on the frequency axis and one slot (420) on the time axis. The control areas (401, 402) may be set on a specific frequency resource (403) within the entire terminal bandwidth part (410) on the frequency axis. The control areas may be set with one or more OFDM symbols on the time axis and may be defined as the control resource set duration (404). Referring to the example illustrated in FIG. 4, control area #1 (401) is set with a control area length of 2 symbols, and control area #2 (402) is set with a control area length of 1 symbol.

[0111] A base station can set a control area in the aforementioned 5G to a terminal through upper layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Setting a control area to a terminal may mean providing information such as a control area identifier, a frequency location of the control area, and a symbol length of the control area. For example, the information for setting a control area may include at least one of the information in Table 8.

[0112] [Table 8]

[0113]

[0114] In Table 8, the tci-StatesPDCCH (e.g., named as the TCI (Transmission Configuration Indication) state for convenience) 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 area.

[0115] 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 a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G.

[0116] According to FIG. 5, the basic unit of time and frequency resources constituting a control channel can be referred to as REG (Resource Element Group, 503), and 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 REG (503) to form a downlink control channel allocation unit.

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

[0118] The basic unit of the downlink control channel (e.g., REG (503)) illustrated in FIG. 5 may include both REs to which DCI is mapped and areas to which DMRS (505), which is a reference signal for decoding, is mapped. As shown in FIG. 5, three DMRS (505) may be transmitted within one REG (503). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level, 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.

[0119] The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs can be defined for blind decoding. The search space may refer to a set of downlink control channel candidates consisting of CCEs that the terminal must attempt to decode at a given aggregation level. Since there may be various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, the terminal may have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0120] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages for system information. For example, a terminal may search the common search space of the PDCCH to receive PDSCH scheduling allocation information for the transmission of an SIB containing cell operator information. In the case of the common search space, since a certain group of terminals or all terminals need to receive the PDCCH, it may be defined as a set of pre-agreed CCEs. A terminal may receive scheduling allocation information for a terminal-specific PDSCH or PUSCH by searching the UE-specific search space of the PDCCH. The UE-specific search space may be defined specifically based on the terminal's identity and a function of various system parameters.

[0121] In 5G, parameters for the search space for a PDCCH can be set from the base station to the terminal via upper layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may set to the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, or the control area index to be monitored in the search space. For example, parameters for the search space for a PDCCH may include at least one of the information in Table 9.

[0122] [Table 9]

[0123]

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

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

[0126] In the common search space, the following combinations of DCI formats and RNTI may be monitored, but this is merely an example and is not limited to the following examples.

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

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

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

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

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

[0132] In terminal-specific search spaces, the following combinations of DCI formats and RNTIs may be monitored, but this is merely an example and is not limited to the following examples.

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

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

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

[0136] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0137] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

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

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

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

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

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

[0143] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0144] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0145] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

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

[0147] [Table 10]

[0148]

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

[0150] [Mathematical Formula 1]

[0151]

[0152] - : Lamination level

[0153] - : Carrier Index

[0154] - : Slot Index

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

[0156] - : PDCCH candidate index of aggregation level L

[0157] -

[0158] - , 0, , , ,

[0159] - : Terminal identifier

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

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

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

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

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

[0165] The base station can dynamically notify the terminal via DCI whether to rate match a data channel in the rate matching resource portion configured through additional settings (e.g., corresponding to the “rate matching indicator” within the aforementioned DCI format). Specifically, the base station can select some of the configured rate matching resources and group them into rate matching resource groups. The base station can indicate to the terminal via DCI using a bitmap method whether to rate match a data channel for each rate matching resource group. For example, if four rate matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are configured, the base station can configure the rate matching groups as RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4}, and can indicate to the terminal via a bitmap whether to rate match in RMG#1 and RMG#2, respectively, using 2 bits within the DCI field. For example, the base station can be instructed to "1" if rate matching is required, and "0" if rate matching is not required.

[0166] In 5G, the granularity of “RB symbol level” and “RE level” is supported by configuring the aforementioned rate matching resources on the terminal. More specifically, the following configuration method may be followed.

[0167] RB symbol level

[0168] The terminal may receive up to four RateMatchPatterns as upper-layer signaling for each bandwidth portion, and one RateMatchPattern may include the following. Of course, it may not be limited to the examples below.

[0169] - As a Reserved Resource within the bandwidth portion, a resource may be included in which the time and frequency resource domains of the said Reserve Resource are set as a combination of an RB level bitmap and a symbol level bitmap along the frequency axis. The Reserve Resource may span one or two slots (e.g., may be spanned). A periodicity and pattern in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may be additionally set.

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

[0171] RE level

[0172] The terminal can receive the following configurations through upper-layer signaling. Of course, it may not be limited to the examples below.

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

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

[0175] [PDSCH: Regarding Frequency Resource Allocation]

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

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

[0178] Referring to FIG. 7, if a terminal is configured 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 include a bitmap composed of bits. In this case, N RBG This may refer to the number of resource block groups (RBG) determined as shown in [Table 11] below, based on the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and data may be transmitted to the RBG indicated as 1 by the bitmap.

[0179] [Table 11]

[0180]

[0181] 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 the frequency axis resources continuously allocated therefrom.

[0182] If the 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 consisting of bits of the larger value (735) of the payload (715) for setting resource type-0 resource allocation and the payload (720, 725) for setting resource type-1 resource allocation. The 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 within the DCI, and if the bit has a value of '0', it indicates that resource type-0 resource allocation is used, and if it has a value of '1', it indicates that resource type-1 resource allocation is used.

[0183] [PDSCH / PUSCH: Time Resource Allocation]

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

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

[0186] [Table 12]

[0187]

[0188] [Table 13]

[0189]

[0190] 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., may be indicated by the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

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

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

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

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

[0195] [PUSCH: Regarding transmission method]

[0196] The scheduling method for PUSCH transmissions is described below. PUSCH transmissions may be dynamically scheduled by a UL grant within the DCI, or operated by a configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmissions may be available in DCI format 0_0 or 0_1.

[0197] Configured grant Type 1 PUSCH transmissions can be configured semi-statically by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 14], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 14], through the upper signaling. When PUSCH transmissions are operated by configured grants, parameters applied to the PUSCH transmissions can be applied through configuredGrantConfig, the upper signaling of [Table 14], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling 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 transmissions operated by the configured grant.

[0198] [Table 14]

[0199]

[0200] The PUSCH transmission method is described below. 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 and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config in [Table 15], the upper signaling, is 'codebook' or 'nonCodebook'.

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

[0202] [Table 15]

[0203]

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

[0205] The SRI can be provided via the SRS resource indicator field within the DCI or configured via the higher-level signaling srs-ResourceIndicator. During codebook-based PUSCH transmission, the terminal is configured with at least one SRS resource and can be configured with up to two. If the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The TPMI and transmission rank can be provided via the precoding information and number of layers field within the DCI or configured via the higher-level signaling precodingAndNumberOfLayers. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. If the terminal is configured with one SRS resource, the TPMI can be used to indicate the precoder to be applied from the configured single SRS resource. When a terminal is configured with multiple SRS resources, TPMI can be used to specify the precoder to be applied in the SRS resource indicated by SRI.

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

[0207] A terminal can receive one SRS resource set in which the value of 'usage' in the upper signaling SRS-ResourceSet is set to 'codebook'. Within that SRS resource set, one SRS resource can be indicated via SRI. If multiple SRS resources are configured within the SRS resource set in which the value of 'usage' 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 will be set to the same value for all SRS resources.

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

[0209] The following describes non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission via DCI format 0_1.

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

[0211] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the associated NZP CSI-RS may be indicated by the SRS request field in DCI format 0_1 ​​or 1_1. If the associated NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the associated NZP CSI-RS may be indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. The DCI may not indicate cross-carrier or cross-BWP scheduling. If the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS may be located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier may not be set to QCL-TypeD.

[0212] When a periodic or semi-continuous SRS resource set is established, the associated NZP CSI-RS may be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal may not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

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

[0214] A base station can transmit one NZP-CSI-RS associated with an SRS resource set to a terminal. Based on the results measured upon receiving the NZP-CSI-RS, the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the corresponding SRS resource set. The terminal can apply the calculated precoder when transmitting one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station. The base station can select one or more SRS resources from among the received one or more SRS resources. In non-codebook-based PUSCH transmission, an SRI may represent an index capable of expressing a combination of one or more SRS resources. The SRI may be included within a DCI. The number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH. The terminal can transmit the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0215] [CA / DC Related]

[0216] FIG. 10 illustrates the 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.

[0217] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system can 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) at the terminal and the NR base station, respectively.

[0218] The main functions of NR SDAP (1025, 1070) may include at least some of the following functions.

[0219] - User data transfer function (transfer of user plane data)

[0220] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

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

[0222] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0223] For SDAP layer devices, the terminal may receive from an RRC message a setting on whether to use the SDAP layer device header or the SDAP layer device functions for each PDCP layer device, bearer, or logical channel. If the SDAP header is set, the RRC message may instruct the terminal to update or reset the mapping information for the uplink and downlink QoS flows and data bearers through the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0224] The main functions of NR PDCP (1030, 1065) may include at least some of the following functions.

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

[0226] - User data transfer function (Transfer of user data)

[0227] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0229] - Reordering function (PDCP PDU reordering for reception)

[0230] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0231] - Retransmission of PDCP SDUs

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

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

[0234] Referring to the functions described above, the reordering function of the NR PDCP device may mean a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number). The reordering function may include a function that transmits data to an upper layer in the reordered order. The reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, and may include a function that records lost PDCP PDUs by reordering them. The reordering function may include a function that reports the status of lost PDCP PDUs to the transmitting side, and may include a function that requests retransmission of lost PDCP PDUs.

[0235] The main functions of NR RLC (1035, 1060) may include at least some of the following functions.

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

[0237] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

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

[0240] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0241] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0242] - Reordering function (Reordering of RLC data PDUs)

[0243] - Duplicate detection

[0244] - Error detection function (Protocol error detection)

[0245] - RLC SDU discard function

[0246] RLC re-establishment function

[0247] The in-sequence delivery function of the NR RLC device described above may refer to a function of delivering RLC SDUs received from a lower layer to an upper layer in sequence. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering RLC SDUs when a single RLC SDU is originally received divided into multiple RLC SDUs. The in-sequence delivery function of the NR RLC device may include a function of rearranging received RLC PDUs based on an 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 the status of 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 the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer in the event of a lost RLC SDU. The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received before the timer started to the upper layer in order, provided that a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present to the upper layer in order, provided that a predetermined timer has expired even if there is a lost RLC SDU. Additionally, the RLC PDUs may be processed in the order they are received (e.g., in the order of arrival, regardless of the order of the serial number) and delivered to the PDCP device out of order (out-of-sequence delivery).The sequential delivery function of the NR RLC device can receive segments that are stored in a buffer or will be received later, reconstruct them into a single complete RLC PDU, process them, and deliver them to the PDCP device. The NR RLC layer may not include a concatenation function, and the above-described functions may be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0248] The out-of-sequence delivery function of the NR RLC device described above may refer to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. The out-of-sequence delivery function of the NR RLC device may include a function of reassembling and delivering RLC SDUs when a single RLC SDU is originally received as multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record lost RLC PDUs.

[0249] The NR MAC (1040, 1055) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include at least some of the following functions.

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

[0251] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0252] - Scheduling information reporting function

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

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

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

[0256] - MBMS service identification function

[0257] - Transport format selection function

[0258] - Padding

[0259] The NR PHY layer (1045, 1050) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols, and transmitting them over a wireless channel. The NR PHY layer can perform the operation of demodulating OFDM symbols received through the wireless channel, channel decoding, and transmitting them to the upper layer.

[0260] 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 (1000). 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 RLC but multiplexing the PHY layer through the MAC layer (1010). 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 RLC but multiplexing the PHY layer through the MAC layer (1020).

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

[0262] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The contents of the present disclosure may be applied to frequency division duplex (FDD) and time division duplex (TDD) systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted to a terminal using the downlink data channel of the physical layer of a base station, or to a base station using the uplink data channel of the physical layer of a terminal, and may be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (MAC CE).

[0263] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator that indicates whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the terminal receiving a PDSCH to which cooperative communication is applied based on conditions similar to those above may be referred to as an NC-JT case.

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

[0265] In the following disclosure, the examples described above are explained through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0266] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, gNB, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included therein. Accordingly, 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 judged by a person skilled in the art. The content of the present disclosure is applicable to FDD and TDD systems.

[0267] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

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

[0269] - MIB (Master Information Block)

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

[0271] - RRC (Radio Resource Control)

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

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

[0274] - PDCCH (Physical Downlink Control Channel)

[0275] - DCI (Downlink Control Information)

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

[0277] - Group common DCI

[0278] - Common DCI

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

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

[0281] - PUCCH (Physical Uplink Control Channel)

[0282] - UCI (Uplink Control Information)

[0283] 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. By receiving uplink transmissions from terminals equivalent to the increased uplink resources, it expands the uplink coverage of the terminal and reduces feedback delay by receiving feedback on downlink transmissions from the terminals using the expanded uplink resources. In this disclosure, a terminal capable of receiving information from a base station regarding SBFD support and performing uplink transmissions using a portion of downlink resources may be referred to as an SBFD terminal (SBFD-capable UE) for convenience. To define 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), the following method may be considered.

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

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

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

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

[0288] In the embodiments, the system information for transmitting information regarding SBFD support may be system information transmitted separately, distinguished from system information for a terminal supporting a different version of the standard within the cell (e.g., an existing TDD terminal). An 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 regarding non-support of SBFD, the SBFD terminal may determine that the cell (or base station) supports only TDD.

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

[0290] In the embodiments, if information regarding SBFD support is included in system information for a terminal supporting a different version of the specification (e.g., an existing TDD terminal), the information regarding SBFD support may be transmitted via a separate PDSCH so as not to affect the acquisition of system information for the existing TDD terminal. For example, an SBFD non-supporting terminal may receive a first SIB (or SIB1) containing existing TDD-related system information from the first PDSCH. An SBFD-supporting terminal may receive a first SIB (or SIB) containing existing TDD-related system information from the first PDSCH and may receive a second SIB containing SBFD-related system information from the second PDSCH. Here, the first PDSCH and the second PDSCH may be scheduled as the first PDCCH and the second PDCCH, and the cyclic redundancy code (CRC) 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 first PDCCH.

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

[0292] According to various embodiments, a base station may set up separate random access resources for each of the existing TDD terminals or SBFD terminals (e.g., including both SBFD terminals supporting duplex communication and SBFD terminals 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 terminals via system information. The system information for transmitting information for the random access resources may include system information transmitted separately that is distinguished from system information for terminals supporting different versions of specifications within the cell (e.g., existing TDD terminals).

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

[0294] In embodiments, the SBFD terminal may be instructed by the base station whether a random access resource for the TDD terminal is available. Such instruction may be provided by being included in the SIB. For example, the SIB may set a separate random access resource for the SBFD terminal and, along with the setting, may also indicate whether a random access resource for the TDD terminal is available. Such instruction may be provided via 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 can use the random access resource for the TDD terminal. Depending on the various embodiments, this is merely an example, and the opposite case may, of course, be included.

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

[0296] In the embodiments, when the base station determines that the terminal in question is an SBFD terminal, the base station may schedule msg2, msg3, msg4, etc. to the terminal based on uplink subband settings. For example, when the base station schedules the reception of msg2 and msg4 to the terminal, the base station may schedule msg2 and msg4 so that they are not received in the uplink subband (for example, when the terminal receives a PDSCH containing msg2 and msg4, the PDSCH is received in a frequency resource excluding the uplink subband). Or, when the base station schedules a msg3 PUSCH to the terminal, the base station may schedule the msg3 PUSCH so that it is transmitted within the uplink subband.

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

[0298] According to various embodiments of the present disclosure, a base station may not set a separate random access resource for an SBFD terminal, but may set a common random access resource for all terminals within a cell. In this case, information regarding the setting of the random access resource may be transmitted to all terminals within the cell via system information, and an SBFD terminal that receives such system information may perform random access on the set random access resource. Subsequently, 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 or physical signal from the base station that determines that a portion of the frequency resources of the downlink time resources has been set as an uplink resource, and accordingly, may perform an SBFD operation (e.g., transmitting an uplink signal from the set uplink resource).

[0299] In the embodiments, when a cell determines that it 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, which includes at least one of whether the terminal supports SBFD, whether it supports full-duplex or half-duplex communication, or the number of transmitting or receiving antennas it has (or supports). In the embodiments, if half-duplex communication support is an essential implementation for the SBFD terminal, the half-duplex communication support status may be omitted from the capability information. The SBFD terminal's report of capability information may be reported to the base station through a random access process, may be reported separately to the base station after the random access process 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.

[0300] In the 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 it may support full-duplex communication, which performs both uplink transmission and downlink reception at a specific moment. Accordingly, whether such half-duplex or full-duplex communication is supported can be reported to the base station by the SBFD terminal through capability reporting, and after the report, the base station may set to the SBFD terminal whether 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 to change RF between transmission and reception may be required when operating in FDD or TDD, as a duplexer generally does not exist.

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

[0302] 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 will be described with reference to FIG. 11.

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

[0304] In the second step (1120), the base station may transmit a random access response (RAR) (or message 2 (message 2, msg2)) to the terminal for the detected random access attempt. The base station may 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. Additionally, the base station may transmit uplink resource and power control commands to be used by the terminal as scheduling information. The scheduling information transmitted by the base station may include control information for the terminal's uplink transmission beam. The RAR may be transmitted via PDSCH and may include at least one of the following information.

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

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

[0307] - Uplink scheduling grant

[0308] - Timing advance value

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

[0310] In the third step (1130), the terminal may transmit uplink information (e.g., scheduled transmission or message 3) containing its terminal identifier (e.g., UE contention resolution identity) (or, if the terminal already has a valid terminal identifier (C-RNTI) within the cell before the random access procedure begins, that valid terminal identifier) ​​to the base station via the 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). Additionally, the transmission power of the uplink data channel for transmitting message 3 may be determined by taking into account 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 that the terminal transmits to the base station after the terminal transmits a random access preamble.

[0311] In step 4 (1140), if the base station determines that the terminal has performed random access without collision with another terminal, it may transmit to the terminal a message (e.g., a contention resolution message (CR message) or message 4) containing the identifier of the terminal that transmitted uplink data in step 3 (1130). In this regard, if multiple terminals receive the same TC-RNTI in step 2 (1120), the multiple terminals that received the same TC-RNTI may each transmit to the base station a message 3 (message 3) containing their own terminal identifier (UE contention resolution identity) in step 3 (1130), and the base station may transmit a message 4 (CR message) containing the terminal identifier of one of the multiple terminals to resolve the contention. A terminal can determine that random access has succeeded if it receives a message 4 (CR message) containing its terminal identifier from a base station in the fourth step (1140) (or transmits a message 3 (message 3) containing a terminal identifier (C-RNTI) in the third step (1130) and receives terminal-specific control information containing a cyclic redundancy check (CRC) based on the terminal identifier (C-RNTI) via PDCCH in the fourth step (1140). Accordingly, among multiple terminals that have received the same TC-RNTI from a base station, a terminal that confirms that its terminal identifier is included in message 4 (CR message) can confirm that it has succeeded in the competition. The terminal can transmit a HARQ-ACK / NACK indicating successful reception of message 4 to the base station via a physical uplink control channel (PUCCH).

[0312] In the embodiments, if the data transmitted by the terminal in the third step (1130) and the data of another terminal collide with each other, causing the base station to fail to receive a data signal from the terminal, the base station may not perform further data transmission to the terminal. Accordingly, if the terminal fails to receive data transmitted from the base station in the fourth step (1140) for a certain period of time, it may determine the random access procedure as a failure and restart from the first step (1110).

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

[0314] In the embodiments, the base station may provide the terminal with 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, upper layer signaling (RRC (Radio Resource Control) information), or DCI (Downlink Control Information). The frequency resources for PRACH transmission may indicate the terminal the starting RB point of transmission, and the number of RBs used may be determined according to the preamble format transmitted via PRACH and the applied subcarrier interval. The time resources for PRACH transmission may provide the PRACH configuration index (e.g., 0 to 255), which includes a pre-set PRACH configuration period, a PRACH transmission time (e.g., may be used interchangeably with PRACH occasion, transmission time, etc.), a subframe index and start symbol, or the number of PRACH transmission times within a slot, as shown in Table 16 below. The terminal can determine the validity of the PRACH transmission timestamps indicated in the PRACH setting index and determine only the valid PRACH transmission timestamps as PRACH transmission timestamps capable of transmitting a random access preamble. Through the PRACH setting index, the random access setting information included in the SIB, and the index of the SSB selected by the terminal, the terminal can identify the time and frequency resources for transmitting the random access preamble and transmit the selected sequence to the base station as a preamble.

[0315] Meanwhile, according to an embodiment of the present disclosure, a method is required for an SBFD terminal to determine the validity of a PRACH transmission time point through a PRACH setting index and an SBFD setting for performing PRACH transmission, and to perform PRACH transmission through a PRACH transmission time point determined to be valid, or a method of a procedure performed by an SBFD terminal when a valid PRACH transmission time point overlaps with a downlink reception.

[0316] [Table 16]

[0317]

[0318]

[0319]

[0320]

[0321]

[0322]

[0323]

[0324]

[0325] 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 an SBFD being operated in the TDD band of a wireless communication system to which the present disclosure applies.

[0326] Figure 12 (a) illustrates a case where TDD is operated in a specific frequency band. In a cell operating TDD, the base station can transmit and receive signals containing data / control information in a downlink slot (or symbol), an uplink slot (or symbol) (1201), and a flexible slot (or symbol) based on a setting according to TDD UL-DL resource setting information indicating TDD downlink slot (or symbol) resources and uplink slot (or symbol) resources.

[0327] In FIG. 12, it can be assumed that the DDDSU slot format is configured according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols (1201, 1211, 1221, 1231), and 'S' may be a slot that is not 'D' or 'U' (e.g., a slot containing downlink symbols or uplink symbols, or a flexible symbol). Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols, but this is merely an example and is not limited to the example described above. 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., 5ms for a 15kHz SCS, 2.5ms for a 30kHz SCS, etc.).

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

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

[0330] Referring to FIG. 12(c), the terminal can be configured to set a portion of the cell's frequency band as a frequency band (1220) capable of uplink transmission and to set a time range in which the frequency band is activated. Here, such a frequency band may be referred to as an uplink subband (UL subband). Referring to FIG. 12(c), the uplink subband (UL subband) on the first slot may be deactivated, and the uplink subband (UL subband) on the remaining slots may be activated. Accordingly, the terminal can transmit an uplink channel or signal on the uplink subband (UL subband) (1222) of the remaining slots. That is, FIG. 12(c) illustrates an example in which the uplink subband (UL subband) is activated on a slot-by-slot basis, but this is merely an example, and it goes without saying that activation status can be set on a symbol-by-symbol basis.

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

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

[0333] [PUSCH Muting Symbol]

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

[0335] The base station can use muting REs within the PUSCH to estimate the power of a leaked signal from an adjacent base station, the signal's covariance matrix, or the channel between adjacent base stations. If there are no muting REs within the PUSCH, it may be difficult to estimate the power of a leaked signal caused by a transmitted signal from the terminal, the signal's covariance matrix, or the channel between adjacent base stations. Using the estimated power of the leaked signal, the leaked signal's covariance matrix, or the estimated channel between adjacent base stations, the base station can suppress the leaked signal that affects reception in the PUSCH.

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

[0337] Referring to FIG. 13(a), the muting symbol may be a comb-2 pattern. That is, PUSCH data is assigned to the even-numbered REs or odd-numbered REs (power assignment), and the remaining REs may be muted (power non-assigned).

[0338] Referring to Fig. 13(b), all REs can be muted (power unassigned) at the muting symbol.

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

[0340] 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 3 of the 12 REs along the frequency axis within the PRB. Here, the indices of the 3 REs may include any one of {0, 4, 8}, {1, 5, 9}, {2, 6, 10}, or {3, 7, 11}, and the interval between the REs is 4.

[0341] In one embodiment, for the Comb-6 pattern, muting may be applied to 2 of the 12 REs in the frequency axis within the PRB. Here, the indices of the 2 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.

[0342] In the Muting symbol, the Muting pattern may be applied to all PRBs scheduled for PUSCH, or to some PRBs. If applied to some PRBs, the PRBs may be configured from the base station. The indices of the PRBs scheduled for PUSCH are N start , N start +1, N start +2, … N start +N PRB If -1 is used, the PRB with a PRB index of 0 may be the PRB with the lowest frequency in the UL BWP. The PRB with a PRB index of 0 may be the PRB with the lowest frequency in the UL subband. The PRB with a PRB index of 0 may be a Common Resource Block (CRB) with an index of 0. Among the subcarriers included in the CRB with an index of 0, the subcarrier with the lowest frequency may be the subcarrier specified at Point A. Point A can be configured by the base station to the terminal via system information. N start is the index of the first PRB for which PUSCH was scheduled. N PRB can 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 K-th RBs among the PRBs. Here, K can be at least one of 1, 2, 4, 8, or 16. When the terminal is instructed by the base station to have a value of K, the index is N start , N start +K, N start +2*K, N start A muting pattern may be applied to PRBs such as +3*K, …. The terminal may additionally receive an offset value (M) for the starting PRB to which the muting pattern will be applied. The offset value may include at least one of 0, 1, … or K-1. When the terminal is instructed by the base station to use the K value and the M value, the index is N start +M+K, N start +M+2*K, N startMuting patterns can be applied to PRBs such as +M+3*K, …

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

[0344] In one embodiment, when a muting RE and a PTRS (phase tracking reference signal) RE overlap with respect to a muting symbol, the terminal may not determine that the RE is a muting RE. That is, the PTRS may be transmitted in that RE.

[0345] In the embodiments, the terminal may receive a setting from the base station to use a muting pattern. The setting for which muting pattern to use may be included in the base station's RRC signal. Specifically, the PUSCH setting information of the base station's RRC signal may include information regarding the muting pattern. For example, the PUSCH setting information may include a comb-2 pattern-based muting pattern as shown in FIG. 13(a) and information in which all REs set at least one of the muting patterns as shown in FIG. 13(b).

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

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

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

[0349] [DFT-s-OFDM Signal Generation]

[0350] A method for generating a DFT-s-OFDM signal is disclosed. Here, the case where no muting pattern is applied is described. For specific methods for generating a DFT-s-OFDM signal, refer to the 3GPP standard document TS38.211.

[0351] Figure 14 is a flowchart for generating a DFT-s-OFDM signal.

[0352] The terminal is a channel-coded bit stream It can be scrambled using a scrambling block. The scrambled signal is It is. Here is the length of the bit stream.

[0353] The terminal is a scrambled signal It can be modulated or modulated using a modulation block. Here, the modulation can be one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16QAM (16 Quadrature Amplitude Modulation), 64QAM (64 Quadrature Amplitude Modulation), 256QAM (256 Quadrature Amplitude Modulation), or 1024QAM (1024 Quadrature Amplitude Modulation). The modulated symbols are It could be. Here is the number of modulated symbols, and It could be. Here, The number of bits per modulation symbol can be determined by the following Table 17.

[0354] [Table 17]

[0355]

[0356] Modulated symbols It can be mapped to a MIMO layer according to the layer mapping block. DFT-s-OFDM can only support a single layer. Therefore, the layer-mapped signal It could be. Here, am.

[0357] Layer-mapped signal Transmission precoding can be applied through the Transform precoding block. This can be applied only when generating the DFT-s-OFDM signal.

[0358] Layer-mapped signal PTRS can be added to it. The signal after PTRS is added It can be expressed as follows.

[0359] If PTRS is not added, It could be.

[0360] If PTRS is added, Is It can be divided into sets, and the set In The values ​​include dog values. The above values ​​are It can be mapped to. Here, And, is. And PTRS is It can be included in. The value of m is described later. If OFDM symbol If this PTRS is included, and OFDM symbol If this PTRS is not included, It could be.

[0361] Is It can be divided into sets. And each set can be transmitted in a single OFDM symbol. Each set includes Can include values. Here may be the number of subcarriers (or REs) contained in a single OFDM symbol of a scheduled PUSCH. For reference, since all subcarriers (REs) of a scheduled PUSCH are used for data transmission, It could be. Here, is the number of RBs included in the scheduled PUSCH.

[0362] It can be transmitted at OFDM symbol 0 of the scheduled PUSCH (the first OFDM symbol excluding the DMRS symbol). It can be transmitted in OFDM symbol 1 of the scheduled PUSCH (the second OFDM symbol excluding the DMRS symbol). is the scheduled PUSCH OFDM symbol (excluding DMRS symbols) It can be transmitted in the (th OFDM symbol).

[0363] The terminal is the OFDM symbol of the scheduled PUSCH Corresponding to Transform precoding can be performed on the set as in mathematical formula 2.

[0364] [Mathematical Formula 2]

[0365]

[0366] Mathematical Equation 2 can be defined as a Discrete Fourier Transform (DFT) operation. Here, the size of the DFT is It could be. And is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be sample values. By performing Transform precoding on all OFDM symbols, This can be obtained.

[0367] Since the operation of Equation 2 is required when generating DFT-s-OFDM signals, the complexity of the terminal may increase. To reduce complexity, the number of PRBs that the terminal can be scheduled for ( The following conditions may exist in ).

[0368]

[0369] Here can be a non-negative integer value. That is, the terminal is It can be scheduled, but It cannot be scheduled.

[0370] Transmit precoded signal It can be precoded through a Precoding block. DFT-s-OFDM can only support a single layer. Therefore, It can be. Here, p0 can be the index of the antenna port where PUSCH is transmitted.

[0371] Precoded signal It can be mapped to Virtual resource blocks (VRBs). First, the precoded signal corresponds to the transmit power of PUSCH. It can be multiplied. And it can be mapped to the REs of the scheduled VRBs. The indices of the REs are It can be represented as, is the subcarrier index, and can be an index of an OFDM symbol (excluding DMRS symbols). The following conditions may be followed during mapping.

[0372] - REs must be included in VRBs scheduled for PUSCH transmission.

[0373] - These are REs excluding the REs corresponding to DM-RS for DM-RS, PT-RS, or other concurrently scheduled terminals.

[0374] The Mapping from VRBs to PRBs block can change signals mapped to VRBs to PRBs. Since only the non-interleaved method is used during PUSCH transmission, a signal mapped to VRB n can be mapped to PRB n.

[0375] The OFDM baseband signal generation block can generate a signal according to the following Table 18. Here, is RE It is a signal corresponding to.

[0376] [Table 18]

[0377]

[0378] <1st Embodiment: OFDM Signal Generation Using Different DFT Sizes>

[0379] In one embodiment of the present disclosure, the terminal can generate an OFDM signal using different DFT sizes.

[0380] Different DFT sizes can be applied to different OFDM symbols of a scheduled PUSCH. More specifically, a first DFT size may correspond to symbols in a scheduled PUSCH that are not muted, and a second DFT size may correspond to symbols in a scheduled PUSCH that are muted.

[0381] The first DFT size can be equal to the number of all subcarriers contained in an unmuted OFDM symbol. That is, the first DFT size is It could be.

[0382] The second DFT size can be equal to the number of subcarriers used for data transmission (not used for muting) in an OFDM symbol with muting applied. If muting is used with a comb-2 pattern, the second DFT size It could be.

[0383] FIGS. 15a and 15b are diagrams for generating a DFT-S OFDM signal according to a first embodiment. FIG. 15a is a diagram for generating a DFT-S OFDM signal when muting is not applied. FIG. 15b is a diagram for generating a DFT-S OFDM signal when muting is applied.

[0384] According to the first embodiment, when muting is applied to PUSCH, the Transform precoding block can perform the following operations.

[0385] Layer-mapped signal Transmission precoding can be applied through the Transform precoding block. This can be applied only when generating the DFT-s-OFDM signal.

[0386] If PTRS is not added, It could be.

[0387] If PTRS is added, Is It can be divided into sets, and the set In The values ​​include dog values. The above values ​​are It can be mapped to. Here, And, is. And PTRS is It can be included in. The value of m is described later. If OFDM symbol If this PTRS is included, and OFDM symbol If this PTRS is not included, It could be.

[0388] It can be divided into L sets. And each set can be transmitted in a single OFDM symbol. Each set includes A value or Can include values. L sets can be divided as follows depending on the position of the muting symbol.

[0389]

[0390] Here The value of can be determined as follows.

[0391]

[0392] in other words, The value of may be determined by the position of the UL muting symbol. For example, assuming that OFDM symbols 0 through 7 (indexed excluding DMRS symbols) are scheduled on PUSCH and the UL resource muting symbols are OFDM symbol 1 and OFDM symbol 5, P l It can be determined as follows.

[0393]

[0394] (The UL muting symbol did not exist prior to OFDM symbol 1)

[0395] (Prior to OFDM Symbol 2, there was one UL muting symbol)

[0396] (Prior to OFDM Symbol 3, there was one UL muting symbol)

[0397] (Prior to OFDM Symbol 4, there was one UL muting symbol)

[0398] (Prior to OFDM Symbol 5, there was one UL muting symbol)

[0399] (Prior to OFDM symbol 6, there were two UL muting symbols)

[0400] (Prior to OFDM Symbol 7, there were two UL muting symbols)

[0401] (Prior to OFDM Symbol 8, there were two UL muting symbols)

[0402] Therefore, L sets can be as follows.

[0403] ( (Including dog values)

[0404] ( (Including dog values)

[0405] ( (Including dog values)

[0406] ( (Including dog values)

[0407] ( (Including dog values)

[0408] ( (Including dog values)

[0409] ( (Including dog values)

[0410] ( (Including dog values)

[0411] is the scheduled PUSCH OFDM symbol (excluding DMRS symbols) It can be transmitted in the (th OFDM symbol).

[0412] The terminal is the OFDM symbol of the scheduled PUSCH Corresponding to Transform precoding can be performed on the scheduled PUSCH OFDM symbols Different formulas may be applied depending on whether Muting is applied or not.

[0413] Scheduled PUSCH OFDM symbols If Muting is not applied, Transform precoding can be performed as in Equation 3.

[0414] [Mathematical Formula 3]

[0415]

[0416] k=0,..., -1

[0417] Here, the OFDM symbol of the scheduled PUSCH Since Muting is not applied to it, the size of the DFT is It could be. And, A set containing dog values is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be several sample values.

[0418] Scheduled PUSCH OFDM symbols When Muting is applied, Transform precoding can be performed as shown in Equation 4.

[0419] [Mathematical Formula 4]

[0420]

[0421] Here, the OFDM symbol of the scheduled PUSCH Since Muting is applied to it, the size of the DFT is It could be. And, A set containing dog values is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be several sample values.

[0422] Mathematical formulas 3 and 4 can be combined and described as mathematical formula 5.

[0423] [Mathematical Formula 5]

[0424]

[0425] k=0,....

[0426]

[0427] Here, the OFDM symbol of the scheduled PUSCH If Muting is not applied to, and the scheduled PUSCH OFDM symbol When Muting is applied to, It could be.

[0428] In Equation 5, L is the number of OFDM symbols scheduled in PUSCH (excluding DMRS symbols). This can be determined as in Equation 6.

[0429] [Mathematical Formula 6]

[0430]

[0431] The terminal is the result of the DFT corresponding to all OFDM symbols of the scheduled PUSCH. You can obtain.

[0432] Transmit precoded signal It can be precoded through a Precoding block. DFT-s-OFDM can only support a single layer. Therefore, It can be. Here, p0 can be the index of the antenna port where PUSCH is transmitted.

[0433] Precoded signal It can be mapped to Virtual Resource Blocks (VRBs). First, the transmit power of PUSCH can be multiplied to the precoded signal. The transmit power can be multiplied differently depending on the OFDM symbol. For example, the precoded signal When transmitted in OFDM symbols where muting is not applied, the transmit power of PUSCH This can be multiplied. Precoded signal When transmitted in OFDM symbols with muting applied, the transmit power of PUSCH This can be multiplied.

[0434] And it can be mapped to the REs of the scheduled VRBs. The indices of the REs are It can be represented as, is the subcarrier index, and can be an index of an OFDM symbol (excluding DMRS symbols). The following conditions may be followed during mapping.

[0435] - REs must be included in VRBs scheduled for PUSCH transmission.

[0436] - These are REs excluding the REs corresponding to DM-RS for DM-RS, PT-RS, or other concurrently scheduled terminals.

[0437] These are the REs to which Muting applies, excluding those from the Muting symbol.

[0438] <Additional Scheduling Constraints>

[0439] By comparing Equation 3 and Equation 4, different DFT sizes can be applied to symbols to which Muting is applied and symbols to which Muting is not applied in PUSCH. More specifically, for symbols to which Muting is not applied, a DFT size of half the size ( ) can be used. This may require additional complexity of the terminal.

[0440] To reduce additional complexity, when a Muting symbol is applied to PUSCH, the number of PRBs a terminal can be scheduled ( There may be additional conditions in ).

[0441] for example, The DFT size of PUSCH scheduling without muting applied is 12*9=108. Therefore, a DFT size of 108 can be a value supported by the terminal. If muting is applied to the above PUSCH, the terminal's DFT size can be reduced by half. That is, The DFT size of a PUSCH symbol with muting applied is 12 * 9 / 2 = 54. A DFT size of 54 is a value not supported by existing terminals. This is because existing terminals used values ​​corresponding to multiples of 12 as the DFT size. Therefore, If is odd, the terminal requires the implementation of a new DFT size. Methods to solve this are disclosed.

[0442] In the first method, when muting is applied to PUSCH, only scheduling that satisfies the following conditions can be determined to be valid. Here, can always be an even number.

[0443]

[0444] Here can be a non-negative integer value. That is, the terminal is It can be scheduled, but It cannot be scheduled. The above condition is half the size of the DFT ( It is determined that a DFT size is valid only if the DFT size corresponding to ) is included in the existing DFT size.

[0445] In the second method, when muting is applied to PUSCH, the terminal, existing scheduling conditions ( , It can report to the base station whether processing is possible with a non-negative integer value). The above reporting may be included in the terminal capability report of the terminal. If the terminal reports that it has the above capability, the base station reports to the terminal the existing scheduling conditions ( , A PUSCH with muting applied can be scheduled as a non-negative integer value. If the terminal reports that it lacks the above capability, the base station provides the terminal with new scheduling conditions PUSCH with muting applied can be scheduled as a non-negative integer value. In other words, the terminal One may not expect that is odd. The terminal If is odd, the above scheduling information is determined to be invalid, and the transmission of the PUSCH may not be performed. As another example, if CP-OFDM-based PUSCH transmission (transform precoding not applied) and DFT-s-OFDM-based PUSCH transmission (transform precoding applied) are configured for the terminal, the number of scheduled PRBs If is odd, the above PUSCH can be transmitted based on CP-OFDM (transform precoding not applied).

[0446] In the third method, when the terminal determines whether muting is applied to PUSCH, The number of can be considered. More specifically, If is even, muting can be applied to PUSCH. However, If is odd, muting may not be applied to the PUSCH. For example, muting to the PUSCH may be indicated via a higher-layer signal or DCI. The terminal determines whether to apply the muting symbol to the PUSCH. It can be determined based on. Therefore, even if muting is instructed If is odd, muting may not be applied.

[0447] <Second Embodiment: OFDM Signal Generation Using Identical DFT Size>

[0448] In one embodiment of the present disclosure, the terminal can generate a DFT-s-OFDM signal using the same DFT size.

[0449] The DFT size used is the number of all subcarriers included in the scheduled PUSCH ( It can be equal to ). The above DFT size can be applied to all OFDM symbols of the scheduled PUSCH.

[0450] FIGS. 16a and 16b are diagrams for generating a DFT-S OFDM signal according to a second embodiment. FIG. 16a is a diagram for generating a DFT-S OFDM signal when muting is not applied. FIG. 16b is a diagram for generating a DFT-S OFDM signal when muting is applied.

[0451] According to the second embodiment, when muting is applied to PUSCH, the Transform precoding block can perform the following operations.

[0452] Layer-mapped signal Transmission precoding can be applied through the Transform precoding block. This can be applied only when generating the DFT-s-OFDM signal.

[0453] Layer-mapped signal PTRS can be added to.

[0454] If PTRS is not added, It could be.

[0455] If PTRS is added, Is It can be divided into sets, and the set In The values ​​include dog values. The above values ​​are It can be mapped to. Here, And, is. And PTRS is It can be included in. The value of m is described later. If OFDM symbol If this PTRS is included, and OFDM symbol If this PTRS is not included, It could be. If OFDM symbol If muting is applied to, and, if OFDM symbol If muting is not applied to, It could be.

[0456] It can be divided into L sets. And each set can be transmitted in a single OFDM symbol. Each set includes A value or Can include values. L sets can be divided as follows depending on the position of the muting symbol.

[0457] ,

[0458] Here, The value of can be determined as follows.

[0459]

[0460] in other words, The value of may be determined by the position of the UL muting symbol. For example, let's assume that OFDM symbols 0 through 7 (indexed excluding DMRS symbols) are scheduled on PUSCH, and the UL resource muting symbols are OFDM symbol 1 and OFDM symbol 5. In this case, It can be determined as follows.

[0461]

[0462] (The UL muting symbol did not exist prior to OFDM symbol 1)

[0463] (Prior to OFDM Symbol 2, there was one UL muting symbol)

[0464] (Prior to OFDM Symbol 3, there was one UL muting symbol)

[0465] (Prior to OFDM Symbol 4, there was one UL muting symbol)

[0466] (Prior to OFDM Symbol 5, there was one UL muting symbol)

[0467] (Prior to OFDM symbol 6, there were two UL muting symbols)

[0468] (Prior to OFDM Symbol 7, there were two UL muting symbols)

[0469] (Prior to OFDM Symbol 8, there were two UL muting symbols)

[0470] Therefore, L sets can be as follows.

[0471] ( (Including dog values)

[0472] ( (Including dog values)

[0473] ( (Including dog values)

[0474] ( (Including dog values)

[0475] ( (Including dog values)

[0476] ( (Including dog values)

[0477] ( (Including dog values)

[0478] ( (Including dog values)

[0479] is the scheduled PUSCH OFDM symbol (excluding DMRS symbols) It can be transmitted in the (th OFDM symbol).

[0480] The terminal is the OFDM symbol of the scheduled PUSCH Corresponding to Transform precoding can be performed on the scheduled PUSCH OFDM symbols Different formulas may be applied depending on whether Muting is applied or not.

[0481] Scheduled PUSCH OFDM symbols If Muting is not applied, Transform precoding can be performed as in Equation 7.

[0482] [Mathematical Formula 7]

[0483]

[0484] A set containing dog values is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be several sample values.

[0485] Scheduled PUSCH OFDM symbols When Muting is applied, Transform precoding can be performed as shown in Equation 8.

[0486] [Mathematical Formula 8]

[0487]

[0488] Here, the OFDM symbol of the scheduled PUSCH Since Muting is applied to, ...can be repeated. That is, When saying that, the repeated thing is It can be. In each iteration, w=[1, 1] or w=[1, -1] can be multiplied. If w=

[0011] is applied, And, if w=[1, -1] is applied, It could be.

[0489] w=

[0011] or w=[1 -1] can be called an orthogonal cover code. One of the two orthogonal cover codes can be selected by the terminal according to the muting setting from the base station. For example, if the muting setting is a comb-2 pattern and odd subcarriers are muted, w=

[0011] can be selected, and if the muting setting is a comb-2 pattern and even subcarriers are muted, w=[1 -1] can be selected.

[0490] A set containing dog values OCC spreading is performed, A set containing dog values inside This can be generated. The above set can be used as input values ​​for the DFT. is the output value of the DFT in the frequency domain. There can be several sample values.

[0491] Referring to Equation 8 of the second embodiment, the terminal can perform frequency axis muting using OCC spreading. Equation 8 is an example, and the second embodiment can be implemented in other ways.

[0492] For example, the above L sets OCC spreading can be applied to the set corresponding to the index to which the muting symbol is to be applied. More specifically, the index to which the muting symbol is to be applied When saying, or It is possible. OCC spreading may not be applied to the set corresponding to the index to which muting symbols are not applied. More specifically, the index to which muting symbols are not applied When saying, It may be. The terminal is the above Set or The next value can be obtained by arranging the values ​​included in the set in ascending order of the set's indices. For reference, the above Set or The values ​​included in the set are am.

[0493]

[0494] Using mathematical formula 2, the transform precoding block can be performed. A set containing dog values is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be several sample values.

[0495] Transmit precoded signal It can be precoded through a Precoding block. DFT-s-OFDM can only support a single layer. Therefore, It can be. Here, p0 can be the index of the antenna port where PUSCH is transmitted.

[0496] Precoded signal It can be mapped to Virtual Resource Blocks (VRBs). First, the transmit power of PUSCH can be multiplied to the precoded signal. The transmit power can be multiplied differently depending on the OFDM symbol. For example, the precoded signal When transmitted in OFDM symbols where muting is not applied, the transmit power of PUSCH This can be multiplied. Precoded signal When transmitted in OFDM symbols with muting applied, the transmit power of PUSCH This can be multiplied.

[0497] And it can be mapped to the REs of the scheduled VRBs. The indices of the REs are It can be represented as, is the subcarrier index, and can be an index of an OFDM symbol (excluding DMRS symbols). The following conditions may be followed during mapping.

[0498] - REs must be included in VRBs scheduled for PUSCH transmission.

[0499] - These are REs excluding the REs corresponding to DM-RS for DM-RS, PT-RS, or other concurrently scheduled terminals.

[0500] <Third Embodiment: Performing Time-axis Muting>

[0501] In a third embodiment of the present disclosure, muting can be applied to the time axis (signal before the transform precoding block). This may have the following advantages compared to the first and second embodiments, which apply muting to the frequency axis (signal after the transform precoding block).

[0502] As an advantage, the terminal may not require separate complex computations. Referring to the first and second embodiments, if muting is applied in the frequency axis, different DFT sizes or OCC spreading can be used. This may cause additional computational complexity for the terminal. However, if muting is applied in the time axis, the additional complexity of the terminal may be negligible or small.

[0503] Another advantage is that the signal quality (Peak-to-Average-Power ratio, PAPR) of the terminal's transmitted signal can be improved. When muting is applied in the frequency domain, the signal quality (PAPR) may vary depending on the muting pattern applied in that domain. However, a transmitted signal that has muting applied in the time domain and undergone transform precoding can exhibit superior signal quality (PAPR) characteristics.

[0504] FIGS. 17a and 17b are diagrams for generating a DFT-S OFDM signal according to a third embodiment. FIG. 17a is a diagram for generating a DFT-S OFDM signal when muting is not applied. FIG. 17b is a diagram for generating a DFT-S OFDM signal when muting is applied.

[0505] According to the third embodiment, the method for performing time-axis muting is as follows.

[0506] L sets of the second embodiment Muting can be applied to the set corresponding to the index to which the muting symbol is to be applied. More specifically, the index to which the muting symbol is to be applied When saying, or It is possible. Muting may not be applied to the set corresponding to the index to which the muting symbol is not applied. More specifically, the index to which the muting symbol is not applied When saying, It may be. The terminal is the above Set or The next value can be obtained by arranging the values ​​included in the set in ascending order of the set's indices. For reference, the above Set or The values ​​included in the set are am.

[0507]

[0508] Using mathematical formula 2, the transform precoding block can be performed. A set containing dog values is the input value of the DFT in the time domain. It is a sample value, and is the output value of the DFT in the frequency domain. There can be several sample values.

[0509] <4th Embodiment: PTRS Location Determination According to Muting>

[0510] One embodiment of the present disclosure relates to a method for determining the PTRS location of a terminal when PTRS is included in a PUSCH transmitted as a DFT-s-OFDM signal. When a muting symbol is applied, it is necessary to transmit PTRS in the muting symbol. This is because if PTRS is not transmitted in the muting symbol, phase noise may not be estimable or compensated. However, in the case of DFT-s-OFDM, since PTRS is included in the time axis (signal prior to the transform precoding block) and DFT operations are performed, PTRS is transmitted across the entire band (all subcarriers) of the scheduled PUSCH. Therefore, when muting is applied, PTRS transmitted from some subcarriers cannot be transmitted, so PTRS performance degradation may be expected.

[0511] For symbols to which Muting has not been applied, PTRS may be included as follows.

[0512] First, the terminal is in the PTRS group ( ) and number of samples per PTRS ( ) can be set, instructed, or determined from the base station. The said value may be determined according to the number of PRBs scheduled in PUSCH. More specifically, the terminal receives N from the base station RB0 , NRB1 , N RB2 , N RB3 , N RB4 A value can be set. The above value can have one integer value between 1 and 276, and N RB0 < N RB1 < N RB2 < N RB3 < N RB4 The conditions must be satisfied. The terminal, based on the above setting value and the number of PRBs of the scheduled PUSCH, PTRS group ( ) and number of samples per PTRS ( ) can be determined. This can be determined based on Table 19.

[0513] [Table 19]

[0514]

[0515] Based on the above values, the terminal can generate a PTRS signal as shown in Equation 9.

[0516] [Mathematical Formula 9]

[0517]

[0518] Here, c(i) is a pseudo-random sequence, and is the number of samples per PTRS ( If ) is 2, then [w(0) w(1)] =

[0011] or [w(0) w(1)] = [1 -1], and is the number of samples per PTRS ( If ) is 4, [w(0) w(1) w(2) w(3)] = [1 1 1 1] or [w(0) w(1) w(2) w(3)] = [1 -1 1 -1] or [w(0) w(1) w(2) w(3)] = [1 1 -1 -1] or [w(0) w(1) w(2) w(3)] = [1 -1 -1 1].

[0519] Layer-mapped signal PTRS can be added to it. The signal with added PTRS is {} and, here are the PTRS samples is corresponding to the transmission power value Multiply by, It can be included in.

[0520] Here, m can be determined according to Table 20.

[0521] [Table 20]

[0522]

[0523] Referring to Table 20, the terminal PTRS r(m') When placed in, the number of subcarriers scheduled in PUSCH ( ) can be used. The number of subcarriers scheduled for the symbol to which Muting is applied is Therefore, the number of subcarriers scheduled for symbols to which muting does not apply It can be half of. Therefore, based on the table above, PTRS r(m') It cannot be placed in. Methods to solve this are disclosed.

[0524] [Method 1: No Muting Symbols Applied to PTRS Symbols in DFT-s-OFDM]

[0525] In one method of the present disclosure, if a PTRS symbol and a Muting symbol overlap in a DFT-s-OFDM signal, the terminal may apply PTRS and not apply muting. That is, even if the terminal receives a Muting symbol from the base station and is instructed to apply (or activate) said muting symbol, the terminal may not apply muting if said muting symbol and a PTRS symbol overlap. That is, all subcarriers of the PUSCH scheduled in said symbol may be used for data or reference signal transmission. Accordingly, PTRS is a PTRS group (determined in Table 20) ) and number of samples per PTRS ( It can be generated based on ) and Table 19.

[0526] [Method 2: PTRS not applied to Muting symbols in DFT-s-OFDM]

[0527] In one method of the present disclosure, when a PTRS symbol and a Muting symbol overlap in a DFT-s-OFDM signal, the terminal may apply muting and not apply PTRS. That is, even if the terminal receives a Muting symbol from a base station and is instructed to apply (or activate) the muting symbol, if the muting symbol and the PTRS symbol overlap, the terminal may not transmit PTRS on the symbol. That is, the terminal may apply a muting pattern (e.g., a comb-2 pattern) to the symbol and map data to an unmuted subcarrier (or RE). Here, PTRS may not be mapped to the unmuted subcarrier (or RE).

[0528] [Method 3: When applying PTRS to the Muting symbol of DFT-s-OFDM Created based on

[0529] In one method of the present disclosure, when a PTRS symbol and a Muting symbol overlap in a DFT-s-OFDM signal, the terminal may apply muting and PTRS simultaneously. That is, the terminal receives a Muting symbol from a base station and is instructed to apply (or activate) the muting symbol, and when the muting symbol and the PTRS symbol overlap, the terminal may apply a muting pattern (e.g., a comb-2 pattern) to the symbol and map data or PTRS to the unmuted subcarrier (or RE). Here, the mapping of PTRS to the unmuted subcarrier (or RE) may be determined by the following process.

[0530] r(m') is It can be mapped to. Here, the value of m mapped is the PTRS group ( ) and number of samples per PTRS ( It can be determined according to ). More specifically, for non-muting symbols, m can be determined based on Table 20, and for muting symbols, m can be determined based on Table 21.

[0531] [Table 21]

[0532]

[0533] For reference, Tables 20 and 21 can be combined as in Table 22. Here, OFDM symbol If muting is not applied to and OFDM symbol If muting is applied to It could be.

[0534] [Table 22]

[0535]

[0536] Referring to Tables 21 and 22, PTRS r(m') When mapping to, the number of PRBs scheduled on PUSCH is N RB In that case, for muting symbols, it can be equivalent to having only half of the PRBs scheduled. Therefore, the PTRS group of muting symbols ( ) and number of samples per PTRS ( ) is 2*N RB It can be determined based on. More specifically, PUSCH PTRS group including muting symbols ( ) and number of samples per PTRS ( ) can be determined based on one of the following methods.

[0537] In the first method, the number of PRBs scheduled in PUSCH is N RBBased on Table 19, PTRS group ( ) and number of samples per PTRS ( ) can be determined. That is, PTRS group ( ) and number of samples per PTRS ( The value can be applied commonly to symbols that are not muted and symbols that are muted.

[0538] In the second method, when muting is applied to PUSCH, the scaled value M*N of the number of PRBs scheduled on PUSCH RB Based on Table 23, PTRS group ( ) and number of samples per PTRS ( ) can be determined. Here, M=2 (twice the value, 2*N RB ) or M=1 / 2 (half value N RB / 2) It can be. That is, PTRS group ( ) and number of samples per PTRS ( The ) value can be applied commonly to symbols that are not muted and symbols that are muted. Here, Table 23 may be as follows.

[0539] [Table 23]

[0540]

[0541] In the third method, for symbols where muting is not applied to PUSCH, the number of PRBs N scheduled on PUSCH. RB Based on Table 19, PTRS group ( ) and number of samples per PTRS ( ) can be determined, and for symbols where muting is applied to PUSCH, the scaled value M*N of the number of PRBs scheduled on PUSCH. RB Based on Table 23, PTRS group ( ) and number of samples per PTRS ( ) can be determined. That is, PTRS group ( ) and number of samples per PTRS ( The value of ) can be determined differently for symbols that are not muted and symbols that are muted.

[0542] PTRS included It can be transmitted via PUSCH by applying a transmit precoding block based on at least one method of the first embodiment, the second embodiment, and the third embodiment.

[0543] In the case of a PUSCH transmitted as a CP-OFDM signal, the index of the subcarrier (or the index of the RE) occupied by the PTRS may vary depending on the index of the DM-RS antenna port of the PUSCH. For example, Table 24 is a table showing the index of the subcarrier (or the index of the RE) occupied by the PTRS.

[0544] Referring to Table 24, if DMRS configuration type 1 is set and the DM-RS antenna ports are 0, 1, 8, or 9, determine the RE index The value of can be an even number. If DMRS configuration type 1 is set, and the DM-RS antenna ports are 2, 3, 10, or 11, determines the RE index. The value of can be odd.

[0545] Determining the RE index Based on the value of, the RE to which the PT-RS of the PUSCH transmitted as a CP-OFDM signal is transmitted can be determined as follows.

[0546] [Mathematical Formula 10]

[0547]

[0548] Here is a value set by the base station as one of 2 or 4, and It can be an RNTI value in DCI format that schedules. k is the index of the subcarrier to which the PTRS is transmitted. If the value is odd, k is odd, and If the value is even, k can be even. Therefore, PTRS can be transmitted on a subcarrier corresponding to an odd number or an even number, depending on the index of the DMRS antenna port.

[0549] In one method of the present disclosure, when PUSCH is transmitted via CP-OFDM and includes PTRS, the frequency axis position of the comb-2 muting pattern can be determined according to the DMRS antenna port. More specifically, corresponding to the DMRS antenna port If the value is odd, the comb-2 muting pattern can be applied to the subcarriers corresponding to even numbers. That is, PTRS can be transmitted on subcarriers with odd indices of PUSCH, and muting can be applied to subcarriers with even indices. Therefore, PTRS and muting may not overlap on a single subcarrier. Corresponding to the DMRS antenna port If the value is even, the comb-2 muting pattern can be applied to the subcarriers corresponding to the odd values. That is, PTRS can be transmitted to the subcarriers of the even indices of PUSCH, and muting can be applied to the subcarriers of the odd indices. Therefore, PTRS and muting may not overlap on a single subcarrier.

[0550] In one method of the present disclosure, the frequency axis position of the comb-2 muting pattern can be set for each DMRS antenna port. That is, a first comb-2 muting pattern (e.g., muting applied to subcarriers of even indices) can be set for a first DMRS antenna port index, and a second comb-2 muting pattern (e.g., muting applied to subcarriers of odd indices) can be set for a second DMRS antenna port index. A terminal can apply muting using a comb-2 pattern corresponding to the indicated DMRS antenna port.

[0551] In one method of the present disclosure, the frequency axis position of a comb-2 muting pattern may be indicated in a time domain resource assignment (TDRA) row of a DCI format that schedules a PUSCH. More specifically, a corresponding comb-2 muting pattern (e.g., whether to apply muting to even-indexed subcarriers or to odd-indexed subcarriers) may be set in each TDRA row. A terminal may obtain the muting pattern from the TDRA row of the DCI format that schedules a PUSCH. The pattern may be applied to a PUSCH.

[0552] [Table 24]

[0553]

[0554] <5th Embodiment: Almost Contiguous Allocation>

[0555] In order to satisfy the transmission signal quality (PAPR) of the CP-OFDM signal, the terminal may allow PUSCH transmission only when the following conditions are satisfied. This can be referred to as the Almost contiguous allocation condition.

[0556] [Table 25]

[0557]

[0558] In the case of CP-OFDM, the terminal may not transmit the scheduled PUSCH if the above Almost contiguous allocation condition is not satisfied. If the above Almost contiguous allocation condition is satisfied, the terminal may add a value corresponding to Equation 11 to the maximum power reduction value to satisfy the transmission signal quality (PAPR). That is, N RB_gap / N RB_alloc Depending on the value of, more transmission power reduction can be performed.

[0559] [Mathematical Formula 11]

[0560] CEIL{ 10 log 10 (1 + N RB_gap / N RB_alloc ), 0.5} dB,

[0561] N in PUSCH RB One PRB or N RB Let us assume that 12 subcarriers are scheduled. If muting is applied to PUSCH, the number of subcarriers used for data transmission in the muting symbol is N RB It can be equivalent to *12 / 2, which means the number of scheduled PRBs is N RB It may be equal to / 2. Therefore, the Almost contiguous allocation condition of the terminal or the corresponding maximum power reduction value may change depending on whether muting is present or not. More specifically, the Almost contiguous allocation condition or the corresponding maximum power reduction value may be determined according to at least the following conditions.

[0562] - In the first method, when determining the almost contiguous allocation condition of the terminal or the corresponding maximum power reduction value, NRB_alloc (the total number of allocated RBs) is N RB_alloc It can be changed to / 2. That is, depending on the Muting pattern, it may be determined that only half of the scheduled PRBs are scheduled, and the above value (N RB_alloc Based on / 2), the Almost contiguous allocation condition or the corresponding maximum power reduction value can be determined.

[0563] - By the second method, when determining the almost contiguous allocation condition of the terminal or the corresponding maximum power reduction value, N RB_gap (the total number of unallocated RBs) is N RB_gap + N RB_alloc It can be changed to / 2. That is, depending on the Muting pattern, among the scheduled PRBs, the unscheduled (muted) subcarriers are N RB_gap It can be included in. That is, N RB_alloc / 2 is N RB_gap Added to, and N RB_gap + N RB_alloc Based on / 2, the Almost contiguous allocation condition or the corresponding maximum power reduction value can be determined.

[0564] - By the third method, when determining the Almost contiguous allocation condition of the terminal or the corresponding maximum power reduction value, N RB_alloc (the total number of allocated RBs) is N RB_alloc Changed to / 2, and N RB_gap (the total number of unallocated RBs) is N RB_gap + N RB_alloc It can be changed to / 2. That is, depending on the Muting pattern, it can be determined that only half of the scheduled PRBs are scheduled, and N RB_allocInstead of N RB_alloc / 2 can be used. Also, depending on the muting pattern, among the scheduled PRBs, the unscheduled (muted) subcarriers are N RB_gap It can be included in. That is, N RB_alloc / 2 is N RB_gap Added to, and N RB_gap Instead of N RB_gap + N RB_alloc / 2 can be used. Therefore, (N RB_alloc , N RB_gap Instead of ) (N RB_alloc / 2, N RB_gap + N RB_alloc Based on / 2), the Almost contiguous allocation condition or the corresponding maximum power reduction value can be determined.

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

[0566] 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), memory (1820), and 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. Additionally, the processor (1830), the transceiver (1810), and the memory (1820) may be implemented as a single chip. Additionally, the processor (1830) may include at least one processor.

[0567] The transceiver (1810) collectively refers to a UE receiver and a 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 up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise amplification and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (1810), and the components of the transceiver (1810) are not limited to an RF transmitter and an RF receiver.

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

[0569] The processor (1830) can control a series of processes to operate the terminal. 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.

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

[0571] 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), memory (1920), and 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 those described above. Additionally, the processor (1930), the transceiver (1910), and the memory (1920) may be implemented as a single chip. Additionally, the processor (1930) may include at least one processor.

[0572] 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 transmitted signal and an RF receiver for low-noise amplification and down-converting the frequency of a received signal. However, this is merely an example of the transceiver (1910), and the components of the transceiver (1910) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1910) can receive a signal through a wireless channel and output it to a processor (1930), and transmit the signal output from the processor (1930) through a wireless channel.

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

[0574] The processor (1930) can control a series of processes to enable the base station to operate as described above. For example, the transceiver (1910) can receive a data signal including a control signal transmitted by a terminal, and the processor (1930) can determine the result of receiving the control signal and the data signal transmitted by the terminal.

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

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

[0577] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0578] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0579] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0580] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure with parts of another embodiment. For example, a base station and a terminal may be operated by combining parts of the first embodiment and the second embodiment of the present disclosure. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as TDD LTE systems, 5G, or NR systems.

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

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

[0583] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the invention.

Claims

1. A method performed by a terminal in a wireless communication system, A step of receiving configuration information regarding a muting resource via an RRC (radio resource control) signal from a base station; A step of identifying whether muting is applied to OFDM (orthogonal frequency division multiplexing) symbols allocated for PUSCH (physical uplink shared channel) transmission based on the above configuration information; Based on whether the above muting is applied, a set corresponding to the OFDM symbol Step to determine; and The above three Based on, it includes the step of performing transform precoding for the above OFDM symbol, and If the muting is not applied to the above OFDM symbol, the above set silver Includes dog values, When the muting is applied to the above OFDM symbol, the set silver A method containing the values ​​of.

2. In paragraph 1, the step of performing the transform precoding is, If the above muting is not applied to the above OFDM symbol, Perform transform precoding based on, and When the above muting is applied to the above OFDM symbol, It performs transform precoding based on, The above set A method representing a symbol for.

3. In paragraph 1, the above three silver It includes dog symbols, The above three If PTRS (phase tracking reference signal) samples are included, is 1, and The above three If PTRS samples are not included, is 0, and represents the number of PTRS groups, is a method representing the number of PTRS samples by PTRS group.

4. In Paragraph 1, If the muting is not applied to the above OFDM symbol, for the transmit power of the PUSCH to the signal including the transform-precoded OFDM symbol As this is multiplied, When the muting is applied to the above OFDM symbol, for the transmit power of the PUSCH to the signal including the transform-precoded OFDM symbol This multiplying method.

5. In paragraph 1, the above three If PTRS samples are included, The index m of the above PTRS sample is and It is determined based on, represents the number of PTRS groups, is a method representing the number of PTRS samples by PTRS group.

6. In Paragraph 5, ga is 2, and In the case of this 2, the above index m is And, and is, ga is 2, and In the case of this 4, the above index m is And, is, ga is 4 and, In the case of this 2, the above index m is And, and is, ga is 4 and, In the case of this 4, the above index m is And, is, ga is 8 and, In the case of this 4, the above index m is And, Person, method.

7. In Paragraph 1, The method further includes the step of performing VRB (virtual resource block) mapping based on the above transform-precoded OFDM symbols, and A method in which a muted RE (resource element) in the above transform-precoded OFDM symbol is excluded from VRB mapping.

8. A method performed by a base station in a wireless communication system, A step of transmitting configuration information regarding a muting resource to a terminal via an RRC (radio resource control) signal, wherein the configuration information indicates an OFDM symbol to which muting is applied among a plurality of OFDM (orthogonal frequency division multiplexing) symbols allocated for PUSCH (physical uplink shared channel) transmission; and Set corresponding to OFDM symbols The method includes the step of receiving a signal containing OFDM symbols transformed and precoded based on, If the muting is not applied to the above OFDM symbol, the above set silver Includes dog values, When the muting is applied to the above OFDM symbol, the set silver A method containing the values ​​of.

9. In a terminal in a wireless communication system, Transmitter / receiver; and It includes at least one processor connected to the above-mentioned transmitting and receiving unit, and the at least one processor is: Receive configuration information regarding muting resources from the base station via RRC (radio resource control) signals, and Based on the above configuration information, it identifies whether muting is applied to OFDM (orthogonal frequency division multiplexing) symbols allocated for PUSCH (physical uplink shared channel) transmission, and Based on whether the above muting is applied, a set corresponding to the OFDM symbol Decide, The above three Based on this, transform precoding for the above OFDM symbols is performed, and If the muting is not applied to the above OFDM symbol, the above set silver Includes dog values, When the muting is applied to the above OFDM symbol, the set silver A terminal containing values.

10. In paragraph 9, the above at least one processor, If the above muting is not applied to the above OFDM symbol, Perform transform precoding based on, and When the above muting is applied to the above OFDM symbol, It performs transform precoding based on, The above set A terminal representing a symbol for.

11. In Paragraph 9, the above three silver It includes dog symbols, The above three If PTRS (phase tracking reference signal) samples are included, is 1, and The above three If PTRS samples are not included, is 0, and represents the number of PTRS groups, is a terminal representing the number of PTRS samples per PTRS group.

12. In Paragraph 9, If the muting is not applied to the above OFDM symbol, for the transmit power of the PUSCH to the signal including the transform-precoded OFDM symbol As this is multiplied, When the muting is applied to the above OFDM symbol, for the transmit power of the PUSCH to the signal including the transform-precoded OFDM symbol This multiplying, terminal.

13. In Paragraph 9, the above three If PTRS samples are included, The index m of the above PTRS sample is and It is determined based on, represents the number of PTRS groups, is a terminal representing the number of PTRS samples per PTRS group.

14. In Paragraph 13, ga is 2, and In the case of this 2, the above index m is And, and is, ga is 2, and In the case of this 4, the above index m is And, is, ga is 4 and, In the case of this 2, the above index m is And, and is, ga is 4 and, In the case of this 4, the above index m is And, is, ga is 8 and, In the case of this 4, the above index m is And, Person, terminal.

15. In paragraph 9, the above at least one processor, VRB (virtual resource block) mapping is performed based on the above transform-precoded OFDM symbols, and A terminal in which the RE (resource element) to which muting has been applied in the above transform-precoded OFDM symbol is excluded from VRB mapping.

Images