Method and device for reducing overhead of downlink control information during multi-cell scheduling in wireless communication system
The method and device address the challenge of high downlink control information overhead in multi-cell scheduling by employing dynamic waveform changes and integer-multiple frequency resource allocation, enhancing the efficiency of control information transmission and resource management in wireless communication systems.
Patent Information
- Application Number
- PCT/KR2024/006095
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2024-05-07
- Publication Date
- 2024-11-14
AI Technical Summary
The existing wireless communication systems face challenges in efficiently managing the overhead of downlink control information, particularly in multi-cell scheduling scenarios, which affects the performance and resource allocation in 5G and beyond mobile communication technologies.
A method and device that reduce the overhead of downlink control information by using a terminal and base station to transmit and receive information for uplink data transmission, including dynamic waveform changes for the physical uplink shared channel, where the frequency resource allocation information is a multiple of predetermined integers, allowing for efficient scheduling and resource allocation.
This approach enables efficient transmission and reception of control information, reducing overhead and improving the overall performance of multi-cell scheduling in wireless communication systems, particularly in 5G and future 6G technologies.
Smart Images

Figure KR2024006095_14112024_PF_FP_ABST
Abstract
Description
Method and device for reducing overhead of downlink control information during multi-cell scheduling in a 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 for reducing the overhead of downlink control information during multi-cell scheduling in a wireless communication system, and a device capable of performing the same.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] Additionally, technology is being studied to effectively schedule data transmission and reception through multi-cell scheduling.
[0009] The disclosed embodiments provide a device and method for effectively providing services in a mobile communication system. Specifically, a method and device for reducing the overhead of downlink control information are proposed.
[0010] In order to solve the above problems, the present invention provides a method performed by a terminal of a communication system, the method comprising: receiving information for setting uplink data transmission supporting up to 8 layers from a base station; receiving information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) from the base station; receiving downlink control information (DCI) for scheduling the uplink data transmission from the base station, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH; and transmitting the PUSCH to the base station based on the DCI, wherein the scheduling information includes frequency resource allocation information for the PUSCH, and a value of the frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
[0011] In addition, a method performed by a base station of a communication system comprises the steps of: transmitting information for setting uplink data transmission supporting up to 8 layers to a terminal; transmitting information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) to the terminal; transmitting downlink control information (DCI) for scheduling the uplink data transmission to the terminal, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH; and receiving the PUSCH corresponding to the DCI from the terminal, wherein the scheduling information includes frequency resource allocation information for the PUSCH, and a value of the frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
[0012] In addition, in a terminal of a communication system, a transceiver; and receiving information for setting up uplink data transmission supporting up to 8 layers from a base station, receiving information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) from the base station, receiving downlink control information (DCI) for scheduling the uplink data transmission from the base station, the DCI including scheduling information for the PUSCH and a waveform change indicator for the PUSCH, and a control unit configured to transmit the PUSCH to the base station based on the DCI, wherein the scheduling information includes frequency resource allocation information for the PUSCH, and a value of the frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
[0013] In addition, in a base station of a communication system, a transceiver; and a terminal, transmitting information for setting up uplink data transmission supporting up to 8 layers, transmitting information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) to the terminal, transmitting downlink control information (DCI) for scheduling the uplink data transmission to the terminal, the DCI including scheduling information for the PUSCH and a waveform change indicator for the PUSCH, and a control unit configured to receive the PUSCH corresponding to the DCI from the terminal, wherein the scheduling information includes frequency resource allocation information for the PUSCH, and a value of the frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
[0014] The disclosed embodiments provide a device and method capable of effectively providing services in a mobile communication system. Specifically, the overhead of downlink control information is reduced, enabling efficient transmission and reception of control information.
[0015] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.
[0016] FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system.
[0017] Figure 3 is a diagram illustrating an example of bandwidth portion settings in a 5G system.
[0018] FIG. 4 is a diagram illustrating an example of base station beam allocation according to TCI state settings in a 5G system.
[0019] FIG. 5 is a diagram illustrating an example of a control region (CORESET) in which a downlink control channel is transmitted in a 5G system.
[0020] FIG. 6 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.
[0021] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.
[0022] FIG. 8 is a diagram illustrating an example of a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to one embodiment of the present disclosure.
[0023] FIG. 9 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.
[0024] FIG. 10 is a diagram illustrating an example of MC-DCI including multiple FDRA fields according to one embodiment of the present disclosure.
[0025] FIG. 11 is a diagram illustrating an example of an MC-DCI according to one embodiment of the present disclosure, wherein the MC-DCI includes at least one of a cell set indicator field, a scheduling cell indicator field, and a plurality of FDRA fields.
[0026] FIG. 12 is a diagram illustrating an example of a field indicating frequency domain resource allocation information according to a subcarrier spacing of a cell according to one embodiment of the present disclosure.
[0027] FIG. 13 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.
[0028] FIG. 14 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.
[0029] FIG. 15 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0030] FIG. 16 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0032] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.
[0033] 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.
[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.
[0035] 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 through 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.
[0036] 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).
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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 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 each user's data or control information to be distinguished.
[0041] 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).
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] Hereinafter, a / b can be understood as at least one of a or b.
[0047] Below, the frame structure of the 5G system is described in more detail with reference to drawings.
[0048] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.
[0049] 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.
[0050] FIG. 2 is a diagram illustrating an example of a frame, subframe, and slot structure in a 5G system.
[0051] 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 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In the example of Fig. 2, the cases where μ = 0 (204) and μ = 1 (205) as the subcarrier spacing setting value 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 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.
[0052] μ 0141011142022144043148084141601651432032
[0053] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.
[0054] Figure 3 is a diagram illustrating an example of bandwidth portion settings in a 5G communication system.
[0055] 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.
[0056] 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)}
[0057] 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).
[0058] 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 occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set 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.
[0059] 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.
[0060] In a wireless communication system, one or more different antenna ports (or one or more channels, signals, and combinations thereof, but for convenience, they will be referred to as different antenna ports in the following description of the present disclosure) can be associated with each other by a quasi co-location (QCL) setting as shown in Table 3 below. The transmission configuration indicator (TCI) state is to notify the QCL relationship between the PDCCH (or PDCCH demodulation reference signal (DMRS)) and other reference signals (RSs) or channels. When a reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at the antenna port A to the channel measurement from the antenna port B. QCL may need to relate different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Accordingly, NR supports four types of QCL relationships, as shown in Table 3 below.
[0061] QCL typeLarge-scale characteristicsADoppler shift, Doppler spread, average delay, delay spreadBDoppler shift, Doppler spreadCDoppler shift, average delayDSpatial Rx parameter
[0062] The above spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.
[0063] The above QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 4 below. Referring to Table 4, the base station can set one or more TCI states to the terminal and inform the RS referencing the ID of the TCI state, i.e., up to two QCL relationships (qcl-Type1, qcl-Type2) for the target RS. At this time, each QCL information (QCL-Info) included in the above TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 3 above.
[0064] TCI-State ::= SEQUENCE {tci-StateId TCI-StateId,(ID of the corresponding TCI state)qcl-Type1 QCL-Info,(QCL information of the first reference RS of the RS (target RS) referencing the corresponding TCI state ID)qcl-Type2 QCL-Info OPTIONAL, -- Need R(QCL information of the second reference RS of the RS (target RS) referencing the corresponding TCI state ID)...}QCL-Info ::= SEQUENCE {cell ServCellIndex OPTIONAL, -- Need R(serving cell index of the reference RS indicated by the corresponding QCL information)bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated(BWP index of the reference RS indicated by the corresponding QCL information)referenceSignal CHOICE {csi-rs NZP-CSI-RS-ResourceId,ssb SSB-Index(either the CSI-RS ID or SSB ID indicated by the corresponding QCL information) one)},qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},...}
[0065] Figure 4 is a diagram illustrating an example of base station beam allocation according to TCI state settings.
[0066] Referring to FIG. 4, the base station can transmit information about N different beams to the terminal through N different TCI states.
[0067] As shown in FIG. 4, when N=3, the base station can notify that the antenna ports referencing the different TCI states 400, 405, or 410 have different spatial Rx parameters, i.e., are associated with different beams, by setting the qcl-Type2 parameters included in the three TCI states (400, 405, 410) to QCL type D and associated with CSI-RS (channel state information reference signal) or SSB (synchronization signal block, which can be used interchangeably with SS / PBCH block).
[0068] Next, we will specifically explain downlink control information (DCI) in 5G systems.
[0069] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a 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.
[0070] 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 knows that the message was transmitted to the UE.
[0071] 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).
[0072] 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 5 below.
[0073] - 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
[0074] 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 6 below.
[0075] - 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
[0076] 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 7 below.
[0077] - 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
[0078] 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 8 below.
[0079] - 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.
[0080] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.
[0081] FIG. 5 is a diagram illustrating an example of a control region (CORESET) in which a downlink control channel is transmitted in a 5G communication system. FIG. 8 illustrates an example in which two control regions (control region #1 (501), control region #2 (502)) are set within a UE bandwidth part (510) on the frequency axis and one slot (520) on the time axis. The control regions (501, 502) can be set to specific frequency resources (503) within the entire UE bandwidth part (510) 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, 804). Referring to the example illustrated in FIG. 5, control region #1 (501) is set to a control region length of two symbols, and control region #2 (502) is set to a control region length of one symbol.
[0082] 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 9 below.
[0083] 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}
[0084] In Table 9, the tci-StatesPDCCH (simply named TCI state) configuration information may include information on one or more SS / PBCH block (synchronization signal / physical broadcast channel 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.
[0085] FIG. 6 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. 6, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (resource element group, 603), and a REG (603) can be defined as 1 OFDM symbol (601) on the time axis and 1 PRB (physical resource block, 902) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (603) to constitute a downlink control channel allocation unit.
[0086] As illustrated in FIG. 6, if the basic unit to which a downlink control channel is allocated in a 5G system is called a CCE (control channel element, 604), 1 CCE (604) can be composed of multiple REGs (603). Taking the REG (603) illustrated in FIG. 6 as an example, the REG (603) can be composed of 12 REs, and if 1 CCE (604) is composed of 6 REGs (603), 1 CCE (604) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (604), and a specific downlink control channel can be mapped to one or multiple CCEs (904) and transmitted according to the aggregation level (AL) within the control region. CCEs (604) within the control area are distinguished by numbers, and the numbers of the CCEs (604) can be assigned according to a logical mapping method.
[0087] The basic unit of the downlink control channel illustrated in FIG. 6, that is, the REG (603), may include both the REs to which the DCI is mapped and the area to which the DMRS (605), which is a reference signal (RS) for decoding the REs, is mapped. As shown in FIG. 6, three DMRSs (605) may be transmitted within one REG (603). 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.
[0088] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can scan 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 scanning 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 scanning 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.
[0089] In a 5G system, parameters for a search space for PDCCH can be set from a base station to a terminal via higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can set the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, it can include the information in Table 10 below.
[0090] 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},...}.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] - 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
[0095] - DCI format 2_0 with CRC scrambled by SFI-RNTI
[0096] - DCI format 2_1 with CRC scrambled by INT-RNTI
[0097] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI
[0098] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI
[0099] 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.
[0100] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0101] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0102] The RNTIs specified may follow the definitions and uses below.
[0103] C-RNTI (cell RNTI): For terminal-specific PDSCH scheduling purposes
[0104] TC-RNTI (temporary cell RNTI): For terminal-specific PDSCH scheduling purposes
[0105] CS-RNTI (configured scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.
[0106] RA-RNTI (random access RNTI): Used for PDSCH scheduling in the random access phase.
[0107] P-RNTI (paging RNTI): Used for scheduling PDSCH where paging is transmitted.
[0108] SI-RNTI (system information RNTI): Used for scheduling PDSCH where system information is transmitted.
[0109] INT-RNTI (interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.
[0110] TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to indicate power control commands for PUSCH.
[0111] TPC-PUCCH-RNTI (transmit power control for PUCCH (physical uplink control channel) RNTI): Used to indicate power control commands for PUCCH
[0112] TPC-SRS-RNTI (transmit power control for SRS(sounding reference signla) RNTI): Used to indicate power control commands for SRS
[0113] The aforementioned specified DCI formats may follow the definitions in Table 11 below.
[0114] 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
[0115] 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.
[0116] [Mathematical Formula 1]
[0117]
[0118] - L: Integration level
[0119] - n CI : Carrier Index
[0120] - n CCE,p : Total number of CCEs present in CORESET p
[0121] - : slot index
[0122] - : Number of PDCCH candidates for aggregation level L
[0123] - = 0, ..., -1: PDCCH candidate index of aggregation level L
[0124] - l = 0, ..., L -1
[0125] - , 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
[0126] - n RNTI : Terminal identifier
[0127] The value can be 0 for a common search space.
[0128] 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.
[0129] In a 5G system, since multiple search space sets can be configured with different parameters (e.g., parameters in Table 10), the set of search space sets monitored by a terminal at each point in time can be different. For example, if search space set #1 is configured with an X-slot period and search space set #2 is configured with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.
[0130] Next, we describe frequency domain resource assignment (FDRA) for PDSCH and PUSCH in NR.
[0131] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to an embodiment of the present disclosure.
[0132] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, FDRA type 0 (700), FDRA type 1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.
[0133] Referring to FIG. 7, if the terminal is configured to use only FDRA type 0 through upper layer signaling (700), some downlink control information (DCI) for scheduling PDSCH or PUSCH to the terminal is N RBG It contains a bitmap consisting of N bits. The conditions for this will be explained later. At this time, N RBGrefers to the number of RBGs (resource block groups) determined according to the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size as shown in Table 12 below, and data is transmitted to the RBG indicated as 1 by the bitmap.
[0134] Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616
[0135] The size of the frequency resource in the bandwidth part can be defined as the number of RBs included in the bandwidth part. More specifically, if the terminal is instructed to allocate FDRA type-0 resources, the length of the FDRA field of the DCI received by the terminal is the number of RBGs (N) in the bandwidth part. RBG ) and Here, the first RBG within the bandwidth section is It contains RBs of the dog, and the last RBG within the bandwidth part is On the other hand, Contains the RBs of the dog, otherwise, It contains P RBs. The remaining RBGs within the bandwidth portion contain P RBs, where P is the nominal number of RBGs determined according to Table 12 above.
[0136] If the terminal is configured to use only FDRA type 1 through upper layer signaling (705), the DCI that allocates PDSCH or PUSCH to the terminal is It contains frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the bandwidth portion. Through this, the base station can set the starting VRB (virtual resource block, 720) and the length of frequency axis resources (725) allocated continuously therefrom.
[0137] If the terminal does not receive the upper layer signaling vrb-ToPRB-Interleaver, the terminal can connect the resources allocated to the VRB to the PRB without interleaving. If the terminal receives the upper layer signaling vrb-ToPRB-Interleaver, the upper layer signaling has a value of 2 or 4, and this value can be the unit of multiple RBs that perform interleaving. In other words, RB bundles of 2 or 4 units can be used for interleaving.
[0138] If the terminal Starting from the position and length The i-th BWP consisting of RBs is set, and the vrb-ToPRB-Interleaver is L i If set to , the terminal will set the i-th BWP It can be divided into RB bundles, each RB bundle having L i It can be made up of RBs.
[0139] - In the i-th BWP, the first RB bundle is It can be made up of RBs.
[0140] - In the i-th BWP, the last RB bundle is if If the value is greater than 0 It can be made up of RB of a dog, otherwise L i It can be made up of RBs.
[0141] - In the i-th BWP, the remaining RB bundles are L i It can be made up of RBs.
[0142] At this time, VRB can be connected to PRB according to the following method.
[0143] - The last VRB bundle can be connected to the last PRB bundle.
[0144] - jth (j = 0, 1, ..., N bundle - 1) A VRB bundle can be connected to the f(j)th PRB bundle, and f(j) can be expressed as in the following mathematical expression 2.
[0145] [Equation 2]
[0146] f(j) = rC + c
[0147] j = cR + r
[0148] r = 0, 1, ... , R-1
[0149] c = 0, 1, ... , C-1
[0150] R=2
[0151]
[0152] FIG. 8 is a diagram illustrating an example of a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to an embodiment of the present disclosure. In FIG. 8, the first and last VRB bundles (800) in a BWP consisting of 10 RBs are represented as a case (810) in which one VRB is comprised. Therefore, the number of VRB bundles, N bundle can be 6, and by the above mathematical expression 2 =3 can be calculated. Therefore, since the jth VRB bundle can be connected to the f(j)th PRB bundle by the above mathematical expression 2, the connection from the VRB bundle to the PRB bundle can be performed as 820 through the result 830 calculated by the above mathematical expression 2. For example, VRB bundle 1 (840) can be connected to PRB bundle 3 (850).
[0153] As in 710 of FIG. 7, if a terminal is configured to use both FDRA type-0 resource allocation and FDRA type-1 resource allocation through upper layer signaling, some DCIs that allocate PDSCH / PUSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring FDRA type-0 resource allocation and the payload (720, 725) for configuring FDRA type-1 resource allocation. The conditions for this will be explained later. At this time, one bit may be added to the most significant bit (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that FDRA type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that FDRA type-1 resource allocation is used.
[0154] If the terminal has been set to use the FDRA type-2 resource allocation method through upper layer signaling, the terminal can be instructed by the base station about the FDRA type-2 resource allocation according to the following method.
[0155] Additionally, the terminal can be instructed of a set of M interlace indices through RB allocation information from the base station.
[0156] The interlace index m ∈ {0, 1, ... , M-1} can be composed of common RBs {m, M+m, 2M+m,3M+m, ...}, and M can be defined as in Table 13.
[0157] μM01015
[0158] RB in interlace m and bandwidth part i and common RB The relationship with can be defined as follows:
[0159] -
[0160] - where is the common resource block where bandwidth part starts relative to common resource block 0. μ is subcairre spacing index
[0161] When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlace set with m0 + l indices can be notified from the base station to the terminal. In addition, the resource allocation field can be configured with a resource individuation value (RIV). The resource individuation value is 0≤RIV. <M(M+1) / 2, L=0, 1, ... , L-1 일 때, 시작 인터레이스 m0와 연속된 인터레이스 수 L (L≥1)로 구성될 수 있으며, 그 값은 다음과 같다.
[0162] if then
[0163] RIV = M(L-1)+m0
[0164] else
[0165] RIV = M(M-L+1) + (M-1-m0)
[0166] When the resource indicator value is RIV ≥ M(M+1) / 2, the resource indicator value is composed of the start interlace index m0 and l values and can be composed as shown in Table 14.
[0167] RIV-M(M+1) / 2m0l00{0, 5}10{0, 1, 5, 6}21{0, 5}31{0, 1, 2, 3, 5, 6, 7, 8}42{0, 5}52{0, 1, 2, 5, 6, 7}63{0, 5}74{0, 5}
[0168] When the subcarrier spacing is 30 kHz (u=1), RB allocation information can be notified from the base station to the terminal in the form of a bitmap indicating the interlaces allocated to the terminal. The size of the bitmap is M, and each bit in the bitmap corresponds to an interlace. The order of the interlace bitmap can be mapped from the MSB to the LSB (least significant bit) from interlace index 0 to M-1.
[0169] Also, the least significant bit (LSB) of the FDRA field for 15 kHz and 30 kHz can mean a set of consecutive RBs of PUSCH scheduled with DCI format 0_1. The Y bit is a resource indication value (RIV RBset ) can be composed of. , l=0, 1, ... L RBset - RIV in 1 RBset The value starts at the RB set ( ) and the number of consecutive RB sets (L RBset , L RBset ≥1) can be determined. RIV RBset The value can be defined as follows:
[0170] if then
[0171]
[0172] else
[0173]
[0174] It refers to the number of RB sets included in the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set by upper signaling (or preset).
[0175] Below, a time domain resource allocation method for data channels in a 5G system is described.
[0176] A base station can set up a table for time domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) to a terminal via higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for the PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for the PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as Table 15 or Table 16 below may be transmitted from the base station to the terminal.
[0177] PDSCH-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)}
[0178] PUSCH-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)}
[0179] 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., it can be indicated by the time domain resource allocation (TDRA) 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.
[0180] FIG. 9 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to an embodiment of the present disclosure.
[0181] Referring to FIG. 9, 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 start position (900) and length (905) of the OFDM symbol within a slot dynamically indicated through DCI.
[0182] Next, the scheduling method for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by UL grants within DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.
[0183] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 17 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 17 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 17, except dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by pusch-Config of Table 18. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of Table 17, the terminal applies tp-pi2BPSK in pusch-Config of Table 18 to PUSCH transmission operated by the configured grant.
[0184] 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...}.
[0185] 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 18, is 'codebook' or 'nonCodebook'.
[0186] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by configured grant. 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 18, the UE does not expect to be scheduled with DCI format 0_1.
[0187] 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...}.
[0188] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or 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).
[0189] 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.
[0190] 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'.
[0191] 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.
[0192] 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.
[0193] 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.
[0194] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations on a precoder for SRS transmission through measurements on the NZP CSI-RS 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.
[0195] 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.
[0196] 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.
[0197] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. 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.
[0198] 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.
[0199] Below, we specifically describe frequency hopping of the uplink data channel (PUSCH) in a 5G system.
[0200] In the 5G system, two methods are supported for frequency hopping of uplink data channels for each PUSCH repetition transmission type. First, PUSCH repetition transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, and PUSCH repetition transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.
[0201] The intra-slot frequency hopping method supported by PUSCH repetitive transmission type A is a method in which a terminal transmits by changing the allocated frequency domain resources by a set frequency offset in two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be expressed using mathematical equation 3.
[0202] [Equation 3]
[0203]
[0204] In Equation 3, i=0 and i=1 represent the first and second hops, respectively, and RB start Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. RB offset The upper layer parameter indicates the frequency offset between two hops. The number of symbols in the first hop is can be represented as , and the number of symbols in the second hop is can be expressed as is the length of PUSCH transmission within one slot, expressed as the number of OFDM symbols.
[0205] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal changes the allocated resources of the frequency domain by a set frequency offset for each slot and transmits them. In inter-slot frequency hopping, The starting RB during a slot can be expressed by Equation 4.
[0206] [Equation 4]
[0207]
[0208] In mathematical equation 4, is the current slot number, RB in multi-slot PUSCH transmission. start Indicates the starting RB within the UL BWP and is calculated from the frequency resource allocation method. RB offsetIndicates the frequency offset between two hops through upper layer parameters.
[0209] Next, the inter-repetition frequency hopping method supported by PUSCH repetitive transmission type B is to transmit the allocated resources in the frequency domain for one or more actual repetitions within each nominal repetition by shifting them by a set frequency offset. RB is the index of the starting RB in the frequency domain for one or more actual repetitions within the nth nominal repetition. start (n) can follow the following mathematical formula 5.
[0210] [Equation 5]
[0211]
[0212] In Equation 5, n is the index of nominal repetition, RB offset Indicates the RB offset between two hops via upper layer parameters.
[0213] Next, we describe TPMI n indicated from the base station through DCI during codebook-based PUSCH transmission.
[0214] If the terminal is scheduled for 1-layer transmission using a single PUSCH antenna port by the base station via DCI or higher layer signaling, the TPMI can be defined as W=1. Otherwise, that is, if the terminal is scheduled for 1-layer or higher PUSCH scheduling using multiple PUSCH antenna ports by the base station via DCI or higher layer signaling, the TPMI W can be defined through Tables 19 to 25 below.
[0215] [Table 19]
[0216]
[0217] Table 19 above shows the TPMI of 1 layer when the terminal has two PUSCH antenna ports. In Table 19 above, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 and 1, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 5.
[0218] [Table 20]
[0219]
[0220] Table 20 above shows the TPMI for a 1-layer terminal having four PUSCH antenna ports and using transform precoding (i.e., using a DFTS-OFDM waveform). In Table 20, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 3, if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 11, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 27.
[0221] [Table 21]
[0222]
[0223] Table 21 above shows the TPMI for a 1-layer terminal having 4 PUSCH antenna ports and no transform precoding (i.e., CP-OFDM waveform is used). In Table 21, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 3, if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 11, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station can select and instruct the terminal by one of TPMI indices 0 to 27.
[0224] [Table 22]
[0225]
[0226] Table 22 above shows a TPMI for a 2-layer terminal having two PUSCH antenna ports and without transform precoding (i.e., using a CP-OFDM waveform). In Table 22 above, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal to select TPMI index 0, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal to select one of TPMI indices 0 to 2.
[0227] [Table 23]
[0228]
[0229] Table 23 above shows a TPMI for a 2-layer terminal having 4 PUSCH antenna ports and without transform precoding (i.e., using CP-OFDM waveforms). In Table 23, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 5, if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 13, and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 21.
[0230] [Table 24]
[0231]
[0232] Table 24 above shows a TPMI for a 3-layer terminal having 4 PUSCH antenna ports and no transform precoding (i.e., CP-OFDM waveform is used). In Table 24, if the terminal has a non-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by TPMI index 0; if the terminal has a partial-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 2; and if the terminal has a full-coherent antenna structure and has reported the corresponding terminal capability to the base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 6.
[0233] [Table 25]
[0234]
[0235] Table 25 above shows a 4-layer TPMI when a terminal has 4 PUSCH antenna ports and no transform precoding is used (i.e., CP-OFDM waveform is used). In Table 25, if a terminal has a non-coherent antenna structure and has reported its corresponding terminal capability to a base station, the base station may select and instruct the terminal by TPMI index 0; if a terminal has a partial-coherent antenna structure and has reported its corresponding terminal capability to a base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 2; and if a terminal has a full-coherent antenna structure and has reported its corresponding terminal capability to a base station, the base station may select and instruct the terminal by one of TPMI indices 0 to 4.
[0236] In LTE and NR, a terminal, while connected to a serving base station, can perform a procedure to report its supported capabilities to the base station. In the description below, this is referred to as a UE capability report.
[0237] A base station can transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, multiple RAT type-specific UE capabilities can be requested through a single RRC message container transmitted by the base station, or the base station can include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can configure a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, a UE capability request can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). Additionally, the terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but the base station may request it under any conditions when necessary.
[0238] In the above step, the terminal receiving a terminal capability report request from the base station configures its terminal capabilities based on the RAT type and band information requested from the base station. Below, the method by which a terminal configures its terminal capabilities in the NR system is summarized.
[0239] 1. If the UE receives a list of LTE and / or NR bands from the base station as a UE capability request, the UE configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it configures a candidate list of BCs for EN-DC and NR SA based on the bands requested from the base station via FreqBandList. Furthermore, the bands are prioritized in the order listed in FreqBandList.
[0240] 2. If the base station requests a terminal capability report by setting the "eutra-nr-only" flag or the "eutra" flag, the terminal completely removes NR SA BCs from the list of BC candidates configured above. This operation can only occur when the LTE base station (eNB) requests the "eutra" capability.
[0241] 3. The terminal then removes fallback BCs from the BC candidate list constructed in the above step. Here, a fallback BC is a BC obtained by removing at least one band corresponding to an SCell from a random BC. This step can be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step also applies to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list."
[0242] 4. The terminal selects BCs to report by selecting BCs that match the requested RAT type from the final "candidate BC list" above. In this step, the terminal constructs the supportedBandCombinationList in a set order. That is, the terminal constructs BCs and terminal capabilities to report according to the preset rat-Type order (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.
[0243] 5. Also, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set is included only in UE-NR-Capabilities.
[0244] After terminal capabilities are configured, the terminal transmits a terminal capability information message containing the terminal capabilities to the base station. Based on the terminal capabilities received from the terminal, the base station then performs appropriate scheduling and transmission / reception management for the terminal.
[0245] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The present disclosure will describe the examples through a number of embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination. The following describes embodiments of the present disclosure using a 5G system as an example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.
[0246] 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.
[0247] In the present disclosure below, determining the priority between A and B can be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an operation corresponding to it, or omitting or dropping an operation for a lower priority. The term "slot" used in the present disclosure below is a general term that can refer to a specific time unit corresponding to a TTI (Transmit Time Interval), and specifically can mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.
[0248] 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.
[0249] - MIB
[0250] - SIB or SIB
[0251] - RRC
[0252] - MAC CE (medium access control control element)
[0253] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the physical layer channel or signaling below.
[0254] - PDCCH
[0255] - DCI
[0256] - UE-specific DCI
[0257] - Group common DCI
[0258] - Common DCI
[0259] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)
[0260] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)
[0261] - PUCCH
[0262] - UCI (uplink control information)
[0263] <Embodiment 1: MC-DCI Scheduling Method>
[0264] As one embodiment of the present disclosure, a scheduling method using MC-DCI (Multi-cell scheduling DCI) is described. This embodiment can be operated in combination with other embodiments.
[0265] In the present disclosure, one DCI may be a single DCI (single-DCI) or may be a single DCI format, and multiple DCIs may be multiple DCIs (Multi-DCI) or may be multiple DCI formats. In the present disclosure, one DCI may be one PDCCH and / or may be transmitted and received through one PDCCH, and multiple DCIs may be multiple PDCCHs and / or may be transmitted and received through multiple PDCCHs. In the following, scheduling of a specific cell by a DCI may be understood as scheduling a data channel on the specific cell by the DCI. In addition, scheduling for a specific cell may be understood as scheduling a data channel on the specific cell.
[0266] Typically, a terminal receives one DCI, and the DCI may include scheduling information for one cell. For example, in the case of DCI format 0_0 / 0_1 / 0_2, one PUSCH may be scheduled for one uplink cell. In addition, in the case of DCI format 1_0 / 1_1 / 1_2, one PDSCH may be scheduled for one downlink cell. Here, the scheduled cell may be indicated by the CIF (carrier indication field) of the DCI format.
[0267] However, according to this method, when PDSCH or PUSCH is scheduled in each of multiple cells, multiple DCIs must be transmitted and received. Therefore, a lot of DCI overhead may occur. To reduce the DCI overhead, one DCI may schedule PDSCH or PUSCH in each of multiple cells. This may be conveniently referred to as MC-DCI (multi-cell DCI). In the present disclosure, MC-DCI may be one DCI that schedules PDSCH and / or PUSCH in each of multiple cells. In this case, the DCI format of the MC-DCI may be DCI format 1_X or 1_3 for PDSCH scheduling, and may be DCI format 0_X or 0_3 for PUSCH scheduling.
[0268] Within a specific cell, a terminal can report the number of candidates for a cell set that can be scheduled via MC-DCI to the base station as the terminal capability. At this time, a cell set means a set including multiple cells. For example, cell set 1 may include cell 1, cell 2, cell 3, and cell 4, and cell set 2 may include cell 5, cell 6, cell 7, and cell 8. The maximum number of cells that can be included in a cell set may be 4, and the cells included in each cell set may not overlap with each other. At this time, the number of candidates for a cell set that a terminal can report as the terminal capability may be 1 or 2 or more.
[0269] If the terminal reports the number of candidates for a cell set that can be scheduled within a specific cell as 1 via MC-DCI, the terminal can expect no cell set indicator field in the MC-DCI, and the terminal can expect scheduling for cells within one cell set when it receives MC-DCI from the base station.
[0270] If a terminal reports the number of candidates for a cell set that can be scheduled within a specific cell through MC-DCI as two or more, the terminal can expect that a cell set indicator field exists in the MC-DCI, and the terminal can receive a cell set index from the base station through the field. The terminal can receive scheduling information for one or more cells within one of multiple cell sets through MC-DCI. In the following, it is assumed that the number of candidates for the cell set reported by the terminal is one, and a case in which the number of candidates for the cell set is two or more is not excluded.
[0271] The cells that can be scheduled in MC-DCI can be configured by a higher layer. For example, it is assumed that MC-DCI can schedule cell 0, cell 1, cell 2, and cell 3 (simultaneously). When the terminal receives the MC-DCI, the terminal can receive scheduling information for cell 0, cell 1, cell 2, and cell 3. That is, the terminal can obtain scheduling information for cell 0, cell 1, cell 2, and cell 3 from the MC-DCI. For example, it can be configured from a higher layer that MC-DCI can schedule cell 0, cell 1, cell 2, and cell 3. Here, the scheduling information can include time domain resource allocation (TDRA) information and / or frequency domain resource allocation (FDRA) information for transmitting and receiving data channels (PDSCH for downlink, PUSCH for uplink) in each cell. Accordingly, the terminal can obtain scheduling information for each cell through the MC-DCI and transmit and receive data channels on each cell.
[0272] In certain circumstances, a base station may not be able to schedule all cells configured for a terminal. Scheduling may not be possible for at least some of the multiple cells configured by the base station for a terminal. For example, a base station may configure four cells (e.g., Cell 0, Cell 1, Cell 2, and Cell 3) for scheduling with MC-DCI for a terminal, but the base station may not be able to schedule data channels for some of these cells, for example, because they are scheduled for other terminals, channel conditions are poor, or for other various reasons. In this case, the base station must be able to indicate to the terminal which cells among the pre-configured cells that can be scheduled with MC-DCI are scheduled. In other words, the base station must be able to indicate which one or more cells are (actually) scheduled among the multiple cells configured to be scheduled with MC-DCI.
[0273] This may be directed based on one of the following two methods, or a combination of at least one of the following two methods.
[0274] In the first method, the terminal can obtain information indicating cells that are simultaneously scheduled with the current MC-DCI (co-scheduled cells) among the preset cells (e.g., cell 0, cell 1, cell 2, cell 3) from the MC-DCI. That is, among a plurality of cells that are set to be scheduled with the MC-DCI, one or more cells that are (actually) simultaneously scheduled through the MC-DCI can be identified based on the MC-DCI. More specifically, the base station can set a table including cells that are simultaneously scheduled for the terminal. For example, the rows of this table can have unique indexes. The index of each row can include the indexes of cells that are simultaneously scheduled (and / or each row). For example, {cell 0, cell 1} can be set for row 0, {cell 2, cell 3} for row 1, and {cell 0, cell 1, cell 2, cell 3} for row 2. An example of a table set for a terminal can be found in Table 26.
[0275] indexCo-scheduled cell0{0, 1}1{2, 3}2{0, 1, 2, 3}
[0276] The terminal can obtain a value indicating the index of the row from the MC-DCI. Accordingly, the terminal can determine the cell to be (actually) scheduled based on the value. For example, the MC-DCI can include information about the index of the row, and the terminal can identify the cell to be scheduled based on the index of the row obtained from the MC-DCI and the table. For example, if row 0 is indicated from the MC-DCI, the terminal can identify that cell 0 and cell 1 are scheduled cells. For example, if row 1 is indicated from the MC-DCI, the terminal can identify that cell 2 and cell 3 are scheduled cells. For example, if row 2 is indicated from the MC-DCI, the terminal can identify that cell 0, cell 1, cell 2, and cell 3 are scheduled cells.
[0277] In the present disclosure, a table is set for a mapping relationship between a scheduled cell (or an index of a scheduled cell) and an index indicated from DCI, and a scheduled cell can be identified based on the table and the index indicated from DCI.
[0278] Although the present disclosure has described an embodiment in which cells to be scheduled simultaneously are identified based on the index of a row of a table, the present disclosure is not limited thereto, and for example, cells to be scheduled may also be identified based on the index of a column of a table, in which case the rows in the above-described embodiment may be replaced with columns.
[0279] In the present disclosure, if the number of candidates for a cell set that can be scheduled through MC-DCI received by a terminal within a specific cell is two or more, the terminal can set a table as described above for each cell set, and the terminal can determine which table for which cell set to use through a cell set indicator field in the MC-DCI.
[0280] In a second method, the terminal can determine whether there is scheduling information for one or more cells based on the FDRA field of MC-DCI.
[0281] If the terminal reports the number of candidates for a set of cells that can be scheduled within a specific cell as 1 via MC-DCI, the terminal can expect that there will be as many FDRA fields in the MC-DCI as the number of cells included in the set of cells. In this case, if the terminal has not received a higher layer signaling configuration such as the table mentioned in the first method above, the terminal can determine whether scheduling information for each cell exists based on one or more FDRA fields in the MC-DCI.
[0282] If the terminal reports the number of candidate cell sets that can be scheduled via MC-DCI within a specific cell as two or more through the terminal capability report, the terminal can expect the presence of as many FDRA fields as the maximum number of cells included in each of the two or more cell sets. For example, if the terminal reports the number of candidate cell sets as two, and the first cell set includes three cells and the second cell set includes four cells, the terminal can expect the presence of four FDRA fields in the MC-DCI, which is the maximum number of cells included in each of the first and second cell sets.
[0283] - If the terminal has not received the upper layer signaling configuration such as the table mentioned in the first method for all cell sets, the terminal can determine whether scheduling information for each cell exists based on the FDRA fields in the MC-DCI. If the number of cells in the cell set indicated to the terminal through the cell set indicator field is less than the number of FDRA fields, the terminal can consider the FDRA field corresponding to the number of cells in the indicated cell set as an ascending index of the FDRA field, and can ignore the FDRA fields corresponding to indices greater than the number of cells.
[0284] - If the terminal has received the upper layer signaling configuration, such as the table mentioned in the first method, for a specific cell set, but has not received it for the remaining cell sets, the terminal can expect that the MC-DCI includes a scheduling cell indicator field that can indicate the index of a specific row in the table configured with the upper layer signaling, such as the first method. The terminal can determine which cell set is indicated through the cell set indicator field in the MC-DCI, and can use a method of interpreting the scheduling cell indicator field or the FDRA field when determining the presence or absence of scheduling information for one or more cells. In this case, the scheduling cell indicator field that can be included in the MC-DCI may be a separate field distinct from the CIF (carrier indication field), or the CIF may replace the scheduling cell indicator field in the MC-DCI. If the terminal is indicated to a set of cells that have received upper layer signaling such as the table above through the cell set indicator field in the MC-DCI, the terminal can be indicated to the presence or absence of scheduling information for one or more cells through the scheduling cell indicator field. If the terminal is indicated to a set of cells for which upper layer signaling such as the table above has not been set through the cell set indicator field in the MC-DCI, the terminal can be indicated to the presence or absence of scheduling information for one or more cells through the FDRA field.
[0285] FIG. 10 is a diagram illustrating an example of MC-DCI including multiple FDRA fields according to one embodiment of the present disclosure.
[0286] Referring to FIG. 10, MC-DCI (1000) may include multiple FDRA fields. And there may be a corresponding cell for each FDRA field. That is, when cells that can be simultaneously scheduled by MC-DCI (1000) are set as cell 0 (1020), cell 1 (1021), cell 2 (1022), and cell 3 (1023), MC-DCI (1000) may include an FDRA field (1010) for cell 0, an FDRA field (1011) for cell 1, an FDRA field (1012) for cell 2, and an FDRA field (1013) for cell 3. Based on the values of the FDRA fields, it may be determined whether each cell is scheduled. Cells scheduled based on the values of the FDRA fields may be called actually co-scheduled cells.
[0287] FIG. 11 is a diagram illustrating an example of an MC-DCI according to one embodiment of the present disclosure, wherein the MC-DCI includes at least one of a cell set indicator field, a scheduling cell indicator field, and a plurality of FDRA fields.
[0288] Referring to FIG. 11, MC-DCI (1100) may include at least one of a cell set indicator field (1101), a scheduling cell indicator field (1102), and a plurality of FDRA fields (1105, 1106, 1107, 1108). As described above, if a terminal receives MC-DCI within a specific cell and reports to the base station that the number of candidates for a cell set that can be scheduled is two or more, the terminal may expect the presence of the cell set indicator field (1101) in the MC-DCI, and if one is reported to the base station, the field may not be present. In Fig. 11, a case is illustrated where a terminal reports the number of candidate cell sets as 2, and cell set 0 (1110) may include three cells, namely cell 0 (1111), cell 1 (1112), and cell 2 (1113), and cell set 1 (1120) may include cell 3 (1121), cell 4 (1122), cell 5 (1123), and cell 6 (1124). Accordingly, the terminal may expect that 4 FDRA fields, which is the maximum number of cells included in each of cell set 0 (1110) and cell set 1 (1120), are present in the MC-DCI.
[0289] In addition, in Fig. 11, it is assumed that the terminal has not set up upper layer signaling, such as the table above, for cell set 0 (1110). Therefore, as in the second method, the presence or absence of scheduling information for cells in cell set 0 (1110) can be indicated by the FDRA fields (1105, 1106, 1107, 1108) in MC-DCI. At this time, since there are three cells in cell set 0 (1110), the terminal can be indicated with scheduling information for cell 0 (1111), cell 1 (1112), and cell 2 (1113) through the first, second, and third FDRA fields (1108, 1107, 1106).
[0290] In addition, in FIG. 11, it can be assumed that the terminal has received upper layer signaling, such as the table, for cell set 1 (1120). Accordingly, as in the first method, the presence or absence of scheduling information for cells within cell set 1 (1120) can be indicated by the scheduling cell indicator field (1102) within MC-DCI. For example, the terminal can be indicated to a specific row among all rows within the table set by upper layer signaling, through the scheduling cell indicator field (1102) within MC-DCI, and the row can indicate scheduling information for, for example, cell 3 (1121) and cell 5 (1123) within cell set 1 (1120).
[0291] A terminal can receive FDRA fields included in a single DCI and determine a cell corresponding to each FDRA field. The terminal can determine whether a data channel is scheduled for the cell based on the FDRA type of the cell and the value of the FDRA field. The terminal can identify whether a cell is scheduled and / or whether a scheduled cell and / or an unscheduled cell based on one or more of the FDRA type or the FDRA field. For example, the method of interpreting the FDRA field may vary depending on the subcarrier spacing of the corresponding cell.
[0292] The FDRA field can be divided into valid and invalid values. A valid value may be one in which a frequency domain assignment corresponding to the value in the FDRA field exists. Conversely, an invalid value may be one in which a frequency domain assignment corresponding to the value in the FDRA field does not exist.
[0293] For example, valid and invalid values are described based on FDRA type-0. FDRA type-0 is a method of indicating RBs (or RBGs) to be scheduled based on a bitmap. Here, each bit may have corresponding RBs (or RBGs). If the bit is '1', the corresponding RBs (or RBGs) may be scheduled, and if the bit is '0', the corresponding RBs (or RBGs) may not be scheduled. Therefore, if at least one bit is '1', it may be determined as a valid value, and if all bits are '0', it may be determined as an invalid value.
[0294] For example, valid and invalid values are explained based on FDRA type-1. FDRA type-1 is a method of indicating RBs to be scheduled based on RIV. Here, FDRA type-1 can schedule consecutive RBs in the frequency domain. FDRA type-1 can indicate the index of the start RB and the number of consecutive RBs. The RIV value can be one of 0, 1, ..., N * (N + 1) / 2 - 1. Here, N is the number of RBs included in the frequency domain (or BWP where the data channel is scheduled). Therefore, if the RIV value is one of 0, 1, ..., N * (N + 1) / 2 - 1, it can be determined as a valid value, and a value equal to or greater than N * (N + 1) / 2 can be determined as an invalid value.
[0295] Some cells scheduled by MC-DCI may be in licensed bands, while others may be in unlicensed bands (or shared spectrum). For example, for cells in unlicensed bands, FDRA type-2 may need to be used for uplink scheduling.
[0296] When a terminal is set to FDRA type-2 in a cell, whether the cell is scheduled or not can be determined based on at least one or a combination of the following.
[0297] If the above cell is a 15kHz subcarrier spacing, the terminal can determine that the cell is not scheduled if the value of the FDRA field is as follows.
[0298] In the first case, all bit(s) of the FDRA field are "1".
[0299] The second case is when all of the first 6 bits of the FDRA field are "1". That is, when all 6 MSBs of the bits of the FDRA field are "1".
[0300] The third case is when all of the trailing Y bit(s) of the FDRA field are "1". That is, when all of the Y LSBs of the bits of the FDRA field are "1".
[0301] If the above cell is a 30 kHz subcarrier spacing, the terminal can determine that the cell is not scheduled if the value of the FDRA field is as follows.
[0302] In the first case, the first 5 bit(s) of the FDRA field are all "0" and the following Y bit(s) are all "1". That is, the 5 MSBs of the FDRA field are all "0" and the Y LSBs are all "1".
[0303] The second case is when all bit(s) of the FDRA field are "0".
[0304] The third case is when the first 5 bits of the FDRA field are all "0". That is, when all 5 MSBs of the bits of the FDRA field are "0".
[0305] The fourth case is when all of the trailing Y bit(s) of the FDRA field are "1". That is, when all of the Y LSBs of the bits of the FDRA field are "1".
[0306] Each situation is described in more detail below.
[0307] Situation 1. When one cell has a 15 kHz subcarrier spacing.
[0308] The terminal can check the subcarrier spacing and FDRA type information of each cell included in the set of candidate cells scheduled by MC-DCI. If one of the cells included in the set of candidate cells scheduled by MC-DCI is configured to use FDRA type-2, the terminal can check whether the subcarrier spacing of the cell is 15 kHz (μ=0) or 30 kHz (μ=1). This embodiment may be the case where the terminal has confirmed that the subcarrier spacing of the cell is 15 kHz (μ=0).
[0309] FIG. 12 is a diagram illustrating an example of a field indicating frequency domain resource allocation information according to a subcarrier spacing of a cell according to one embodiment of the present disclosure.
[0310] Referring to 1200 of FIG. 12, when the subcarrier spacing of a cell is 15 kHz, the length of a field indicating frequency domain allocation information of the cell within MC-DCI may be 6+Y bit(s). Here, 6 bit(s) (1210) may indicate the start index (m0) and length (L) of M=10 interlaces included in one RB-set, and Y bit(s) (1212) may indicate the scheduled RB-set. Here, the Y bit(s) can indicate the index and length of the starting RB set among the RB sets included in the UL BWP. In the present disclosure may be the number of RB-sets set for indicated active UL BWP. In the present disclosure, for convenience, 6 bit(s) and Y bit(s) may be referred to as RIV method (or RIV-like).
[0311] More specifically, the 6 bit(s) (1210) are as follows:
[0312] When μ=0, X=6 MSBs of resource block allocation information (or frequency domain resource allocation information) can represent a set of interlace indices m0+l allocated to the UE. Here, the representation for the set of interlace indices is composed of RIV. 0≤RIV <M(M+1) / 2이고 l=0,1,...,L-1인 경우 리소스 표시 값은 시작 인터레이스 인덱스 m0과 연속적인 인터레이스 인덱스의 수에 해당한다. RIV 값은 다음과 같이 정의된다.
[0313] if then
[0314] RIV = M(L-1)+m0
[0315] else
[0316] RIV = M(M-L+1) + (M-1-m0)
[0317] For RIV ≥ M(M+1) / 2, the RIV values correspond to the starting interlace index m0 and l values in Table 27 below.
[0318] RIV-M(M+1) / 2m0l00{0, 5}10{0, 1, 5, 6}21{0, 5}31{0, 1, 2, 3, 5, 6, 7, 8}42{0, 5}52{0, 1, 2, 5, 6, 7}63{0, 5}74{0, 5}
[0319] Referring to the RIV formula or Table 27 above, among the RIV values, 0, 1, ..., M(M+1) / 2-1(=54) can indicate the starting interlace index and the number of consecutive interlace indices according to the RIV formula, and thereafter, RIV = M(M+1) / 2=55, M(M+1) / 2+1=56, ..., M(M+1) / 2+7=62 can indicate the starting interlace index (m0) and the l value according to Table 27. The 6 bit(s) of the RIV value can represent one of the values 0, 1, ..., 63, and 0, 1, ..., 62 are the values used to schedule the interlace. However, RIV=63 (6 bit(s) in binary are '111111') may be an unused value. In other words, there may not be a scheduled interlace corresponding to the above value (RIV=63). Therefore, using the above value (RIV=63 (6 bit(s) in binary are '111111')), an unscheduled cell can be indicated.
[0320] More specifically, the Y bit(s) (1212) are as follows:
[0321] When μ=0 to μ=1, the resource block allocation information (or frequency domain resource allocation information) The LSB indicates a contiguous RB set to the terminal. For example, the Y bit(s) may be present in DCI format 0_1. The resource allocation field It consists of 0≤ < , l=0,1,...,L RBset For -1, the resource indication value is the starting RB set index ( ) and the number of consecutive RB sets (L RB-set ) is indicated. The resource indication value is defined as follows.
[0322] if then
[0323]
[0324] else
[0325]
[0326] where , L RB-set ≥ 1 and shall not exceed
[0327] Referring to the above formula, the following can be observed.
[0328] - When 1 RB-set is included in UL BWP ( =1), Y=0 bit(s) (Y=0). Therefore, when Y=0 bit(s), cells that are not scheduled with the Y bit(s) may not be indicated.
[0329] - When two RB-sets are included in the UL BWP ( = 2), Y=2 bit(s) (Y=2). Here, RIV RB-set =0,1,2 can be used to indicate the starting RB set index and the number of consecutive RB sets. The Y bit(s) can have the values 0,1,...,3. Therefore, there can be no scheduled RB-set corresponding to 3 (both bit(s) are '11', 2 bit(s) are '11' in binary). Therefore, an unscheduled cell can be indicated using the above value (3 (2 bit(s) are '11' in binary).
[0330] - When 3 RB-sets are included in UL BWP ( = 3), Y=3 bit(s) (Y=3). Here, RIV RB-set=0,1,2,3,4,5 can be used to indicate the starting RB set index and the number of consecutive RB sets. The Y bit(s) can have the values 0,1,...,7. Therefore, there can be no scheduled RB-set corresponding to the Y bit(s) being 7 (all 3 bit(s) are '111'. In binary, 3 bit(s) are '111'). Therefore, an unscheduled cell can be indicated using the above value (7 (3 bit(s) are '111' in binary).
[0331] - When 4 RB-sets are included in UL BWP ( =4), Y=4 bit(s) (Y=4). Here, RIV RB-set =0,1,...,9 are used to indicate the starting RB set index and the number of consecutive RB sets. The Y bit(s) can have the values 0,1,...,15. Therefore, there may be no scheduled RB-set corresponding to the Y bit(s) equal to 15 (all 4 bit(s) are '1111'. In binary, the 4 bit(s) are '1111'). Therefore, an unscheduled cell can be indicated using the above value (15 (4 bit(s) are '1111' in binary).
[0332] - When 5 RB-sets are included in UL BWP ( =5), Y=4 bit(s)(Y=4). Here, RIV RB-set =0,1,...,14 are used to indicate the starting RB set index and the number of consecutive RB sets. The Y bit(s) can have the values 0,1,...,15. Therefore, there may be no scheduled RB-set corresponding to the Y bit(s) equal to 15 (all 4 bit(s) are '1111'. In binary, the 4 bit(s) are '1111'). Therefore, an unscheduled cell can be indicated using the above value (15 (in binary, the 4 bit(s) are '1111')).
[0333] In summary, in all cases except for the case where Y=0 among the sizes of Y bit(s), an unscheduled cell may be indicated if all Y bit(s) are '1'. That is, if all bits included in the Y LSB of FDRA are '1', an unscheduled cell may be indicated.
[0334] In the present disclosure, the method for indicating that a cell with a 15 kHz subcarrier spacing is not scheduled may be one or a combination of at least one of the following. In the description of the present method, the FDRA field is a field corresponding to a cell with the 15 kHz subcarrier spacing. And the FDRA type may be FDRA type-2.
[0335] - In the first method, the terminal can determine whether a cell is scheduled based on all bits (6+Y bit(s)) of the FDRA field. For example, if all bits of the FDRA field are '1', the terminal can determine that the cell is an unscheduled cell. Here, the FDRA field can include 6 MSBs and Y LSBs. Therefore, the terminal can determine that the cell of the 15 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all bits of the total 6+Y bit(s) are '1' (if all bit values of the bits included in the 6+Y bit(s) are 1).
[0336] For example, if all 6 MSBs are '1' and the remaining Y LSBs are not all '1' (if the bit values of the bits included in the 6 MSBs are all 1 and at least some of the bit values of the bits included in the Y LSBs are 0 or if the bit values of the bits included in the 6 MSBs are all 1 and the bit values of the bits included in the Y LSBs are all 0), the terminal can determine that the DCI format including the above information is an error case. Alternatively, if all Y LSBs are not all '1' and the remaining 6 MSBs are not all '1' (if the bit values of the bits included in the Y LSBs are all 1 and at least some of the bit values of the bits included in the 6 MSBs are 0 or if the bit values of the bits included in the Y LSBs are all 1 and the bit values of the bits included in the 6 MSBs are all 0), the terminal can determine that the DCI format including the above information is an error case. If the terminal determines that the case is an error case, the terminal may discard (or ignore) the information indicated by the DCI format without applying it. Alternatively, if the terminal determines that the case is an error case, the terminal may discard (or not apply) the information regarding the cell (the cell corresponding to the FDRA field determined to be an error case) among the information indicated by the DCI format, and apply the information regarding the remaining cells (the remaining cells excluding the cell corresponding to the FDRA field determined to be an error case).
[0337] - In a second method, the terminal can determine whether a cell is scheduled based on only the 6 MSBs of the FDRA field. The terminal can identify whether a cell is scheduled through the 6 MSBs of the FDRA field. For example, if all bits of the 6 MSBs of the FDRA field are '1' (if the bit values of all bits included in the 6 MSBs are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 15 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the 6 MSBs are '1'. For example, in this case, the bit of the Y LSB may not provide information. That is, whether a cell is scheduled may be determined based on the 6 MSBs regardless of the value of the Y LSB. For example, the Y LSB may be discarded, ignored, or not included in the FDRA field (for example, Y may be 0).
[0338] - In a third method, the terminal can determine whether a cell is scheduled based only on the Y LSB of the FDRA field. The terminal can identify whether a cell is scheduled through the Y LSB of the FDRA field. For example, if all bits of the Y LSB of the FDRA field are '1' (if the bit values of all bits included in the Y LSB are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 15 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the total Y LSBs are '1'. For example, in this case, the bits of the 6 MSBs may not provide information. That is, whether a cell is scheduled can be determined based on the Y LSB regardless of the value of the 6 MSBs. For example, the 6 MSBs may be discarded, ignored, or not included in the FDRA field.
[0339] In one embodiment, the third method can be used when Y>0. If Y=0, the second method can be used. That is, based on the value of Y, the second method or the third method can be selectively used. That is, based on the value of Y (the bit size of the Y LSB of the FDRA field), the method to be used by the terminal can be determined.
[0340] Situation 2: When one cell has a 30 kHz subcarrier spacing
[0341] The terminal can check the subcarrier spacing and FDRA type information of each cell included in the set of candidate cells scheduled by MC-DCI. If one of the cells included in the set of candidate cells scheduled by MC-DCI is set to FDRA type-2, the terminal can check whether the subcarrier spacing of the cell is 15 kHz (μ=0) or 30 kHz (μ=1). This embodiment may be the case where the terminal has confirmed that the subcarrier spacing of the cell is 30 kHz (μ=1).
[0342] 1220 of FIG. 12 illustrates an example of a field indicating frequency domain resource allocation information when the subcarrier spacing of a cell is 30 kHz.
[0343] Referring to 1220 of FIG. 12, when the subcarrier spacing of a cell is 30 kHz, the length of a field indicating frequency domain allocation information of the cell within MC-DCI may be 5+Y bit(s). Here, the 5 bit(s) (1230) may indicate, as a bitmap, whether M=5 interlaces included in one RB-set are scheduled. That is, each of the 5 bit(s) may be used to indicate whether one interlace is scheduled. Here, an interlace corresponding to a bit having a value of '1' among the 5 bit(s) may be determined to be scheduled. An interlace corresponding to a bit having a value of '0' among the 5 bit(s) may be determined to be not scheduled. The Y bit(s) (1232) indicates a scheduled RB-set, Here, the Y bit(s) can indicate the index and length of the starting RB set among the RB sets included in the UL BWP. In the present disclosure may be the number of RB-sets set for the indicated activation UL BWP. In the present disclosure, for convenience, 5 bit(s) are called bitmap mode and Y bit(s) are called RIV mode (or RIV-like).
[0344] The above 5 bit(s) can indicate an interlace to be scheduled based on a bitmap. If each bit of the 5 bit(s) is '1', the terminal can determine that the interlace corresponding to '1' is scheduled. In other words, the interlace corresponding to a bit with a value of '1' among the 5 bit(s) can be determined to be scheduled. If all of the 5 bit(s) are '0', no interlace may be scheduled. Therefore, if the 5 bit(s) are all '0', the 5 MSBs can be used to determine that the cell is not scheduled.
[0345] Since the Y bit(s) in situation 2 are the same as in Example 1, their explanation is omitted. For this, refer to the explanation of the Y bit(s) in situation 1.
[0346] The FDRA field of a cell with a 30 kHz subcarrier spacing contains 5+Y bit(s), where 5 MSBs indicate interlaces scheduled within an RB set in a bitmap manner, and Y LSBs indicate RB sets scheduled in a RIV manner. Therefore, whether a cell is scheduled can be determined based on the values of the 5 MSBs and Y LSB.
[0347] In the present disclosure, a method for indicating that a cell with a 30 kHz subcarrier spacing is not scheduled may be one or a combination of at least one of the following. In the description of the present method, the FDRA field is a field corresponding to a cell with the 30 kHz subcarrier spacing. And the FDRA type may be FDRA type-2.
[0348] - In the first method, the terminal can determine whether a cell is scheduled based on all bits (5+Y bit(s)) of the FDRA field. For example, if all bits of the FDRA field are '0', the terminal can determine that the cell with the 30kHz subcarrier spacing is an unscheduled cell. Here, the FDRA field can include 5 MSBs and Y LSBs. Therefore, the terminal can determine that the cell with the 30kHz subcarrier spacing corresponding to the FDRA field is not scheduled if all of the 5+Y bit(s) are '0' (if all bit values of the bits included in the 5+Y bit(s) are 0). For example, if all Y LSBs are '0', RIV RB-setThere may be corresponding values depending on the equation. However, since all 5 MSBs are '0', the RB set indicated by Y LSB may not be used as information on whether or not to schedule. That is, since it is determined that there is no scheduled interlace since all 5 MSBs are '0', the RB set corresponding to Y LSB may be ignored.
[0349] - In a second method, the terminal can determine whether a cell is scheduled based on only the 5 MSBs of the FDRA field. The terminal can identify whether a cell is scheduled based on the 5 MSBs of the FDRA field. For example, if all bits of the 5 MSBs of the FDRA field are '0' (if the bit values of all bits included in the 5 MSBs are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 30 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the 5 MSBs are '0'. For example, in this case, the bit of the Y LSB may not provide information. That is, whether a cell is scheduled may be determined based on the 5 MSBs regardless of the value of the Y LSB. For example, the Y LSB may be discarded, ignored, or not included in the FDRA field (for example, Y may be 0).
[0350] - In a third method, the terminal can determine whether a cell is scheduled based only on the Y LSB of the FDRA field. The terminal can identify whether a cell is scheduled through the Y LSB of the FDRA field. For example, if all bits of the Y LSB of the FDRA field are '1' (if the bit values of all bits included in the Y LSB are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 30 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the total Y LSBs are '1'. For example, in this case, the bit of the 5 MSB may not provide information. That is, whether a cell is scheduled can be determined based on the Y LSB regardless of the value of the 5 MSB. For example, the 5 MSB may be discarded, ignored, or not included in the FDRA field.
[0351] In one embodiment, the third method can be used when Y>0. If Y=0, the second method can be used. That is, based on the value of Y, the second method or the third method can be selectively used. That is, based on the value of Y (the bit size of the Y LSB of the FDRA field), the method to be used by the terminal can be determined.
[0352] <Example 2: PUSCH transmission method of 8TX terminal>
[0353] As one embodiment of the present disclosure, a method for transmitting a PUSCH by a terminal supporting eight transmit antennas for transmitting an uplink channel and signal is described. This embodiment can be operated in combination with all other embodiments of the present disclosure.
[0354] Eight transmit antennas for uplink may refer to eight physical antennas, or may refer to a case where the physical antennas of an actual terminal are eight or more (or less than eight), but configured as eight logical uplink transmit ports through a method of virtualizing multiple antennas into a single antenna. However, the number of transmit antennas for uplink according to various embodiments of the present disclosure is not limited, and may include all cases where a terminal can be assumed to have eight transmit antennas through other antenna configuration methods, etc. In addition, a case where the number of transmit antennas is less than or equal to eight (for example, 6, 12, 16, or any other value) may also correspond to a case where the embodiments of the present disclosure are applied.
[0355] A terminal supporting four transmit antennas can perform PUSCH transmission using up to four layers through CP-OFDM waveform-based uplink data channel transmission, and the up to four layers can be included in one codeword (CW) (or up to four layers can be used to transmit one CW). That is, the modulation symbol of one CW can be mapped to four layers. In the following description, the inclusion of a specific layer in a CW can be understood to mean that the modulation symbol of the CW is mapped to a specific layer. Meanwhile, in subsequent NR releases (e.g. NR Release 18), terminals supporting eight transmit antennas can perform PUSCH transmission using up to eight layers through CP-OFDM waveform-based uplink data channel transmission to enhance performance, such as uplink maximum transmission throughput, of terminals such as customer premises equipment (CPE) or fixed wireless access (FWA) with improved form factors compared to terminals with relatively small size and performance, such as smartphones.
[0356] If a terminal is scheduled for a PUSCH consisting of five layers from a base station, the terminal may include the first to second layers in the first CW and the third to fifth layers in the second CW.
[0357] If a terminal is scheduled for a PUSCH consisting of 6 layers from a base station, the terminal may include the first to third layers in the first CW and the fourth to sixth layers in the second CW.
[0358] If a terminal is scheduled for a PUSCH consisting of 7 layers from a base station, the terminal may include the 1st to 3rd layers in the first CW and the 4th to 7th layers in the second CW.
[0359] If a terminal is scheduled for a PUSCH consisting of 8 layers from a base station, the terminal may include the 1st to 4th layers in the first CW and the 5th to 8th layers in the second CW.
[0360] When a terminal transmits a PUSCH to a base station, the PUSCH transmission method of the terminal can be distinguished into 'codebook'-based PUSCH transmission and 'non-Codebook'-based PUSCH transmission. When the terminal performs 'codebook'-based PUSCH transmission, the terminal can transmit SRS resource(s) that can be configured with multiple SRS ports (or can be configured with a single SRS port) to the base station, and the base station can receive the SRS resource(s) and perform estimation of the uplink channel. Thereafter, the base station can select one SRS resource from among the multiple SRS resources (if multiple SRS resources are received) based on uplink channel information acquired through the received SRS resources, and indicate the corresponding SRS resource through SRI in the DCI that schedules the PUSCH. At this time, when the terminal interprets the SRI indicated through DCI from the base station, it may consider that the SRS resource ID that can be indicated through the SRI corresponds to the SRS resource that was most recently transmitted before receiving the DCI among multiple transmission locations for the SRS resource having the SRS resource ID before receiving the DCI.
[0361] Additionally, the base station can select the number of layers and precoders of the uplink data channel based on the selected SRS resource, and determine the TPMI field in the same PUSCH scheduling DCI that includes the SRI field. If the terminal supports four transmit antennas, the row of precoders indicated by the TPMI can mean the PUSCH antenna ports (e.g., [abcd]). T In , a, b, c, and d may represent values for the first PUSCH antenna port, the second PUSCH antenna port, the third PUSCH antenna port, and the fourth PUSCH antenna port, respectively.), and may consist of up to four rows. If the terminal supports eight transmit antennas as described above, in one embodiment, if up to eight PUSCH antenna ports, instead of up to four, are used to support a codebook-based uplink data channel (which may also include an uplink control channel), a codebook that can support up to eight PUSCH antenna ports may be required, as well as a codebook that can support up to four PUSCH antenna ports.
[0362] In addition, the terminal can expect that the DCI for scheduling the PUSCH received from the base station includes two each of MCS (modulation and coding scheme), RV (redundancy version), and NDI (new data indicator) fields for PUSCH transmission including five or more layers. If the terminal receives scheduling information for PUSCH transmission including five or more layers from the base station through the DCI, that is, if the terminal receives a PUSCH transmission consisting of two codewords from the base station, the terminal can understand that the first MCS, first RV, and first NDI fields in the DCI are applied to the first CW, and the second MCS, second RV, and second NDI fields are applied to the second CW. At this time, the condition that there are two MCS, RV, and NDI fields in DCI formats 0_1 and 0_2 may be a case where the terminal receives a specific upper layer signaling from the base station (for example, the terminal may receive a signaling that is distinct from maxNrofCodeWordsScheduledByDCI, which is an upper layer signaling that means that the terminal can receive up to 8 layers of PDSCH, such as maxNrofCodeWordsScheduledByDCI-PUSCH, or the upper layer signaling that means that the terminal can receive up to 8 layers of PDSCH may be commonly applied, or the parameter value for the maximum rank value of PUSCH that the terminal can set as upper layer signaling from the base station may be 5 or more).
[0363] If a UE receives PUSCH scheduling for two CWs from a base station, the UE can assume that two different TBs (transport blocks) are transmitted for the corresponding PUSCHs. If the UE receives the 26th index for the first MCS field, the RV index for the first RV field as 1, and the first NDI field as 0 or 1, the UE can consider the first TB as not transmitted (disabled). If the UE receives the 26th index for the second MCS field, the RV index for the second RV field as 1, and the second NDI field as 0 or 1, the UE can consider the second TB as not transmitted (disabled). In this way, if the terminal performs transmission for only one TB due to the first or second TB not being transmitted from the terminal, the terminal may include the transmitted one TB in the first CW of the PUSCH.
[0364] A terminal may schedule PUSCH transmission including up to 8 layers for one or more cells through the MC-DCI (e.g., DCI format 0_X or 0_3), and may receive specific upper layer signaling from a base station for this purpose. The upper layer signaling may be one of the following:
[0365] - The upper layer signaling, such as the upper layer signaling related to the DCI format 0_1 or 0_2 (for example, the upper layer signaling is a separate upper layer signaling that is distinct from maxNrofCodeWordsScheduledByDCI, which is an upper layer signaling that means that up to 8 layers of PDSCH can be received, such as maxNrofCodeWordsScheduledByDCI-PUSCH, similar to the DCI format 0_1 or 0_2, or the upper layer signaling for PDSCH can be commonly applied to PUSCH, or the parameter value for the maximum rank value of PUSCH that the terminal can be configured with the upper layer signaling from the base station is 5 or more) may be configured in the cell in which the terminal receives MC-DCI, or may be configured in each of one or more cells in which the terminal can be scheduled through MC-DCI.
[0366] - Additional upper layer signaling for supporting up to 8 layers in MC-DCI, which is distinct from the upper layer signaling corresponding to the above DCI format 0_1 or 0_2, may be set in the cell where the terminal receives MC-DCI or in each of one or more cells where the terminal can be scheduled via MC-DCI.
[0367] If the UE can be scheduled for PUSCH transmission including up to 4 layers for one or more cells through the MC-DCI (for example, DCI format 0_X or 0_3), i.e., only PUSCH transmission consisting of 1 CW is possible, then as many MCS fields, RV fields, and NDI fields as the number of cells that can be scheduled through the MC-DCI can be included in the MC-DCI. For example, if the UE can be scheduled for up to 4 different cells, the UE can expect the MC-DCI to contain 4 MCS fields, 4 RV fields, and 4 NDI fields, and can expect that 1 MCS field, 1 RV field, and 1 NDI field can be used per cell for which the UE can receive scheduling information through the MC-DCI.
[0368] At this time, if there are multiple MCS fields in MC-DCI, the size of all MCS fields can be the same as 5 bits. At this time, if there are multiple RV fields in MC-DCI, the size of each RV field can be different for each cell that the terminal can schedule through MC-DCI, and the terminal can determine the size of each RV field for each cell through upper layer signaling from the base station, and the size of the RV field can be 0, 1, or 2 bits. At this time, if there are multiple NDI fields in MC-DCI, the size of all NDI fields can be the same as 1 bit. At this time, if there are multiple MCS fields, RV fields, and NDI fields in MC-DCI, the terminal can expect that the order of each field in MC-DCI is such that multiple MCS fields are arranged first, then multiple RV fields are arranged, and then multiple NDI fields are arranged.
[0369] If the UE can be scheduled for PUSCH transmissions including up to 8 layers for one or more cells via the MC-DCI (for example, DCI format 0_X or 0_3), the number of MCS fields, RV fields, and NDI fields may be included in the MC-DCI twice as many as the number of cells for which it can be scheduled via the MC-DCI. For example, if the UE can be scheduled for up to 4 different cells, the UE can expect the MC-DCI to contain 8 MCS fields, 8 RV fields, and 8 NDI fields, and the UE can expect that 2 MCS fields, 2 RV fields, and 2 NDI fields can be used per cell for which it can receive scheduling information via the MC-DCI.
[0370] At this time, if there are multiple MCS fields in MC-DCI, the size of all MCS fields can be the same, 5 bits. At this time, if there are multiple RV fields in MC-DCI, the size of each RV field can be different for each cell that the terminal can be scheduled for through MC-DCI, and the terminal can determine the size of each RV field for each cell through upper layer signaling from the base station, and the size of the RV field can be 0, 1, or 2 bits. In addition, when there are two RV fields as described above for one cell that can be scheduled through MC-DCI, that is, when a PUSCH consisting of two CWs is scheduled for a UE, the UE can expect that the two RV fields corresponding to one cell have the same size through the upper layer signaling for the size of the RV field of each cell, or can expect that the two RV fields corresponding to one cell have the same or different sizes because there are individual upper layer signalings for the respective sizes of the two RV fields for one cell. In this case, if there are multiple NDI fields in MC-DCI, the sizes of all NDI fields can be the same, 1 bit.
[0371] At this time, if there are multiple MCS fields, RV fields, and NDI fields in the MC-DCI, the terminal can expect that the order of each field in the MC-DCI is such that multiple MCS fields corresponding to the first TB scheduled for each cell are placed first, then multiple RV fields corresponding to the first TB scheduled for each cell are placed, then multiple NDI fields corresponding to the first TB scheduled for each cell are placed, then multiple MCS fields corresponding to the second TB scheduled for each cell are placed, then multiple RV fields corresponding to the second TB are placed, then multiple NDI fields corresponding to the second TB scheduled for each cell are placed.
[0372] The terminal can be configured by the base station through upper layer signaling as to whether there is one antenna port field (e.g., Antenna port(s) field) in the MC-DCI (e.g., DCI format 0_X or 0_3) or whether there are as many independent fields as the number of different cells for which the terminal can be scheduled through MC-DCI. If the terminal has been configured by the base station through upper layer signaling that there is one antenna port field in the MC-DCI, the terminal can equally and commonly apply information about a PUSCH DMRS port indicated through the corresponding one antenna port field to the PUSCH of one or more cells for which the terminal can be scheduled through MC-DCI. In this case, the size of one antenna port field may correspond to the largest size among the sizes of the antenna port fields required for PUSCH scheduling of each cell according to the upper layer signaling for each cell for which the terminal can be scheduled through MC-DCI.
[0373] If the terminal has been configured by the base station through upper layer signaling that there are as many antenna port fields as there are different cells that can be scheduled through MC-DCI in MC-DCI, the terminal can apply each of the multiple antenna port fields to different cells that can be scheduled through MC-DCI. In this case, the terminal can expect that the size of the antenna port field corresponding to each cell is determined according to the upper layer signaling for each cell that can be scheduled through MC-DCI.
[0374] The terminal can be configured by the base station through upper layer signaling as to whether there will be one TPMI field (e.g., precoding information and number of layers field) in the MC-DCI (e.g., DCI format 0_X or 0_3) or whether there will be as many independent fields as the number of different cells that the terminal can schedule through MC-DCI. If the terminal has been configured by the base station through upper layer signaling that there will be one TPMI field in the MC-DCI, the terminal can equally and commonly apply information about a PUSCH DMRS port indicated through the corresponding one TPMI field to the PUSCH of one or more cells that the terminal can schedule through MC-DCI. In this case, the size of one TPMI field may correspond to the largest size among the sizes of TPMI fields required for scheduling for each cell according to the upper layer signaling for each cell that the terminal can schedule through MC-DCI.
[0375] If the terminal has been configured by the base station through upper layer signaling that there are as many TPMI fields as the number of different cells that can be scheduled through MC-DCI in the MC-DCI, the terminal can apply each of the multiple TPMI fields to the PUSCH of each different cell that can be scheduled through MC-DCI. In this case, the terminal can expect that the size of the TPMI field corresponding to each cell is determined according to the upper layer signaling for each cell that can be scheduled through MC-DCI.
[0376] The terminal may expect that the PTRS-DMRS association field within the MC-DCI (e.g., DCI format 0_X or 0_3) will exist as independent fields as the number of different cells for which the terminal can be scheduled via MC-DCI.
[0377] The terminal may expect that there is one DMRS sequence initialization field in the MC-DCI (for example, DCI format 0_X or 0_3), and the terminal may apply information about the initialization of the DMRS sequence indicated through the corresponding one DMRS sequence initialization field equally and commonly to one or more cells that the terminal can schedule through the MC-DCI.
[0378] It is possible that at least one combination of the above-described MC-DCI configurations is applied to the MC-DCI.
[0379] <Third Embodiment: Method for Configuring a Waveform Change Indicator in MC-DCI>
[0380] As one embodiment of the present disclosure, a method for configuring a waveform change indicator that may exist within MC-DCI is described. This embodiment may operate in combination with other embodiments.
[0381] A terminal may include a PUSCH waveform change indicator field in DCI formats 0_1 and 0_2. This may require a terminal capability report from a corresponding terminal and upper layer signaling configuration from a base station. The PUSCH waveform change indicator may be 1 bit, and when the value of the field is 0, a PUSCH scheduled through the corresponding DCI may be transmitted based on a DFTS-OFDM waveform, and when the value of the field is 1, a PUSCH scheduled through the corresponding DCI may be transmitted based on a CP-OFDM waveform. The definition of each bit value of the field is, conversely, that when the value of the field is 1, the terminal may perform PUSCH transmission based on a DFTS-OFDM waveform, and when the value is 0, the terminal may perform PUSCH transmission based on a CP-OFDM waveform.
[0382] If the terminal does not receive upper layer signaling from the base station indicating 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.
[0383] - 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.
[0384] - 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.
[0385] The terminal can decide whether to use CP-OFDM or DFTS-OFDM when enabled for PUSCH transmission based on Configured grant Type 2 via DCI format 0_1 or 0_2, or when enabled 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.
[0386] - If the terminal has the transformPrecoder in the configuredGrantConfig set to enabled, 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 when it is configured for PUSCH transmission based on configured grant Type 1 through upper layer signaling.
[0387] - If the terminal receives the above transformPrecoder as disabled, the terminal can use the CP-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 when it is configured for PUSCH transmission based on Configured grant Type 1 through upper layer signaling.
[0388] If a terminal is enabled for PUSCH transmission based on Configured grant type 2 through DCI format 0_1 or 0_2 or is dynamically scheduled for PUSCH transmission, and if transformPrecoder in configuredGrantConfig or transformPrecder in PUSCH-Config is set to enabled or disabled as described above, the terminal can expect that the antenna port field, TPMI field, PTRS-DMRS association field, and DMRS sequence initialization field in DCI format 0_1 or 0_2 have different bit sizes as follows.
[0389] - For example, if the terminal uses a DFTS-OFDM waveform when transmitting PUSCH by the upper layer signaling setting, the bit length of the antenna port field can be from a minimum of 2 bits to a maximum of 4 bits, and the bit length of the TPMI field can be from a minimum of 1 bit to a maximum of 5 bits, depending on the upper layer signaling setting in the BWP.
[0390] - As another example, if the terminal uses a CP-OFDM waveform when transmitting PUSCH by the upper layer signaling setting, the bit length of the antenna port field can be from a minimum of 3 bits to a maximum of 5 bits, and the bit length of the TPMI field can be from a minimum of 1 bit to a maximum of 6 bits, depending on the upper layer signaling setting in the BWP.
[0391] If the terminal has received upper layer signaling from the base station that the PUSCH waveform change indicator field is included in DCI formats 0_1 and 0_2, the terminal may use, for each field, a bit length corresponding to the maximum value among the bit sizes of each field determined according to the waveform of a specific PUSCH as described above.
[0392] - For example, for the antenna port field, if the terminal has a length of 3 bits when using DFTS-OFDM and 5 bits when using CP-OFDM, as described above, if the PUSCH waveform change indicator field is included in DCI formats 0_1 and 0_2, the terminal can expect the antenna port field in the corresponding DCI formats 0_1 and 0_2 to have a length of 5 bits, which is the maximum value between 3 bits and 5 bits.
[0393] - As another example, for the TPMI field, if the terminal has a length of 2 bits when using DFTS-OFDM and 5 bits when using CP-OFDM, as described above, if the PUSCH waveform change indicator field is included in DCI formats 0_1 and 0_2, the terminal can expect the TPMI field in the corresponding DCI formats 0_1 and 0_2 to have a length of 5 bits, which is the maximum value between 2 bits and 5 bits.
[0394] Similarly to the above, the terminal can determine the bit length of each field by using the maximum value among the bit lengths for each waveform for the antenna port field, TPMI field, PTRS-DMRS association field, and DMRS sequence initialization field.
[0395] The terminal may include a PUSCH waveform change indicator field in the MC-DCI for uplink scheduling, referred to as the DCI format 0_X or DCI format 0_3. This may require a terminal capability report from the corresponding terminal and upper layer signaling configuration from the base station. The terminal may assume the format of the PUSCH waveform change indicator field in the MC-DCI through various methods as follows.
[0396] [Method 1]
[0397] The terminal can expect that the MC-DCI includes one PUSCH waveform change indicator field with a length of 1 bit, and can determine the waveform of all PUSCHs in BWPs in all cells scheduled through the MC-DCI equally based on the value of one bit, 0 or 1. For example, as described above, if the value of the PUSCH waveform change indicator in the MC-DCI is 0, all PUSCHs in BWPs in all cells scheduled through the MC-DCI can be transmitted based on DFTS-OFDM waveforms, and if the value of the field is 1, all PUSCHs in all cells scheduled through the MC-DCI can be transmitted based on CP-OFDM waveforms. The definition of each bit value of the field is the opposite of the above, in which the terminal can perform PUSCH transmission based on DFTS-OFDM when the value is 1, and based on CP-OFDM when the value is 0.
[0398] Additionally, the terminal may consider that the waveform of the PUSCH within a specific BWP within one or more specific cells scheduled through the MC-DCI is determined to be identical when the PUSCH waveform change indicator field is defined as 1 bit within the MC-DCI, wherein the specific cell may be a cell for which the terminal has received upper layer signaling that means that the PUSCH waveform change indicator field can be applied to the corresponding cell, and the specific BWP may be a BWP for which the terminal has received upper layer signaling that means that the PUSCH waveform change indicator field can be applied to the corresponding BWP.
[0399] At this time, the terminal can determine that a PUSCH waveform change indicator field exists in the MC-DCI and / or that the field is 1 bit long based on a parameter that can be set as upper layer signaling in the cell receiving the MC-DCI, or based on a parameter that can be set as upper layer signaling in the BWP in the cell receiving the MC-DCI.
[0400] [Method 2]
[0401] A terminal may expect that MC-DCI includes one PUSCH waveform change indicator field with a length of at least 1 bit, and each code point of the PUSCH waveform change indicator field may include waveform change information for each cell that can be scheduled via MC-DCI. Each code point may exist in the form of a list for waveform change indications, and one or more lists may be configured by the terminal from the base station through upper layer signaling. For example, waveform list 1, which is a list for waveform change indications corresponding to a specific code point, may have a form such as {CP-OFDM, DFTS-OFDM, CP-OFDM, DFTS-OFDM}, and the meaning of this list may be to perform PUSCH transmission by applying CP-OFDM for the first cell and the third cell that can be scheduled via MC-DCI, and DFTS-OFDM for the second cell and the fourth cell.
[0402] Alternatively, each code point of the PUSCH waveform change indicator field may include waveform change information for a specific cell group that can be scheduled via MC-DCI. In this case, the specific cell group may be configured by the terminal through upper layer signaling from the base station, and the specific cell group may be a concept that is distinct from or the same as the cell set. If the specific cell group is a concept that is distinct from the cell set, the specific cell group may include some cells among all cells in the cell set. For example, if there are four cells in the cell set, two of them may form one cell group, and the remaining two cells may form another cell group. In this case, each code point of the MC-DCI may exist in the form of a list for waveform change indication, and one or more lists may be configured by the terminal through upper layer signaling from the base station, and each list may include waveform change information as many as the number of cell groups. For example, if there are two cell groups within the cell set as described above, waveform list 1, which is a list of waveform change instructions corresponding to specific code points, may have a form such as {CP-OFDM, DFTS-OFDM}, and the meaning of this list may be to perform PUSCH transmission by applying CP-OFDM to the first cell group that can be scheduled with MC-DCI, and DFTS-OFDM to the second cell group.
[0403] The bit length of the PUSCH waveform change indicator field in MC-DCI can be determined according to the number of lists for the waveform change indication. If the number of lists is N, the bit length can be determined as ceil(log2(N)), for example. In this case, ceil(.) can mean a rounding function, and log2(.) can mean a logarithmic function with a base of 2.
[0404] Additionally, values such as 'none', 'void', and 'empty' may be set within the above list, which may mean that no dynamic waveform change instruction will be performed for the corresponding cell, and the waveform will be determined based on the upper layer signaling settings within the corresponding cell and the corresponding BWP.
[0405] At this time, the terminal can determine that a PUSCH waveform change indicator field exists in the MC-DCI and / or that the field is 1 bit or more long based on a parameter that can be set as upper layer signaling in the cell receiving the MC-DCI, or based on a parameter that can be set as upper layer signaling in the BWP in the cell receiving the MC-DCI.
[0406] [Method 3]
[0407] The terminal can expect that the MC-DCI includes one PUSCH waveform change indicator field with a length of 1 bit, and can determine the waveform of the PUSCH in the BWP in a specific cell scheduled through the MC-DCI based on the value of 0 or 1 of the one bit. The specific cell may be the first cell or the last cell among all cells scheduled through the MC-DCI, or a cell with a specific index according to upper layer signaling set by the terminal from the base station. In this case, there may be more than one cell with a specific index according to upper layer signaling. In this case, if the value of the PUSCH waveform change indicator in the MC-DCI is 0, the PUSCH in the BWP in the specific cell scheduled through the MC-DCI can be transmitted based on the DFTS-OFDM waveform, and if the value of the field is 1, the PUSCH in the BWP in the specific cell scheduled through the MC-DCI can be transmitted based on the CP-OFDM waveform. The definition of each bit value of the field may be the opposite of the above, in which case PUSCH transmission may be performed based on DFTS-OFDM waveform when the value is 1, and based on CP-OFDM waveform when the value is 0.
[0408] [Method 4]
[0409] The terminal can expect that the MC-DCI includes one PUSCH waveform change indicator field with a length of at least 1 bit, and each code point of the PUSCH waveform change indicator field can indicate waveform change information for each cell that can be scheduled through the MC-DCI. The PUSCH waveform change indicator field can have a bit length as many as the maximum number of cells that can be scheduled through the MC-DCI. If the terminal reports two or more sets of cells that can be scheduled through the MC-DCI within a cell that can receive the MC-DCI, or two or more sets of cells that can be scheduled through the MC-DCI are set through upper layer signaling, the terminal can determine the length of the PUSCH waveform change indicator field as the number of cells that the cell set that includes the largest number of cells among the multiple cell sets has. If the first cell set includes three cells and the second cell set includes four cells, a 4-bit PUSCH waveform change indicator can be included in the MC-DCI. Meanwhile, since the maximum number of cells that can be included in a specific cell set is four, the PUSCH waveform change indicator field in the MC-DCI can have a length of up to 4 bits through this method.
[0410] The PUSCH waveform change indicator of the bit length included in the MC-DCI is applied to each cell in the form of a bitmap, and each bit applied to each cell can determine the waveform of the PUSCH scheduled in the corresponding cell. At this time, as described above, if the value of the bit (or bit position) corresponding to a specific cell in the PUSCH waveform change indicator in the MC-DCI is 0, the PUSCH in the BWP in the specific cell scheduled through the MC-DCI can be transmitted based on the DFTS-OFDM waveform, and if the value of the bit (or bit position) corresponding to the specific cell is 1, the PUSCH in the BWP in the specific cell scheduled through the MC-DCI can be transmitted based on the CP-OFDM waveform. The definition of each bit value of the corresponding field may be the opposite of the above, such that if the value is 1, PUSCH transmission may be performed based on the DFTS-OFDM waveform, and if the value is 0, PUSCH transmission may be performed based on the CP-OFDM waveform.
[0411] [Method 5]
[0412] The terminal may expect that the MC-DCI includes a plurality of PUSCH waveform change indicator fields, each of which is 1 bit long, and each PUSCH waveform change indicator field may include waveform change information for each cell that can be scheduled through the MC-DCI. The number of PUSCH waveform change indicator fields may be equal to the maximum number of cells that can be scheduled through the corresponding MC-DCI. If the terminal reports two or more sets of cells that can be scheduled through the MC-DCI within a cell that can receive the MC-DCI, or if two or more sets of cells that can be scheduled through the MC-DCI are configured through upper layer signaling, the terminal may determine the number of PUSCH waveform change indicator fields as the number of cells included in the cell set that includes the largest number of cells among the plurality of cell sets. If the first cell set includes three cells and the second cell set includes four cells, the terminal can include four PUSCH waveform change indicator fields in the MC-DCI, and the length of one field can be 1 bit as described above. Meanwhile, since the maximum number of cells that can be included in a specific cell set is four, the PUSCH waveform change indicator fields in the MC-DCI can be included at most four through the method. At this time, as described above, when the value of the PUSCH waveform change indicator is 0, the PUSCH in the BWP in the specific cell corresponding to the field scheduled through the MC-DCI can be transmitted based on the DFTS-OFDM waveform, and when the value of the field is 1, the PUSCH in the BWP in the specific cell corresponding to the field scheduled through the MC-DCI can be transmitted based on the CP-OFDM waveform. The definition of each bit value of the field may be the opposite of the above, in which case PUSCH transmission may be performed based on DFTS-OFDM waveform when the value is 1, and based on CP-OFDM waveform when the value is 0.
[0413] [Method 6]
[0414] The terminal may be configured by a higher layer signaling from the base station for at least one combination of [Method 1] to [Method 5], activated by MAC-CE, instructed by L1 signaling, or notified by a combination of at least one of the higher layer signaling, MAC-CE, and L1 signaling. Alternatively, it may be fixedly defined in the standard to use at least one combination of [Method 1] to [Method 5]. For example, the terminal may be notified by the base station of the form of the PUSCH waveform change indicator field in the MC-DCI according to one of the [Method 1] and [Method 5] through higher layer signaling. [Method 1] is the simplest method of indicating the same information to all cells with the least overhead, and conversely, [Method 5] is a method of indicating individual information for each cell with the greatest overhead, so that the base station can indicate the form of the PUSCH waveform change indicator field to the terminal depending on the situation through upper layer signaling for one of the two methods. This uses a method similar to the antenna port field and the TPMI field, which can be affected by the PUSCH waveform. The antenna port field and the TPMI field can also be defined as a single field through upper layer signaling from the base station so that common information is applied to all cells that can be scheduled with MC-DCI (similar to [Method 1] above), or can be defined as multiple individual fields so that individual information is applied to each cell that can be scheduled with MC-DCI (similar to [Method 5] above).
[0415] A terminal may report to a base station a terminal capability that means that it can support at least one combination of [Method 1] to [Method 6]. The terminal capability may be defined separately for [Method 1] to [Method 6], or may be defined as a single terminal capability that means that it can support at least one combination of [Method 1] to [Method 6]. In addition, if the terminal cannot support at least one combination of [Method 1] to [Method 6], it may support at least one combination of [Method 1] to [Method 6] as an alternative method. For example, if the terminal reports a terminal capability that it cannot support [Method 5] or does not report a terminal capability that it supports [Method 5], the terminal may achieve the same effect as if it had conveyed to the base station that it can support [Method 1].
[0416] In the above [Method 1] to [Method 6], the waveform of the PUSCH that can be determined through the PUSCH waveform change indicator has been described as two examples, CP-OFDM or DFTS-OFDM, but is not limited thereto. That is, one of three or more waveforms can be selected and applied to PUSCH transmission within a cell that can be scheduled through MC-DCI. When considering three or more waveforms, in addition to CP-OFDM or DFTS-OFDM, at least one or more of waveforms such as FBMC (filter-bank multi-carrier), GFDM (generalized frequency domain multiplexing), or F-OFDM (filtered-OFDM) can be considered.
[0417] <Example 4: MC-DCI Overhead Reduction Method>
[0418] In one embodiment of the present disclosure, a method for reducing overhead of MC-DCI is described, in which a terminal can receive scheduling for a PUSCH transmission configured with 2CW in a specific cell through MC-DCI, and at the same time, receive a waveform change indicator in the specific cell through MC-DCI to receive a PUSCH based on one of a waveform of DFTS-OFDM or CP-OFDM. This embodiment can operate in combination with other embodiments.
[0419] If a terminal is equipped with 8TX and receives scheduling information for PUSCH transmission consisting of up to 8 layers from a base station through MC-DCI, and the number of cells that the terminal can be scheduled for through MC-DCI is 4, the terminal can expect a total of 8 MCS fields, 8 RV fields, and 8 NDI fields to be included in the MC-DCI as described above. At the same time, if the terminal receives the waveform change indicator described above through MC-DCI, the terminal can determine the waveform to be used for PUSCH transmission in each cell that can be scheduled through MC-DCI. The waveform change indicator can be used to enable the base station to schedule DFTS-OFDM-based PUSCH transmission when the terminal operates in an area where the coverage of a specific cell is poor, and in this case, the DFTS-OFDM-based PUSCH can be configured with up to 1 layer. Conversely, if a terminal wants to obtain high throughput in an area with good coverage of a specific cell, it can use a waveform change indicator to enable the base station to schedule CP-OFDM-based PUSCH transmission, where the CP-OFDM-based PUSCH can be configured with up to 8 layers.
[0420] Therefore, if a terminal can receive a waveform change indicator via MC-DCI and can receive scheduling for up to 8 layers in case of CP-OFDM, the terminal may have to prepare for each cell from DFTS-OFDM-based PUSCH transmission, which consists of 1 layer and requires relatively little DCI overhead, to CP-OFDM-based PUSCH transmission, which can consist of up to 8 layers and therefore may require relatively large DCI overhead. Therefore, if a terminal operates in an area with poor coverage within a specific cell and is scheduled for DFTS-OFDM-based PUSCH via MC-DCI, the terminal may expect a combination of fields within MC-DCI that can prepare the possibility of scheduling CP-OFDM-based PUSCH for up to 8 layers, depending on the parameters set by the upper layer signaling from the base station, which may entail unnecessary DCI overhead.
[0421] For example, let's examine the MCS, RV, and NDI fields in MC-DCI. If a UE is scheduled for DFTS-OFDM-based PUSCH transmission in all four cells that can be scheduled through MC-DCI, the fields actually used by the UE for DFTS-OFDM-based PUSCH transmission among the fields in MC-DCI are four MCS fields, four RV fields, and four NDI fields, requiring a maximum of 32 bits. On the other hand, for CP-OFDM-based PUSCH transmission consisting of up to eight layers, the fields that the UE needs to decode when receiving DCI can be twice as many, eight MCS fields, a total of eight RV fields, and a total of eight NDI fields, for a total of 64 bits.
[0422] In addition, if the UE is scheduled for a DFTS-OFDM based PUSCH, the UE may be 2 to 4 bits per cell or across all cells for the antenna port field, 1 to 5 bits per cell or across all cells for the TPMI field, and 0 bits for the PTRS-DMRS association field and the DMRS sequence initialization field, depending on the higher layer signaling conditions, whereas if the UE is scheduled for a CP-OFDM based PUSCH, the UE may be 3 to 5 bits per cell or across all cells for the antenna port field, 1 to 6 bits per cell or across all cells for the TPMI field, 2 bits per cell or across all cells for the PTRS-DMRS association field, and 1 bit for the DMRS sequence initialization field, depending on the higher layer signaling conditions. Therefore, considering the antenna port field, TPMI field, PTRS-DMRS association field, and DMRS sequence initialization field within MC-DCI, a minimum of 3 bits and a maximum of 46 bits may be required for DFTS-OFDM based PUSCH, and a minimum of 7 bits and a maximum of 53 bits may be required for CP-OFDM based PUSCH, so the maximum difference between the two waveforms may be 50 bits.
[0423] Therefore, when considering all fields within MC-DCI that are affected by the waveform of the PUSCH that can be scheduled through MC-DCI (e.g., MCS field, RV field, NDI field, antenna port field, TPMI field, PTRS-DMRS association field, DMRS sequence initialization field, etc.), the UE can receive dynamic switching and corresponding scheduling for DFTS-OFDM-based PUSCH and CP-OFDM-based PUSCH composed of up to 8 layers by considering an additional maximum of 32 + 50 = 82 bits compared to receiving scheduling considering only DFTS-OFDM-based PUSCH. Therefore, the UE must be able to prepare for the possibility of scheduling PUSCH transmissions of two waveforms before receiving MC-DCI. Such a very large difference in the number of bits can be very inefficient, and can affect the coding rate of the PDCCH and the DCI reception performance at the UE. Therefore, if a terminal can receive a waveform change indicator through MC-DCI and can receive CP-OFDM-based PUSCH scheduling consisting of up to 8 layers, the terminal and the base station can consider a combination of at least one of the following methods to reduce overhead of MC-DCI.
[0424] [Method 1]
[0425] In order to reduce the overhead of MC-DCI, the length of each FDRA field corresponding to each cell that can be scheduled through MC-DCI is expressed as A1 + A2 bits, and the bit length of the FDRA field can be adjusted to be smaller than FDRA type 0, 1, or 2. The value of A1 is up to 6 bits, and it can be assumed that some or all of the total 53 RB lengths expressed in Table 28 below can be indicated through an index indicated by 6 bits (or a smaller number of bits), for example. In this case, the RB lengths (or numbers) expressed in columns 5 and 10 of Table 28 below are 2 less than 275. A 3 B 5 C (At this time, A expressed in columns 2 and 7, B expressed in columns 3 and 8, and C expressed in columns 4 and 9 can be non-negative integers.) The reason why only 53 RB values can be indicated to the terminal through the FDRA field is that the frequency resource allocation of DFTS-OFDM based PUSCH is 2. A 3 B 5 C This is because it is only possible for consecutive RB numbers corresponding to multiples of , and all of the following RB numbers can be applied to CP-OFDM based PUSCH.
[0426] IndexABC# RBsIndexABC# RBs0000127320721100228012752010329401803200430040814001531121905110632510966300833202100702093 4230108810110353111209210123600312510011153770012811400163803113512120183942014413201204011215 01431024415011601500225421401621603027432211801711130446101921850032453022001922036463302162030140470222252102145484112402241048490502432310250501032502413054518002562521160521312702660064
[0427] The above A2 bit may be determined to indicate the starting point of the frequency resource allocation information of the PUSCH composed of consecutive RBs indicated by the A1 bit. For example, A2 may be defined as 0 (i.e., the A2 bit is not included in the FDRA field and only the A1 bit is included), or the value of the A2 bit may be set to a predetermined value (e.g., 0). In this case, the starting position of the frequency resource of the PUSCH may always start from the starting RB of the bandwidth portion, or the position of the starting RB may be determined so that the PUSCH is located at the center of the bandwidth portion, or may be set by higher layer signaling. In this case, if the terminal receives the starting RB position of the PUSCH frequency resource by higher layer signaling, the corresponding configuration information may be expressed in units of 1, 2, or 4 RBs, or may be expressed as a value greater than or equal to that.
[0428] As another example, A2 can be used to indicate the start RB position of PUSCH frequency resource allocation expressed through N RB units. For example, if the maximum RB size of the bandwidth portion that the UE can be configured is 275 RBs, A2 = ceil (log2(275 / N)), ceil(.) can be a rounding function, and log2(.) can be a logarithmic function with base 2. If N is 8, A1 can be 6 bits. The UE can receive the N value from the base station through upper layer signaling, or the N value can be fixedly defined in the specification. In summary, the A1 + A2 bits determined using the above method can be smaller than the maximum 18 bits when the RBG size is 4 for FDRA type 0 and the maximum 16 bits for FDRA type 1, so the overhead of MC-DCI can be reduced.
[0429] [Method 2]
[0430] In order to reduce the overhead of MC-DCI, the terminal and the base station can place restrictions on the FDRA field corresponding to each cell that can be scheduled through MC-DCI. If the terminal is equipped with 8TX as described above through MC-DCI and can schedule CP-OFDM-based PUSCH consisting of up to 8 layers, and / or dynamic switching is possible for either DFTS-OFDM or CP-OFDM-based PUSCH through a waveform change indicator in MC-DCI, the FDRA indication type of the FDRA field corresponding to each cell that can be scheduled through MC-DCI can be restricted to FDRA type 0 in bitmap format, and at the same time, the size of the RBG represented by each bit of the FDRA field defined based on FDRA type 0 can be additionally defined.
[0431] For example, the terminal can be notified of one of three types of configuration information through upper layer signaling from the base station as shown in Table 29 below, and can determine the RBG size of each bit indicated through FDRA type 0 according to the size of the bandwidth portion for each configuration information. In Table 29 below, for example, if the terminal is configured with Configuration 3 and the size of the activated bandwidth portion of the terminal is 50 RB, the terminal can consider the RBG size to be used in FDRA type 0 as 16 RB. In this way, if the terminal is configured with Configuration 3 from the base station through upper layer signaling, the size of one RBG is up to four times that of when Configuration 1 is configured, or up to twice that of when Configuration 2 is configured, so the bit length of the FDRA field can be reduced by up to one-fourth or half, and thus the overhead of MC-DCI can be reduced.
[0432] Bandwidth Part RB Size Configuration 1 Configuration 2 Configuration 31 - 3624837 - 72481673 - 14481632145 - 275161632
[0433] [Method 3]
[0434] In order to reduce the overhead of MC-DCI, the terminal and the base station can place another restriction on the FDRA field corresponding to each cell that can be scheduled through MC-DCI. If the terminal is equipped with 8TX as described above and can schedule CP-OFDM-based PUSCH consisting of up to 8 layers through MC-DCI, and / or, at the same time, dynamic switching is possible for either DFTS-OFDM or CP-OFDM-based PUSCH through a waveform change indicator in MC-DCI, the FDRA indication type of the FDRA field corresponding to each cell that can be scheduled through MC-DCI can be restricted to FDRA type 1. In addition, when considering the SLIV (start and length indicator value) defined based on the conventional FDRA type 1, both the start position and the length are considered as 1 RB unit, but in the case of such a restrictive FDRA type 1, both the start position and the length can be considered as N RB units. At this time, the terminal can be configured by upper layer signaling from the base station for N RB units, and N can be, for example, 1, 2, 4, 8, or other values. Alternatively, the value of N may be predetermined, or a predetermined value may be used according to the size of the bandwidth portion. In this way, if the base station and the terminal use SLIV for the start position and length defined using N units of RB, the RB size in the bandwidth portion may be reduced as if using SLIV for the start position and length defined using 1 unit of RB. In other words, considering the same bandwidth portion size, the code points that can be expressed by SLIV are reduced, so the bit length of the FDRA field is reduced, which may reduce the overhead of MC-DCI.
[0435] [Method 4]
[0436] The UE and the BS may consider using different FDRA-related configurations for CP-OFDM-based PUSCH transmission and DFTS-OFDM-based PUSCH. If the UE can schedule CP-OFDM-based PUSCH consisting of up to 8 layers by integrating 8TX as described above through MC-DCI, and / or dynamically switch between DFTS-OFDM-based or CP-OFDM-based PUSCH through a waveform change indicator in MC-DCI, the UE may expect to receive configuration information for FDRA types from the BS for CP-OFDM and DFTS-OFDM, respectively.
[0437] The terminal can be configured with different FDRA types for each waveform. For example, the terminal can be configured with FDRA type 1 from the base station through upper layer signaling for CP-OFDM-based PUSCH for each cell that can be scheduled through MC-DCI, and can be configured with higher layer signaling for the unit of the number of RBs to be considered when using SLIV (for example, based on the above [Method 3]) to transmit a PUSCH based on FDRA type 1. The terminal can be configured with FDRA type 0 from the base station through upper layer signaling for DFTS-OFDM-based PUSCH scheduled through MC-DCI, can be configured with higher layer signaling for the size of RBG from the base station, and can transmit a PUSCH based on FDRA type 0. In this case, the length of the FDRA field of a specific cell that can be scheduled via MC-DCI can be defined according to the larger value between the bit length according to the FDRA-related configuration information for CP-OFDM-based PUSCH and the bit length according to the FDRA-related configuration information for DFTS-OFDM-based PUSCH.
[0438] Alternatively, the terminal may be configured with a common FDRA type for both waveforms, and additional upper layer signaling required for the FDRA type may be configured for each of the two waveforms. For example, the terminal may be configured with the same FDRA type 0 for both CP-OFDM-based and DFTS-OFDM-based PUSCHs for each cell that can be scheduled via MC-DCI, and for example, the terminal may be configured with Configuration 3 of Table 29 as upper layer signaling from the base station for CP-OFDM-based PUSCHs, and may be configured with Configuration 2 of Table 29 as upper layer signaling from the base station for DFTS-OFDM-based PUSCHs. In this case, in the case of DFTS-OFDM-based PUSCH, even if it is FDRA type 0, only scheduling for consecutive RBs may be possible. In this case, the length of the FDRA field of a specific cell that can be scheduled via MC-DCI can be defined according to the larger value between the bit length according to the FDRA-related configuration information for CP-OFDM-based PUSCH and the bit length according to the FDRA-related configuration information for DFTS-OFDM-based PUSCH.
[0439] The above method may have the advantage of reducing the overhead of MC-DCI and securing scheduling flexibility that can be supported through each waveform when transmitting PUSCH based on two different waveforms of DFTS-OFDM and CP-OFDM. For example, DFTS-OFDM based PUSCH is a continuous RB with 2 A 3 B 5 COnly scheduling is possible for RBs corresponding to values that are multiples of (where A, B, and C may be integers not less than 0), but CP-OFDM-based PUSCH may allow scheduling for both contiguous and discontinuous RBs and may not be restricted to the number of RBs corresponding to multiples of a specific value like DFTS-OFDM-based PUSCH.
[0440] [Method 5]
[0441] To reduce the overhead of MC-DCI, the terminal and the base station can restrict the bit length of the FDRA field. If the terminal can be scheduled for CP-OFDM-based PUSCH consisting of up to 8 layers by mounting 8TX as described above through MC-DCI, and / or dynamic switching is possible for either DFTS-OFDM or CP-OFDM-based PUSCH through a waveform change indicator in MC-DCI, the terminal can receive upper layer signaling from the base station regarding the bit length of the FDRA field to be reduced for each cell that can be scheduled through MC-DCI.
[0442] The corresponding upper layer signaling configuration information may be individually configured for each cell that the terminal can schedule via MC-DCI, or may be configured commonly for all cells. For example, if the terminal has FDRA type 0 configured for both cells that the terminal can schedule via MC-DCI, the terminal may receive upper layer signaling from the base station that the bit lengths of the FDRA fields for the first and second cells are reduced by 3 and 5 bits, respectively. In this case, the terminal may interpret the field as the field length before the length was reduced, but may regard all bits corresponding to the reduced length as 0.
[0443] Alternatively, the UE may redefine the meaning of each code point in the FDRA field to correspond to the reduced field length. For example, if the FDRA field is set to FDRA type 0 for each cell that the UE can schedule via MC-DCI, the UE may determine the positions of RBGs corresponding to the reduced number of bits, and PUSCH frequency resources may not be allocated to the RBGs in those positions. In this case, the RBGs to which frequency resources are not allocated may be located from the start RB or the end RB of the uplink bandwidth portion, or may be located separately between the start RB and the end RB of the uplink bandwidth portion so that the PUSCH can be allocated to the center of the uplink bandwidth portion when PUSCH frequency resources are allocated based on the reduced-length FDRA field. For example, if the number of reduced bits is an odd number, such as three, the RBG corresponding to two bits (or one bit) can be positioned from the start RB of the uplink bandwidth portion, and the RBG corresponding to one bit (or two bits) can be positioned from the end RB of the uplink bandwidth portion. That is, in this case, PUSCH frequency resource allocation cannot be performed through the corresponding FDRA field for two consecutive RBGs including the start RB of the uplink bandwidth portion and one RBG including the end RB of the uplink bandwidth portion.
[0444] Reducing the bit length of the FDRA field in this way may reduce the flexibility of PUSCH frequency resource allocation, but it can reduce the DCI payload overhead of MC-DCI. UEs and base stations can also apply this approach to other fields within MC-DCI, not just FDRA. For example, UEs can similarly restrict the bit length of the TPMI field and the antenna port field.
[0445] [Method 6]
[0446] To reduce MC-DCI overhead, terminals and base stations can impose constraints on the formats of the TPMI and antenna port fields within MC-DCI. As described above, terminals can receive one of the following two field formats from the base station via upper-layer signaling.
[0447] - The terminal may expect that there will be one TPMI field and one antenna port field in the MC-DCI, and may expect that the one TPMI field and one antenna port field are commonly applied to the PUSCH of all cells that can be scheduled through the MC-DCI. At this time, the terminal may determine the length of the largest TPMI field among the lengths of the TPMI fields and the lengths of the antenna ports required for each cell determined according to the upper layer signaling for each cell that can be scheduled through the MC-DCI as the size of one TPMI field existing in the MC-DCI, and may determine the length of the largest antenna port field as the size of one antenna port field existing in the MC-DCI.
[0448] - The terminal can expect that the TPMI field and antenna port field corresponding to each cell that can be scheduled through MC-DCI exist independently.
[0449] If a terminal is capable of scheduling a CP-OFDM-based PUSCH consisting of up to 8 layers by mounting 8TX as described above through MC-DCI, and / or dynamic switching is possible for either DFTS-OFDM or CP-OFDM-based PUSCH through a waveform change indicator in MC-DCI, the terminal may expect that the TPMI field and antenna port field that may exist in MC-DCI correspond to the first field type among the two field types described above. Or / and the terminal may receive the same upper layer signaling configuration for each cell that can be scheduled through MC-DCI, so that the lengths of the TPMI field and antenna port field required for each cell may be constrained to be the same for all cells.
[0450] With such constraints, the terminal can expect that there will be only one TPMI field and one antenna port field in MC-DCI, and can apply that one field in common to all cells that can be scheduled through MC-DCI, thereby reducing the overhead of MC-DCI.
[0451] [Method 7]
[0452] To reduce the overhead of MC-DCI, the UE and the base station can introduce restrictions on the PTRS-DMRS association field in the MC-DCI. If the UE can schedule a CP-OFDM-based PUSCH configured with up to 8 layers by mounting 8TX as described above through MC-DCI, and / or dynamically switch between DFTS-OFDM or CP-OFDM-based PUSCH through a waveform change indicator in the MC-DCI, the UE can expect that the PTRS-DMRS association field does not exist in the MC-DCI. In other words, a UE that can dynamically switch between a CP-OFDM-based PUSCH configured with up to 8 layers and a DFTS-OFDM-based PUSCH through MC-DCI as described above can be configured by the base station to disable uplink PTRS transmission through upper layer signaling. Through this, the terminal can achieve an overhead reduction of at least 8 bits (considering a total of 4 cells with at least 2 bits per cell) due to the PTRS-DMRS association field that may exist for each cell that can be scheduled via MC-DCI.
[0453] [Method 8]
[0454] The terminal may be configured by a higher layer signaling from a base station to perform at least one combination of [Method 1] to [Method 7], activated by MAC-CE, instructed by L1 signaling, or notified by a combination of at least one of higher layer signaling, MAC-CE, and L1 signaling. Alternatively, the standard may define that at least one combination of [Method 1] to [Method 4] is to be used.
[0455] For example, the terminal can be notified of a payload overhead reduction method of MC-DCI by one of the above [Method 1] to [Method 7] through upper layer signaling from the base station. The above [Method 1] to [Method 5] are all for the FDRA field in the MC-DCI, and the terminal can be configured through upper layer signaling for at least one of the above five methods for adjusting the overhead using the FDRA field.
[0456] As another example, the terminal may use a combination of at least one of the above [Method 1] to [Method 5] and at least one of the above [Method 6] and [Method 7]. The above [Method 1] to [Method 5] are overhead reduction methods for the FDRA field, the above [Method 5] may be applicable to fields other than the FDRA field, and the above [Method 6] and [Method 7] may be applicable to the TPMI field, the antenna port field, and the PTRS-DMRS association field. Therefore, depending on the combination of at least one of these methods, the terminal and the base station may individually apply each method to applicable fields to reduce the overhead of MC-DCI.
[0457] A terminal may report to a base station a terminal capability that means that it can support at least one combination of [Method 1] to [Method 8]. The terminal capability may be defined separately for [Method 1] to [Method 8], or may be defined as a single terminal capability that means that it can support at least one combination of [Method 1] to [Method 8]. In addition, if the terminal cannot support at least one combination of [Method 1] to [Method 8], it may support at least one combination of [Method 1] to [Method 8] as an alternative method. For example, if the terminal reports a terminal capability that it cannot support [Method 1] or does not report a terminal capability that it supports [Method 1], the terminal may achieve the same effect as if it had conveyed to the base station that it can support [Method 5].
[0458] In the above [Method 1] to [Method 8], the waveform of the PUSCH that can be determined through the PUSCH waveform change indicator has been described as two examples, CP-OFDM or DFTS-OFDM, but is not limited thereto. That is, one of three or more waveforms can be selected and applied to PUSCH transmission within a cell that can be scheduled through MC-DCI. When considering three or more waveforms, in addition to CP-OFDM or DFTS-OFDM, at least one or more of waveforms such as FBMC (filter-bank multi-carrier), GFDM (generalized frequency domain multiplexing), or F-OFDM (filtered-OFDM) can be considered.
[0459] Although the effect of reducing the overhead of the DCI payload may be less than that of MC-DCI, the terminal and the base station can apply at least one combination of [Method 1] to [Method 8] not only for MC-DCI but also for DCI format 0_1 or 0_2. To this end, the terminal can report the relevant terminal capability to the base station, and the base station can configure upper layer signaling for this, thereby enabling the DCI payload overhead reduction method to be used for DCI formats 0_1 and 0_2 as well.
[0460] FIG. 13 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.
[0461] A terminal may report terminal capabilities to a base station (1300). At this time, the terminal capabilities that the terminal may report to the base station may include at least one of the following: the number of cell sets that can be scheduled via MC-DCI, the maximum number of cells per cell set, support for at least one combination of [Method 1] to [Method 6] of the third embodiment related to a method for dynamically changing a PUSCH transmission waveform via MC-DCI, and support for at least one combination of [Method 1] to [Method 8] of the fourth embodiment related to a method for reducing overhead of MC-DCI.
[0462] The terminal can receive upper layer signaling from the base station (1305). At this time, the upper layer signaling that the terminal can receive from the base station can include at least one of one or more cell indexes included in one or more cell sets, a table including cell scheduling information in each cell set that can be scheduled via MC-DCI, information according to a combination of at least one of [Method 2-1] to [Method 2-6] related to a method for dynamically changing a PUSCH transmission waveform via MC-DCI, and information according to a combination of at least one of [Method 4-1] to [Method 4-8] related to a method for reducing overhead of MC-DCI. The above-described information can be received from the base station simultaneously or at different times.
[0463] The terminal can determine the payload size of the MC-DCI based on the signaling in steps 1300 and 1305, and can receive the MC-DCI from the base station based on the determined payload size of the MC-DCI (1310). At this time, the MC-DCI may include at least one of a cell set indicator field, a scheduling cell indicator field, one or more TDRA fields, and one or more FDRA fields, and may include L1 signaling according to a combination of at least one of [Method 1] to [Method 6] of the third embodiment related to a PUSCH transmission waveform change indicator through MC-DCI according to at least one embodiment of the present disclosure, and L1 signaling according to a combination of at least one of [Method 1] to [Method 8] of the fourth embodiment related to an overhead reduction method of MC-DCI.
[0464] The terminal may perform PUSCH transmission for multiple cells based on scheduling information in the MC-DCI received from the base station (1315). Specifically, according to at least one embodiment of the present disclosure, based on a combination of at least one of the [Method 1] to [Method 6] of the third embodiment related to a PUSCH transmission waveform change indicator via MC-DCI, based on upper layer signaling and / or L1 signaling (or one or more information or fields) included in the MC-DCI, and based on a combination of at least one of the [Method 1] to [Method 8] of the fourth embodiment related to an overhead reduction method of MC-DCI, PUSCH transmission on each cell may be performed.
[0465] 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.
[0466] FIG. 14 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.
[0467] The base station can receive terminal capabilities from the terminal (1400). At this time, the terminal capabilities that the base station can receive from the terminal may include at least one of the following: the number of cell sets that can be scheduled via MC-DCI, the maximum number of cells per cell set, whether to support at least one combination of [Method 1] to [Method 6] of the third embodiment related to the method for dynamically changing PUSCH transmission waveforms via MC-DCI, and whether to support at least one combination of [Method 1] to [Method 8] of the fourth embodiment related to the method for reducing overhead of MC-DCI.
[0468] The base station may transmit upper layer signaling to the terminal (1405). At this time, the upper layer signaling that the base station may transmit to the terminal may include at least one of one or more cell indexes included in each of one or more cell sets, a table including cell scheduling information in each cell set that can be scheduled via MC-DCI, information according to a combination of at least one of [Method 1] to [Method 6] of the third embodiment related to a method for dynamically changing a PUSCH transmission waveform via MC-DCI, and information according to a combination of at least one of [Method 1] to [Method 8] of the fourth embodiment related to a method for reducing overhead of MC-DCI. The above-described information may be received from the base station simultaneously or at different times.
[0469] The base station can determine the payload size of the MC-DCI based on the signaling in steps 1400 and 1405, and can transmit the MC-DCI to the terminal (1410). At this time, the MC-DCI may include at least one of a cell set indicator field, a scheduling cell indicator field, one or more TDRA fields, and one or more FDRA fields, and may include L1 signaling according to a combination of at least one of [Method 1] to [Method 6] of the third embodiment related to a PUSCH transmission waveform change indicator through MC-DCI according to at least one embodiment of the present disclosure, and L1 signaling according to a combination of at least one of [Method 1] to [Method 8] of the fourth embodiment related to an overhead reduction method of MC-DCI.
[0470] The base station can receive PUSCH transmissions on multiple cells corresponding to scheduling information in MC-DCI transmitted from a terminal to the terminal (1415). Specifically, the base station can receive PUSCH on each cell transmitted from the terminal corresponding to upper layer signaling and / or L1 signaling (or one or more information or fields) included in MC-DCI based on at least one combination of [Method 1] to [Method 6] of the third embodiment related to a PUSCH transmission waveform change indicator via MC-DCI according to at least one embodiment of the present disclosure, and at least one combination of [Method 1] to [Method 8] of the fourth embodiment related to an overhead reduction method of MC-DCI.
[0471] 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.
[0472] FIG. 15 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0473] Referring to FIG. 15, the terminal may include a transceiver, which refers to a terminal receiving unit (1500) and a terminal transmitting unit (1510), a memory (not shown), and a terminal processing unit (1505, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1500, 1510), the memory, and the terminal processing unit (1505) 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.
[0474] 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.
[0475] 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.
[0476] 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.
[0477] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform component control operations of the terminal by executing programs stored in memory.
[0478] FIG. 16 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0479] Referring to FIG. 16, the base station may include a transceiver, which refers to a base station receiver (1600) and a base station transmitter (1610), a memory (not shown), and a base station processor (1605, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (1600, 1610), the memory, and the base station processor (1605) 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.
[0480] 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.
[0481] 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.
[0482] 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.
[0483] The processor can control a series of processes to enable the base station to operate according to the aforementioned embodiments of the present disclosure. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.
[0484] 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.
[0485] 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.
[0486] 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.
[0487] 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.
[0488] 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.
[0489] 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.
[0490] 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.
[0491] 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.
[0492] 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.
[0493] 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 for setting up uplink data transmission supporting up to 8 layers from a base station; A step of receiving information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) from the base station; A step of receiving downlink control information (DCI) for scheduling the uplink data transmission from the base station, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH; and Including a step of transmitting the PUSCH based on the DCI to the base station, The above scheduling information includes frequency resource allocation information for the PUSCH, A method characterized in that the value of the above frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
2. In the first paragraph, the multiple of one or more of the predetermined integers is 2 less than 275. A 3 B 5 C A method characterized in that A, B and C are non-negative integers.
3. In paragraph 1, A method characterized in that the frequency resource allocation information further includes information indicating a starting point of the consecutive resource blocks.
4. In paragraph 3, The information indicating the starting point of the above consecutive resource blocks is ceil (log 2 A method characterized in that the bits are (275 / N)), wherein N is set by upper layer signaling.
5. In a method performed by a base station of a communication system, A step of transmitting information for setting up uplink data transmission supporting up to 8 layers to a terminal; A step of transmitting information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) to the terminal; A step of transmitting downlink control information (DCI) for scheduling the uplink data transmission to the terminal, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH; and Including a step of receiving the PUSCH corresponding to the DCI from the terminal, The above scheduling information includes frequency resource allocation information for the PUSCH, A method characterized in that the value of the above frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
6. In paragraph 5, the multiple of one or more of the predetermined integers is 2 less than 275. A 3 B 5 C A method characterized in that A, B and C are non-negative integers.
7. In paragraph 5, A method characterized in that the frequency resource allocation information further includes information indicating a starting point of the consecutive resource blocks.
8. In paragraph 7, The information indicating the starting point of the above consecutive resource blocks is ceil (log 2 A method characterized in that the bits are (275 / N)), wherein N is set by upper layer signaling.
9. At the terminal of the communication system, Transmitter and receiver; and Receive information for setting up uplink data transmission supporting up to 8 layers from a base station, Receive information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) from the base station, Receive downlink control information (DCI) for scheduling the uplink data transmission from the base station, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH, and Including a control unit set to transmit the PUSCH based on the DCI to the base station, The above scheduling information includes frequency resource allocation information for the PUSCH, A terminal characterized in that the value of the above frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
10. In paragraph 9, the multiple of one or more of the predetermined integers is 2 less than 275. A 3 B 5 C A terminal, characterized in that A, B and C are non-negative integers.
11. In paragraph 9, A terminal characterized in that the frequency resource allocation information further includes information indicating a starting point of the consecutive resource blocks.
12. In paragraph 11, The information indicating the starting point of the above consecutive resource blocks is ceil (log 2 A terminal characterized in that the bits are (275 / N) and N is set by upper layer signaling.
13. In the base station of the communication system, Transmitter and receiver; and Transmits information for setting up uplink data transmission supporting up to 8 layers to the terminal, Transmit information for setting dynamic waveform change for a physical uplink shared channel (PUSCH) to the above terminal, Transmitting downlink control information (DCI) for scheduling the uplink data transmission to the terminal, wherein the DCI includes scheduling information for the PUSCH and a waveform change indicator for the PUSCH, and Including a control unit set to receive the PUSCH corresponding to the DCI from the terminal, The above scheduling information includes frequency resource allocation information for the PUSCH, A base station, characterized in that the value of the above frequency resource allocation information indicates one number among multiples of one or more predetermined integers, and a number of consecutive resource blocks corresponding to the one number are scheduled.
14. In the 13th paragraph, the multiple of one or more of the predetermined integers is 2 less than 275. A 3 B 5 C A base station, wherein A, B, and C are non-negative integers.
15. In paragraph 13, The above frequency resource allocation information further includes information indicating the starting point of the consecutive resource blocks, The information indicating the starting point of the above consecutive resource blocks is ceil (log 2 A base station characterized in that the number of bits is (275 / N), wherein N is set by upper layer signaling.
Citation Information
Patent Citations
Method, server and computer program for detecting fire based on virtual sensor
KR1020230019896A
Composition and manufacturing method of roasted eel sauce, and roasted eel by using the sauce
KR102411249B1
Control signal configuration waveform type
WO2021260659A1
