Method and device for changing dynamic waveform in wireless communication system

The integration of a waveform change indicator in DCI within the terminal and base station system dynamically adjusts the PUSCH waveform in response to bandwidth changes, addressing efficiency and adaptability challenges in high-frequency bands, thus enhancing data transmission for advanced mobile communication systems.

WO2024237595A1PCT designated stage expired Publication Date: 2024-11-21SAMSUNG ELECTRONICS CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006368
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-10
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in dynamically changing waveforms to efficiently manage bandwidth and ensure reliable data transmission, particularly in high-frequency bands, which affects the performance of 5G and emerging 6G mobile communication technologies.

Method used

The method involves a terminal and base station system where a waveform change indicator is included in downlink control information (DCI) to dynamically adjust the waveform of the physical uplink shared channel (PUSCH) based on indicated bandwidth changes, allowing for seamless transmission using either CP-OFDM or DFT-S-OFDM waveforms, depending on the DCI settings.

Benefits of technology

This approach enhances data transmission efficiency and adaptability, improving coverage and throughput in high-frequency bands by allowing waveform adjustments in response to changing bandwidth conditions, thereby supporting advanced services and future communication standards.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006368_21112024_PF_FP_ABST
    Figure KR2024006368_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Provided is a method comprising the steps of: receiving, from a base station, information indicating through higher layer signalling that a waveform change indicator for a PUSCH is included in DCI; receiving the DCI for scheduling the PUSCH from the base station, the DCI including the waveform change indicator; and transmitting uplink data on the PUSCH to the base station on the basis of the DCI, wherein the PUSCH is transmitted on the basis of CP-OFDM when the DCI includes an FDRA field and the FDRA field corresponds to resource allocation type 0.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for dynamic waveform change in wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and device for a terminal to dynamically change a waveform to transmit and receive data.

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

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

[0004] Currently, the services that 5G mobile communication technology was intended to support

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

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

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

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

[0009] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

[0010] The disclosed embodiment aims to provide a device and method capable of effectively providing a service in a mobile communication system. Specifically, when a bandwidth portion change is indicated through downlink control information (DCI) and a dynamic waveform change field is set, a method and device for determining a waveform of a physical uplink shared channel (PUSCH) in the indicated bandwidth portion and transmitting the PUSCH are proposed.

[0011] According to the invention of the present disclosure, at least the following methods may be considered.

[0012] As a first method, the terminal can be configured with a default waveform for use in each BWP. If this occurs, the terminal can transmit an uplink signal using the default waveform.

[0013] As a second method, the terminal can set the waveform corresponding to '0' in the 1-bit dynamic waveform change field as the default waveform, and set the waveform corresponding to '1' to a waveform other than the default waveform. Accordingly, in the above case, the terminal can determine the value of the 1-bit waveform change field as '0' through zero-padding and transmit the default waveform.

[0014] According to at least one embodiment of the present disclosure, a method performed by a terminal of a communication system comprises the steps of: receiving information indicating that a waveform change indicator for a physical uplink shared channel (PUSCH) is included in downlink control information (DCI) through upper layer signaling from a base station; receiving, from the base station, the DCI for scheduling the PUSCH, the DCI including the waveform change indicator; transmitting uplink data on the PUSCH to the base station based on the DCI, wherein when the DCI includes a frequency domain resource assignment (FDRA) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is characterized in that it is transmitted based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

[0015] In addition, in a method performed by a base station of a communication system, the method comprises: a step of transmitting information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling to a terminal; a step of transmitting the DCI for scheduling the PUSCH to the terminal, the DCI including the waveform change indicator; and a step of receiving uplink data from the terminal on the PUSCH scheduled by the DCI, wherein when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is characterized in that it is received based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

[0016] In addition, in a terminal of a communication system, a transceiver; receives information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling from a base station, receives the DCI for scheduling the PUSCH from the base station, the DCI includes the waveform change indicator, and includes a control unit configured to transmit uplink data on the PUSCH to the base station based on the DCI, and when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is characterized in that it is transmitted based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

[0017] In addition, in a base station of a communication system, a transceiver; and a control unit configured to transmit information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling to a terminal, transmit the DCI for scheduling the PUSCH to the terminal, the DCI including the waveform change indicator, and receive uplink data from the terminal on the PUSCH scheduled by the DCI, wherein when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is characterized in that it is received based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

[0018] The disclosed embodiments provide devices and methods capable of effectively providing services in a mobile communication system. Specifically, when a bandwidth portion change is indicated through DCI and a dynamic waveform change field is set according to at least one embodiment described in the present disclosure, a terminal and a base station can determine a PUSCH waveform in the indicated bandwidth portion and transmit the PUSCH.

[0019] FIG. 1 is a diagram illustrating an example of the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.

[0020] FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system.

[0021] Figure 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system in a 5G system.

[0022] FIG. 4 is a diagram illustrating an example of a control region (CORESET) in which a downlink control channel is transmitted in a 5G communication system.

[0023] FIG. 5 is a diagram illustrating an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system.

[0024] FIG. 6 is a diagram illustrating an example of frequency-axis resource allocation of PDSCH or PUSCH in a 5G system.

[0025] FIG. 7 is a diagram illustrating an example of time axis resource allocation of PDSCH in a 5G system.

[0026] FIG. 8 is a diagram illustrating an example of time-domain resource allocation according to the subcarrier spacing of a data channel and a control channel in a 5G system.

[0027] FIG. 9 is a diagram illustrating an example of reception of a DCI format indicating a BWP change.

[0028] Figure 10 is a diagram illustrating an example of the configuration of an FDRA field and a dynamic waveform change field.

[0029] FIG. 11 is a drawing illustrating an example of an operation performed by a terminal of the present disclosure.

[0030] FIG. 12 is a diagram illustrating an example of an operation performed by a base station of the present disclosure.

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

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

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

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

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

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

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

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

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

[0040] Here, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

[0042] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (orthogonal frequency division multiplexing, which can be used interchangeably with CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing)) method in the downlink, and the SC-FDMA (single carrier frequency division multiple access, which can be used interchangeably with DFTS-OFDM (discrete Fourier transform-spread-orthogonal frequency division multiplexing)) method in the uplink. The above multiple access method typically allocates and operates the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so that orthogonality is established, thereby enabling the data or control information of each user to be distinguished.

[0043] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

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

[0045] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the Internet of Things, mMTC requires support for large-scale terminal connection within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The Internet of Things provides communication functions by attaching various sensors and various devices, so a large number of terminals (e.g., 1,000,000 terminals / km) are required within a cell. 2 ) must be able to support. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements of buildings, due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be composed of low-cost terminals, and because it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

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

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

[0048] Hereinafter, a / b can be understood as at least one of a or b.

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

[0050] FIG. 1 is a diagram illustrating an example of the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.

[0051] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can constitute one resource block (RB, 104). One subframe (110) on the time axis can include multiple OFDM symbols (102). For example, the length of one subframe can be 1 ms.

[0052] FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system.

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

[0054] μ 0141011142022144043148084141601651432032

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

[0056] Figure 3 is a diagram illustrating an example of bandwidth portion settings in a 5G system.

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

[0058] BWP ::= SEQUENCE {bwp-Id BWP-Id,(bandwidth part identifier)locationAndBandwidth INTEGER (1..65536),(bandwidth part location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(subcarrier spacing)cyclicPrefix ENUMERATED { extended}(cyclic prefix)}

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

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

[0061] The terminal can receive the physical downlink shared channel (PDSCH) through the configured initial bandwidth portion, through which the SIB is transmitted. In addition to receiving the SIB, the initial bandwidth portion can also be used for other system information (OSI), paging, and random access.

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

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

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

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

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

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

[0068] μNR Slot length (ms)BWP switch delay T BWP (slots)Type 1 Note 1 Type 2 Note 1 011310.52520.253930.125618Note 1: Depends on UE capability.Note 2: If the BWP switch involves changing of SCS, the BWP switch delay is determined by the larger one between the SCS before BWP switch and the SCS after BWP switch.

[0069] The requirement for bandwidth part change delay time supports type 1 or type 2 depending on the capability of the terminal. The terminal can report the type of bandwidth part delay time that it can support to the base station. According to the requirement for bandwidth part change delay time mentioned above, if the terminal receives DCI including a bandwidth part change indicator in slot n, the terminal changes to a new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWPIt can be completed at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. If the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules a data channel with a new bandwidth portion, in the method of determining time domain resource allocation for the data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal determines that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP ) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

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

[0071] Next, we will explain the SS / PBCH block (synchronization signal / physical broadcast channel block, SS / PBCH block) in the 5G system.

[0072] An SS / PBCH block may refer to a physical layer channel block consisting of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH. Specifically, it is as follows.

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

[0074] - SSS: It serves as a 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.

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

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

[0077] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH and set control region #0 (control resource set #0, CORESET #0, which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (demodulation reference signal) transmitted in control region #0 are quasi-co-located (QCL). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (random access channel)-related configuration information required for initial access from the received system information. The terminal can transmit a PRACH (physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

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

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

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

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

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

[0083] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment - [ ] bits- Time domain resource assignment - X bits- Frequency hopping flag - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- TPC command for scheduled PUSCH - [2] bits- UL / SUL indicator (uplink / supplementary UL indicator) - 0 or 1 bit

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

[0085] - Carrier indicator - 0 or 3 bits- UL / SUL indicator - 0 or 1 bit- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1, or 2 bits- Frequency domain resource assignment- For resource allocation type 0 bits- For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- 1st downlink assignment index (first downlink allocation index)- 1 or 2 bits○ 1 bit for semi-static HARQ-ACK codebook (semi-static HARQ-ACK In case of codebook);○ 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook(When dynamic HARQ-ACK codebook is used with single HARQ-ACK codebook).- 2nd downlink assignment index (2nd downlink assignment index) - 0 or 2 bits○ 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks(When dynamic HARQ-ACK codebook is used with two HARQ-ACK sub-codebooks);○ 0 bit otherwise.TPC command for scheduled PUSCH - 2 bits- SRS resource indicator (SRS resource indicator) -. or bits○ bits for non-codebook based PUSCH transmission; ○ bits for codebook based PUSCH transmission. - Precoding information and number of layers - up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association (Phase tracking reference signal-demodulation reference signal relationship) - 0 or 2 bits - beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0 or 1 bit

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

[0087] - Identifier for DCI formats - [1] bit- Frequency domain resource assignment -[ ] bits- Time domain resource assignment - X bits- VRB-to-PRB mapping - 1 bit.- Modulation and coding scheme - 5 bits- New data indicator - 1 bit- Redundancy version - 2 bits- HARQ process number - 4 bits- Downlink assignment index - 2 bits- TPC command for scheduled PUCCH - [2] bits- PUCCH resource indicator (physical uplink control channel, PUCCH) - 3 bits- PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ feedback timing indicator) - [3] bits

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

[0089] - Carrier indicator - 0 or 3 bits- Identifier for DCI formats - [1] bits- Bandwidth part indicator - 0, 1 or 2 bits- Frequency domain resource assignment○ For resource allocation type 0, bits○ For resource allocation type 1, bits- Time domain resource assignment -1, 2, 3, or 4 bits- VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.○ 0 bit if only resource allocation type 0 is configured;○ 1 bit otherwise.- PRB bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger - 0, 1, or 2 bits For transport block 1 (for the first transport block): - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits For transport block 2 (for the second transport block): - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports - 4, 5, or 6 bits- Transmission configuration indication - 0 or 3 bits- SRS request - 2 bits- CBG transmission information - 0, 2, 4, 6, or 8 bits- CBG flushing out information - 0 or 1 bit- DMRS sequence initialization - 1 bit.

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

[0091] FIG. 4 is a diagram illustrating an example of a control region (CORESET) in which a downlink control channel is transmitted in a 5G system. FIG. 4 illustrates an example in which two control regions (control region #1 (401), control region #2 (402)) are set within a UE bandwidth part (UE bandwidth part, 410) on the frequency axis and within one slot (420) on the time axis. The control regions (401, 402) can be set to specific frequency resources (403) within the entire UE bandwidth part (410) on the frequency axis. The time axis can be set to one or more OFDM symbols, which can be defined as the control region length (control resource set duration, 404). Referring to the example illustrated in FIG. 4, control region #1 (401) is set to a control region length of two symbols, and control region #2 (402) is set to a control region length of one symbol.

[0092] In the aforementioned 5G system, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, MIB, RRC signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 8.

[0093] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID' controlResourceSetId ControlResourceSetId,(Control domain identifier (Identity)) frequencyDomainResources BIT STRING (SIZE (45)),(Frequency axis resource allocation information) duration INTEGER (1..maxCoReSetDuration),(Time axis resource allocation information) cce-REG-MappingType CHOICE {(CCE-to-REG mapping method) interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},(REG bundle size) precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, interleaverSize ENUMERATED {n2, n3, n6}(interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL(Interleaved Shift)},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,(QCL setting information)tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}

[0094] In Table 8, the tci-StatesPDCCH (simply named TCI (transmission configuration indication) state) configuration information may include information on one or more SS / PBCH block indices or CSI-RS (channel state information reference signal) indices that are in a QCL relationship with the DMRS transmitted in the corresponding control region.

[0095] FIG. 5 is a diagram illustrating an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (resource element group, 503), and a REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (physical resource block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to constitute a downlink control channel allocation unit.

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

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

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

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

[0100] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,(search space identifier)controlResourceSetId ControlResourceSetId,(control space identifier)monitoringSlotPeriodicityAndOffset CHOICE {(monitoring slot level period)sl1 NULL,sl2 INTEGER (0..1),sl4 INTEGER (0..3),sl5 INTEGER (0..4),sl8 INTEGER (0..7),sl10 INTEGER (0..9),sl16 INTEGER (0..15),sl20 INTEGER (0..19)} OPTIONAL,duration(monitoring length) INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,(슬롘 내 나이스 심보)nrofCandidates SEQUENCE {(집성 별보 PDCCH 이리군 수)aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}},searchSpaceType CHOICE {(தமம்ப்புக்குக்க்கு திய்)-- Configures this search space as common search space (CSS) and DCI formats to monitor.common SEQUENCE {(공통이이국이)}ue-Specific SEQUENCE {(단말-특정이스국)-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},...}.

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

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

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

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

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

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

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

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

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

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

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

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

[0113] C-RNTI (cell RNTI): For terminal-specific PDSCH scheduling purposes

[0114] TC-RNTI (temporary cell RNTI): For terminal-specific PDSCH scheduling purposes

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

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

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

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

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

[0120] TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0121] TPC-PUCCH-RNTI (transmit power control for PUCCH (physical uplink control channel) RNTI): Used to indicate power control commands for PUCCH

[0122] TPC-SRS-RNTI (transmit power control for SRS(sounding reference signla) RNTI): Used to indicate power control commands for SRS

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

[0124] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

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

[0126] [Mathematical Formula 1]

[0127]

[0128] - L: Integration level

[0129] - n CI : Carrier Index

[0130] - n CCE,p : Total number of CCEs present in CORESET p

[0131] - : slot index

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

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

[0134] - l = 0, ..., L -1

[0135] - , Y p,-1 = nRNTI≠0, A p = 39827 for p mod 3 = 0, A p = 39829 for p mod 3 = 1, A p = 39839 for p mod 3 = 2, D= 65537

[0136] - n RNTI : Terminal identifier

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

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

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

[0140] FIG. 6 is a diagram illustrating an example of frequency-axis resource allocation of PDSCH or PUSCH in a 5G system.

[0141] FIG. 6 is a diagram illustrating three frequency axis resource allocation methods, Type-0 (600), Type-1 (605), and dynamic switch (610), which can be set through an upper layer in an NR wireless communication system.

[0142] Referring to Fig. 6, if the terminal is configured to use only Type-0 resource allocation through upper layer signaling (600), some downlink control information (DCI) that allocates PDSCH / PUSCH to the terminal is N RBG Contains a bitmap consisting of N bits. RBG refers to the number of RBGs (resource block groups) determined as shown in Table 11 below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0143] Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616

[0144] The size of the BWP is the number of RBs included in the BWP. More specifically, when type-0 resource allocation is instructed, the length of the frequency domain resource assignment (FDRA) field of the DCI received by the terminal is the number of RBGs (N RBG ) and Here, the first RBG is It contains RBs of the dog, and the last RBG is On the other hand, Contains the RBs of the dog, otherwise, It contains RBs of RBs. The remaining RBGs contain P RBs, where P is the number of nominal RBGs determined according to Table 11.

[0145] If the terminal is configured to use only type-1 resource allocation through upper layer signaling (605), the DCI that allocates PDSCH / PUSCH to the terminal It contains frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the BWP. Through this, the base station can set the starting VRB (620) and the length of frequency axis resources (625) allocated continuously therefrom.

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

[0147] Below, a time domain resource allocation method for data channels in a 5G system is described.

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

[0149] PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PDSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PDSCH mapping type)startSymbolAndLength INTEGER (0..127)(PDSCH start symbol and length)}

[0150] PUSCH-TimeDomainResourceAllocation information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PUSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PUSCH mapping type)startSymbolAndLength INTEGER (0..127)(PUSCH start symbol and length)}

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

[0152] FIG. 7 is a diagram illustrating an example of time axis resource allocation of PDSCH in a 5G system.

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

[0154] FIG. 8 is a diagram illustrating an example of time-domain resource allocation according to the subcarrier spacing of a data channel and a control channel in a 5G system.

[0155] Referring to Fig. 8, when the subcarrier spacing of the data channel and the control channel is the same (800, μ PDSCH = μ PDCCH ), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (805, μ PDSCH ≠ μ PDCCH), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier spacing of the PDCCH.

[0156] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible using DCI formats 0_0 or 0_1.

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

[0158] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

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

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

[0161] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

[0162] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRI (SRS resource indicator), TPMI (transmission precoding matrix indicator), and transmission rank (the number of PUSCH transmission layers).

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

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

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

[0166] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

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

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

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

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

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

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

[0173] Hereinafter, embodiments of the present disclosure will be described in detail with the accompanying drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Specific examples may be as follows.

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

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

[0176] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

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

[0178] - MIB

[0179] - SIB (system information block) or SIB

[0180] - RRC

[0181] - MAC (medium access control) CE (control element)

[0182] - PDCP (packet data convergence protocol) signaling

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

[0184] - PDCCH

[0185] - DCI

[0186] - UE-specific DCI

[0187] - Group common DCI

[0188] - Common DCI

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

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

[0191] - PUCCH

[0192] - UCI (uplink control information)

[0193] Additionally, DCI format below may mean DCI with a specific DCI format applied.

[0194] Below, we describe the waveform switching used by a terminal when transmitting a PUSCH.

[0195] A base station can configure a waveform to be used when transmitting PUSCH to a terminal. The waveform can be either CP-OFDM or DFT-S-OFDM. The terminal can transmit PUSCH according to the configured waveform. In this case, the terminal cannot transmit PUSCH using a waveform other than the configured waveform.

[0196] For example, if a terminal is configured with CP-OFDM, it must transmit PUSCH using the configured CP-OFDM even when the terminal's uplink coverage is insufficient. Therefore, even though DFT-S-OFDM can provide wider uplink coverage, the terminal can only use the configured CP-OFDM for PUSCH transmission.

[0197] Conversely, if the terminal is configured for DFT-S-OFDM, the terminal's uplink channel is improved, enabling multiple MIMO layer transmissions. However, the terminal must transmit the PUSCH as a single MIMO layer transmission using the configured DFT-S-OFDM. Therefore, the terminal's throughput may be limited.

[0198] To address this issue, the DCI format for scheduling the PUSCH may include a PUSCH waveform change indicator field. The terminal may receive the DCI format and determine the waveform to be used when transmitting the PUSCH.

[0199] This may require reporting of terminal capabilities from the corresponding terminal and setting of upper layer signaling from the base station. The PUSCH waveform change indicator may be 1 bit, and when the value of the corresponding field is 0, the PUSCH scheduled through the corresponding DCI may be transmitted based on the DFTS-OFDM waveform, and when the value of the corresponding field is 1, the PUSCH scheduled through the corresponding DCI may be transmitted based on the CP-OFDM waveform. The definition of each bit value of the corresponding field is applied in the opposite way as above, so that when the value of the corresponding field is 1, the terminal may perform PUSCH transmission based on the DFTS-OFDM waveform, and when the value is 0, the terminal may perform PUSCH transmission based on the CP-OFDM waveform.

[0200] If the terminal does not receive upper layer signaling from the base station that indicates that the PUSCH waveform change indicator field is included in DCI formats 0_1 and 0_2, the terminal can determine whether to use CP-OFDM or DFTS-OFDM when transmitting PUSCH dynamically scheduled through DCI format 0_1 ​​or 0_2 through a parameter called transformPrecoder set in PUSCH-Config, which is an upper layer signaling within the BWP.

[0201] - If the terminal has the transformPrecoder in the above PUSCH-Config set to enabled, the terminal can use the DFTS-OFDM waveform when transmitting PUSCH dynamically scheduled through DCI format 0_1 ​​or 0_2 from the base station.

[0202] - If the terminal receives the above transformPrecoder as disabled, the terminal can use the CP-OFDM waveform when transmitting PUSCH dynamically scheduled through DCI format 0_1 ​​or 0_2 from the base station.

[0203] The terminal can determine whether to use CP-OFDM or DFTS-OFDM when the terminal is activated for PUSCH transmission based on configured grant Type 2 via DCI format 0_1 ​​or 0_2 or is configured for PUSCH transmission based on configured grant Type 1 via upper layer signaling, through a parameter called transformPrecoder set in configuredGrantConfig, which is an upper layer signaling within BWP.

[0204] - If the terminal is set to enabled for transformPrecoder in the configuredGrantConfig, the terminal can use the DFTS-OFDM waveform when it is activated for PUSCH transmission based on configured grant Type 2 through DCI format 0_1 ​​or 0_2 from the base station or is set for PUSCH transmission based on configured grant Type 1 through upper layer signaling.

[0205] - If the terminal receives the above transformPrecoder as disabled, the terminal can use the CP-OFDM waveform when the terminal is activated for PUSCH transmission based on configured grant Type 2 through DCI format 0_1 ​​or 0_2 from the base station or is set for PUSCH transmission based on configured grant Type 1 through upper layer signaling.

[0206] PUSCH-Config or configuredGrantConfig can be set for each uplink BWP. That is, transformPrecoder can be disabled in PUSCH-Config or configuredGrantConfig set for the first uplink BWP, and transformPrecoder can be enabled in PUSCH-Config or configuredGrantConfig set for the second uplink BWP.

[0207] FIG. 9 is a diagram illustrating an example of reception of a DCI format indicating a BWP change.

[0208] Referring to FIG. 9, the uplink active BWP can be changed through the DCI format that schedules the PUSCH received by the terminal. In this case, the DCI format (950) received in the currently activated BWP (referring to the BWP in which the DCI format is received, 910) can indicate a BWP (920) to be newly activated. In addition, the DCI format can schedule a PUSCH (960) in the newly activated BWP (920). In this case, the terminal must determine the waveform of the PUSCH to be transmitted in the newly activated BWP.

[0209] For reference, indicating the waveform of PUSCH in DCI format is called dynamic waveform change.

[0210] The present disclosure then addresses a method for determining the waveform of a PUSCH to be transmitted to a newly activated BWP. Here, dynamic waveform changes can be configured for the newly activated BWP.

[0211] The terminal can be configured to enable dynamic waveform changes as follows from the base station.

[0212] The terminal can be configured to allow dynamic waveform changes for each uplink BWP.

[0213] More specifically, an RRC parameter for dynamic waveform change may be added to the PUSCH-Config of the uplink BWP. The name of the added RRC parameter is called DynamicWaveform, and when DynamicWaveform is set in the PUSCH-Config, when the terminal monitors the PDCCH to receive DCI in the downlink BWP corresponding to the uplink BWP, the DCI format of the DCI may include 1 bit for dynamic waveform change. Here, the uplink BWP and the downlink BWP with the same ID can be expressed as corresponding to each other.

[0214] In addition, an RRC parameter for dynamic waveform change can be added to the configuredGrantConfig of the uplink BWP. Let the name of the added RRC parameter be DynamicWaveform. When DynamicWaveform is set in configuredGrantConfig, when the terminal monitors the PDCCH to receive DCI in the downlink BWP corresponding to the uplink BWP, the DCI format of the DCI can include 1 bit for dynamic waveform change. Here, the uplink BWP and the downlink BWP with the same ID can be expressed as corresponding to each other.

[0215] The above DCI format can schedule dynamic PUSCH or activate configured grant (CG) PUSCH. According to the above configuration, whether dynamic waveform change of dynamic PUSCH scheduling is possible follows DynamicWaveform of PUSCH-Config, but whether dynamic waveform change of CG PUSCH is possible follows DynamicWaveform setting of configuredGrantConfig. Therefore, one of the two may allow dynamic waveform change, but the other may not.

[0216] As above, if DynamicWaveform is set in PUSCH-Config for the UE or DynamicWaveform is set in configuredGrantConfig (either one is set), the UE can determine whether the DCI format for scheduling dynamic PUSCH or activating CG PUSCH includes 1 bit indicating dynamic waveform change. For example, if DynamicWaveform is set in PUSCH-Config for the UE and DynamicWaveform is not set in configuredGrantConfig, the UE can assume that the DCI format always includes 1 bit indicating dynamic waveform change. When the UE receives the DCI format, if the DCI format schedules dynamic PUSCH (when C-RNTI or MCS-C-RNTI or CS-RNTI is scrambled with NDI=0), the UE can interpret the 1 bit as a meaningful bit. That is, the 1 bit can be used to determine whether the dynamic waveform of the dynamic PUSCH is changed. If the terminal receives the DCI format and the DCI format activates CG PUSCH (scrambled with CS-RNTI with NDI=0), the terminal may ignore the 1 bit. That is, regardless of the value of the 1 bit, the waveform of the CG PUSCH may be determined according to the transformPrecoder of configuredGrantConfig. Here, the value of the 1 bit is fixed to '0', and the value may be used to verify the validity of the DCI format that activates CG PUSCH.

[0217] In the previous example, there was no distinction according to a separate DCI format, but the base station can set whether dynamic waveform change is possible differently for each DCI format. For example, in PUSCH-Config, an RRC parameter DynamicWaveforDCI0_x can be set to set dynamic waveform change of DCI format 0_x. If the RRC parameter is set, the terminal can obtain 1 bit indicating dynamic waveform change in DCI format 0_x. Here, 0_x can be 0_0, 0_1, 0_2, or 0_3. Here, the RRC parameter for 0_0 may not exist.

[0218] Hereinafter, the present disclosure proposes a method for determining the waveform of a PUSCH transmitted in a newly activated BWP when dynamic waveform change is indicated in a newly activated BWP, even though dynamic waveform change is not supported in an active BWP. Since dynamic waveform change is not configured in an active BWP for which a UE monitors a PDCCH, the DCI format received via the PDCCH does not include a 1-bit indicating a dynamic waveform. However, since dynamic waveform change is possible in a newly activated BWP, a 1-bit indicating a dynamic waveform change may be required.

[0219] According to 3GPP standard document TS 38.213, the method of interpreting DCI field when terminal changes BWP is described.

[0220] If a bandwidth part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the active DL BWP, from the configured DL BWP set, for DL receptions as described in [5, TS 38.212]. If a bandwidth part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the active UL BWP, from the configured UL BWP set, for UL transmissions as described in [5, TS 38.212]. If a bandwidth part indicator field is configured in a DCI format and indicates an UL BWP or a DL BWP different from the active UL BWP or DL BWP, respectively, the UE shall

[0221] - for each information field in the DCI format

[0222] * if the size of the information field is smaller than the one required for the DCI format interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, the UE prepends zeros to the information field until its size is the one required for the interpretation of the information field for the UL BWP or DL BWP prior to interpreting the DCI format information fields, respectively

[0223] * if the size of the information field is larger than the one required for the DCI format interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, the UE uses a number of least significant bits of the DCI format equal to the one required for the UL BWP or DL BWP indicated by bandwidth part indicator prior to interpreting the DCI format information fields, respectively

[0224] - set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in the DCI format

[0225] According to the standard document, the DCI format received by the terminal from a BWP where dynamic waveform change is not set does not include a 1-bit dynamic waveform change field, but the DCI format of a newly activated BWP requires a 1-bit dynamic waveform change field, so the terminal can obtain a dynamic waveform change field in which 1 bit is set to '0' according to zero padding, and transmit a PUSCH using a waveform corresponding to '0'.

[0226] In this way, since the terminal always transmits PUSCH with the waveform corresponding to '0' when the BWP is changed, it may not be suitable for dynamic waveform changes. For example, let's assume DFT-S-OFDM as the waveform corresponding to '0'. In this case, the base station wants to receive PUSCH with high throughput along with the BWP change, but can only receive PUSCH using DFT-S-OFDM. Conversely, let's assume CP-OFDM as the waveform corresponding to '0'. In this case, the base station wants to receive PUSCH with wide coverage along with the BWP change, but can only receive PUSCH using CP-OFDM, which may result in performance degradation.

[0227] First embodiment: Setting a waveform corresponding to the value of the dynamic waveform change field

[0228] In one embodiment of the present disclosure, the base station may set a first waveform corresponding to a value '0' of a 1-bit dynamic waveform change field for the terminal. In addition, the base station may set a second waveform corresponding to a value '1' of the 1-bit dynamic waveform change field for the terminal. Here, if the first waveform is DFT-S-OFDM, the second waveform is CP-OFDM. If the first waveform is CP-OFDM, the second waveform is DFT-S-OFDM. The base station may set the first waveform corresponding to the value '0' of the 1-bit dynamic waveform change field for the terminal, and may not set the second waveform corresponding to '1'. In this case, the second waveform corresponding to '1' is not separately set, but may be determined as a waveform other than the first waveform (i.e., if the first waveform is DFT-S-OFDM, then CP-OFDM). The base station may set the second waveform corresponding to the value '1' of the 1-bit dynamic waveform change field to the terminal, and may not set the first waveform corresponding to '0'. In this case, the first waveform corresponding to '0' does not have a separate setting, but may be determined as a waveform other than the second waveform (i.e., if the second waveform is DFT-S-OFDM, CP-OFDM).

[0229] When a terminal receives a DCI format in a BWP where dynamic waveform change is set, the terminal can acquire the value of a 1-bit dynamic waveform change field in the DCI format. If the value of the dynamic waveform change field is '0', the terminal can transmit a PUSCH with the set first waveform, and if it is '1', the set terminal can transmit a PUSCH with the set second waveform.

[0230] When a terminal receives a DCI format in a BWP for which dynamic waveform change is not configured, the DCI format may not include a 1-bit dynamic waveform change field. If the DCI format indicates a BWP change, dynamic waveform change may be configured in the newly activated BWP. In this case, the terminal may transmit a PUSCH using a first waveform corresponding to '0'. For reference, the terminal here assumes '0' as the value of the dynamic waveform change field, which may be a value determined according to the zero padding described above.

[0231] According to the present embodiment, the base station can set the waveform to be used when changing the BWP to the dynamic waveform change value '0' for the terminal. For example, if the base station wants higher throughput when changing the BWP, it can set CP-OFDM to the dynamic waveform change value '0', and if it wants wider coverage, it can set DFT-S-OFDM to the dynamic waveform change value '0'.

[0232] Embodiment 2: Setting a default waveform and transmitting PUSCH with the set default waveform

[0233] In one embodiment of the present disclosure, a terminal may receive a default waveform to be used for a BWP from a base station. The default waveform may be set for each BWP. For example, the base station may set a first waveform as the default waveform for a first BWP, and a second waveform as the default waveform for a second BWP. The first and second waveforms may be either CP-OFDM or DFT-S-OFDM. The first and second waveforms may be the same or different.

[0234] When a terminal receives a DCI format in a BWP for which dynamic waveform change is set, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to an instruction of the dynamic waveform change field. However, when the terminal receives a DCI format in a BWP for which dynamic waveform change is not set, the terminal cannot obtain the dynamic waveform change field from the DCI. In this case, the terminal can transmit a PUSCH using a default waveform. More specifically, it is assumed that the terminal receives a DCI format in a BWP for which dynamic waveform change is not set, and the DCI format indicates a BWP change. When dynamic waveform change is set in a newly activated BWP, the terminal must determine the waveform of the PUSCH through the DCI format, but since the DCI format received by the terminal does not have a dynamic waveform change field, in this case, the terminal can transmit the PUSCH with the default waveform set in the BWP.

[0235] Here, the BWP may be a newly activated BWP according to the DCI format. That is, the base station may set a default waveform for each BWP for the terminal. If a first waveform is set for the active BWP and a second waveform is set for the newly activated BWP, the terminal may determine the waveform of the PUSCH based on the second waveform of the newly activated BWP. That is, if dynamic waveform change is set for the newly activated BWP, the base station may set a default waveform for the BWP.

[0236] Alternatively, the BWP here may be an active BWP (a BWP for which the terminal has received the DCI format). That is, the base station may set a default waveform for each BWP for the terminal. If a first waveform is set for the active BWP and a second waveform is set for a newly activated BWP, the terminal may determine the waveform of the PUSCH based on the first waveform of the active BWP. If dynamic waveform change is not set for the active BWP and dynamic waveform change is set for other BWPs (including the BWP to be newly activated here), the base station may set a default waveform for the active BWP.

[0237] In one embodiment of the present disclosure, a terminal can receive a default waveform set from a base station to be used in common across all BWPs of a cell. That is, the default waveform can be set identically across all BWPs. When the terminal receives a DCI format in a BWP for which dynamic waveform change is set, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to an instruction of the dynamic waveform change field. However, when the terminal receives a DCI format in a BWP for which dynamic waveform change is not set, the terminal cannot obtain the dynamic waveform change field from the DCI format. In this case, the terminal can transmit a PUSCH using a default waveform set in common across cells.

[0238] According to this embodiment, the overhead of upper layer signaling can be reduced compared to an embodiment in which a default waveform is set for each BWP.

[0239] Example 3: PUSCH transmission using the PUSCH waveform used during initial cell access.

[0240] When a terminal receives a DCI format in a BWP for which dynamic waveform change is set, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to the instructions of the dynamic waveform change field. However, when a DCI format is received in a BWP for which dynamic waveform change is not set, the terminal cannot obtain the dynamic waveform change field from the DCI. In this case, the terminal can transmit a PUSCH using the waveform used during initial cell access.

[0241] The waveform used during the initial cell connection is as follows.

[0242] - If the terminal has performed cell access according to the 4-step RACH procedure, the waveform of Msg-3 PUSCH can be configured in msg3-transformPrecoder in RACH-ConfigCommon from rach-ConfigCommon. The terminal can determine the waveform of the PUSCH to be transmitted in the newly activated BWP based on the waveform configured in the msg3-transformPrecoder.

[0243] - If the terminal performs cell access according to the 2-step RACH procedure, the waveform of the Msg-A PUSCH can be set in msgA-transformPrecoder. The terminal can determine the waveform of the PUSCH to be transmitted in the newly activated BWP based on the waveform set according to the msgA-transformPrecoder. If the terminal does not set msgA-transformPrecoder, the terminal can determine the waveform of the PUSCH to be transmitted in the newly activated BWP based on the waveform set in msg3-transformPrecoder.

[0244] - Alternatively, regardless of the RACH procedure being performed (i.e., regardless of whether cell access is performed according to a 4-step RACH procedure or a 2-step RACH procedure), the UE can determine the PUSCH waveform to be transmitted in the newly activated BWP based on the waveform set in msg3-transformPrecoder.

[0245] Example 4: Waveform indication using remaining bits of DCI

[0246] In one embodiment of the present disclosure, when a terminal receives a DCI format in a BWP in which dynamic waveform change is set, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to an instruction of the dynamic waveform change field. However, when the terminal receives a DCI format in a BWP in which dynamic waveform change is not set, the terminal cannot obtain the dynamic waveform change field from the DCI. In this case, the terminal can repurpose some bits of the received DCI format and interpret and use them as a dynamic waveform change field. Here, the dynamic waveform change field can be 1 bit.

[0247] For example, the DCI format received from the active BWP may contain padding bits in addition to the DCI field to adjust the length. The terminal may interpret and use one of the padding bits as a dynamic waveform change field.

[0248] For example, the terminal can change the purpose of 1 bit of a field existing in the DCI format, such as the HARQ process number field, the RV field, and the MCS field, received from the active BWP and interpret it as a dynamic waveform change field. The terminal can interpret the remaining bits excluding the changed bit as the original field (e.g., the HARQ process number field, the RV field, and the MCS field). Preferably, the terminal can change the purpose of 1 bit of the most significant bit (MSB) of a specific field and interpret it as a dynamic waveform change field.

[0249] Embodiment 5: Always include dynamic waveform change field in DCI

[0250] In one embodiment of the present disclosure, when dynamic waveform change is set for at least one BWP of a cell, the terminal may assume that the DCI formats monitored in all BWPs of the cell include a dynamic waveform change field. That is, the DCI formats monitored by the terminal in BWPs where dynamic waveform change is not set do not require a dynamic waveform change field, but the terminal may assume that the DCI formats include a dynamic waveform change field.

[0251] According to the present embodiment, when a terminal receives a DCI format in a BWP in which dynamic waveform change is configured, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to an instruction of the dynamic waveform change field. In addition, even if the terminal receives a DCI format in a BWP in which dynamic waveform change is not configured, the terminal can obtain the dynamic waveform change field from the DCI. Therefore, the problem of not being able to obtain the dynamic waveform change field when the BWP is changed may not occur.

[0252] At this time, if dynamic waveform change is configured for at least one BWP of a cell for a terminal, the base station may configure the DCI format monitored by all BWPs of the cell to include a dynamic waveform change field. For example, if the base station can indicate whether to include a dynamic waveform change field in the DCI format for each BWP, the base station must commonly indicate whether to include a dynamic waveform change field for all BWPs. The terminal may not expect to be configured to include different dynamic waveform change fields for different BWPs.

[0253] Example 6: Determining waveforms based on FDRA type

[0254] The UE can determine the FDRA (frequency domain resource assignment) type of the PUSCH to be transmitted to the newly activated BWP. FDRA types can be Type-0 and Type-1. Type-0 is a method of indicating RBs to be scheduled based on a bitmap, and Type-1 is a method of indicating consecutive RBs based on a resource indication value (RIV). In the case of CP-OFDM, both Type-0 and Type-1 can be used, but in the case of DFT-S-OFDM, only Type-1 can be used.

[0255] The terminal can determine the Type of the FDRA field according to the BWP setting. For the PUSCH transmission of the newly activated BWP, one of Type-0, Type-1, and the FDRA dynamic switch can be set. If Type-0 or Type-1 is set, the terminal can determine the Type of the FDRA field according to the BWP setting. If the FDRA dynamic switch is set, the terminal can determine the Type through the FDRA field. For example, the MSB 1 bit of the FDRA field can be used to indicate one of Type-0 or Type-1.

[0256] When a terminal receives a DCI format in a BWP where dynamic waveform change is set, the terminal can obtain a dynamic waveform change field from the DCI format and transmit a PUSCH with a waveform determined according to the instructions of the dynamic waveform change field. However, when the terminal receives a DCI format in a BWP where dynamic waveform change is not set, the terminal cannot obtain the dynamic waveform change field from the DCI format. In this case, the terminal can determine a waveform using the FDRA type and transmit a PUSCH.

[0257] As an example of the present disclosure, the waveform may be determined as follows.

[0258] - If the FDRA type of the newly activated BWP is Type-0, the terminal can always transmit PUSCH using CP-OFDM.

[0259] - If the FDRA type of the newly activated BWP is Type-1, the terminal must determine one of the waveforms between CP-OFDM and DFT-S-OFDM. In this case, the terminal can determine the PUSCH waveform based on one of the embodiments of the present disclosure.

[0260] As an example of the present disclosure, the waveform may be determined as follows.

[0261] - If the FDRA type of the newly activated BWP is Type-0, the terminal can always transmit PUSCH using CP-OFDM.

[0262] - If the FDRA type of the newly activated BWP is Type-1, the terminal can always transmit PUSCH using DFT-S-OFDM.

[0263] If the FDRA dynamic switch is set as the Type of the FDRA field, the terminal can determine the Type of the FDRA field based on the MSB 1 bit of the FDRA field, and determine the waveform of the PUSCH using the preceding example according to the Type.

[0264] As another example, when the FDRA dynamic switch is set, the waveform can be determined in the following way:

[0265] - When the FDRA dynamic switch is set to a newly activated BWP, the terminal can always transmit PUSCH using CP-OFDM. That is, since Type-0 FDRA may be indicated depending on the FDRA dynamic switch, the terminal can transmit PUSCH using CP-OFDM.

[0266] As another example, when a dynamic switch is set, the waveform can be determined in the following way:

[0267] - When the FDRA dynamic switch is set for a newly activated BWP, the terminal can always transmit a PUSCH using CP-OFDM and interpret the FDRA field assuming Type-0 FDRA. That is, the CP-OFDM waveform can be used while simultaneously assuming Type-0 FDRA suitable for CP-OFDM. The above example can be used when the length of the FDRA field included in the DCI format is shorter than the length of the FDRA field required for the newly activated BWP. That is, when the length of the FDRA field included in the DCI format is equal to or longer than the length of the FDRA field required for the newly activated BWP, the waveform of the PUSCH can be determined based on another embodiment of the present disclosure.

[0268] As another example, when a dynamic switch is set, the waveform can be determined in the following way:

[0269] - When the FDRA dynamic switch is set for a newly activated BWP, the terminal can always transmit a PUSCH using DFT-S-OFDM and interpret the FDRA field assuming Type-1 FDRA. That is, the DFT-S-OFDM waveform can be used while at the same time as assuming Type-1 FDRA suitable for DFT-S-OFDM. The above example can be used when the length of the FDRA field included in the DCI format is shorter than the length of the FDRA field required for the newly activated BWP. That is, when the length of the FDRA field included in the DCI format is equal to or longer than the length of the FDRA field required for the newly activated BWP, the waveform of the PUSCH can be determined based on another embodiment of the present disclosure.

[0270] As another example, when the FDRA dynamic switch is set, the waveform can be determined in the following way:

[0271] - When the FDRA dynamic switch is set to a newly activated BWP, the terminal can determine the waveform or FDRA Type based on the length of the required FDRA field when assuming the FDRA type to be Type-0 and the length of the required FDRA field when assuming the FDRA type to be Type-1.

[0272] For example, if the length of the required FDRA field assuming Type-0 is less than or equal to the length of the required FDRA field assuming Type-1, the terminal can assume that the FDRA Type is Type-0 FDRA. Conversely, if the length of the required FDRA field assuming Type-0 is longer than the length of the required FDRA field assuming Type-1, the terminal can assume Type-1 FDRA. In other words, the terminal can select an FDRA type with a shorter length.

[0273] Alternatively, the terminal may select an FDRA type having a longer length of the required FDRA field. In another example, the terminal may select an FDRA type having a longer length of the required FDRA field if the longer length of the required FDRA field is equal to or shorter than the length of the FDRA field included in the DCI format, and otherwise, may select an FDRA type having a shorter length. In other words, the terminal may select an FDRA type having the longest length among the FDRA types having a length equal to or shorter than the length of the FDRA field included in the DCI format.

[0274] The terminal can determine the waveform based on the selected FDRA Type. This can be determined based on one of the examples described above in the present disclosure.

[0275] As described above, a terminal can acquire a 1-bit dynamic waveform change field in the DCI format. This disclosure describes a method for acquiring the 1-bit field.

[0276] Figure 10 is a diagram illustrating an example of the configuration of an FDRA field and a dynamic waveform change field.

[0277] According to FIG. 10, (a)(1000) is a diagram in which an FDRA field and a dynamic waveform change field are independently configured. It is assumed that an FDRA dynamic switch is set in an active BWP of a terminal. The terminal can determine the FDRA type through the MSB 1 bit (1022) of the FDRA field of the DCI format. If a dynamic waveform change is set in the active BWP of the terminal, the terminal can be instructed to receive a waveform through a 1-bit dynamic waveform change field (1010) in the DCI format. In this case, the lengths of the FDRA field and the 1-bit dynamic waveform change field included in the DCI format can be as follows (1010, 1020).

[0278]

[0279] Here, is the number of RBs included in the UL BWP, and N RBG is the number of RBGs included in UL BWP.

[0280] Referring to (a)(1000) of Fig. 10, the dynamic waveform change field (1010) is 1 bit, and the FDRA field (1020) is bits. Here, MSB 1 bit (1022) indicates FDRA dynamic switching, and the rest bits indicate frequency domain resource allocation according to FDRA Type-0 and FDRA Type-1. (a)(1010) is N RBG > was assumed. Therefore, if FDRA-Type-1 is indicated, N RBG - bits may contain zero bits (1026).

[0281] When the terminal is instructed to use CP-OFDM with the 1-bit dynamic waveform change field, the MSB 1 bit of the FDRA field can indicate one FDRA Type between Type-0 and Type-1. That is, the MSB 1 bit of the FDRA field is meaningful. When the terminal is instructed to use DFT-S-OFDM with the 1-bit dynamic waveform change field, the MSB 1 bit of the FDRA field can only indicate Type-1 FDRA Type. That is, the MSB 1 bit of the FDRA field is meaningless.

[0282] In one embodiment of the present disclosure, the terminal may jointly configure an FDRA field and a dynamic waveform change field.

[0283] If the MSB of the FDRA field of the DCI format indicates Type-1 FDRA, the DCI format may have 1 bit indicating dynamic waveform change, and if the MSB of the FDRA field indicates Type-0 FDRA, the DCI format may not include 1 bit indicating dynamic waveform change. Here, if Type-0 FDRA is indicated, the terminal can transmit PUSCH with CP-OFDM.

[0284] More specifically, if the MSB of the FDRA field indicates Type-0 FDRA, the remaining bits of the FDRA field can be interpreted as FDRA Type-0. That is, among the remaining bits of the FDRA field, N RBG Indicates frequency domain scheduling information of PUSCH. And PUSCH can be transmitted with CP-OFDM.

[0285] If the MSB of the FDRA field indicates Type-1 FDRA, one bit of the remaining bits of the FDRA field is interpreted as a dynamic waveform change field, and among the remaining bits of the FDRA field (the bit indicating FDRA switching in the FDRA field and the remaining bits excluding the dynamic waveform change field), bits can be interpreted as FDRA Type-1.

[0286] According to this embodiment, the length of the FDRA field and the 1-bit dynamic waveform change field included in the DCI format may be as follows.

[0287]

[0288] Figure 10 (b)(1050) is a drawing showing an example in which an FDRA field and a dynamic waveform change field are jointly configured.

[0289] The first MSB 1 bit (1062) of the FDRA field (1060) can indicate FDRA dynamic switching. If the first MSB 1 bit (1062) indicates FDRA Type-0, the remainder of the FDRA field is N to indicate frequency domain scheduling information of FDRA Type-0. RBG bit. If the first MSB 1 bit indicates FDRA Type-1, the second MSB 1 bit (1064) of the FDRA field can indicate dynamic waveform change. And among the remaining bits of the FDRA field, bits represents the frequency domain scheduling information of FDRA Type-1. In Fig. 12(b), N RBG > was assumed. Therefore, if FDRA-Type-1 is indicated, N RBG - ( +1) bits may contain zero bits

[0290] The FDRA field in Figure 10 is only an example and can be applied with obvious modifications.

[0291] FIG. 11 is a drawing illustrating an example of an operation performed by a terminal of the present disclosure.

[0292] Referring to Figure 11, although not shown, a terminal may receive information from a base station that enables dynamic waveform changes for a cell or a BWP within a cell. This information may be transmitted via higher-layer signaling. Further details may follow the description above.

[0293] A terminal may receive a DCI format indicating a BWP change from an active BWP (1100). The terminal may receive the DCI format from the active BWP, and the DCI format may include a BWP change indicator field, which may include an index of a BWP different from the currently active BWP. In this case, the terminal may determine the DCI format as a BWP change DCI format.

[0294] The terminal can check whether dynamic waveform change is enabled for a newly activated BWP (1110). Here, whether dynamic waveform change is enabled can be set for each BWP and can be checked based on the configuration information described above.

[0295] When dynamic waveform change is configured in a newly activated BWP, the terminal checks whether a dynamic waveform change field exists in the received DCI format (1120). Here, for example, the presence of a dynamic waveform change field in the DCI format may depend on the settings of the active BWP in which the DCI format was received. Alternatively, the method described above may be followed.

[0296] If a dynamic waveform change field exists in the received DCI format, the terminal can use the field to determine the waveform of the PUSCH to be transmitted in the newly activated BWP. If the DCI format does not include a dynamic waveform change field, the terminal determines the waveform for PUSCH transmission according to the example described above (1130).

[0297] The terminal transmits a PUSCH with a waveform determined in the newly activated BWP (1140).

[0298] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts herein. For example, although depicted as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, steps may be omitted or replaced with other steps.

[0299] FIG. 12 is a diagram illustrating an example of an operation performed by a base station of the present disclosure.

[0300] Referring to Figure 12, although not shown, the base station may transmit information to the terminal that enables dynamic waveform changes for a cell or a BWP within the cell. This information may be transmitted via higher-layer signaling. Further details may follow the description above.

[0301] A base station may transmit a DCI format indicating a change in a BWP from an active BWP to a terminal (1200). The terminal may receive the DCI format from the active BWP, and the DCI format may include a BWP change indicator field, which may include an index of a BWP different from the currently active BWP. If dynamic waveform change is set for a BWP to be newly activated by the BWP change indicator field, the DCI format may or may not include a dynamic waveform change field according to the example described above.

[0302] The base station receives a PUSCH from the terminal in a newly activated BWP (1210). The waveform of the PUSCH received at this time may be based on the transmitted DCI format. If the transmitted DCI format includes a dynamic waveform change field, the waveform of the PUSCH may be a waveform indicated by the field. If the transmitted DCI format does not include a dynamic waveform change field, the waveform of the PUSCH may be a waveform determined according to the example described above.

[0303] The above flowchart illustrates exemplary methods that can be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts herein. For example, although depicted as a series of steps, various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, steps may be omitted or replaced with other steps.

[0304] As another example, when a terminal receives a dynamic waveform switching change setting in a BWP, the DCI format monitored by the terminal in that BWP may include a dynamic waveform change field, through which the waveform may be determined. The lengths of the DCI fields included in the DCI format may differ depending on the two waveforms.

[0305] For example, when using a CP-OFDM waveform in DCI format 0_1 ​​and when using a DFT-OFDM waveform, the lengths of the Precoding information and number of layers field, antenna ports field, PTRS-DMRS field, and DMRS sequence initialization field may differ as follows.

[0306] ○ Precoding information and number of layers - number of bits determined by the following- 0 bits if the higher layer parameter txConfig = nonCodeBook;

[0307] - 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

[0308] - 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;

[0309] - 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;

[0310] - 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset;

[0311] - 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset.

[0312] ○ Antenna ports - number of bits determined by the following

[0313] - 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, dmrs-Type=1, and maxLength=1;

[0314] - 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, dmrs-Type=1, and maxLength=2;

[0315] - 3 bits as defined by Tables 7.3.1.1.2-8 / 9 / 10 / 11, if transform precoder is disabled, dmrs-Type=1, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

[0316] - 4 bits as defined by Tables 7.3.1.1.2-12 / 13 / 14 / 15, if transform precoder is disabled, dmrs-Type=1, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

[0317] - 4 bits as defined by Tables 7.3.1.1.2-16 / 17 / 18 / 19, if transform precoder is disabled, dmrs-Type=2, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;

[0318] - 5 bits as defined by Tables 7.3.1.1.2-20 / 21 / 22 / 23, if transform precoder is disabled, dmrs-Type=2, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook.

[0319] where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

[0320] If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, the bitwidth of this field equals max{x A , x B } , where x A is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeA and x B is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeB. A number of |x A -x B | zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of x A and x B .

[0321] ○ PTRS-DMRS association - number of bits determined as follows

[0322] - 0 bit if PTRS-UplinkConfig is not configured and transform precoder is disabled, or if transform precoder is enabled, or if maxRank=1;

[0323] - 2 bits otherwise, where Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports field.

[0324] If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part.

[0325] - DMRS sequence initialization - 0 bit if transform precoder is enabled; 1 bit if transform precoder is disabled.

[0326] Therefore, the length of a DCI format including a dynamic waveform change field may vary depending on the waveform indicated by the field. If the length of a DCI format varies depending on the waveform, this may result in an increase in the number of blind decodings required by the terminal. To prevent this, the terminal must be able to receive a DCI format with a single DCI format length, regardless of the waveform indicated.

[0327] Let the length of the DCI format including the DCI fields generated assuming DFT-S-OFDM be the first length, and let the length of the DCI format including the DCI fields generated assuming CP-OFDM be the second length. If the first and second lengths are not the same, the base station can make the shorter length DCI format equal to the longer length by adding '0' to the LSB (least significant bit). For example, if the first length is 40 bits and the second length is 50 bits, the base station can add 10 bits of '0' to the DCI format of the first length (the DCI format including the DCI fields generated assuming DFT-S-OFDM). The 10 bits of '0' can be added to the last bits (LSB) of the DCI format of the first length.

[0328] The terminal may perform PDCCH monitoring to receive a DCI format based on a longer length between the first length and the second length. When the terminal successfully receives the DCI format, the terminal may determine the length of the indicated waveform and the DCI fields corresponding to the indicated waveform through the dynamic waveform change field. Here, the dynamic waveform change field must be located at the same bit position in the DCI format of the first length and the DCI format of the second length. That is, the dynamic waveform change field must be located at a position preceding the DCI fields whose lengths change according to the dynamic waveform change. For example, since the length of the FDRA field may change according to the indicated waveform, the dynamic waveform change field may always be located at a position preceding the FDRA field.

[0329] Preferably, the location of the dynamic waveform change field can be located at the following location in DCI format 0_1.

[0330] 1st batch:

[0331] - Identifier for DCI formats - 1 bit

[0332] - Carrier indicator - 0 or 3 bits

[0333] - DFI flag - 0 or 1 bit

[0334] - UL / SUL indicator - 0 or 1 bit

[0335] - Bandwidth part indicator - 0, 1 or 2 bits

[0336] -Dynamic waveform switch - 0 or 1 bit

[0337] - Frequency domain resource assignment

[0338] - ...

[0339] Second batch:

[0340] - Identifier for DCI formats - 1 bit

[0341] - Carrier indicator - 0 or 3 bits

[0342] - DFI flag - 0 or 1 bit

[0343] - UL / SUL indicator - 0 or 1 bit

[0344] -Dynamic waveform switch - 0 or 1 bit

[0345] - Bandwidth part indicator - 0, 1 or 2 bits

[0346] - Frequency domain resource assignment

[0347] - ...

[0348] 제3 배치:

[0349] - Identifier for DCI formats - 1 bit

[0350] - Carrier indicator - 0 or 3 bits

[0351] - DFI flag - 0 or 1 bit

[0352] -Dynamic waveform switch - 0 or 1 bit

[0353] - UL / SUL indicator - 0 or 1 bit

[0354] - Bandwidth part indicator - 0, 1 or 2 bits

[0355] - Frequency domain resource assignment

[0356] - ...

[0357] Alternatively, the length of the DCI format including the DCI fields generated assuming DFT-S-OFDM is referred to as the first length, and the length of the DCI format including the DCI fields generated assuming CP-OFDM is referred to as the second length. Here, the 1-bit dynamic waveform change field can always be located at the last bit of the DCI format regardless of the waveform. In addition, if the first length is shorter than the second length, the base station can adjust the lengths to be the same by adding '0' to the LSB of the bits remaining except the last bit of the DCI format of the first length. For example, if the first length is 40 bits and the second length is 50 bits, 10 bits can be added to the DCI format of the first length, and the 10 bits can be added right before the last 1 bit of the DCI format of the first length.

[0358] The terminal may perform PDCCH monitoring to receive a DCI format based on the longer length between the first length and the second length. If the terminal successfully receives the DCI format, the terminal may determine the indicated waveform and the length of the DCI fields corresponding to the indicated waveform through the dynamic waveform change field. Here, the dynamic waveform change field may be located at the same last bit position in the DCI format of the first length and the DCI format of the second length. The terminal may determine the waveform based on the last bit, and determine the length of the DCI fields for the remaining bits.

[0359] When a terminal receives a DCI format indicating a BWP change, dynamic waveform changes may not be set for the newly activated BWP, but may be set for the currently active BWP. In this case, the terminal must assume a specific waveform to determine the length of the DCI fields in the DCI format.

[0360] The terminal can interpret the received DCI format based on the waveform used in the newly activated BWP. For example, if the waveform of the PUSCH scheduled for the newly activated BWP is a DFT-S-OFDM waveform, the terminal can determine the length of the DCI fields of the received DCI format as a length according to the DFT-S-OFDM waveform. For example, if the waveform of the PUSCH scheduled for the newly activated BWP is a CP-OFDM waveform, the terminal can determine the length of the DCI fields of the received DCI format as a length according to the CP-OFDM waveform.

[0361] Alternatively, the terminal may interpret the received DCI format based on the waveform indicated in the dynamic waveform change field. That is, even if dynamic waveform change is not possible in the newly activated BWP, the terminal may use the value of the dynamic waveform change field to determine the DCI field length. Here, the waveform of the PUSCH scheduled in the newly activated BWP may be determined according to the setting of the newly activated BWP, regardless of the value of the dynamic waveform change field. For example, if the dynamic waveform change field of the received DCI format indicates a DFT-S-OFDM waveform, the terminal may determine the length of the DCI fields of the received DCI format as a length according to the DFT-S-OFDM waveform. For example, if the dynamic waveform change field of the received DCI format indicates a CP-OFDM waveform, the terminal may determine the length of the DCI fields of the received DCI format as a length according to the CP-OFDM waveform.

[0362] Here, the estimated length of the DCI fields in the DCI format is determined based on the settings of the currently activated BWP. The length of the DCI fields may vary depending on the different settings of the currently activated BWP and the newly activated BWP. In this case, the terminal can assume that the length of the DCI fields in the DCI format is determined based on the settings of the activated BWP.

[0363] When a terminal receives a DCI format indicating a BWP change, dynamic waveform change may be set for the newly activated BWP, and dynamic waveform change may not be set for the currently active BWP. In this case, the length of the DCI field of the received DCI format may be determined based on the waveform used in the current BWP. That is, the lengths of the Precoding information and number of layers field, antenna ports field, PTRS-DMRS field, DMRS sequence initialization field, etc. are determined based on the waveform used in the currently activated BWP.

[0364] Since a newly activated BWP can dynamically change its waveform, the lengths of the required DCI fields may vary depending on the indicated (or determined) waveform. For example, while the currently active BWP may use DFT-S-OFDM, the newly activated BWP may use CP-OFDM. Therefore, different DCI field lengths may be required.

[0365] To address this, the base station can always determine the length of the DCI field by considering the waveform used for the currently active BWP. That is, while a newly activated BWP can dynamically change its waveform, the length of the DCI field can be determined solely based on the waveform used for the active BWP. In this case, the waveform scheduled for the newly activated BWP may be the same waveform used for the active BWP.

[0366] The above describes a method for a terminal to determine the length of a DCI field in a DCI format, but a base station can also generate a DCI format and transmit it to a terminal according to the length of a DCI field according to the same method.

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

[0368] Referring to FIG. 13, the terminal may include a transceiver, which refers to a terminal receiving unit (1300) and a terminal transmitting unit (1310), a memory (not shown), and a terminal processing unit (1305), or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1300, 1310), the memory, and the terminal processing unit (1305) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

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

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

[0371] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0372] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. There may be multiple processors, and the processors can perform component control operations of the terminal by executing programs stored in memory.

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

[0374] Referring to FIG. 14, the base station may include a transceiver, which refers to a base station receiver (1430) and a base station transmitter (1410), a memory (not shown), and a base station processor (1405), or a base station control unit or processor). According to the communication method of the base station described above, the transceiver (1400, 1410), the memory, and the base station processor (1405) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

[0378] The processor can control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

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

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

[0381] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes. Or, they may be stored in memories composed of some or all of these combinations. In addition, each configuration memory may include multiple copies.

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

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

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

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

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

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

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

Claims

1. In a method performed by a terminal of a communication system, A step of receiving information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling from a base station; A step of receiving the DCI scheduling the PUSCH from the base station, the DCI including the waveform change indicator; Including a step of transmitting uplink data on the PUSCH based on the DCI to the base station, A method characterized in that, when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is transmitted based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

2. In paragraph 1, A method characterized in that, when the DCI includes the FDRA field and the resource allocation type of the FDRA field corresponds to dynamic switching and the most significant bit (MSB) 1 bit of the FDRA field indicates resource allocation type 0, the PUSCH is transmitted based on CP-OFDM. In paragraph 3.1, A method characterized in that, when the DCI includes the FDRA field and a BWP (bandwidth part) indicator, and a resource allocation type of the FDRA field of the BWP indicated by the BWP indicator corresponds to dynamic switching, and the length of the FDRA field is shorter than the length of the FDRA field corresponding to the indicated BWP, the PUSCH is transmitted based on CP-OFDM in the indicated BWP.

4. A method according to claim 1, characterized in that when the DCI is related to a CS-RNTI (configured scheduling radio network temporary identifier) ​​and includes an NDI (new data indicator) field with a value of 0 in the DCI, the waveform change indicator is ignored.

5. In a method performed by a base station of a communication system, A step of transmitting information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling to a terminal; A step of transmitting the DCI for scheduling the PUSCH to the terminal, the DCI including the waveform change indicator; A step of receiving uplink data on the PUSCH scheduled by the DCI from the terminal, A method characterized in that, when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is received based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

6. In paragraph 5, A method characterized in that, when the DCI includes the FDRA field and the resource allocation type of the FDRA field corresponds to dynamic switching and the most significant bit (MSB) 1 bit of the FDRA field indicates resource allocation type 0, the PUSCH is received based on the CP-OFDM.

7. In paragraph 5, A method characterized in that, when the DCI includes the FDRA field and a BWP (bandwidth part) indicator, and a resource allocation type of the FDRA field of the BWP indicated by the BWP indicator corresponds to dynamic switching, and the length of the FDRA field is shorter than the length of the FDRA field corresponding to the indicated BWP, the PUSCH is received based on the CP-OFDM in the indicated BWP.

8. A method according to claim 5, characterized in that when the DCI is related to a CS-RNTI (configured scheduling radio network temporary identifier) ​​and includes an NDI (new data indicator) field with a value of 0 in the DCI, the waveform change indicator is ignored.

9. At the terminal of the communication system, Transmitter and receiver; Receive information indicating that a waveform change indicator for a PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling from a base station, Receive the DCI scheduling the PUSCH from the base station, the DCI including the waveform change indicator, Including a control unit configured to transmit uplink data on a PUSCH based on the DCI to the base station, A terminal characterized in that, when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is transmitted based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

10. In paragraph 9, A method characterized in that, when the DCI includes the FDRA field and the resource allocation type of the FDRA field corresponds to dynamic switching and the most significant bit (MSB) 1 bit of the FDRA field indicates resource allocation type 0, the PUSCH is transmitted based on CP-OFDM.

11. In paragraph 9, A terminal characterized in that, when the DCI includes the FDRA field and a BWP (bandwidth part) indicator, and a resource allocation type of the FDRA field of the BWP indicated by the BWP indicator corresponds to dynamic switching, and the length of the FDRA field is shorter than the length of the FDRA field corresponding to the indicated BWP, the PUSCH is transmitted based on CP-OFDM in the indicated BWP.

12. A terminal according to claim 9, characterized in that the waveform change indicator is ignored when the DCI is related to a CS-RNTI (configured scheduling radio network temporary identifier) ​​and an NDI (new data indicator) field with a value of 0 is included in the DCI.

13. In the base station of the communication system, Transmitter and receiver; and Transmitting information indicating that a waveform change indicator for PUSCH (physical uplink shared channel) is included in DCI (downlink control information) through upper layer signaling to the terminal, Transmitting the DCI for scheduling the PUSCH to the terminal, wherein the DCI includes the waveform change indicator, Including a control unit configured to receive uplink data on the PUSCH scheduled by the DCI from the terminal, A base station, characterized in that when the DCI includes an FDRA (frequency domain resource assignment) field and the FDRA field corresponds to resource allocation type 0, the PUSCH is received based on CP-OFDM (cyclic prefix-orthogonal frequency division multiplexing).

14. In paragraph 13, A base station, characterized in that when the DCI includes the FDRA field and the resource allocation type of the FDRA field corresponds to dynamic switching and the most significant bit (MSB) 1 bit of the FDRA field indicates resource allocation type 0, the PUSCH is received based on the CP-OFDM.

15. In paragraph 13, A base station, characterized in that when the DCI includes the FDRA field and a BWP (bandwidth part) indicator, and a resource allocation type of the FDRA field of the BWP indicated by the BWP indicator corresponds to dynamic switching, and the length of the FDRA field is shorter than the length of the FDRA field corresponding to the indicated BWP, the PUSCH is received based on the CP-OFDM in the indicated BWP.

Citation Information

Patent Citations

  • Soy sauce pickled food and its manufacturing method

    KR1020200145370A

  • Uplink power modification and communication scheme change requests

    US20200053730A1

  • Transmission using an adapted downlink waveform type

    US20220345261A1

  • Requesting a waveform change

    WO2021260655A1