Method and apparatus for scheduling multiple shared channels in wireless communication system

By using time domain resource allocation configuration information and cell index in 5G mobile communication system, the downlink control information is exchanged between the terminal and the base station, the problem of low scheduling efficiency of multi-cell data channel is solved, and efficient resource allocation and performance are achieved promote.

CN119054394APending Publication Date: 2024-11-29SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035413.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-22
Filing Date
2023-04-19
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In 5G mobile communication systems, it is difficult for the prior art to effectively schedule data channels of multiple cells, resulting in low resource allocation efficiency and unable to meet the rapidly growing needs of connected devices for performance and integrated operations.

Method used

By introducing time domain resource allocation (TDRA) configuration information into the wireless communication system, the terminal and the base station exchange downlink control information including multi-line data channel scheduling information in a high-level signaling manner, and use the cell index and the TDRA field to indicate the specific information. The data channel scheduling information realizes effective scheduling of data channels of multiple cells.

Benefits of technology

It realizes the efficient scheduling of data channels of multiple cells through a single DCI, improves data transmission and reception efficiency, reduces the overhead of downlink control channels, and supports rapidly growing connection equipment and service needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054394A_ABST
    Figure CN119054394A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure provides a method and apparatus for scheduling multi-cell transmission via a single piece of DCI in a wireless communication system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system. In particular, the present disclosure relates to a method for interpreting downlink control information for scheduling multiple downlinks and multiple uplinks of a terminal and a device capable of performing the method. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called millimeter waves (mmWave) including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.

[0003] In the initial stage of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC) and massive machine-type communication (mMTC), there is ongoing standardization on the following items: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, parameter sets for dynamic operation of efficient utilization of millimeter wave resources and time slot formats (for example, operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-capacity data transmission and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks customized for specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as: Vehicle-to-Everything (V2X), for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience; New Radio Unlicensed (NR-U), for system operation that is intended to comply with various regulatory-related requirements in unlicensed bands; NR UE power saving; Non-Terrestrial Network (NTN), which is UE satellite direct communication for ensuring coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] In addition, in the field of wireless interface architecture / protocol, there is already ongoing standardization on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization in the field of system architecture / services for 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] If such a 5G mobile communication system is commercialized, the already exponentially growing number of connected devices will be connected to the communication network, and it is accordingly expected that enhanced functions and performance of the 5G mobile communication system and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged to effectively support augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., to improve 5G performance and reduce complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, meta-service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for ensuring coverage in the terahertz band for 6G mobile communication technology, full-dimensional MIMO (FD-MIMO), multi-antenna transmission technologies such as array antennas and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources.

[0008] With the advancement of wireless communication systems as described above, various services can be provided, and thus a way of smoothly providing these services is required. Summary of the invention

[0009] Technical issues

[0010] Based on the above discussion, the present disclosure provides a device and method capable of effectively providing services in a mobile communication system. Specifically, the present disclosure provides a method and device for performing multi-cell scheduling through downlink control information.

[0011] Technical Solution

[0012] The disclosure for solving the above-mentioned problem relates to a method performed by a terminal in a wireless communication system, the method comprising: receiving time domain resource allocation (TDRA) configuration information from a base station through high-layer signaling, wherein the TDRA configuration information includes multiple rows and each row includes one or more data channel scheduling information; receiving downlink control information for scheduling data channels from the base station, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of the multiple rows; and sending or receiving a data channel in each of the cells corresponding to the one or more cell indexes based on the one or more data channel scheduling information included in the indicated row and the one or more cell indexes indicated by the cell index indicator.

[0013] In addition, the present disclosure relates to a method performed by a base station in a wireless communication system, the method comprising: sending time domain resource allocation (TDRA) configuration information to a terminal through high-layer signaling, wherein the TDRA configuration information includes multiple rows and each row includes one or more data channel scheduling information; sending downlink control information for scheduling data channels to the terminal, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of the multiple rows; and receiving or sending a data channel in each of the cells corresponding to one or more cell indexes related to the cell index indicator, wherein the data channel corresponds to one or more data channel scheduling information included in the indicated row.

[0014] In addition, the present disclosure relates to a terminal in a wireless communication system, the terminal comprising: a transceiver; and a controller configured to perform control to receive time domain resource allocation (TDRA) configuration information from a base station through high-layer signaling, wherein the TDRA configuration information includes multiple rows and each row includes one or more data channel scheduling information; receive downlink control information for scheduling data channels from the base station, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of the multiple rows; and based on the one or more data channel scheduling information included in the indicated row and the one or more cell indexes indicated by the cell index indicator, send or receive a data channel in each of the cells corresponding to the one or more cell indexes.

[0015] In addition, the present disclosure relates to a base station in a wireless communication system, the base station comprising: a transceiver; and a controller configured to perform control to send time domain resource allocation (TDRA) configuration information to a terminal through high-layer signaling, wherein the TDRA configuration information includes multiple rows and each row includes one or more data channel scheduling information; send downlink control information for scheduling a data channel to the terminal, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of the multiple rows; and receive or send a data channel in each of the cells corresponding to one or more cell indexes related to the cell index indicator, wherein the data channel corresponds to one or more data channel scheduling information included in the indicated row.

[0016] Beneficial Effects

[0017] According to the apparatus and method of the embodiments of the present disclosure, data channel scheduling for multiple cells and data transmission and reception in the multiple cells can be efficiently performed through a single DCI. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The basic structure of the time-frequency domain in the wireless communication system according to the embodiment of the present disclosure is shown;

[0019] Figure 2 The structure of frames, subframes and time slots in a wireless communication system according to an embodiment of the present disclosure is shown;

[0020] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown;

[0021] Figure 4 An example of a control resource set configuration of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0022] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0023] Figure 6 A diagram for explaining a method in which a base station and a UE transmit / receive data in consideration of a downlink data channel and a rate matching resource in a wireless communication system according to an embodiment of the present disclosure is shown;

[0024] Figure 7 An example of frequency domain resource allocation for a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown;

[0025] Figure 8An example of time domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown;

[0026] Fig. 9 An example of time domain resource allocation according to subcarrier spacing for a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0027] Fig.10 The radio protocol structures of a base station and a UE in the case of a single cell, carrier aggregation and dual connectivity according to an embodiment of the present disclosure are shown;

[0028] Fig.11 An example of a scheme for scheduling multiple PDSCHs according to an embodiment of the present disclosure is shown;

[0029] Fig.12 An example of the structure of DCI for single PDSCH scheduling and multi-PDSCH scheduling is shown;

[0030] Fig.13 An example of a method for scheduling multi-cell multi-PDSCH according to an embodiment of the present disclosure is shown;

[0031] Fig.14 An example of a multi-cell scheduling index application method according to an embodiment of the present disclosure is shown;

[0032] Fig.15 An example of a multi-cell scheduling index application method according to an embodiment of the present disclosure is shown;

[0033] Fig.16 An example of a DCI format for multi-cell multi-PDSCH according to an embodiment of the present disclosure is shown;

[0034] Fig.17 An example of a DCI format for a PUCCH group of multi-cell multi-PDSCH according to an embodiment of the present disclosure is shown;

[0035] Fig.18 An example of HARQ-ACK operation according to a PUCCH group according to an embodiment of the present disclosure is shown;

[0036] Fig.19 An example of a multi-cell scheduling indication method using a bitmap according to an embodiment of the present disclosure is shown;

[0037] Fig.20a An example of illustrating the operation of a base station according to an embodiment of the present disclosure; and

[0038] Fig.20b An example of an operation of a terminal according to an embodiment of the present disclosure is shown.

[0039] Fig.21shows the structure of a UE according to an embodiment of the present disclosure; and

[0040] Fig. 22 The structure of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

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

[0042] When describing the embodiments, descriptions related to technical contents that are well known in the relevant field and not directly related to the present disclosure will be omitted. Such unnecessary omissions are intended to prevent the main concept of the present disclosure from being obscured and to convey the main concept more clearly.

[0043] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In each of the accompanying drawings, the same or corresponding elements are provided with the same reference numerals.

[0044] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements. In addition, when describing the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are terms defined in view of the functions in the present disclosure, and may be different according to the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content of the entire specification.

[0045] In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, an eNode B, a node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, "downlink (DL)" may indicate a radio link via which a base station sends a signal to a terminal, and "uplink (UL)" may indicate a radio link via which a terminal sends a signal to a base station. In addition, in the following description, an LTE or LTE-A system may be described by way of example, but embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, new radio, and NR) developed beyond LTE-A, and in the following description, "5G" may be a concept covering existing LTE, LTE-A, and other similar services. In addition, based on determinations made by those skilled in the art, the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0046] In this article, it will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific way, so that the instructions stored in the computer-usable or computer-readable memory produce an article of instruction device including the function specified in one or more flowchart boxes. The computer program instructions can also be loaded on a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the function specified in one or more flowchart boxes.

[0047] In addition, each frame in the flowchart diagram can represent a module, fragment or part of a code, which includes one or more executable instructions for implementing a specified logical function (or multiple). It should also be noted that in some alternative embodiments, the functions mentioned in the frame may not occur in order. For example, two frames shown in succession can actually be performed substantially simultaneously, or frames can sometimes be performed in reverse order, depending on the functions involved.

[0048] As used in the embodiments of the present disclosure, "unit" indicates a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions provided by "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, elements and "units" can be implemented as one or more CPUs in a reproduction device or a secure multimedia card. In addition, "unit" in the embodiment can include one or more processors.

[0049] Wireless communication systems are evolving into broadband wireless communication systems for providing high-speed and high-quality packet data services using communication standards such as 3GPP's High Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), Advanced LTE (LTE-A), LTE-Pro, 3GPP2's High Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, etc., as well as typical voice-based services.

[0050] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink indicates a radio link via which a user equipment (UE) or a mobile station (MS) sends data or a control signal to a base station (BS) or an eNodeB, and the downlink indicates a radio link via which a base station sends data or a control signal to a UE. The above-mentioned multiple access scheme can separate the data or control information of each user by allocating and operating time-frequency resources for sending data or control information to each user so as to avoid overlapping with each other, that is, so as to establish orthogonality.

[0051] Since the 5G communication system as a post-LTE communication system must freely reflect various requirements of users, service providers, etc., it is necessary to support services that meet various requirements. Services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc.

[0052] eMBB aims to provide a higher data rate than that supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink for a single base station. In addition, the 5G communication system must provide an increased user-perceived data rate and a maximum data rate to the UE. In order to meet such requirements, it is necessary to improve the transmission / reception technology including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, a frequency bandwidth greater than 20MHz can be used in a frequency band of 3 to 6GHz or 6GHz or higher to obtain the data rate required by the 5G communication system, instead of using a transmission bandwidth of up to 20MHz to send signals in the 2GHz frequency band used in LTE.

[0053] In addition, mMTC is being considered to support application services of the Internet of Things (IoT) in the 5G communication system. mMTC has requirements such as supporting the connection of a large number of UEs in a cell, enhancing the coverage of UEs, improving battery time, reducing the cost of UEs, etc., in order to effectively provide the Internet of Things. Since the Internet of Things provides a communication function while being provided to various sensors and various devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UE / km 2 ). In addition, a UE supporting mMTC may require wider coverage than the coverage of other services provided by the 5G communication system because the UE may be located in a shadow area (such as a basement of a building) that is not covered by a cell due to the nature of the service. A UE supporting mMTC must be configured to be cheap and may require a very long battery life, such as 10 to 15 years, because it is difficult to frequently replace the battery of the UE.

[0054] URLLC is a mission-critical cellular-based wireless communication service. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC must provide communications with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms and may also require 10 -5Or a smaller packet error rate. Therefore, for services supporting URLLC, the 5G system must provide a transmission time interval (TTI) that is shorter than that of other services, and may also require a design for allocating a large amount of resources in the frequency band to ensure the reliability of the communication link.

[0055] The three services in 5G, namely eMBB, URLLC and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services to meet the different requirements of each service. Of course, 5G is not limited to the three services described above.

[0056] [NR time-frequency resources]

[0057] Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the accompanying drawings.

[0058] Figure 1 The basic structure of the time-frequency domain in the 5G system is shown, wherein the time-frequency domain is a radio resource domain used to send data or control channels.

[0059] exist Figure 1 In the , the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time-frequency domain is a resource element (RE) 101, which can be defined as one orthogonal frequency division multiplexing (OFDM) symbol 102 along the time axis and one subcarrier 103 along the frequency axis. In the frequency domain, (eg, 12) consecutive REs may constitute one resource block (RB) 104 .

[0060] Figure 2 The structures of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure are shown.

[0061] Figure 2 An example of the structure of a frame 200, a subframe 201, and a time slot 202 is shown. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 millisecond (ms), so one frame 200 may include a total of ten subframes 201. One time slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols per time slot is 14 OFDM symbols). ). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 of each subframe 201 may vary according to the configured value μ of the subcarrier spacing 204 or 205. Figure 2The example in FIG. 2 shows a case where the subcarrier spacing configuration value is μ=0 (204) and a case where μ=1 (205). In the case where μ=0 (204), one subframe 201 may include one time slot 202, and in the case where μ=1 (205), one subframe 201 may include two time slots 203. That is, the number of time slots per subframe is The number of slots per frame may vary depending on the subcarrier spacing configuration value μ. May be different accordingly. and It can be defined according to each subcarrier spacing configuration as shown in Table 1 below.

[0062] [Table 1]

[0063]

[0064] [Bandwidth Part (BWP)]

[0065] Hereinafter, a bandwidth part (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.

[0066] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0067] Figure 3 An example is shown in which the UE bandwidth 300 is configured to include two bandwidth parts, namely, bandwidth part #1 (BWP#1) 301 and bandwidth part #2 (BWP#2) 302. The base station may configure one or more bandwidth parts for the UE and may configure the following information about each bandwidth part, as given in Table 2 below.

[0068] [Table 2]

[0069]

[0070] Obviously, the above examples are not restrictive, and in addition to the above configuration information, various parameters related to the bandwidth part can also be configured for the UE. The base station can transmit the configuration information to the UE through upper layer signaling, such as radio resource control (RRC) signaling. At least one bandwidth part among a configured bandwidth part or multiple configured bandwidth parts can be activated. Whether to activate the configured bandwidth part can be transmitted from the base station to the UE semi-statically through RRC signaling or dynamically through downlink control information (DCI).

[0071] According to an embodiment, before a radio resource control (RRC) connection, an initial bandwidth part (BWP) for initial access may be configured for a UE by a base station through a master information block (MIB). More specifically, the UE may receive configuration information about a control resource set (CORESET) and a search space, which may be used to send a PDCCH for receiving system information (which may correspond to the remaining system information (RMSI) or system information block 1 (SIB1)) necessary for initial access through the MIB in an initial access step. Each of the control resource set and the search space configured through the MIB may be considered as an identification (ID) 0. The base station may notify the UE of configuration information about CORESET#0, such as frequency allocation information, time allocation information, and parameter set, through the MIB. In addition, the base station may notify the UE of configuration information related to a monitoring period and timing of the control resource set #0, that is, configuration information about the search space #0, through the MIB. The UE may consider the frequency domain configured by the CORESET#0 acquired from the MIB to be the initial bandwidth part for initial access. The ID of the initial bandwidth part may be considered to be 0.

[0072] The UE may receive a physical downlink shared channel (PDSCH) through which the SIB is transmitted through the configured initial bandwidth part. The initial bandwidth part may be used not only for the purpose of receiving the SIB but also for other system information (OSI), paging, random access, etc.

[0073] [Bandwidth Part (BWP) Change]

[0074] If the UE has one or more bandwidth parts configured for it, the base station can indicate to the UE to change (or switch or transition) the bandwidth part by using the bandwidth part indicator field in the DCI. As an example, if the UE's currently activated bandwidth part is Figure 3 If the bandwidth part #1 301 in the received DCI is used, the base station can use the bandwidth part indicator inside the DCI to indicate the bandwidth part #2 302, and the UE can change the bandwidth part to the bandwidth part #2 302 indicated by the bandwidth part indicator inside the received DCI.

[0075] As described above, the DCI-based bandwidth part change can be indicated by the DCI for scheduling PDSCH or PUSCH. Therefore, upon receiving the bandwidth part change request, the UE needs to be able to receive or send the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part without any problem. To this end, the delay time (T BWP ) requirements, and it can be defined, for example, in Table 3 below.

[0076] [Table 3]

[0077]

[0078] The bandwidth part change delay time requirement can support type 1 or type 2, depending on the UE's capabilities. The UE can report the supported bandwidth part delay time type to the base station.

[0079] If the UE has received the DCI including the bandwidth part change indicator in the time slot n, then according to the requirements on the bandwidth part change delay time described above, the UE can complete the change to the new bandwidth part indicated by the bandwidth part change indicator at a time point no later than the time slot n+TBWP, and can send / receive the data channel scheduled by the corresponding DCI in the newly changed bandwidth part. If the base station wants to schedule the data channel by using the new bandwidth part, the base station can consider the bandwidth part change delay time (T BWP ) determines the time domain resource allocation for the data channel. That is, when scheduling the data channel by using the new bandwidth part, in combination with the method for determining the time domain resource allocation for the data channel, the base station may schedule the corresponding data channel after the bandwidth part change delay time. Therefore, the UE may not expect that the DCI indicating the bandwidth part change will indicate a bandwidth less than the bandwidth part change delay time (T BWP )’s time slot offset (K0 or K2) value.

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

[0081] [SS / PBCH block]

[0082] Next, the synchronization signal / physical broadcast channel (SS / PBCH) block in 5G will be described.

[0083] The SS / PBCH block may indicate a physical layer channel block including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH. The details thereof are as follows.

[0084] PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides partial information of the cell ID.

[0085] SSS: Becomes a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. In addition, SSS can be used as a reference signal for PBCH demodulation of PBCH.

[0086] PBCH: Provides necessary system information necessary for data channel and control channel transmission / reception of UE. Necessary system information may include search space-related control information indicating radio resource mapping information of control channel, scheduling control information about a separate data channel for transmitting system information, etc.

[0087] SS / PBCH block: SS / PBCH block includes a combination of PSS, SSS and PBCH. One or more SS / PBCH blocks can be sent in a 5 ms period, and each sent SS / PBCH block can be distinguished by an index.

[0088] The UE can detect the PSS and SSS in the initial access phase and can decode the PBCH. The UE can obtain the MIB from the PBCH, and this can be used to configure the control resource set (CORESET) #0 (which can correspond to the control resource set with the control resource set index 0). The UE can monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) and the control resource set #0 sent in the selected SS / PBCH block are quasi-co-located (QCL). The UE can receive system information using the downlink control information sent in CORESET #0. The UE can obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. The UE can send a physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station can obtain information about the SS / PBCH block index selected by the UE when receiving the PRACH. The base station can know which block the UE has selected from the various SS / PBCH blocks and the fact that CORESET #0 associated with it is monitored.

[0089] Typically, the UE can establish a radio link to the network through a random access procedure based on synchronization with the network and system information acquired during a cell search process for the corresponding cell. As a random access, a contention-based scheme or a contention-free scheme can be used. If the UE performs cell selection and cell reselection in the initial access step, a contention-based scheme can be used, for example, in the case of transitioning from the RRC_IDLE state to the RRC_CONNECTED state, and for other purposes. A contention-free scheme can be used to reconfigure uplink synchronization in the case of downlink data arrival, in the case of handover, or in the case of position measurement.

[0090] [PDCCH: About DCI]

[0091] Next, downlink control information (DCI) in the 5G communication system will be described in detail.

[0092] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is included in the DCI and sent from the base station to the UE via the DCI. The UE can monitor the fallback DCI format and the non-fallback DCI format with respect to the PUSCH or PDSCH. The fallback DCI format may include a fixed field predefined between the base station and the UE, and the non-fallback DCI format may include a configurable field.

[0093] The DCI may be subjected to a channel coding and modulation process and then sent through a physical downlink control channel (PDCCH) after the channel coding and modulation process. A cyclic redundancy check is attached to the DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control commands, or random access responses, etc.). That is, the RNTI may not be sent explicitly, but may be sent while being included in the CRC calculation process. Upon receiving a DCI message sent via the PDCCH, the UE may identify the CRC by using the assigned RNTI, and if the CRC identification result is correct, the UE may know that the corresponding message has been sent to the UE.

[0094] DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, and the CRC may be scrambled by the C-RNTI. For example, DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include the following information fragments given in Table 4 below.

[0095] [Table 4]

[0096]

[0097] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling PUSCH, and the CRC may be scrambled by the C-RNTI. For example, DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI may include the following pieces of information given in Table 5 below.

[0098] [Table 5]

[0099]

[0100]

[0101] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH, and the CRC may be scrambled by the C-RNTI. For example, DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include the following pieces of information given in Table 6 below.

[0102] [Table 6]

[0103]

[0104] DCI format 1_1 may be used as a non-fallback DCI for scheduling PDSCH, and the CRC may be scrambled by the C-RNTI. For example, DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include the following pieces of information given in Table 7 below.

[0105] [Table 7]

[0106]

[0107]

[0108] [PDCCH: CORESET, REG, CCE and search space]

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

[0110] Figure 4 An example of a CORESET for transmitting a downlink control channel in a 5G wireless communication system is shown. Figure 4 An example is shown in which a UE bandwidth portion 410 is configured along the frequency axis, and two CORESETs (CORESET#1 401 and CORESET#2 402) are configured within a time slot 420 along the time axis. CORESETs 401 and 402 may be configured in specific frequency resources 410 within the entire UE bandwidth portion 403 along the frequency axis. One or more OFDM symbols may be configured along the time axis, and this may be defined as a control resource set duration 404. Figure 4 In the example shown in FIG. 4 , CORESET#1 401 is configured to have a CORESET duration of two symbols, and CORESET#2 402 is configured to have a CORESET duration of one symbol.

[0111] The base station can configure the control resource set in 5G described above for the UE through upper layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring the description of CORESET for the UE means providing information such as the identity of CORESET, the frequency position of CORESET, and the symbol duration of CORESET. For example, the CORESET configuration information may include the following information: given in Table 8 below.

[0112] [Table 8]

[0113]

[0114]

[0115] In Table 8, the tci-StatesPDCCH (abbreviated as transmission configuration indication (TCI) state) configuration information may include information of one or more SS / PBCH block indices or channel state information reference signal (CSI-RS) indices, which are quasi co-located (OCL) with the DMRS transmitted in the corresponding CORESET.

[0116] Figure 5 An example of a basic unit of time and frequency resources constituting a downlink control channel available in a 5G system is shown. Figure 5 , the basic unit of time and frequency resources constituting the control channel may be referred to as a resource element group (REG) 503, and the REG 503 may be defined by one OFDM symbol 501 along the time axis and one physical resource block (PRB) 502 along the frequency axis, i.e., 12 subcarriers. The base station may configure the downlink control channel allocation unit by cascading the REG 503.

[0117] Assume that the basic unit of downlink control channel allocation in 5G is as follows Figure 5 For the control channel elements shown in FIG. 1 , a CCE may include multiple REGs. Figure 5 503, for example, REG 503 may include 12 REs, and if one CCE 504 includes six REGs 503, then one CCE 504 may include 72 REs. A downlink control resource set may include multiple CCEs 504 once configured, and a specific downlink control channel may be mapped to one or more CCEs 504 and then transmitted according to an aggregation level (AL) in the control resource set. CCEs 504 in a CORESET are distinguished by numbers, and the numbers of CCEs 504 may be allocated according to a logical mapping scheme.

[0118] Figure 5The basic unit of the downlink control channel (ie, REG 503) shown in FIG. 5 may include both REs to which DCI is mapped and regions to which a reference signal (DMRS 505) for decoding the same is mapped. Figure 5 , three DRMS ​​503 can be sent inside one REG 505. Depending on the aggregation level (AL), the number of CCEs required to send the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, one downlink control channel can be sent by L CCEs. The UE needs to detect the signal while having no information about the downlink control channel, so a search space indicating a CCE set has been defined for blind decoding.

[0119] A search space is a set of downlink control channel candidates, including CCEs that the UE needs to try to decode with a given AL. Since 1, 2, 4, 8 or 16 CCEs are bundled in various ALs, a UE can have multiple search spaces. A search space set can be defined as a set of search spaces in all configured ALs. Search spaces can be classified into common search spaces and UE-specific search spaces. A group of UEs or all UEs can search the common search space of the PDCCH in order to perform dynamic scheduling about system information. For example, PDSCH scheduling allocation information for sending SIBs including cell operator information, etc. can be received by searching the common search space of the PDCCH. In the case of a common search space, a group of UEs or all UEs need to receive the PDCCH, and therefore it can be defined as a predetermined CCE set. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by investigating the UE-specific search space of the PDCCH. The UE-specific search space can be specific to the UE and defined as a function of various system parameters and the identity of the UE.

[0120] In 5G, the base station may configure the parameters of the search space of the PDCCH for the UE through upper layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may provide the UE with configurations such as: the number of PDCCH candidates at each aggregation level L, the monitoring period of the search space, the monitoring timing of each symbol in the time slot of the search space, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI format to be monitored in the corresponding search space, the CORESET index used to monitor the search space, etc. For example, the search space configuration information may include the following pieces of information: given in Table 9 below.

[0121] [Table 9]

[0122]

[0123]

[0124] According to the configuration information, the base station may configure one or more search space sets for the UE. According to an embodiment, the base station may configure search space set 1 and search space set 2 for the UE, may configure DCI format A scrambled by X-RNTI to be monitored in the common search space in search space set 1, and may configure DCI format B scrambled by Y-RNTI to be monitored in the UE-specific search space in search space set 2.

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

[0126] The combinations of DCI formats and RNTIs given below may be monitored in the common search space. Obviously, the examples given below are not limiting.

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

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

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

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

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

[0132] The combinations of DCI formats and RNTIs given below may be monitored in the UE-specific search space. Obviously, the examples given below are not limiting.

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

[0134] The enumerated RNTI can follow the definition and usage given below

[0135] Cell RNTI (C-RNTI): used to schedule UE-specific PDSCH

[0136] Temporary cell RNTI (TC-RNTI): used to schedule UE-specific PDSCH

[0137] Configured Scheduling RNTI (CS-RNTI): used to schedule a semi-statically configured UE-specific PDSCH Random Access RNTI (RA-RNTI): used to schedule PDSCH in the random access step

[0138] Paging RNTI (P-RNTI): used to schedule the PDSCH in which paging is sent

[0139] System Information RNTI (SI-RNTI): used to schedule the PDSCH in which system information is sent Interruption RNTI (INT-RNTI): used to indicate whether the PDSCH is punctured

[0140] Transmit Power Control for PUSCH RNTI (TPC-PUSCH-RNTI): used to indicate the power control command for PUSCH

[0141] Transmit Power Control for PUCCH RNTI (TPC-PUCCH-RNTI): used to indicate power control commands for PUCCH

[0142] Transmit Power Control for SRS RNTI (TPC-SRS-RNTI): used to indicate power control commands for SRS

[0143] The DCI formats listed above may follow the definition given in, for example, Table 10 below.

[0144] [Table 10]

[0145]

[0146]

[0147] In 5G, the search space at aggregation level L combined with CORESET p and search space set s can be expressed by the following Equation 1.

[0148] [Equation 1]

[0149]

[0150] L: Aggregation level

[0151] n CI : Carrier index

[0152] NCCE,p : The total number of CCEs present in control resource set p

[0153] Time slot index

[0154] Number of PDCCH candidates at aggregation level L

[0155] PDCCH candidate index for aggregation level L

[0156] i=0,…,L-1

[0157] - Y p,-1 =n RNTI ≠0, for pmod3=0, A p =39827, for pmod3 = 1, A p =39829, for pmod3 = 2, A p =39839, D=65537

[0158] -n RNTI :UE ID

[0159] In the case of a public search space, The value may correspond to 0.

[0160] In case of UE-specific search space, The value may correspond to a value changed by the UE's identity (C-RNTI or an ID configured by the base station for the UE) and a time index.

[0161] In 5G, multiple search space sets may be configured by different parameters (e.g., the parameters in Table 9), and the group of search space sets monitored by the UE at each time point may be different accordingly. For example, if search space set #1 is configured with an X time slot cycle, if search space set #2 is configured with a Y time slot cycle, and if X and Y are different, the UE may monitor both search space set #1 and search space set #2 in a specific time slot, and may monitor one of search space set #1 and search space set #2 in another specific time slot.

[0162] [About rate matching / puncturing]

[0163] Hereinafter, the rate matching operation and the puncturing operation will be described in detail.

[0164] If time and frequency resource A for transmitting symbol sequence A overlaps with time and frequency resource B, the rate matching or puncturing operation can be considered as an operation of transmitting / receiving channel A taking into account resource C (the area where resource A and resource B overlap). The specific operation can follow the following description.

[0165] Rate Matching Operation

[0166] The base station may transmit channel A to the UE after mapping channel A only to the remaining resource region except resource C (region overlapping with resource B) among the entire resource A to be used for transmitting the symbol sequence A. For example, assuming that the symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol 4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station may transmit the symbol sequence A after continuously mapping the symbol sequence A to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) among resource A. Therefore, the base station may transmit the symbol sequence {symbol #1, symbol #2, symbol #3} after mapping the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0167] The UE may estimate resource A and resource B from scheduling information about symbol sequence A from the base station, thereby estimating resource C. The UE may receive symbol sequence A based on an assumption that symbol sequence A has been mapped and transmitted in the remaining region except resource C among the entire resource A. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol 4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE may receive symbol sequence A based on an assumption that symbol sequence A has been continuously mapped to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) among resource A. Therefore, the UE may perform a series of the following reception operations based on an assumption that the symbol sequence {symbol #1, symbol #2, symbol #3} has been transmitted after being respectively mapped to {resource #1, resource #2, resource #4}.

[0168] Punching operation

[0169] If there is resource C (an area overlapping with resource B) within the entire resource A to be used to send symbol sequence A to the UE, the base station can map symbol sequence A to the entire resource A, but may not perform transmission in the resource area corresponding to resource C, and may only perform transmission with respect to the remaining resource area within resource A except resource C. For example, assuming that the symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol 4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station may respectively map the symbol sequence {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, may only transmit the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) in resource A, and may not transmit {symbol #3} mapped to {resource #3} (corresponding to resource C). Therefore, the base station may transmit the symbol sequence {symbol #1, symbol #2, symbol #4} after respectively mapping the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4}.

[0170] The UE can evaluate resource A and resource B according to the scheduling information about symbol sequence A from the base station, thereby evaluating resource C (the region where resource A and resource B overlap). The UE can receive symbol sequence A based on the assumption that symbol sequence A has been mapped to the entire resource A but is transmitted only in the remaining region of resource region A except resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol 4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol 4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} (corresponding to resource C) is not sent, and based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A except {resource #3} (corresponding to resource C) has been mapped and sent, the UE can receive the symbol sequence. Therefore, the UE can perform a series of the following reception operations based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} has been transmitted after being respectively mapped to {resource #1, resource #2, resource #4}.

[0171] Hereinafter, a method for configuring rate matching resources for the purpose of rate matching in a 5G communication system will be described. Rate matching indicates adjusting the size of a signal taking into account the amount of resources that can be used to send the signal. For example, data channel rate matching may mean not mapping and sending a data channel with respect to a specific time and frequency resource domain, and adjusting the size of the data accordingly.

[0172] Figure 6 is a diagram for explaining a method in which a base station and a UE transmit / receive data in consideration of a downlink data channel and a rate matching resource.

[0173] Figure 6 A downlink data channel (PDSCH) 601 and a rate matching resource 602 are shown. The base station can configure one or more rate matching resources 602 for the UE through upper layer signaling (e.g., RRC signaling). The rate matching resource 602 configuration information may include time domain resource allocation information 603, frequency domain resource allocation information 604, and period information 605. The bitmap corresponding to the frequency domain resource allocation information 604 will be referred to as the "first bitmap" hereinafter, the bitmap corresponding to the time domain resource allocation information 603 will be referred to as the "second bitmap", and the bitmap corresponding to the period information 605 will be referred to as the "third bitmap". If all or some of the time and frequency resources of the scheduled PDSCH 601 overlap with the configured rate matching resource 602, the base station can perform rate matching and transmit the PDSCH 602 in the rate matching resource 601 part, and the UE can perform reception and decoding after assuming that the PDSCH 602 has been rate matched in the rate matching resource 601 part.

[0174] The base station can dynamically notify the UE through DCI whether the PDSCH will be rate matched in the configured rate matching resource part through additional configuration (for example, corresponding to the "rate matching indicator" inside the DCI format described above). Specifically, the base station can select some from the configured rate matching resources and group them into rate matching resource groups, and can indicate to the UE through DCI whether the PDSCH is rate matched with respect to each rate matching resource group by using a bitmap type. For example, if four rate matching resources RMR#1, RMR#2, RMR#3 and RMR#4 are configured, the base station can configure rate matching groups RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4}, and can indicate to the UE whether rate matching occurs in RMG#1 and RMG#2 respectively by using two bits by a bitmap inside the DCI field. For example, in the case where rate matching is to be performed, the base station can indicate this situation by "1", and in the case where rate matching is not to be performed, the base station can indicate this situation by "0".

[0175] 5G supports the granularity of "RB symbol level" and "RE level" as a method for configuring the rate matching resources described above for the UE. More specifically, the following configuration method can be followed.

[0176] RB symbol level

[0177] The UE may have up to four RateMatchPatterns configured per bandwidth part through upper layer signaling, and one RateMatchPatterns may include the following contents.

[0178] In conjunction with the reserved resources within the bandwidth portion, resources in the time and frequency resource domains with corresponding reserved resources configured as a combination of an RB level bitmap and a symbol level bitmap in the frequency domain may be included. The reserved resources may span one or two time slots. A time domain pattern (periodicityAndPattern) may be additionally configured, wherein the time domain and frequency domain including the corresponding RB level and symbol level bitmap pairs are repeated.

[0179] A resource region corresponding to a time domain pattern configured by a time domain and frequency domain resource region configured by a CORESET inside a bandwidth part and a search space configuration in which a corresponding resource region is repeated may be included.

[0180] RE Level

[0181] The UE may have the following contents configured through upper layer signaling.

[0182] Regarding the configuration information (lte-CRS-ToMatchAround) of REs corresponding to the LTE CRS (cell-specific reference signal or common reference signal) pattern, it may include the port number (nrofCRS-Ports) and LTE-CRS-vshift (or multiple) values ​​(v-shift) of the LTE CRS, the position information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the multicast broadcast single frequency network (MBSFN), etc. The UE can determine the position of the CRS inside the NR time slot corresponding to the LTE subframe based on the above information.

[0183] Configuration information regarding resource sets corresponding to one or more zero-power (ZP) CSI-RS within the bandwidth portion may be included.

[0184] [About LTE CRS rate matching]

[0185] Next, the rate matching process for the LTE CRS mentioned above will be described in detail. For coexistence between LTE and NR, NR provides the NR UE with a function for configuring the pattern of the CRS of LTE. More specifically, the CRS pattern may be provided by RRC signaling including at least one parameter within a ServingCellConfig IE (information element) or a ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, and the like.

[0186] Rel-15 NR provides a function through which one CRS pattern can be configured per serving cell through the parameter lte-CRS-ToMatchAround. In Rel-16 NR, the above function has been extended so that multiple CRS patterns can be configured per serving cell. More specifically, a UE with a single transmit and receive point (TRP) configuration can now have one CRS pattern configured for each LTE carrier, and a UE with a multi-TRP configuration can now have two CRS patterns configured for each LTE carrier. For example, a UE with a single TRP configuration can have up to three CRS patterns configured per serving cell through the parameter lte-CRS-PatternList1-r16. As another example, a UE with a multi-TRP configuration can have a CRS configured for each TRP. That is, the CRS pattern regarding TRP1 can be configured by the parameter lte-CRS-PatternList1-r16, and the CRS pattern regarding TRP2 can be configured by the parameter lte-CRS-PatternList2-r16. If two TRPs are configured as above, the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is used to determine whether the CRS patterns of both TRP1 and TRP2 are applied to a specific physical downlink shared channel (PDSCH) or only the CRS pattern of one TRP is applied, wherein if the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is configured as "enabled", only the CRS pattern of one TRP is applied, and in other cases the two CRS patterns of the two TRPs are applied.

[0187] Table 11 shows ServingCellConfig IE including the CRS pattern, and Table 12 shows RateMatchPatternLTE-CRS IE including at least one parameter regarding the CRS pattern.

[0188] [Table 11]

[0189]

[0190]

[0191] [Table 12]

[0192]

[0193] [PDSCH / PUSCH: About time resource allocation]

[0194] Figure 7 An example of frequency domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0195] Figure 7 Three frequency domain resource allocation methods of type 0700, type 1705, and dynamic switch 710 that can be configured by the upper layer in the NR wireless communication system are shown.

[0196] refer to Figure 7 , in the case 700 where the UE is configured to use only resource type 0 by upper layer signaling, part of the downlink control information (DCI) for allocating PDSCH to the UE includes a bitmap including an NRBG bit. Its conditions will be described later. As used herein, NRBG refers to the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, as in Table 13 below, and data is transmitted in the RBG indicated by the bitmap as "1".

[0197] [Table 13]

[0198] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 2 27-72 4 8 73-144 8 16 145-275 16 16

[0199] In case 705 where the UE is configured to use only resource type 1 through upper layer signaling, the partial DCI includes frequency domain resource allocation information, which includes The conditions thereof will be described again later. The base station can thereby configure the starting VRB 720 and the length 725 of the frequency domain resources continuously allocated therefrom.

[0200] In the case 710 where the UE is configured to use both resource type 0 and resource type 1 by upper layer signaling, the partial DCI for allocating the PDSCH to the corresponding UE includes frequency domain resource allocation information, which includes as many bits as the payload 715 for configuring resource type 0 and the larger value 735 between the payloads 720 and 725 for configuring resource type 1. The conditions will be described again later. One bit may be added to the frontmost part (MSB) of the frequency domain resource allocation information inside the DCI. If the bit has a value of "0", the use of resource type 0 may be indicated, and if the bit has a value of "1", the use of resource type 1 may be indicated.

[0201] [PDSCH / PUSCH: About time resource allocation]

[0202] Hereinafter, a time domain resource allocation method for a data channel in a next-generation mobile communication system (5G or NR system) will be described.

[0203] The base station can configure a table of time domain resource allocation information about the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) for the UE through upper layer signaling (e.g., RRC signaling). A table including a maximum of maxNrofDL-Allocations=16 entries can be configured for PDSCH, and a table including a maximum of maxNrofUL-Allocations=16 entries can be configured for PUSCH. In an embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH time slot timing (e.g., the time slot unit time interval between the time point when the PDCCH is received and the time point when the PDSCH scheduled by the received PDCCH is sent; marked as K0), PDCCH-to-PUSCH time slot timing (e.g., the time slot unit time interval between the time point when the PDCCH is received and the time point when the PDSCH scheduled by the received PDCCH is sent; marked as K2 below), information about the position and length of the starting symbol by which the PDSCH or PUSCH is scheduled in the time slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as in Table 14 or Table 15 below may be sent from the base station to the UE.

[0204] [Table 14]

[0205]

[0206] [Table 15]

[0207]

[0208] The base station may inform the UF of one of the entries in the table about the time domain resource allocation information described above through L1 signaling (e.g., DCI) (e.g., the "time domain resource allocation" field in the DCI may indicate the same content). The UE may acquire the time domain resource allocation information about the PDSCH or PUSCH based on the DCI acquired from the base station.

[0209] Figure 8 An example of time domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0210] refer to Figure 8 The base station can use the subcarrier spacing (SCS) (μ PDSCH , μ PDCCH ), scheduling offset (K0) value, and the OFDM symbol starting position 800 and length 805 within a time slot dynamically indicated by DCI to indicate the time domain position of the PDSCH resource.

[0211] Fig. 9 An example of time domain resource allocation according to subcarrier spacing regarding a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0212] refer to Fig. 9 , if the data channel and the control channel have the same subcarrier spacing of 900 (μ PDSCH =μ PDCCH ), the time slot number for data and the time slot number for control are the same, and the base station and the UE can therefore generate a scheduling offset consistent with the predetermined time slot offset K0. On the other hand, if the data channel and the control channel have different subcarrier spacings 905 ( PDSCH ≠μ PDCCH ), the time slot number used for data and the time slot number used for control are different, and the base station and the UE can therefore refer to the subcarrier spacing of the PDCCH to generate a scheduling offset consistent with the predetermined time slot offset K0.

[0213] [PUSCH: About transmission scheme]

[0214] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmission can be dynamically scheduled by UL grant in DCI, or operate with the help of configured grant type 1 or type 2. Dynamic scheduling indication on PUSCH transmission can be made by DCI format 0_0 or 0_1.

[0215] The configured grant type 1 PUSCH transmission may be semi-statically configured by receiving a configuredGrantConfig including the rrc-ConfiguredUplinkGrant in Table 16 via upper layer signaling without receiving an UL grant within the DCI. After receiving a configuredGrantConfig not including the rrc-ConfiguredUplinkGrant in Table 16 via upper layer signaling, the configured grant type 2 PUSCH transmission may be semi-persistently scheduled by an UL grant within the DCI. If the PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied by configuredGrantConfig (upper layer signaling) in Table 16, in addition to the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config (upper layer signaling) in Table 17. If TransformMPrecoder is provided in configuredGrantConfig (upper layer signaling) in Table 16, the UE applies tp-pi2BPSK in pusch-Config in Table 17 to PUSCH transmissions operated by the configured grant.

[0216] [Table 16]

[0217]

[0218]

[0219]

[0220] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the value of txConfig in pusch-Config in Table 17 as upper layer signaling is "codebook" or "nonCodebook", PUSCH transmission can follow a codebook-based transmission method and a non-codebook-based transmission method.

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

[0222] [Table 17]

[0223]

[0224]

[0225] Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1 and can be operated semi-statically through a configured grant. If codebook-based PUSCH is dynamically scheduled through DCI format 0_1 ​​or semi-statically configured through a configured grant, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transmit precoding matrix indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

[0226] SRI can be indicated by an SRS resource indicator (field within DCI) or configured by srs-ResourceIndicator (upper layer signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured for it and can have up to two SRS resources configured for it. If the UE is provided with SRI through DCI, the SRS resource indicated by the corresponding SRI indicates the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the corresponding SRI. TPMI and transmission rank can be given by "precoding information and number of layers" (field within DCI) or configured by precodingAndNumberOfLayers (upper layer signaling). TPMI is used to indicate the precoder to be applied to PUSCH transmission. If one SRS resource is configured for the UE, TPMI is used to indicate the precoder to be applied in the configured SRS resource. If multiple SRS resources are configured for the UE, TPMI is used to indicate the precoder to be applied in the SRS resource indicated by SRI.

[0227] A precoder to be used for PUSCH transmission may be selected from an uplink codebook having the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config (upper layer signaling). In conjunction with codebook-based PUSCH transmission, the UE determines a codebook subset based on the codebook subset in pusch-Config (upper layer signaling) and the TPMI. Based on the UE capabilities reported by the UE to the base station, codebookSubset in pusch-Config (upper layer signaling) may be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "noncoherent". If the UE reports "partialAndNonCoherent" as the UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullyAndPartialAndNonCoherent". Additionally, if the UE reports "nonCoherent" as the UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If nrofSRS-Ports in SRS-ResourceSet (upper layer signaling) indicates two SRS antenna ports, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "partialAndNonCoherent".

[0228] The UE may have one SRS resource set configured for it, where the usage value in the SRS-ResourceSet (upper layer signaling) is "codebook", and one SRS resource may be indicated by the SRI in the corresponding SRS resource set. If multiple SRS resources are configured in an SRS resource set, where the usage value in the SRS-ResourceSet (upper layer signaling) is "codebook", the UE expects the value of nrofSRS-Ports in the SRS-Resource (upper layer signaling) to be the same for all SRS resources.

[0229] The UE sends one or more SRS resources included in the SRS resource set to the base station, wherein the usage value is configured as a "codebook" according to upper layer signaling, and the base station selects one from the SRS resources sent by the UE and instructs the UE to send PUSCH by using the transmit beam information of the corresponding SRS resource. In conjunction with the codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. In addition, the base station adds information indicating the rank and TPMI to be used by the UE for PUSCH transmission to the DCI. Using the SRS resource indicated by SRI, the UE applies the precoder indicated by the rank and TPMI indicated based on the transmit beam of the corresponding SRS resource when performing PUSCH transmission, thereby performing PUSCH transmission.

[0230] In the following, non-codebook based PUSCH transmission will be described. Non-codebook based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be operated semi-statically configured by the configured grant. If at least one SRS resource is configured in an SRS resource set, where the usage value in SRS-ResourceSet (upper layer signaling) is "nonCodebook", non-codebook based PUSCH transmission can be scheduled for the UE through DCI format 0_1.

[0231] Regarding SRS resource sets, where the usage value within the SRS-ResourceSet (upper layer signaling) is "nonCodebook", a connected NZP CSI-RS resource (non-zero power CSI-RS) can be configured for the UE. The UE can calculate the precoder for SRS transmission by measuring 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 in the UE is less than 42 symbols, the UE does not expect the information about the precoder used for SRS transmission to be updated.

[0232] If the configuration value of resourceType within SRS-ResourceSet (upper layer signaling) is "non-periodic", the connected NZP CSI-RS can be indicated by an SRS request as a field within DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated by the value of the SRS request (field within DCI format 0_1 ​​or 1_1) being not "00". The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of NZP CSI-RS, the NZP CSI-RS is located in the time slot used to send the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier is not configured as QCL-TypeD.

[0233] If there is a configured periodic or semi-persistent SRS resource set, the connected NZP CSI-RS can be indicated by the associatedCSI-RS in the SRS-ResourceSet (upper layer signaling). Regarding non-codebook based transmission, the UE does not expect spatialRelationInfo (which is upper layer signaling about SRS resources) and the associated CSI-RS in the SRS-ResourceSet (which is upper layer signaling) to be configured together.

[0234] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to the PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by the SRS resource indicator (field inside the DCI) or configured by the srs-ResourceIndicator (upper layer signaling). Similar to the codebook-based PUSCH transmission described above, if the UE is provided with SRI through DCI, the SRS resource indicated by the corresponding SRI indicates the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be sent simultaneously in the same symbol within an SRS resource set and the maximum number of SRS resources are determined by the UE capabilities reported by the UE to the base station. The SRS resources sent simultaneously by the UE occupy the same RB. The UE configures an SRS port for each SRS resource. There may be only one configured SRS resource set, where the usage value within the SRS-ResourceSet (upper layer signaling) is "nonCodebook", and a maximum of four SRS resources may be configured for non-codebook based PUSCH transmission.

[0235] The base station sends one NZP-CSI-RS connected to the SRS resource set to the UE, and the UE calculates the precoder to be used when sending one or more SRS resources within the corresponding SRS resource set based on the measurement result when the corresponding NZP-CSI-RS is received. When sending one or more SRS resources within the SRS resource set to the base station, the UE applies the calculated precoder, where the configured usage is "nonCodebook", and the base station selects one or more SRS resources from the received one or more SRS resources. In conjunction with non-codebook based PUSCH transmission, the SRI can indicate an index that can express one SRS resource or a combination of multiple SRS resources. The number of SRS resources indicated by the SRI sent by the base station can be the number of transmission layers of the PUSCH, and the UE sends the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0236] [About CA / DC]

[0237] Fig.10 The radio protocol structures of a base station and a UE in the case of a single cell, carrier aggregation, and dual connectivity according to an embodiment of the present disclosure are shown.

[0238] refer to Fig.10 The radio protocol of the next generation mobile communication system includes an NR service data adaptation protocol (SDAP) 1025 or 1070, an NR packet data convergence protocol (PDCP) 1030 or 1065, an NR radio link control (RLC) 1035 or 1060, and an NR medium access control (MAC) 1040 or 1055 on each of the UE and NR base station sides.

[0239] The main functions of NR SDAP 1025 or 1070 may include some of the following functions.

[0240] User plane data transmission

[0241] Mapping between QoS flows and DRBs for both DL and UL

[0242] Marking QoS Flow ID in both DL and UL packets

[0243] Reflective QoS Flow to DRB Mapping for UL SDAP PDU

[0244] The main functions of NR PDCP 1030 or 1065 may include some of the following functions:

[0245] Header compression and decompression: ROHC only

[0246] Transmission of user data

[0247] Sequential delivery of upper layer PDUs

[0248] Out-of-order delivery of upper layer PDUs

[0249] Reordering of PDCP PDUs for reception

[0250] Duplicate detection of lower layer SDUs

[0251] Retransmission of PDCP SDU

[0252] Encryption and Decryption

[0253] Timer-based SDU discard in uplink

[0254] The main functions of NR RLC 1035 or 1060 may include some of the following functions:

[0255] Transmission of upper layer PDU

[0256] Sequential delivery of upper layer PDUs

[0257] Out-of-order delivery of upper layer PDUs

[0258] Error correction via ARQ

[0259] Concatenation, segmentation, and reassembly of RLC SDUs

[0260] Re-segmentation of RLC data PDUs

[0261] Reordering of RLC data PDUs

[0262] Duplicate Detection

[0263] Protocol error detection

[0264] RLC SDU discarded

[0265] RLC re-establishment

[0266] NR MAC 1040 or 1055 can be connected to multiple NR RLC layer devices configured in one UE, and the main functions of NR MAC may include some of the following functions.

[0267] Mapping between logical channels and transport channels

[0268] MAC SDU multiplexing / demultiplexing

[0269] Dispatch Information Report

[0270] Error correction through HARQ

[0271] Priority handling between logical channels of a UE

[0272] Priority handling between UEs with dynamic scheduling

[0273] MBMS Service Identifier

[0274] Transmission format selection

[0275] filling

[0276] The NR PHY layer 1045 or 1050 may perform operations of channel coding and modulating the upper layer data to obtain OFDM symbols and deliver the OFDM symbols through a radio channel, or demodulate the OFDM symbols received through the radio channel, channel-decode the OFDM symbols, and deliver the OFDM symbols to the upper layer.

[0277] The detailed structure of the radio protocol structure may be changed differently depending on the carrier (or cell) operation scheme. As an example, assuming that the base station sends data to the UE based on a single carrier (or cell), the base station and the UE use a protocol structure having a single structure with respect to each layer, such as 1000. On the other hand, assuming that the base station sends data to the UE, based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, such as 1010. As another example, assuming that the base station sends data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the UE use a protocol structure having a single structure up to RLC but multiplexing the PHY layer through the MAC layer, such as 1020.

[0278] Hereinafter, embodiments of the present disclosure will be described in detail in conjunction with the accompanying drawings. The content of the present disclosure can be applied to FDD and TDD systems. As used herein, upper signaling (or "upper layer signaling") is a method for transmitting a signal from a base station to a UE by using a downlink data channel of a physical layer or transmitting a signal from a UE to a base station by using an uplink data channel of a physical layer, and may also be referred to as "RRC signaling", "PDCP signaling" or "MAC control element (MAC CE)".

[0279] Hereinafter, determining the priority between A and B may be variously described as, for example, selecting an entity with a higher priority and performing an operation corresponding thereto according to a predetermined priority rule, or omitting or discarding an operation on an entity with a lower priority.

[0280] Hereinafter, the above-mentioned examples may be described through a plurality of embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.

[0281] Hereinafter, embodiments of the present disclosure will be described in detail in conjunction with the accompanying drawings. In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the following description, embodiments of the present disclosure will be described in conjunction with a 5G system by way of example, but embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include LTE or LTE-A mobile communication systems and mobile communication technologies developed beyond 5G. Therefore, based on the determination made by those skilled in the art, embodiments of the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure. The contents of the present disclosure may be applied to FDD and TDD systems.

[0282] In addition, when describing the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, a detailed description of known functions or configurations incorporated herein will be omitted. The terms to be described below are defined in consideration of the functions in the present disclosure and may differ depending on the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content of the entire specification.

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

[0284] MIB

[0285] SIB or SIB X (X = 1, 2, ...)

[0286] RRC

[0287] MAC CE

[0288] In addition, L1 signaling may refer to signaling corresponding to at least one signaling method among signaling methods using the following physical layer channels or signaling, or a combination of one or more thereof.

[0289] PDCCH

[0290] DCI

[0291] UE-specific DCI

[0292] Group Common DCI

[0293] Public DCI

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

[0295] Non-scheduled DCI (e.g., DCI not used for the purpose of scheduling downlink or uplink data)

[0296] PUCCH

[0297] Uplink Control Information (UCI)

[0298] Hereinafter, determining the priority between A and B may be variously described as, for example, selecting an entity with a higher priority and performing an operation corresponding thereto according to a predetermined priority rule, or omitting or discarding an operation on an entity with a lower priority.

[0299] Hereinafter, the above-mentioned examples may be described through several embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.

[0300] [Related to single-cell multi-PDSCH / PUSCH scheduling]

[0301] A new scheduling method is introduced in Rel-17 NR of 3GPP. The new scheduling method is described below. The new scheduling method introduced in Rel-17 NR includes "multi-PDSCH scheduling" in which one DCI can schedule one or more PDSCHs, and "multi-PUSCH scheduling" in which one DCI can schedule one or more PUSCHs. In multiple PDSCHs or multiple PUSCHs, each PDSCH or each PUSCH delivers different transport blocks. By using multi-PDSCH scheduling and multi-PUSCH scheduling, the base station does not send multiple DCIs for scheduling multiple PDSCHs or multiple PUSCHs in the UE, respectively, so the overhead of the downlink control channel can be reduced. However, one DCI for multi-PDSCH scheduling and multi-PUSCH scheduling needs to include scheduling information for multiple PDSCHs or multiple PUSCHs, so the size of the DCI may increase. To this end, when multi-PDSCH scheduling and multi-PUSCH scheduling are configured for the UE, a method for preferably interpreting the DCI by the UE is required.

[0302] The present disclosure has described multiple PDSCH scheduling, but the concept of the technology proposed in the present disclosure can be used for multiple PUSCH scheduling.

[0303] The base station may configure multiple PDSCH scheduling for the UE. For example, the base station may explicitly configure multiple PDSCH scheduling for the UE by using a high-layer signal. Alternatively, the base station may implicitly configure multiple PDSCH scheduling for the UE by using a high-layer signal. For example, an explicit parameter (explicit indication) indicating multiple PDSCH scheduling may be sent from the base station to the UE via an RRC signal, or when multiple pieces of scheduling information are configured in a row of a TDRA table for a PDSCH configured by RRC signaling, the UE may understand that multiple PDSCH transmission has been implicitly configured.

[0304] The base station may configure the TDRA table for the UE for multi-PDSCH scheduling via a high-layer signal as follows. The TDRA table may include one or more rows. The number of rows may be configured to be up to a maximum value N row , and each row in the row corresponds to a unique index. The unique index can be 1, 2, ..., N row Here, N row It may preferably be 16. One or more pieces of scheduling information may be configured in each row. When one piece of scheduling information is configured in a row, the row schedules one PDSCH. That is, when a row is indicated, it may be understood that a single PDSCH scheduling has been indicated. When multiple pieces of scheduling information are configured in a row, the multiple pieces of scheduling information schedule multiple PDSCHs in sequence. That is, when a row is indicated, the UE may understand that multiple PDSCH scheduling has been indicated.

[0305] The scheduling information may be in the form of (K0, SLIV, and PDSCH mapping type). That is, when multi-PDSCH scheduling is indicated, a row may include multiple (K0, SLIV, and PDSCH mapping type). Among them, the Nth (K0, SLIV, and PDSCH mapping type) is the scheduling information of the Nth PDSCH. For reference, a row may include up to N pdsch (K0, SLIV, and PDSCH mapping type). Here, N pdsch It may preferably be 8 (N pdsch =8). That is, one row can schedule up to 8 PDSCHs.

[0306] Here, K0 indicates the time slot in which the PDSCH is scheduled, and represents the time slot difference (offset) between the time slot in which the PDCCH transmitting the DCI for scheduling the PDSCH is received and the time slot in which the PDSCH is scheduled. That is, if K0=0, the PDSCH and the PDCCH are located in the same time slot. The start and length indicator value (SLIV) indicates the index of the symbol in which the PDSCH starts within a time slot and the number of consecutive symbols to which the PDSCH is allocated. The PDSCH mapping type indicates information related to the position of the first DMRS (frontload DMRS) of the PDSCH. In the case of PDSCH mapping type A, the first DMRS (frontload DMRS) of the PDSCH is located in the third and fourth symbols of the time slot, and in the case of PDSCH mapping type B, the first DMRS (frontload DMRS) of the PDSCH is located in the first symbol among the symbols on which the PDSCH is scheduled.

[0307] Here, when the row of the TDRA table is configured in the high-level signal, part of (K0, SLIV, and PDSCH mapping type) in the scheduling information can be omitted. In this case, it can be interpreted as a default value. For example, when K0 is omitted, the value of K0 can be interpreted as 0. In addition, when the row of the TDRA table is configured, information other than (K0, SLIV, and PDSCH mapping type) can be additionally configured.

[0308] In the following description, it is assumed that multi-PDSCH scheduling is configured for the UE. Multi-PDSCH scheduling configuration may refer to the configuration of multiple pieces of scheduling information in at least one row of the TDRA table. For reference, one piece of scheduling information may be configured in another row of the TDRA table. Therefore, although multi-PDSCH scheduling is configured for the UE, the TDRA field depending on the received DCI may indicate single PDSCH scheduling to the UE or may indicate multi-PDSCH scheduling to the UE. In other words, the multi-PDSCH scheduling indication may be understood as a situation where the row of the TDRA table indicated by the DCI for the UE includes multiple pieces of scheduling information, and the single PDSCH scheduling indication may be understood as a situation where the row of the TDRA table indicated by the DCI for the UE includes one piece of scheduling information.

[0309] In the case of a single PDSCH scheduling indication, one PDSCH is scheduled, and the one PDSCH requires information such as a modulation and coding scheme (MCS), a new data indicator (NDI), a redundancy version (RV), and a HARQ process number (HPN). To this end, the DCI indicating the scheduling of a single PDSCH needs to include information such as MCS, NDI, RV, and HPN of one PDSCH. More specifically,

[0310] - A DCI indicating scheduling of a single PDSCH may include one MCS field. The MCS (ie, the modulation scheme and code rate of the channel code) indicated in the MCS field may be applied to one PDSCH scheduled by the DCI.

[0311] - The DCI indicating the scheduling of a single PDSCH may include a 1-bit NDI field. The UE may obtain the NDI value from the 1-bit NDI field and determine whether one PDSCH is to transmit a new transport block or to retransmit a previous transport block based on the NDI value.

[0312] - The DCI indicating scheduling of a single PDSCH may include a 2-bit RV field. The UE may obtain the RV value from the 2-bit RV field and determine the redundancy version of one PDSCH based on the RV value.

[0313] - A DCI indicating the scheduling of a single PDSCH may include one HPN field. One HPN field may be 4 bits. (For reference, when the UE supports up to 32 HARQ processes, the HPN field may be extended to 5 bits, but for ease of explanation of the present disclosure, it is assumed that the HPN field is 4 bits). One HARQ process ID may be indicated by one HPN field. One HARQ process ID may be the HARQ process ID of one scheduled PDSCH.

[0314] When multi-PDSCH scheduling is indicated, multiple PDSCHs are scheduled, and thus each PDSCH requires information such as MCS, NDI, RV, and HPN. To this end, the DCI indicating multi-PDSCH scheduling needs to include information such as MCS, NDI, RV, and HPN of each scheduled PDSCH. More specifically,

[0315] - A DCI indicating multi-PDSCH scheduling may include an MCS field. The MCS indicated in the MCS field (i.e., the modulation scheme and code rate of the channel code) may be equally applied to all PDSCHs scheduled by the DCI. That is, a DCI for scheduling multi-PDSCHs may not schedule different PDSCHs with different MCSs.

[0316] -The DCI indicating multi-PDSCH scheduling may include a K-bit NDI field. K may be the maximum value among the number of scheduling information included in each row of the TDRA table. For example, when the TDRA table includes two rows, the first row includes four pieces of scheduling information, and the second row includes 8 pieces of scheduling information, K may be 8 (K=8). The k-th bit of the K-bit NDI field may indicate the NDI value of the PDSCH corresponding to the k-th scheduling information. That is, the UE may obtain the NDI value for the k-th PDSCH from the k-th bit of the K-bit NDI field, and determine whether the k-th PDSCH sends a new transport block or retransmits a previous transport block based on the NDI value.

[0317] - The DCI indicating multi-PDSCH scheduling may include a K-bit RV field. The k-th bit of the K-bit RV field may indicate the RV value of the PDSCH corresponding to the k-th scheduling information. That is, the UE may obtain the RV value for the k-th PDSCH from the k-th bit of the K-bit RV field, and determine the redundancy version of the k-th PDSCH based on the RV value.

[0318] -DCI indicating multi-PDSCH scheduling may include one HPN field. One HPN field may be 4 bits. (For reference, when the UE supports up to 32 HARQ processes, the HPN field may be extended to 5 bits, but for ease of explanation of the present disclosure, it is assumed that the HPN field is 4 bits). One HARQ process ID may be indicated by one HPN field.

[0319] One HARQ process ID may be the HARQ process ID of the first PDSCH among the PDSCHs scheduled by the DCI indicating multi-PDSCH scheduling. The first PDSCH corresponds to the first scheduling information. Thereafter, the HPN of the PDSCH may be sequentially increased by 1. That is, in the case of the second PDSCH (corresponding to the second scheduling information), the HPN is a value obtained by increasing the HARQ process ID of the first PDSCH by 1. For reference, if the HARQ process ID exceeds the maximum number of HARQ process IDs (numOfHARQProcessID) configured for the UE, a modulo operation is performed. In other words, when the HARQ process ID indicated by the DCI is "x", the HARQ process ID of the kth PDSCH is determined as follows.

[0320] HPN of kth PDSCH=(x+k-1)modulo numOfHARQProcessID

[0321] As described above, when single PDSCH scheduling is indicated, the DCI includes a 1-bit NDI field or a 2-bit RV field, and when multi-PDSCH scheduling is indicated, the DCI includes a K-bit NDI field or a K-bit RV field. For reference, whether a single PDSCH scheduling indication is indicated or a multi-PDSCH scheduling indication is indicated depends on the indication in the TDRA field of the DCI (i.e., the number of scheduling information included in a row of the indicated TDRA field). Therefore, one DCI is required to support both single PDSCH scheduling and multi-PDSCH scheduling. If the length of the DCI for the single PDSCH scheduling indication and the length of the DCI for the multi-PDSCH scheduling indication are different from each other, "0" is added (filled) to the shorter length of the two DCIs so that the length of each DCI can be adjusted to be the same.

[0322] The DCI interpretation process of the UE is as follows. The UE receives the DCI, and in this case, it is assumed that the length of the DCI is equal to the longer DCI length between the length of the DCI for a single PDSCH scheduling indication and the length of the DCI for a multiple PDSCH scheduling indication. The UE can know the position of the TDRA field in the DCI. The position of the TDRA field can be the same in the DCI for a single PDSCH scheduling indication and the DCI for a multiple PDSCH scheduling indication. The UE can determine whether it is a DCI for a single PDSCH scheduling indication or a DCI for a multiple PDSCH scheduling indication through the TDRA field. That is, if the number of pieces of scheduling information included in a row of the indicated TDRA field is one, the UE can determine that it is a single PDSCH scheduling indication, and if the number of pieces of scheduling information included is two or more, it is determined that it is a multiple PDSCH scheduling indication.

[0323] If the UE determines that single PDSCH scheduling is indicated, the DCI can be interpreted based on the determination. That is, the NDI field can be interpreted as 1 bit and the RV field can be interpreted as 2 bits. If the UE determines that multiple PDSCH scheduling is indicated, the DCI can be interpreted based on the determination. That is, the NDI field can be interpreted as K bits and the RV field can be interpreted as K bits. For reference, the position of other fields within the DCI may vary depending on the length of the NDI field or the RV field. Therefore, depending on whether it is a single PDSCH scheduling indication or a multiple PDSCH scheduling indication, the bit length of the other fields is the same, but the position within the DCI may vary.

[0324] Fig.11 An example of a PDSCH scheduling scheme according to the above description is shown. The present disclosure assumes the following TDRA table.

[0325] -The first row (row 0) of the TDRA table includes four pieces of scheduling information (K0, SLIV, and PDSCH mapping type). Here, the first SLIV is referred to as SLIV 0 0 , the second SLIV is called SLIV 0 1 , the third SLIV is called SLIV 0 2 , and the fourth SLIV is called SLIV 0 3 Therefore, when the UE receives the indication of the first row (row 0) of the TDRA table, the UE can determine that multi-PDSCH scheduling is indicated.

[0326] -The second row (row 1) of the TDRA table includes two pieces of scheduling information (K0, SLIV, and PDSCH mapping type). Here, the first SLIV is referred to as SLIV 1 0 , and the second SLIV is called SLIV 1 1 Therefore, when the UE receives the indication of the second row (row 1) of the TDRA table, the UE can determine that multi-PDSCH scheduling is indicated.

[0327] The third row (row 2) of the TDRA table includes a piece of scheduling information (K0, SLIV, and PDSCH mapping type). Here, SLIV is referred to as SLIV 2 0 Therefore, when the UE receives the indication of the third row (row 2) of the TDRA table, the UE can determine that single PDSCH scheduling is indicated.

[0328] Fig.11 Case (a) 1150 shows a case where the UE has received an indication of the first row (row 0) of the TDRA table. In the DCI received by the UE on the PDCCH 1100, the TDRA field may receive an indication of the first row (row 0). Therefore, the UE may receive four PDSCHs based on the four pieces of scheduling information (K0, SLIV, and PDSCH mapping type) in the first row (row 0). The UE may receive four PDSCHs based on the SLIV as the first SLIV. 0 0 To determine the symbol for receiving the first PDSCH 1101, based on the SLIV as the second SLIV 0 1 To determine the symbol for receiving the second PDSCH 1102, based on the SLIV as the third SLIV 0 2 to determine the symbol for receiving the third PDSCH 1103, and based on the SLIV as the fourth SLIV0 3 To determine the symbol used to receive the fourth PDSCH1104.

[0329] Each of the four PDSCHs may have a unique HARQ process ID. That is, the first PDSCH may have a HPN 0 as the HARQ process ID, and the second PDSCH may have HPN 1 As the HARQ process ID, the third PDSCH may have HPN 2 as the HARQ process ID, and the fourth PDSCH may have HPN 3 As the HARQ process ID. Here, the HARQ process ID of the first PDSCH is indicated in the DCI. For example, the DCI may include HPN 0 =0 indicates the HARQ process ID of the first PDSCH. In this case, the HARQ process ID of the second PDSCH can be HPN 1 =1, the HARQ process ID of the third PDSCH can be HPN 1 =2, and the HARQ process ID of the fourth PDSCH may be HPN 1 =3.

[0330] Fig.11 Case (b) 1160 shows a case where the UE has received an indication of the second row (row 1) of the TDRA table. In the DCI received by the UE on the PDCCH 1110, the TDRA field may receive an indication of the second row (row 1). Therefore, the UE may receive two PDSCHs based on the two pieces of scheduling information (K0, SLIV, and PDSCH mapping type) in the second row (row 1). The UE may receive two PDSCHs based on the SLIV as the first SLIV. 1 0 to determine the symbol for receiving the first PDSCH 1111, and based on the SLIV as the second SLIV 1 1 To determine the symbol used to receive the second PDSCH 1112.

[0331] Each of the two PDSCHs may have a unique HARQ process ID. That is, the first PDSCH may have a HPN 0 as the HARQ process ID, and the second PDSCH may have HPN 1 As the HARQ process ID. Here, the DCI indicates the HARQ process ID of the first PDSCH. For example, the DCI may include HPN 0=0 indicates the HARQ process ID of the first PDSCH. In this case, the HARQ process ID of the second PDSCH can be HPN 1 =1.

[0332] Fig.11 Case (c) 1170 shows a case where the UE has received an indication of the third row (row 2) of the TDRA table. In the DCI received by the UE on the PDCCH 1120, the TDRA field may receive an indication of the third row (row 2). Therefore, the UE may receive a PDSCH based on a piece of scheduling information (K0, SLIV, and PDSCH mapping type) in the third row (row 2). The SLIV may be used as a SLIV. 2 0 To determine the symbol used to receive a PDSCH 1121. The HARQ process ID of a PDSCH is indicated in the DCI, that is, HPN 0 For example, DCI can use HPN 0 =0 indicates the HARQ process ID of the first PDSCH.

[0333] Fig.12 An example of the structure of DCI for single PDSCH scheduling and multi-PDSCH scheduling is shown.

[0334] refer to Fig.12 In cases (a) and (b), the UE can determine the position of the TDRA field 1200 in the received DCI. The position of the TDRA field is the same for single PDSCH scheduled DCI and multi-PDSCH scheduled DCI. According to the value of the TDRA field, the UE can determine whether the received DCI indicates a single PDSCH scheduled DCI or a multi-PDSCH scheduled DCI.

[0335] If the row corresponding to the value of the TDRA field of the received DCI includes a piece of scheduling information (K0, SLIV, and PDSCH mapping type) (e.g., the third row (row 2) of the TDRA table), the UE interprets the DCI as a single PDSCH scheduling DCI, as shown in case (a). Referring to case (a), the single PDSCH scheduling DCI may include a 5-bit MCS field 1205, a 1-bit NDI field 1210, a 2-bit RV field 1215, and a 4-bit HARQ field 1220. In addition, the single PDSCH scheduling DCI may include fields other than the fields described above. For example, the single PDSCH scheduling DCI may include an antenna port (or multiple) field 1225 to a DMRS sequence initialization field 1230. In addition, if the single PDSCH scheduling DCI is shorter than the multi-PDSCH scheduling DCI, the single PDSCH scheduling DCI may include padding bits 1235.

[0336] If the row corresponding to the value of the TDRA field of the received DCI includes two pieces of scheduling information (K0, SLIV, and PDSCH mapping type) (for example, the first row (row 0) or the second row (row 1) of the TDRA table), the UE interprets the DCI as a multi-PDSCH scheduling DCI, as shown in case (b). Referring to case (b), the multi-PDSCH scheduling DCI may include a 5-bit MCS field 1255, K-bit NDI fields 1260 and 1261, K-bit RV fields 1262 and 1263, and a 4-bit HARQ field 1270. In addition, the multi-PDSCH scheduling DCI may include fields other than the fields described above. For example, the multi-PDSCH scheduling DCI may include an antenna port (or multiple) field 1275 to a DMRS sequence initialization field 1280. For reference, case (b) shows a DCI by which up to two PDSCHs are scheduled. The 2-bit NDI fields 1260 and 1261 are shown separately, but may be attached as one 2-bit. In addition, in case (b), the 2-bit RV fields 1262 and 1263 are shown separately, but may be attached as one 2-bit.

[0337] For reference, referring to cases (a) and (b), by assuming that the length of the DCI indicating single PDSCH scheduling is shorter than the length of the DCI indicating multiple PDSCH scheduling, padding bits 1235 have been added to the single PDSCH scheduling DCI. If the length of the DCI indicating single PDSCH scheduling is longer than the length of the DCI indicating multiple PDSCH scheduling, padding bits may be added to the DCI indicating multiple PDSCH scheduling.

[0338] Hereinafter, unless otherwise stated, the present disclosure assumes that the PDSCH transmits a single codeword.If two codeword transmissions are configured for a UE, then unless otherwise stated, the fields of the DCI are for the first codeword.

[0339] [Related to multi-cell multi-PDSCH / PUSCH scheduling]

[0340] In Rel-18, multi-cell multi-PDSCH scheduling in which one DCI schedules PDSCH for each of multiple cells and multi-cell multi-PUSCH scheduling in which one DCI schedules PUSCH for each of multiple cells are being discussed. Here, one DCI can schedule only one PDSCH or one PUSCH for one cell. That is, in the case of multi-cell multi-PDSCH scheduling, when scheduling PDSCH for multiple cells, only up to one PDSCH can be scheduled for each cell. In the case of multi-cell multi-PUSCH scheduling, when scheduling PUSCH for multiple cells, only up to one PUSCH can be scheduled for each cell.

[0341] The present disclosure proposes a DCI format indicated by a base station to a UE and an operation of the UE according to the DCI format. Here, the DCI format may be a DCI format indicating multi-cell multi-PDSCH scheduling or a DCI format indicating multi-cell multi-PUSCH scheduling. In the following, multi-cell multi-PDSCH scheduling may be used interchangeably with multi-cell PDSCH scheduling, and multi-cell multi-PUSCH scheduling may be interchangeable with multi-cell PUSCH scheduling.

[0342] <First Embodiment: Method for Configuring TDRA Information>

[0343] In the first embodiment of the present disclosure, the UE may receive an indication of multi-cell scheduling according to the TDRA table in the DCI format and the indicated TDRA. For multi-cell multi-PDSCH scheduling or multi-cell multi-PUSCH scheduling, the base station may configure the TDRA table for the UE through a high-level signal as follows. The TDRA table may include one or more rows. The number of rows may be configured to be up to a maximum value N row , and each row in the row may correspond to a unique index. The TDRA information for multi-cell multi-PDSCH scheduling may include scheduling information (K0, SLIV, and PDSCH mapping type). The TDRA information for multi-cell multi-PUSCH scheduling may include scheduling information (K0, SLIV, and PUSCH mapping type).

[0344] In the multi-cell multi-PDSCH scheduling described in this embodiment, the TDRA table row information may also include an index of a cell in which the PDSCH is scheduled according to each piece of scheduling information and / or a BWP index within the cell.

[0345] The multi-cell multi-PUSCH scheduling described in this embodiment may include an index of a cell in which a PUSCH according to each piece of scheduling information is scheduled in the TDRA table row information, and if a normal UL (NUL) carrier and a supplementary UL (SUL) carrier are configured in the cell, an index indicating the UL carrier and a BWP index on the UL carrier are included. For reference, if the SUL is not configured in the cell, the index indicating the UL carrier may not be included, and the PUSCH may be scheduled on one UL carrier in the cell.

[0346] In addition, although an example has been described above in which each piece of scheduling information of the TDRA table includes an index of a cell in which the PDSCH is scheduled and / or a BWP index within the cell, the index of the cell in which the PDSCH corresponding to each piece of scheduling information is scheduled and / or the BWP index within the cell can be configured as separate information.

[0347] Here, the cell index may be a unique value for each cell supporting multi-cell transmission. In addition, the BWP index may be a unique value for the BWP supported by each cell. If the index indicating the UL carrier may be 0 to 1, if the index is 0, NUL may be indicated, and if the index is 1, SUL may be indicated.

[0348] Fig.13 An example of scheduling according to the above described scheduling scheme is shown. The present disclosure assumes the following TDRA table.

[0349] -The row (row 0) of the TDRA table includes scheduling information (cell index, K0, SLIV, PDSCH mapping type, and BWP index) for three cells. Here, the first cell index is referred to as cell #0, the second cell index is referred to as cell #1, and the third cell index is referred to as cell #2. Therefore, when the UE receives an indication of the row (row 0) of the TDRA table, the UE can determine that multi-PDSCH scheduling is indicated.

[0350] Fig.13 An example of a case where the UE has received an indication of the first row (row 0) of the TDRA table is shown. In the DCI received by the UE on the PDCCH 1300, the TDRA field may indicate the first row (row 0). Therefore, the UE may receive PDSCHs from three cells based on the three pieces of scheduling information (cell index, K0, SLIV, PDSCH mapping type, and BWP index) in the first row (row 0). The UE may determine a cell for receiving the first PDSCH 1301 based on cell #0 as the first cell index, determine a cell for receiving the second PDSCH 1311 based on cell #1 as the second cell index, and determine a cell for receiving the third PDSCH 1321 based on the third cell index.

[0351] In the TDRA table of high-level configuration information configured by the base station for the UE, downlink control information configuration and indication method may be required to schedule multi-cell operation. Therefore, the following method describes in detail the method for configuring TDRA indication information in downlink control information.

[0352] [Method 1-1. Method of including multiple pieces of information in one TDRA line]

[0353] The base station may configure one TDRA row to include multiple pieces of cell information so as to support a multi-cell multi-PDSCH reception operation or a multi-cell multi-PUSCH transmission operation for the UE.

[0354] The base station can indicate the cell information to be scheduled to the UE through the downlink control information TDRA. Therefore, one TDRA line in the downlink control information can include scheduling information (cell index, K0, SLIV, mapping type, and BWP index) for multiple cells.

[0355] For example, for multi-cell multi-PDSCH scheduling, the base station can configure PDSCH scheduling for N different cells for the UE in one TDRA row and indicate the row through the TDRA field in the downlink control information. In this case, one row in TDRA can include N pieces of scheduling information (cell index, K0, SLIV, mapping type, and BWP index). In this case, the cell indexes in the N pieces of scheduling information in one row can be different from each other.

[0356] The base station may indicate different K0 values ​​to prevent collision during multi-cell PDSCH reception.

[0357] For another example, for multi-cell multi-PUSCH scheduling, the base station can configure PUSCH scheduling for N different cells for the UE in one TDRA row and indicate the row through the TDRA field in the downlink control information. In this case, a row in TDRA can include N pieces of scheduling information (cell index, NUL / SUL index, K2, SLIV, mapping type, and BWP index). In this case, the cell indexes in the N pieces of scheduling information in a row can be different from each other.

[0358] The base station may indicate different K2 values ​​to prevent collision of multi-cell PUSCH transmission. In addition, the base station may perform indication through a corresponding index to inform the UE whether the corresponding uplink transmission uses a normal UL carrier or a supplementary UL carrier.

[0359] As an example of the present disclosure, among the TDRA rows configured by the UE, a specific row includes multiple pieces of scheduling information, but another specific row may include one piece of scheduling information. Therefore, the UE may determine whether it is single scheduling or multi-cell scheduling depending on the TDRA row indicated by the TDRA field of the DCI format.

[0360] As an example of the present disclosure, when a specific row among the TDRA rows configured by the UE includes multiple pieces of scheduling information, the number of pieces of scheduling information included in the first specific row and the number of pieces of scheduling information included in the second specific row may be equal to or different from each other. That is, each TDRA row may include a different number of pieces of scheduling information.

[0361] As an example of the present disclosure, N scheduling information in a row configured by a UE can be interpreted as follows. First, assume that the UE has received two pieces of scheduling information. Here, two pieces of scheduling information are used for description, but this can be extended to any number of pieces of scheduling information.

[0362] The first scheduling information is referred to as (first cell index, first K0, first SLIV, first mapping type, and first BWP index), and the second scheduling information is referred to as (second cell index, second K0, second SLIV, second mapping type, and second BWP index). Here, the scheduling information can be sorted in ascending order of the cell index. That is, the first cell index can always be less than the second cell index. This is because, as mentioned above, only one PDSCH can be scheduled in a cell.

[0363] In addition, the cell index can be configured by using the offset (difference) value from the cell index of the previous scheduling information. For example, assume that the PDSCH according to the first scheduling information is scheduled in a cell with index c, and the PDSCH according to the second scheduling information is scheduled in a cell with index d. Here, c < d. In this case, the value corresponding to d - c instead of d in which the PDSCH according to the second scheduling information is scheduled can be configured as the second cell index of the second scheduling information. In this case, the overhead of configuring each scheduling information in the TDRA table can be reduced.

[0364] As an example of the present disclosure, the BWP index can be omitted. In this case, the PDSCH or PUSCH can be sent in the active BWP. The active BWP can refer to the BWP that is active at the time point when the DCI for scheduling multi-cell multi-PDSCH is received or at the time point when the DCI for scheduling multi-cell multi-PUSCH is received. Therefore, the multi-cell multi-PDSCH scheduling and the multi-cell multi-PUSCH scheduling may not indicate a BWP change.

[0365] If the DCI for scheduling multi-cell multi-PDSCH (or PUSCH) is received and indicates data transmission and reception in a BWP other than the BWP that is active at the time point when the DCI is received, the UE can understand that a BWP change is indicated. In this case, data scheduling can be performed in consideration of the delay time required for changing the BWP as described above.

[0366] [Method 1-2. Method of including single cell information in one TDRA row]

[0367] The base station can include different cell information in each TDRA row to support the multi-cell PDSCH or multi-cell PUSCH transmission operation for the UE.

[0368] Different from method 1-1, in the case where multiple cell scheduling information is included in one TDRA line, the base station can be configured to include scheduling information (cell index, K0, SLIV, mapping type, and BWP index) of one cell in one TDRA line. That is, if the base station can configure a UE with up to a maximum value N row TDRA table, multiple cells can also be configured with up to a maximum value N row In this case, since one TDRA includes information about only one cell, the UE may not need to determine whether it is single-cell scheduling or multi-cell scheduling.

[0369] For example, for multi-cell PDSCH scheduling, the base station may indicate the scheduling of one cell for one TDRA row to the UE through the TDRA field in the downlink control information.

[0370] For another example, for multi-cell PUSCH scheduling, the base station may indicate scheduling of one cell for one TDRA row to the UE through the TDRA field in the downlink control information.

[0371] [Method 2. Method by which UE determines whether it is multi-cell scheduling]

[0372] The UE may determine whether it is multi-cell scheduling through a multi-cell scheduling index in a DCI format indicated by the base station.

[0373] The multi-cell scheduling index may be included in the DCI format. If a row of TDRA scheduled by the base station includes multiple cell scheduling information, the multi-cell scheduling index may be configured as "1". If a row of TDRA scheduled by the base station does not include multiple cell scheduling information, the multi-cell scheduling index may be configured as "0".

[0374] For example, when interpreting the TDRA field transmitted from the base station, the UE can determine whether it is multi-cell scheduling through the multi-cell scheduling index.

[0375] In this case, depending on method 2-1-1 and method 2-1-2, the position of the multi-cell scheduling index may also be changed.

[0376] [Method 2-1-1. Method of indicating a multi-cell scheduling index for each TDRA row]

[0377] In order to inform the UE whether it is multi-cell scheduling, the base station may include a multi-cell scheduling index corresponding to each TDRA row (configured through RRC signaling) in the DCI format.

[0378] According to the above method 1-1, the base station can include multiple cell scheduling information in one TDRA row. Therefore, the base station can notify the UE whether it is multi-cell scheduling by including a multi-cell scheduling index corresponding to each row of TDRA in the DCI format. When performing DCI reception and TDRA analysis, the UE can determine whether it is multi-cell scheduling in each TDRA row by the multi-cell scheduling index. If the multi-cell scheduling index is indicated as "1", the UE can determine that the corresponding TDRA row is a row indicating multi-cell scheduling. On the contrary, if the multi-cell scheduling index is indicated as "0", the UE can determine that the corresponding TDRA row indicates single-cell scheduling.

[0379] Fig.14 An example of the multi-cell scheduling index application method described above is shown. The multi-cell scheduling index 1400 may be located before the TDRA field 1405. If the multi-cell scheduling index is indicated as "1" when the UE receives the DCI, the UE may determine that the row corresponding to the TDRA field is a TDRA row including multi-cell scheduling information. If the multi-cell scheduling index is indicated as "0" when the UE receives the DCI, the UE may determine that the row corresponding to the TDRA field is a TDRA row that does not include multi-cell scheduling information, that is, a TDRA row including single-cell scheduling information.

[0380] [Method 2-1-2. Method of indicating a multi-cell scheduling index at the beginning of TDRA information]

[0381] The base station may include a multi-cell scheduling index in the DCI format to inform the UE whether it is multi-cell scheduling.

[0382] According to the above method 1-2, the base station can include single-cell scheduling information in each TDRA row. Therefore, the base station can notify the UE that the corresponding DCI format schedules multiple cells by including a multi-cell scheduling index in the DCI format. When performing DCI reception and TDRA analysis, the UE can determine whether it is multi-cell scheduling by the multi-cell scheduling index. If the multi-cell scheduling index is indicated as "1", the UE can determine that the corresponding DCI format includes multiple cell scheduling. On the contrary, if the multi-cell scheduling index is indicated as "0", the UE can determine that the corresponding DCI format does not indicate multi-cell scheduling.

[0383] Fig.15An example of the multi-cell scheduling index application method described above is shown. The multi-cell scheduling index 1500 may be located before the MSB of TDRA1505. If the multi-cell scheduling index is indicated as "1" when the UE receives the DCI, the UE may determine that each row of the indicated TDRA field includes multi-cell scheduling information. If the multi-cell scheduling index is indicated as "0" when the UE receives the DCI, the UE may determine that each row of the indicated TDRA field is a TDRA row that does not include multi-cell scheduling information, i.e., a TDRA row that includes single-cell scheduling information.

[0384] [Method 3. Method for configuring DCI format information]

[0385] [Method 3-1. Method for configuring each field for scheduling multi-cell multi-PDSCH and multi-cell multi-PUSCH]

[0386] The base station may configure a downlink control information bit field for each piece of configuration information to schedule multi-cell multi-PDSCH or multi-cell multi-PUSCH to the UE. For example, the DCI configuration information may include a bit field for multi-cell multi-PDSCH and a separate field for multi-cell multi-PUSCH. If the base station expects to schedule multi-cell multi-PDSCH to the UE, the base station may send a DCI including configuration information for multi-cell multi-PDSCH scheduling to the UE. In this case, the bit field for multi-cell multi-PUSCH may be filled with zeros.

[0387] For example, it is assumed that K pieces of scheduling information are included in a row indicated by a TDRA field included in a DCI format received by a UE. Here, K is equal to the number of indices of cells to be scheduled. In this case, at least K of the following DCI fields may be included in the DCI format, and the DCI fields may correspond to each piece of scheduling information, respectively.

[0388] Here, the correspondence between the K DCI fields and the K pieces of scheduling information may be determined according to the ascending order of the indexes of the cells included in the scheduling information. That is, the first of the K DCI fields may correspond to the scheduling information of the lowest cell index.

[0389] When the DCI format schedules PUSCH, at least one of the following DCI fields may be included in K DCI formats. (That is, taking the FDRA field as an example, K FDRA fields such as the first FDRA field, the second FDRA field, ..., the Kth FDRA field may be included)

[0390] - Frequency Domain Resource Allocation (FDRA) field

[0391] -TPC command field for scheduled PUSCH

[0392] -Open loop power control parameter set indicator field

[0393] - Precoding information and layer number field

[0394] - Antenna Port field

[0395] -PTRS-DMRS association field

[0396] - New Data Indicator (NDI) field

[0397] - Redundancy Version (RV) field

[0398] - Invalid symbol pattern field

[0399] When the DCI format schedules PDSCH, at least one of the following DCI fields may be included in K DCI formats. (That is, taking the FDRA field as an example, K FDRA fields such as the first FDRA field, the second FDRA field, ..., the Kth FDRA field may be included)

[0400] - Frequency Domain Resource Allocation (FDRA) field

[0401] -Rate Match Indicator

[0402] -Transmission configuration instructions

[0403] - Antenna Port field

[0404] - New Data Indicator (NDI) field

[0405] - Redundancy Version (RV) field

[0406] For reference, here it is represented as K DCI fields, but this can be defined as K subfields within one DCI field.

[0407] Fig.16 An example of a DCI format for the multi-cell multi-PDSCH described above is shown.

[0408] according to Fig.16 In case (a) 1650, the base station can perform multiple cell scheduling through a single DCI.

[0409] As an example, as described above, the DCI field may include K subfields. If a single DCI schedules PDSCH transmission in two cells for a UE, the DCI format may be configured as a DCI field for cell index #0 1610 and a DCI field for cell index #1 1615. Each DCI field may include the above-mentioned control information. For example, the DCI field for cell index #0 1610 may include fields such as an FDRA field 1603, an NDI field 1604, an RV field 1605, an HPN field 1606, and one or more antenna port fields 160. Such a format may be equally applied to a DCI configuration for multi-cell multi-PUSCH scheduling.

[0410] As another example, as in case (b) 1660, the DCI may be configured such that the same scheduling information field is continuous. For example, if a single DCI schedules PDSCH transmission in two cells for a UE, the FDRA field may be configured as FDRA for PDSCH 1613 of cell #1 and FDRA for PDSCH 1623 of cell #2. Each DCI field may include the above control information in a format such as case (b) 1660. Such a format may be equally applied to DCI configuration for multi-cell multi-PUSCH scheduling.

[0411] refer to Fig.16 If the UE determines multi-cell scheduling after receiving DCI from the base station, the UE may Fig.13 Operate as described in .

[0412] For example, it is assumed that K pieces of scheduling information are included in the TDRA row included in the DCI format received by the UE. Here, K is equal to the number of indices of cells to be scheduled. In this case, when a certain condition is met, for example, two following DCI fields may be included in the DCI format, the first DCI field may correspond to the PUCCH corresponding to the first scheduling information, and the second DCI field may correspond to the PUCCH corresponding to the second scheduling information.

[0413] More specifically, the UE can receive the configuration of up to two PUCCH groups. Each PUCCH group may include an index of at least one downlink cell. One downlink cell index may correspond to one PUCCH group. When the UE receives a PDSCH in a specific downlink cell, HARQ-ACK information for the PDSCH may be sent on the PUCCH in the uplink cell defined in the PUCCH group including the downlink cell. For reference, the uplink cell defined in the PUCCH group may be referred to as a Pcell or a PUCCH cell. That is, HARQ-ACK information about a PDSCH scheduled in a downlink cell included in the PUCCH group may be sent in an uplink cell defined in the PUCCH group. Such a downlink cell set may be referred to as a cell group.

[0414] If the TDRA row indicated by the DCI format received by the UE schedules only PDSCH in downlink cells within one PUCCH group, then one subsequent DCI field related to HARQ-ACK transmission and PUCCH transmission may be sufficient.

[0415] -TPC command for the scheduled PUCCH

[0416] -PUCCH resource indicator

[0417] -PDSCH-to-HARQ_feedback timing indicator

[0418] -PDSCH group index

[0419] - New feedback indicator

[0420] - Number of PDSCH groups (or groups) requested

[0421] -HARQ-ACK retransmission indicator

[0422] -PUCCH cell indicator

[0423] When the TDRA row indicated by the DCI format received by the UE schedules the PDSCH in the downlink cell within two PUCCH groups, in the DCI format, at least one of the following DCI fields related to HARQ-ACK transmission and PUCCH transmission may include a first DCI field and a second DCI field. (Alternatively, the DCI field may also be included in the form of a first sub-DCI field and a second sub-DCI field)

[0424] - A first TPC command field for the scheduled PUCCH, and a second TPC command field for the scheduled PUCCH

[0425] -First PUCCH resource indicator field, and second PUCCH resource indicator field

[0426] - A first PDSCH-to-HARQ_feedback timing indicator field and a second PDSCH-to-HARQ_feedback timing indicator field

[0427] -First PDSCH group index field and second PDSCH group index field

[0428] - First New Feedback Indicator Field, and Second New Feedback Indicator Field

[0429] - A first number of requested PDSCH groups (or groups) field, and a second number of requested PDSCH groups (or groups) field

[0430] -First HARQ-ACK retransmission indicator field, and second HARQ-ACK retransmission indicator field

[0431] -First PUCCH cell indicator field, and second PUCCH cell indicator field

[0432] Here, the two DCI fields may be applied to two PUCCH groups, respectively. The first DCI field may be applied to the first PUCCH group, and the second DCI field may be applied to the second PUCCH group. Here, the first PUCCH group may be a PUCCH group that transmits PUCCH in the Pcell.

[0433] Fig.17 An example of a DCI format for a PUCCH group of multi-cell multi-PDSCH is shown.

[0434] according to Fig.17 In case (a) 1750, the base station can perform scheduling for multiple cell groups through a single DCI.

[0435] As an example, as described above, the DCI field may include subfields. If a single DCI schedules PDSCH transmission in two cell groups for a UE, the DCI format may be configured as a DCI field for cell index #0 1710 and a DCI field for cell index #1 1715. For example, the DCI field for cell index #0 1710 may include an FDRA field 1703, an NDI field 1704, an RV field 1705, an HPN field 1706, and an antenna port (or multiple) field 1707, etc. Such a format may be equally applied to a DCI configuration for multi-cell multi-PUSCH scheduling.

[0436] As another example, as in case (b) 1760, the DCI may be configured such that the same scheduling information field is continuous. For example, if a single DCI schedules PDSCH transmission in two cells for a UE, the FDRA field may be configured as FDRA for the PDSCH of cell group #1 1713 and FDRA for the PDSCH of cell group #2 1723. Each DCI field may include the above-mentioned control information in a format such as case (b) 1760. Such a format may be equally applied to DCI configuration for multi-cell multi-PUSCH scheduling.

[0437] Fig.18 An example of HARQ-ACK operation according to the above-described PUCCH group is shown.

[0438] The base station may pre-configure PUCCH cell groups #0 1840 and #1 1845 for the UE. When the UE receives PDCCH 1800 in a downlink cell, HARQ-ACK information of a PDSCH scheduled by the PDCCH may be transmitted on a PUCCH in an uplink cell defined in the PUCCH group including the downlink cell on which the PDSCH is transmitted.

[0439] For example, if PUCCH cell group #0 1840 is configured for the first cell and the UE is instructed to receive PDSCH #1 1801 in the first cell, HARQ-ACK related thereto may be performed on the PUCCH for cell group #0 1830 configured in PUCCH cell group #0 1840 .

[0440] For another example, if PUCCH cell group #1 1845 is configured for the second cell and the UE is instructed to receive PDSCH #2 1811 in the second cell, HARQ-ACK related thereto may be performed on the PUCCH for cell group #1 1835 configured in PUCCH cell group #1 1845 .

[0441] For another example, if PUCCH cell group #1 1845 is configured for the third cell and the UE is instructed to receive PDSCH #3 1821, HARQ-ACK related thereto may be performed on the PUCCH for cell group #1 1835 configured in PUCCH cell group #1 1845.

[0442] [Method 3-2. Method of sharing a bit field for multi-cell PDSCH scheduling and multi-cell PUSCH scheduling]

[0443] The base station may share the bit field within the same DCI to schedule multi-cell PDSCH or multi-cell PUSCH to the UE. For example, if the bit field of the multi-cell PDSCH scheduling information is N bits and the bit field of the multi-cell PUSCH scheduling information is K bits, the scheduling may be performed with reference to the larger bit field between the N bits and the K bits. If the N bits of the multi-cell PDSCH scheduling information are greater than the K bits of the multi-cell PUSCH scheduling information, the bit field of the multi-cell scheduling information may be configured with reference to the N bits in the DCI. If the base station schedules a multi-cell PDSCH to the UE, the DCI information may configure the scheduling information by using N bits. On the other hand, if the base station schedules a multi-cell PUSCH to the UE, K bits of scheduling information are configured and zero padding corresponding to the remaining NK bits may be included in the DCI information. On the contrary, if the number of bits of the multi-cell PUSCH scheduling information is greater than the number of bits of the multi-cell PDSCH scheduling information, N bits of scheduling information are configured and zero padding corresponding to KN bits may be included in the multi-cell PDSCH scheduling information. K bits of scheduling information may be configured in the multi-cell PUSCH scheduling information.

[0444] <Second embodiment: Method for indicating multi-cell scheduling by using bitmap information in DCI>

[0445] The base station can indicate to the UE whether multi-cell scheduling is performed through bitmap information in the DCI format.

[0446] For multi-cell PDSCH scheduling or multi-cell PUSCH scheduling, the base station can configure the TDRA table for the UE through a high-layer signal. The base station can include a bitmap in the DCI format to indicate multi-cell PDSCH reception or multi-cell PUSCH transmission to each UE. Each bit of the bitmap can correspond to a cell index information or a cell group index obtained by grouping multiple cells.

[0447] For example, for multi-cell multi-PDSCH scheduling or multi-cell multi-PUSCH scheduling, the base station can configure the TDRA table for the UE through a high-level signal. The TDRA table may include one or more rows. The UE may receive an indication of a TDRA row from the base station through the TDRA field included in the DCI. If multiple cell scheduling information is included in the indicated TDRA row, the base station may indicate a cell index (or cell group index) through the bitmap information in the DCI format to indicate one or more cells through which PDSCH reception or PUSCH transmission is to be performed.

[0448] For example, when the nth bit of the bitmap is indicated as 1, the UE can receive the PDSCH or send the PUSCH through the nth cell. In this case, the number of bits indicated as 1 in the bitmap may be one or more. Therefore, the UE can determine the cell through which the PDSCH is to be received or through which the PUSCH is to be sent according to the bitmap indicated by the base station.

[0449] Fig.19 An example of a multi-cell scheduling indication method using the bitmap described above is shown.

[0450] Fig.19 Case (a) 1950 shows a method of indicating a cell index by a bitmap. In the DCI format, the bitmap 1902 for cell index indication can be configured as up to 0, ..N row -1(or 0,...,N cell -1, where N cell is the number of cells configured for the UE), the cell through which the PDSCH is to be received or through which the PUSCH is to be sent can be determined based on the bit indicated as 1. For example, the base station can configure scheduling information of three cells in TDRA row #0 for the UE. In order to indicate multi-cell scheduling to the UE, when TDRA row #0 is indicated in the TDRA field of the DCI, the base station can indicate the index of the cell to be scheduled through a bitmap in the DCI. In this case, for example, three bits of the bitmap within the DCI can be configured as 1, and in this case, the cell indicated by each bit can correspond to each scheduling information in TDRA row #0.

[0451] Fig.19 Case (b) 1960 shows a method of indicating a cell group index by a bitmap. In the DCI format, the bitmap 1912 for cell group index indication can be configured as up to 0, ... N row -1(or 0,...,N cell group -1, where N cell group is the number of cell groups configured for the UE), the cell group through which the PDSCH is to be received or the PUSCH is to be sent can be determined based on the number of bits indicated as 1. For example, the base station can configure the configuration information of two cell groups in TDRA row #0 for the UE. In order to indicate multi-cell scheduling to the UE, when TDRA row #0 is indicated in the TDRA field of the DCI, the base station can indicate the index of the cell group to be scheduled through a bitmap in the DCI. In this case, for example, the cells in the cell group indicated by the bitmap in the DCI can respectively correspond to the individual pieces of scheduling information in TDRA row #0, or the cell groups can respectively correspond to the individual pieces of scheduling information in TDRA row #0.

[0452] <Third embodiment: multi-cell scheduling method using FDRA field information>

[0453] In an embodiment, a method of scheduling multiple cells through a frequency resource configuration information (FDRA) field in a DCI format is described.

[0454] The base station can configure the FDRA type for the UE through high-level configuration information. In this case, the base station can configure the FDRA type for each cell for multi-cell scheduling. The difference from the multi-cell scheduling based on TDRA described above is that the cells to be scheduled are distinguished by frequency resource configuration. In addition, in order to prevent operational ambiguity such as conflicts between cells in the time domain when only FDRA is used, multi-cell scheduling can be performed by combination with other configuration information. The detailed method will be described below.

[0455] [Method 4-1. Method for configuring FDRA for each cell]

[0456] The base station may configure the FDRA field corresponding to each cell for the UE for multi-cell scheduling.

[0457] When the number of cells configurable for a UE is up to N, the number of configurable FDRA fields may also be up to N. In this case, the FDRA field may be type 0 or type 1 frequency resource configuration information depending on the configuration of the base station.

[0458] In addition, in order to enable the UE to know which cell the FDRA field indicated by the base station corresponds to, the cell index included in the DCI format may be located at the very beginning (MSB) of each FDRA bit field.

[0459] For example, cell index #0 may correspond to FDRA#0, and cell index #1 may correspond to FDRA#1. If the base station indicates scheduling by including cell index #0 and cell index #1 in a single DCI, the UE may determine that multiple cells are scheduled. In addition, according to the scheduled cell index, the UE may perform PDSCH reception or PUSCH transmission for cell index #0 through FDRA#0, and perform PDSCH reception or PUSCH transmission for cell index #1 through FDRA#1.

[0460] If the FDRA field satisfies a specific condition, PDSCH reception or PUSCH transmission based on the FDRA field may not be scheduled. For example, when the FDRA field is configured as resource allocation (RA) type 0, if the FDRA field corresponds to all "0", the UE can determine through the FDRA field that PDSCH reception or PUSCH transmission is not scheduled. Alternatively, when the FDRA field is configured as RA type 1, if the FDRA field corresponds to all "1", the UE can determine through the FDRA field that PDSCH reception or PUSCH transmission is not scheduled. If the FDRA field is configured by dynamic switching (RA type 0 and RA type 1 are determined by 1 bit of the FDRA field, and if 1 bit is "0", it indicates RA type 0, and if 1 bit is "1", it indicates RA type 0), the field corresponds to all "0" or all "1", the UE can determine through the FDRA field that PDSCH reception or PUSCH transmission is not scheduled.

[0461] [Method 4-1-1. Method for configuring FDRA for one or more cells]

[0462] The base station can configure information about FDRA for the UE. Here, the DCI format monitored by the UE may include N FDRA fields. The base station may configure the index of the cell corresponding to each FDRA field. Here, the index of one or more cells may be configured in one FDRA field. However, a specific cell index may be configured in one FDRA field, but may not be configured in multiple FDRA fields.

[0463] When the UE obtains scheduling information through the FDRA field, the scheduling information of the FDRA field can be applied to one or more cells configured in the FDRA field. That is, when the indexes of multiple cells corresponding to the FDRA field are configured, the UE can receive PDSCH or send PUSCH by applying the scheduling information obtained from the FDRA field to multiple cells.

[0464] When compared with method 4-1, method 4-1-1 can reduce the overhead of the FDRA field in the DCI format. Therefore, the reliability of PDCCH reception can be increased.

[0465] [Method 4-2. Method for performing instruction in association with other configuration information after configuring FDRA]

[0466] In addition to the TDRA and bitmap indication of the first and second embodiments, the FDRA configuration may also be used.

[0467] Since the operation of method 1 includes dividing multiple cells only by frequency resources, operation ambiguity may occur in the UE, such as collision in transmission from or to different cells in the time domain. To this end, when multi-cell scheduling is performed, FDRA can be configured in association with TDRA configuration or bitmap.

[0468] [Method 4-2-1. FDRA indication method through TDRA]

[0469] The base station may indicate the FDRA field corresponding to each piece of scheduling information through TDRA row information (based on the higher layer configuration information). Here, the DCI format may include a plurality of FDRA fields, and the FDRA field may be assigned a unique index.

[0470] The base station may configure TDRA and FDRA information for the UE through high-layer configuration information. In this case, the TDRA configuration information may include a row including multiple cell scheduling information in one row, as described in the first embodiment. Up to N pieces of FDRA configuration information may be configured.

[0471] When the base station performs multi-cell scheduling, one TDRA line may include scheduling information (cell index, K0, SLIV, mapping type, and FDRA index). The UE may identify the indicated TDRA line to determine the cell through which PDSCH reception or PUSCH transmission is to be performed, and identify the frequency resource by the FDRA index included in the TDRA line information.

[0472] [Method 4-2-2. FDRA indication method using bitmap information]

[0473] The base station may indicate the FDRA through a cell index indication bitmap.

[0474] The base station may configure FDRA information for the UE through high-level configuration information. In this case, each piece of FDRA information may correspond to a cell index. In this case, multi-cell scheduling may be indicated through a bitmap in the DCI format, as described in the second embodiment.

[0475] When the base station performs multi-cell scheduling, the base station can indicate the cell to be scheduled to the UE through the bitmap information in the DCI format. The UE can receive the PDSCH or send the PUSCH in each cell corresponding to the bit indicated as "1" in the indicated bitmap. In this case, the UE can receive the PDSCH or send the PUSCH by applying the FDRA corresponding to the cell index configured according to the RRC signal.

[0476] The first to third embodiments described above are not separate, and the base station and the UE may operate in combination of parts of the first to third embodiments.

[0477] In addition, in the first to third embodiments described above, the cell index may be replaced with a cell group index, and in this case, one or more cells may be configured within the cell group through a higher layer signal.

[0478] Fig.20a An example of the operation of a base station according to an embodiment of the present disclosure is shown.

[0479] according to Fig.20a , the base station may receive the UE capability (or UE capability) information from the UE (2000). The base station may send scheduling information (2002) based on the UE capability through a high-layer signal (e.g., an RRC signal). In this case, the high-layer signal may include multi-cell scheduling related information. The specific content of the multi-cell scheduling related information may follow a combination of at least one of the first to third embodiments described above. The base station may send a DCI including multi-cell scheduling information to indicate multi-cell scheduling to the UE (2004). In this case, the DCI format and the type and content of the control information included in the DCI may follow a combination of at least one of the first to third embodiments described above. According to the scheduling information, the base station may send a PDSCH to the UE or receive a PUSCH from the UE (2006).

[0480] Fig.20b An example of the operation of a UE according to an embodiment of the present disclosure is shown.

[0481] according to Fig.20b , the UE may send UE capability information to the base station (2010). The UE may receive scheduling information from the base station through a high-layer signal (e.g., an RRC signal) (2012). In this case, the high-layer signal may include multi-cell scheduling related information. The specific content of the multi-cell scheduling related information may follow a combination of at least one of the first to third embodiments described above. The UE may receive DCI from the base station (2014), and in this case, the DCI may include multi-cell scheduling information. In this case, the DCI format and the type and content of the control information included in the DCI may follow a combination of at least one of the first to third embodiments described above. Based on the received DCI, the UE may determine whether it is multi-cell scheduling or single-cell scheduling, at least one cell is scheduled, and at least one piece of scheduling information (2016). The UE may receive a PDSCH from the base station or send a PUSCH to the base station based on the scheduling information (2018).

[0482] The flowcharts described above illustrate exemplary methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, an operation can be omitted or replaced with another operation.

[0483] Fig.21 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0484] refer to Fig.21 , the UE may include a transceiver (which refers to the UE receiver 2100 and the UE transmitter 2110 as a whole), a memory (not shown) and a UE processor 2105 (or a UE controller or processor). The UE transceivers 2100 and 2110, the memory and the UE processor 2105 may operate according to the above-described communication method of the UE. However, the components of the UE are not limited to the examples described above. For example, the UE may include a greater or lesser number of 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.

[0485] The transceiver can transmit / receive signals with the base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, an RF receiver configured to low-noise amplify the received signal and down-convert its frequency, etc. However, this is only an embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0486] In addition, the transceiver may receive a signal through a radio channel, output the signal to the processor, and transmit a signal output from the processor through the radio channel.

[0487] The memory may store programs and data necessary for the operation of the UE. In addition, the memory may store control information or data included in the signal sent / received by the UE. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media. In addition, the memory may include multiple memories.

[0488] The processor may control a series of processes so that the UE can operate according to the embodiments described above. For example, the processor may control the components of the UE to receive DCI configured in two layers so as to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the processor may perform operations to control the components of the UE by executing a program stored in a memory.

[0489] Fig. 22The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0490] refer to Fig. 22 , the base station may include a transceiver (which refers to the base station receiver 2200 and the base station transmitter 2210 as a whole), a memory (not shown) and a base station processor 2105 (or a base station controller or processor). The base station transceivers 2200 and 2210, the memory and the base station processor 2205 may operate according to the above-described communication method of the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include a greater or lesser number of 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.

[0491] The transceiver can transmit / receive signals with the UE. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, an RF receiver configured to low-noise amplify the received signal and down-convert its frequency, etc. This is only an embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0492] In addition, the transceiver may receive a signal through a radio channel, output the signal to the processor, and transmit a signal output from the processor through the radio channel.

[0493] The memory may store programs and data necessary for the operation of the base station. In addition, the memory may store control information or data included in the signal sent / received by the base station. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media. In addition, the memory may include a plurality of memories.

[0494] The processor may control a series of processes so that the base station can operate according to the above-described embodiments of the present disclosure. For example, the processor may control the components of the base station to configure a DCI configured in two layers (including allocation information about multiple PDSCHs) and send the DCI. The processor may include multiple processors, and the processor may perform operations to control the components of the base station by executing a program stored in a memory.

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

[0496] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. The at least one program includes instructions for causing the electronic device to execute the method according to the various embodiments of the present disclosure defined by the attached claims and / or disclosed herein.

[0497] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage device, compact disk-ROM (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices or tape cassettes. Alternatively, any combination of some or all of them can form a memory in which the program is stored. In addition, a plurality of such memories can be included in the electronic device.

[0498] In addition, the program can be stored in an attachable storage device that can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), and a storage area network (SAN) or a combination thereof. Such a storage device can access the electronic device via an external port. In addition, a separate storage device on a communication network can access the portable electronic device.

[0499] In the detailed embodiments described above of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to the elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

[0500] The embodiments of the present disclosure described and shown in the specification and the drawings are merely specific examples that have been presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical ideas of the present disclosure can be implemented. In addition, the above-mentioned various embodiments can be adopted in combination as needed. For example, a part of an embodiment of the present disclosure can be combined with a part of another embodiment to operate a base station and a terminal. As an example, a part of the first embodiment of the present disclosure can be combined with a part of the second embodiment to operate a base station and a terminal. Moreover, although the above-mentioned embodiments have been described based on an FDD LTE system, other variations based on the technical ideas of the embodiments can also be implemented in other communication systems such as TDD LTE, and 5G, or NR systems.

[0501] In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order of performing the steps of each method, and the sequential relationship between the steps may be changed or the steps may be performed in parallel.

[0502] Alternatively, in the drawings describing the method of the present disclosure, some elements may be omitted, and only some elements may be included therein without departing from the basic spirit and scope of the present disclosure.

[0503] In addition, in the method of the present disclosure, part or all of the content of each embodiment may be implemented in combination without departing from the essential spirit and scope of the present disclosure.

[0504] Various embodiments of the present disclosure have been described above. The above description of the present disclosure is for illustrative purposes and is not intended to limit the embodiments of the present disclosure to the embodiments set forth herein. Those skilled in the art will appreciate that other specific modifications and changes to the form of the present disclosure may be easily made without changing the technical ideas or essential features of the present disclosure. The scope of the present disclosure is defined by the appended claims, rather than by the above detailed description, and the scope of the present disclosure should be interpreted as including all changes or modifications derived from the meaning and scope of the claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method include: receiving time domain resource allocation (TDRA) configuration information from a base station through high-layer signaling, wherein the TDRA configuration information includes a plurality of rows, and each row includes one or more data channel scheduling information; receiving downlink control information for scheduling a data channel from a base station, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of a plurality of rows; and Based on one or more pieces of data channel scheduling information included in the indicated row and one or more cell indexes indicated by the cell index indicator, a data channel is transmitted or received in each of cells corresponding to the one or more cell indexes.

2. The method according to claim 1, in, The downlink control information also includes a frequency domain resource allocation (FDRA) field, and in a case where the FDRA field is configured as a predetermined value, the FDRA field indicates that a cell corresponding to the FDRA field is not scheduled.

3. The method according to claim 1, in, In case the downlink control information is downlink control information for uplink data channel scheduling, the downlink control information also includes a transmission power control (TPC) command field, an open-loop power control parameter set indication field, a precoding information field, and an antenna port field.

4. The method according to claim 1, in, In case that the downlink control information is downlink control information for downlink data channel scheduling, the downlink control information further includes a rate matching indicator field, a transmission configuration indication (TCI) field, and an antenna port field.

5. A method performed by a base station in a wireless communication system, the method include: Sending time domain resource allocation (TDRA) configuration information to the terminal through high-layer signaling, wherein the TDRA configuration information includes a plurality of rows, and each row includes one or more data channel scheduling information; Sending downlink control information for scheduling a data channel to a terminal, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of a plurality of rows; and receiving or transmitting a data channel in each of the cells corresponding to one or more cell indexes associated with the cell index indicator, The data channel corresponds to one or more pieces of data channel scheduling information included in the indicated row.

6. The method according to claim 5, in, The downlink control information also includes a frequency domain resource allocation (FDRA) field, and in a case where the FDRA field is configured as a predetermined value, the FDRA field indicates that a cell corresponding to the FDRA field is not scheduled.

7. The method according to claim 5, in, In case the downlink control information is downlink control information for uplink data channel scheduling, the downlink control information also includes a transmission power control (TPC) command field, an open-loop power control parameter set indication field, a precoding information field, and an antenna port field.

8. The method according to claim 5, in, In case that the downlink control information is downlink control information for downlink data channel scheduling, the downlink control information further includes a rate matching indicator field, a transmission configuration indication (TCI) field, and an antenna port field.

9. A terminal in a wireless communication system, the terminal include: Transceiver; as well as The controller is configured as: receiving time domain resource allocation (TDRA) configuration information from a base station through high-layer signaling, wherein the TDRA configuration information includes a plurality of rows, and each row includes one or more data channel scheduling information; receiving downlink control information for scheduling a data channel from a base station, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of a plurality of rows, and Based on one or more pieces of data channel scheduling information included in the indicated row and one or more cell indexes indicated by the cell index indicator, a data channel is transmitted or received in each of cells corresponding to the one or more cell indexes.

10. The terminal according to claim 9, in, The downlink control information also includes a frequency domain resource allocation (FDRA) field, and in a case where the FDRA field is configured as a predetermined value, the FDRA field indicates that a cell corresponding to the FDRA field is not scheduled.

11. The terminal according to claim 9, in, In case the downlink control information is downlink control information for uplink data channel scheduling, the downlink control information also includes a transmission power control (TPC) command field, an open-loop power control parameter set indication field, a precoding information field, and an antenna port field.

12. The terminal according to claim 9, in, In case that the downlink control information is downlink control information for downlink data channel scheduling, the downlink control information further includes a rate matching indicator field, a transmission configuration indication (TCI) field, and an antenna port field.

13. A base station in a wireless communication system, the base station include: Transceiver; as well as The controller is configured as: Sending time domain resource allocation (TDRA) configuration information to the terminal through high-layer signaling, wherein the TDRA configuration information includes a plurality of rows, and each row includes one or more data channel scheduling information; sending downlink control information for scheduling a data channel to a terminal, wherein the downlink control information includes a cell index indicator and a TDRA field, and the TDRA field indicates one of a plurality of rows, and receiving or transmitting a data channel in each of the cells corresponding to one or more cell indexes associated with the cell index indicator, The data channel corresponds to one or more pieces of data channel scheduling information included in the indicated row.

14. The base station according to claim 13, in, The downlink control information also includes a frequency domain resource allocation (FDRA) field, and in a case where the FDRA field is configured as a predetermined value, the FDRA field indicates that a cell corresponding to the FDRA field is not scheduled.

15. The base station according to claim 13, in, In the case where the downlink control information is downlink control information for uplink data channel scheduling, the downlink control information further includes a transmission power control (TPC) command field, an open-loop power control parameter set indication field, a precoding information field, and an antenna port field, Wherein, in the case where the downlink control information is downlink control information used for downlink data channel scheduling, the downlink control information further includes a rate matching indicator field, a transmission configuration indication (TCI) field and an antenna port field.