A method and apparatus for scheduling in a wireless communication system

Abstract

The present disclosure relates to a 5G (5th generation) or pre-5G communication system for supporting higher data transmission rates than 4G (4th generation) communication systems such as LTE (Long Term Evolution). The present disclosure relates to transmitting and receiving data and control information in a wireless or communication system, and a method of operation of a terminal comprises the steps of: receiving a radio resource control (RRC) message; confirming from the received RRC message information regarding a scheduling cell and information regarding a format for downlink control information to be received; receiving downlink control information from the scheduling cell according to the confirmed format; and receiving data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the physical downlink shared channel (PDSCH) of the plurality of cells. In addition, various other embodiments are possible.

Description

Technology Field

[0001] The present disclosure relates to a wireless communication system, and more specifically to a scheduling method and apparatus for dynamic spectrum sharing (DSS). Background Technology

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access), are being developed in 5G systems.

[0003] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies.

[0005] Meanwhile, as the number of terminals in the network increases, scheduling capacity may become insufficient, and a method to resolve this is required. The problem to be solved

[0006] The present disclosure provides a method for scheduling physical downlink shared channels (PDSCH) for a plurality of cells using downlink control information transmitted through a physical downlink control channel (PDCCH) of a single cell in a wireless communication system. means of solving the problem

[0007] According to various embodiments of the present disclosure, a method of a terminal in a wireless communication system comprises the steps of: receiving a radio resource control (RRC) message; identifying from the received RRC message information regarding a scheduling cell and information regarding a format for downlink control information to be received; receiving downlink control information from the scheduling cell according to the identified format; and receiving data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for a physical downlink shared channel (PDSCH) of the plurality of cells.

[0008] Additionally, according to various embodiments of the present disclosure, a method of a base station in a wireless communication system comprises the steps of transmitting downlink control information to a terminal through a scheduling cell of the terminal, and transmitting data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells.

[0009] Additionally, according to various embodiments of the present disclosure, a terminal of a wireless communication system comprises a transceiver and a control unit that receives an RRC (radio resource control) message through the transceiver, identifies information regarding a scheduling cell and a format for downlink control information to be received from the received RRC message, receives downlink control information from the scheduling cell according to the identified format, and receives data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells.

[0010] Additionally, according to various embodiments of the present disclosure, a base station of a wireless communication system comprises a transceiver and a control unit that transmits downlink control information to a terminal through a scheduling cell using the transceiver and transmits data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells. Effects of the invention

[0011] According to the present disclosure, by proposing a method for scheduling the PDSCHs of multiple cells through the PDCCH of a single cell in a wireless communication system, scheduling for a terminal can be performed using wireless resources efficiently. Brief explanation of the drawing

[0012] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. FIG. 1 is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 2 is a diagram illustrating the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 3 is a drawing for explaining carrier aggregation (CA) according to one embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of a cross-carrier scheduling method according to one embodiment of the present disclosure. FIG. 5 is a diagram showing the format of downlink control information according to one embodiment of the present disclosure. FIG. 6 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure. FIG. 7 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure. FIG. 8 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure. FIG. 9 is a diagram illustrating a method in which a base station schedules a plurality of cell PDSCHs to a terminal according to one embodiment of the present disclosure. FIG. 10 is a diagram illustrating a method in which a terminal receives data through a plurality of cells' PDSCHs according to one embodiment of the present disclosure. FIG. 11 is a flowchart illustrating a cell according to one embodiment of the present disclosure scheduling a plurality of cell PDSCHs to a terminal. FIG. 12 is a flowchart illustrating a cell according to another embodiment of the present disclosure scheduling a plurality of cell PDSCHs to a terminal. FIG. 13 is a drawing illustrating the structure of a base station according to one embodiment of the present disclosure. FIG. 14 is a drawing illustrating the structure of a terminal according to one embodiment of the present disclosure. Specific details for implementing the invention

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

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

[0015] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference number.

[0016] The advantages and features of the present invention and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below but can be implemented in various different forms. The embodiments of the present disclosure are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.

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

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

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

[0020] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present invention below, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present invention, such detailed description will be omitted. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, such definitions should be based on the content throughout this specification. Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above examples. Hereinafter, the present disclosure describes a technology for a terminal to receive broadcast information from a base station in a wireless communication system. The present disclosure is 4G (4 th 5G (5 generation) to support higher data transmission rates after the system th This disclosure relates to a communication technique and a system that fuses a communication system (generation) with IoT (Internet of Things) technology. The present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology.

[0021] Terms used in the following description to refer to broadcast information, control information, communication coverage, state changes (e.g., events), network entities, messages, and device components are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0022] For the convenience of the following explanation, some terms and names defined in the 3GPP LTE (3rd generation partnership project long term evolution) standard may be used. However, the present invention is not limited by the above terms and names and can be applied in the same way to systems conforming to other standards.

[0023] FIG. 1 is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0024] Referring to FIG. 1, the wireless access network of a next-generation mobile communication system (hereinafter NR or 5G) may be composed of a next-generation base station (new radio node B, hereinafter NR gNB or NR base station) (110) and a next-generation wireless core network (new radio core network, NR CN) (105). A next-generation wireless user terminal (new radio user equipment, NR UE or terminal) (115) may connect to an external network through the NR gNB (110) and the NR CN (105).

[0025] In FIG. 1, the NR gNB (110) can correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (115) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs and perform scheduling, and the NR gNB (110) can handle this. A single NR gNB can control multiple cells. In the next-generation mobile communication system, a bandwidth greater than the current maximum bandwidth can be applied to achieve ultra-high-speed data transmission compared to current LTE. Additionally, beamforming technology can be incorporated by using orthogonal frequency division multiplexing (OFDM) as the wireless access technology. In addition, an adaptive modulation & doding (hereinafter referred to as AMC) scheme that determines the modulation scheme and channel coding rate according to the channel conditions of the terminal may be applied.

[0026] The NR CN (105) can perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for terminals, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with existing LTE systems, and the NR CN can be connected to the MME (125) via a network interface. The MME can be connected to the existing base station eNB (130).

[0027] FIG. 2 is a diagram illustrating the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0028] Referring to FIG. 2, the wireless protocol of the next-generation mobile communication system consists of the NR Service Data Adaptation Protocol (SDAP) (201, 245), NR PDCP (205, 240), NR RLC (210, 235), NR MAC (215, 230), and NR PHY (220, 225) at the terminal and the NR base station, respectively.

[0029] The main functions of NR SDAP (201, 245) may include some of the following functions.

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

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

[0032] - Marking QoS flow ID in both DL and UL packets for uplink and downlink

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

[0034] For SDAP layer devices, the terminal may receive a radio resource control (RRC) message indicating whether to use the SDAP layer device header or the SDAP layer device functions for each PDCP layer device, for each bearer, or for each logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the 1-bit NAS reflective QoS indicator and the 1-bit AS reflective QoS indicator of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0035] The main functions of NR PDCP (205, 240) may include some of the following functions.

[0036] - Header compression and decompression features (ROHC only)

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

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

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

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

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

[0042] - Retransmission of PDCP SDUs

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

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

[0045] In the above description, the reordering function of the NR PDCP device may refer to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP device may include a function to transmit data to an upper layer in the reordered order, a function to transmit immediately without considering the order, a function to record lost PDCP PDUs by reordering, a function to report the status of lost PDCP PDUs to the transmitting side, and a function to request retransmission of lost PDCP PDUs.

[0046] The main functions of NR RLC (210, 235) may include some of the following functions.

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

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

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

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

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

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

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

[0054] - Duplicate detection

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

[0056] - RLC SDU discard function

[0057] RLC re-establishment function

[0058] In the above description, the in-sequence delivery function of the NR RLC device may refer to the function of delivering RLC SDUs received from a lower layer to an upper layer in sequence. In the case where a single RLC SDU is received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.

[0059] The in-sequence delivery function of the NR RLC device may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by rearranging the order, a function to report the status of lost RLC PDUs to the transmitting side, and a function to request retransmission of lost RLC PDUs.

[0060] The in-sequence delivery function of the NR RLC (210, 235) device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU. Additionally, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Additionally, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.

[0061] The NR RLC (210, 235) device can process the RLC PDUs in the order they are received, regardless of the sequence number (Out of sequence delivery), and deliver them to the NR PDCP (205, 240) device.

[0062] When the NR RLC (210, 235) device receives a segment, it may receive segments that are stored in a buffer or will be received later, reconstruct them into a complete RLC PDU, and then transmit it to the NR PDCP device.

[0063] The NR RLC layer may not include a concatenation function, and the function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

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

[0065] The NR MAC (215, 230) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

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

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

[0068] - Scheduling information reporting function

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

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

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

[0072] - MBMS service identification function

[0073] - Transport format selection function

[0074] - Padding

[0075] The NR PHY layer (220, 225) can perform the operation of channel coding and modulating upper layer data, making it into OFDM symbols and transmitting it to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0076] FIG. 3 is a drawing for explaining carrier aggregation (CA) according to one embodiment of the present disclosure.

[0077] Referring to Fig. 3, when CA is configured (300), PCell and SCell can be configured on the terminal.

[0078] PCell is included in the PCC (primary component carrier) and can provide RRC connection establishment / re-establishment, measurement, mobility procedures, random access procedures and selection, system information acquisition, initial random access, security key change, and Non-Access Stratum (NAS) functions.

[0079] Since the terminal performs system information monitoring through the PCell, the PCell is not deactivated, and UL control information is transmitted over the PCC via PUCCH or PUSCH. Additionally, only one RRC can be connected between the terminal and the PCell, and PDCCH / PDSCH / PUSCH / PUCCH transmission is possible. Furthermore, in a secondary cell group, the PSCell can be configured and operate like the PCell. The operations for the PCell described below can also be performed on the PSCell.

[0080] Up to a total of 31 SCells can be added, and SCells can be configured via RRC messages (e.g., dedicated signaling) when additional radio resources are required. RRC messages may include the physical cell ID for each cell and the DL carrier frequency (absolute radio frequency channel number: ARFCN). PDCCH / PDSCH / PUSCH transmission is possible through SCells. Dynamic activation and deactivation procedures for SCells are supported via the MAC layer to conserve the UE's battery.

[0081] Cross-carrier scheduling may mean assigning at least one of all L1 control channels or L2 control channels (e.g., PDCCH) for at least one other component carrier (CC) to a single component carrier (CC). A carrier indicator field (CIF) may be used to transmit data scheduling information of another CC through the PDCCH of one CC.

[0082] Resources for data transmission of said CC (PDSCH, PUSCH) or resources for data transmission of another CC (PDSCH, PUSCH) can be allocated through downlink control information transmitted through the PDCCH of one CC.

[0083] FIG. 4 is a diagram illustrating an example of a cross-carrier scheduling method according to one embodiment of the present disclosure.

[0084] Referring to 410 in Fig. 4, PDSCH or PUSCH for two CCs can be scheduled through PDCCH (401) of one CC.

[0085] In addition, referring to 420 in Fig. 4, when a total of 4 CCs are set, the PDSCH or PUSCH of each CC can be scheduled using the PDCCH (421, 423) of two CCs.

[0086] In addition, referring to 430 in Fig. 4, when a total of 4 CCs are set, the PDSCH or PUSCH of each CC can be scheduled using the PDCCH (431) of one CC.

[0087] Each CC can be mapped to a CI (carrier indicator) value for CIF application, and this can be transmitted from the base station to the terminal via a dedicated RRC signal with UE-specific settings.

[0088] Each PDSCH / PUSCH CC can be scheduled from a single DL CC. Therefore, the UE can monitor the PDCCH only from the said DL CC to obtain PDSCH or PUSCH scheduling information for each PDSCH / PUSCH CC. The terminal can obtain PDSCH or PUSCH scheduling information from the linked carrier by monitoring the PDCCH from the said DL CC.

[0089] Meanwhile, DSS enables LTE (long term evolution) and NR (new radio access technology (RAT)) cells to coexist on the same carrier, thereby providing telecommunication operators with the option to switch to an NR communication system while maintaining their existing LTE communication system.

[0090] As the number of NR terminals in a network increases, a shortage of scheduling capacity for NR terminals may occur. Below, a specific method for scheduling the PDSCH or PUSCH of multiple cells through the PDCCH of a single cell is proposed. A cell that schedules the PDSCH or PUSCH of multiple cells may be referred to as a 'scheduling cell' in this disclosure.

[0091] According to one embodiment of the present disclosure, the scheduling cell and the cell transmitting the RRC message may be the same. According to another example, the scheduling cell and the cell transmitting the RRC message may not be the same. The cell transmitting the RRC message may transmit the RRC message including information about the scheduling cell. [Table 1] below shows, as an example, a CrossCarrierSchedulingConfig that includes information about the scheduling cell among the information included in the RRC message.

[0092]

[0093] Referring to [Table 1], CrossCarrierSchedulingConfig may include schedulingCellId. schedulingCellId may represent the index of a cell that schedules the PDSCH of multiple cells. A terminal can identify the scheduling cell by checking the schedulingCellId of CrossCarrierSchedulingConfig, and identify the scheduled PDSCH of multiple cells by checking the downlink control information transmitted by the scheduling cell.

[0094] The following describes various embodiments that utilize downlink control information to schedule the PDSCH of multiple cells.

[0095] FIG. 5 is a diagram showing the format of downlink control information according to one embodiment of the present disclosure.

[0096] Referring to FIG. 5, the downlink control indicator (DCI) (510) may include one carrier indicator field (CIF) (520) and two frequency domain resource assignment (FDRA) fields (530, 540).

[0097] The base station can set information about the number of FDRAs using a variable (e.g., FDRAadd). For example, if the maximum number of FDRAs that the base station can allocate is 2, the variable can be set to a Boolean type, and if the maximum number of FDRAs that can be allocated is 3 or more, the variable can be set to an integer type.

[0098] The base station may transmit the above variable, which represents information regarding the number of FDRAs, to the terminal via an RRC message. The information transmitted to the terminal via an RRC message may include at least some of CellGroupConfig IE, ServingCellConfig IE, ServingCellConfig IE, and PDCCH-Config IE. If the base station adds the above variable to CellGroupConfig IE, it may be applied to all serving cells belonging to a specific CellGroup. If the base station adds the above variable to ServingCellConfig IE, it may be applied to the corresponding serving cell. If the base station adds the above variable to PDCCH-Config IE, it may be applied to a specific bandwidth part (BWP). Alternatively, if the base station adds the above variable to the scheduling cell part of CrossCarrierSchedulingConfig IE, it may be applied to the scheduling cell.

[0099] The base station may transmit information regarding DCI format (e.g., DCI format 1-1, DCI format 1-2) to the terminal via RRC messages so that the terminal monitors downlink control information including scheduling information on the PDSCHs of multiple cells. Downlink control information may be transmitted via the PDCCH of the scheduling cell.

[0100] The base station can set one CIF and two FDRAs in the DCI format monitored by the terminal using the above variable representing information on the number of FDRAs and CrossCarrierSchedulingConfig IE.

[0101] Referring to FIG. 5, FDRA field #1 (530) may be an FDRA assigned to a PDSCH transmitted by a scheduling cell transmitting DCI (510). FDRA field #2 (540) may be an FDRA assigned to a PDSCH transmitted by a cell other than a scheduling cell. A cell other than a scheduling cell may be indicated by CIF (520).

[0102] In Fig. 5, FDRA field #1 (530) is positioned first and FDRA field #2 (540) is positioned later, but the order can be changed.

[0103] In FIG. 5, FDRA field #1 (530) and FDRA field #2 (540) are shown as being located consecutively, but they may be located discontinuously. For example, information about PDSCH transmitted from a scheduling cell (e.g., time domain resource assignment, VRB-to-PRB mapping, HARQ process number, etc.) may be arranged first, and information about PDSCH transmitted from a cell other than a scheduling cell may be arranged later.

[0104] FIG. 6 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure.

[0105] Referring to FIG. 6, DCI (610) may include two CIFs (620, 630) and two FDRAs (640, 650).

[0106] The base station can set the number of CIFs and FDRAs included in the DCI that the terminal monitors. The base station can transmit information about the set number of CIFs and FDRAs to the terminal via an RRC message. The base station can transmit to the terminal via an RRC message that the number of CIFs and FDRAs included in the DCI (610) is 2.

[0107] [Table 2] below shows a CrossCarrierSchedulingConfig IE modified to indicate the number of CIFs and FDRAs according to an embodiment of the present disclosure.

[0108]

[0109] Referring to [Table 2], a number-of-cif field may be added. The number-of-cif field may indicate the number of CIFs in the DCI's PDCCH. For example, if the value of the number-of-cif field is 1, it indicates that the number of CIFs and FDRAs is 1, and if the value of the number-of-cif field is 2, it indicates that the number of CIFs and FDRAs is 2. The terminal can determine the number of CIFs and FDRAs included in the DCI by checking the value of the number-of-cif field.

[0110] Referring to FIG. 6, each CIF (620, 630) may have a corresponding FDRA (640, 650). Frequency resource information for a PDSCH transmitted from a cell indicated by CIF #1 (620) may be indicated by FDRA field #1 (640). Frequency resource information for a PDSCH transmitted from a cell indicated by CIF #2 (630) may be indicated by FDRA field #2 (650).

[0111] In FIG. 6, FDRA field #1 (640) and FDRA field #2 (650) are shown as being located consecutively, but they may also be located discontinuously. For example, information about the PDSCH transmitted from the cell indicated by CIF #1 (620) (e.g., time domain resource assignment, VRB-to-PRB mapping, HARQ process number, etc.) may be arranged first, and information about the PDSCH transmitted from the cell indicated by CIF #2 (630) may be arranged later.

[0112] The embodiment using one CIF and two FDRAs described in FIG. 5 reduces the DCI overhead but may be limited in terms of scheduling. On the other hand, the embodiment using two CIFs and two FDRAs described in FIG. 6 increases the DCI overhead but may be flexible in terms of scheduling.

[0113] FIG. 7 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure.

[0114] Referring to FIG. 7, DCI (710) may include one extended CIF (720) and two FDRAs (730, 740). The extended CIF (720) may indicate a combination of multiple serving cells existing within a CellGroup. That is, the value indicated by the extended CIF (720) may be one of the combinations of multiple serving cells.

[0115] [Table 3] below shows an extended CIF according to one embodiment of the present disclosure.

[0116]

[0117] Referring to [Table 3], a cell group may contain a total of 8 cells. [Table 3] shows the extended CIF when there are 2 serving cells among the 8 cells. For example, if the extended CIF is '10011', ServingCell1 may represent the cell with index 3 and ServingCell2 may represent the cell with index 5.

[0118] As described in [Table 3], the value expressed as an extended CIF is a combination that can result when two cells within a cell group are selected as serving cells, and can be displayed as (ServingCell1, ServingCell2). The indices of the cells displayed as (ServingCell1, ServingCell2) can be arranged in a specific order. For example, the cell with the smaller index can be placed first (ServingCell1) and the cell with the larger index can be placed second (ServingCell2). As another example, the cell with the larger index can be placed first (ServingCell1) and the cell with the smaller index can be placed second (ServingCell2).

[0119] Values ​​not indicated by [Table 3] may be reserved for future use or used for special purposes.

[0120] Indexing methods such as [Table 3] or information related to [Table 3] may be transmitted to the terminal via RRC messages. Indexing methods or information related to [Table 3] may be stored in inactive memory during the manufacture of the terminal and base station.

[0121] Referring again to FIG. 7, the base station can schedule PDSCHs of multiple cells indicated by the extended CIF (720). Based on the combination of selected cells (ServingCell1, ServingCell2), the FDRA assigned to the PDSCH of each cell can be represented by FDRA field #1 (730) and FDRA field #2 (740).

[0122] The base station can set the CIF included in the DCI monitored by the terminal via an RRC message. The base station may determine the size of the CIF as necessary and / or depending on the terminal's support. For example, the base station may set a variable indicating whether it is an extended CIF or set the size of the CIF (e.g., number of bits) and transmit it to the terminal. The terminal can determine whether it is an extended CIF from the RRC message received from the base station. If it is an extended CIF, the terminal can also determine the size of the CIF.

[0123] FIG. 8 is a diagram showing the format of downlink control information according to another embodiment of the present disclosure.

[0124] FIGS. 5 to 7 describe a method in which a scheduling cell schedules the PDSCH of a plurality of cells, but FIG. 8 describes an embodiment in which the PDSCH of some of the plurality of cells is not scheduled using downlink control information for scheduling the PDSCH of a plurality of cells.

[0125] Referring to 810 in FIG. 8, multiple cells can be indicated by the extended CIF (811). For example, the extended CIF (811) may indicate two cells, one of which may transmit data via PDSCH and the other cell may not transmit data. The FDRA field #1 (812) may indicate frequency resource information for the PDSCH of the cell transmitting data, and the FDRA field #2 (813) may be filled with a pre-specified value to indicate that there is no frequency resource information for the PDSCH. For example, the value of the FDRA field #2 (813) may be filled with a value that does not imply resource allocation. For example, all bits of the FDRA field #2 (813) may be filled with '1'. The terminal can check the DCI (810) to confirm that there is no frequency resource allocated to the PDSCH in one cell.

[0126] Referring to 820 in FIG. 8, a plurality of CIFs (821, 822) and a plurality of FDRAs may be included in DCI (820). Frequency resource information for a PDSCH transmitted from a cell indicated by CIF #1 (821) may be indicated by FDRA field #1 (823). Frequency resource information for a PDSCH transmitted from a cell indicated by CIF #2 (822) may be indicated by FDRA field #2 (824). For example, if there is no frequency resource information for a PDSCH transmitted from a cell indicated by CIF #2 (822), FDRA field #2 (824) may be filled with a pre-specified value. For example, the value of FDRA field #2 (813) may be filled with a value that does not imply resource allocation. For example, all bits of FDRA field #2 (813) may be filled with '1'. A preset value indicating that there is no frequency resource information for PDSCH can be changed by the settings.

[0127] FIG. 9 is a diagram illustrating a method in which a base station schedules a plurality of cell PDSCHs to a terminal according to one embodiment of the present disclosure.

[0128] Referring to FIG. 9, the base station can schedule the PDSCH of multiple cells to the terminal with a single downlink control information.

[0129] The base station may transmit an RRC message to the terminal in step S910. The RRC message may include information about the scheduling cell of the terminal and information about the format of the downlink control information to be received by the terminal (e.g., DCI format 1_1).

[0130] The base station may transmit downlink control information to the terminal in step S920. The downlink control information may include frequency domain resource allocation information for the PDSCHs of the plurality of cells. The downlink control information may include the indices of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCHs. The downlink control information may include information indicating a combination of the indices of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCHs. If a cell that does not schedule a PDSCH is included among the plurality of cells, a value pre-specified in the frequency domain resource allocation information for the PDSCH may be displayed in the downlink control information.

[0131] In step S930, the base station can transmit data to the terminal through the plurality of cells based on the downlink control information.

[0132] FIG. 10 is a diagram illustrating a method in which a terminal receives data through a plurality of cells' PDSCHs according to one embodiment of the present disclosure.

[0133] Referring to FIG. 10, the terminal can receive data through the PDSCH of a plurality of cells indicated by a single downlink control information.

[0134] The terminal may receive an RRC message from the base station in step S1010. The RRC message may include information regarding the scheduling cell of the terminal and information regarding the format of the downlink control information to be received by the terminal. The RRC message may further include at least one of the number of cell indices included in the downlink control information, whether cell index combination information is included, and the number of frequency domain resource allocation information for the PDSCH.

[0135] In step S1020, the terminal can use the received RRC message to check information about the scheduling cell and information about the format of the downlink control information.

[0136] The terminal may receive downlink control information based on the format of the downlink control information confirmed in step S1030. The downlink control information may include frequency domain resource allocation information for the PDSCH of the plurality of cells. The downlink control information may include the index of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCH. The downlink control information may include information indicating a combination of the plurality of cell indices and frequency domain resource allocation information for the corresponding PDSCH. If a cell that does not schedule a PDSCH is included among the plurality of cells, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH.

[0137] The terminal can receive data through multiple cells based on the downlink control information in step S1040.

[0138] FIG. 11 is a flowchart illustrating a cell according to one embodiment of the present disclosure scheduling the PDSCH of a plurality of cells to a terminal. A single base station can operate at least one cell.

[0139] According to one embodiment of the present disclosure, the cell that transmits an RRC message to a terminal and the cell that schedules the PDSCH of a plurality of cells may be the same. In FIG. 11, cell 1 (1110) can not only transmit an RRC message to a terminal (1130) but also schedule the PDSCH.

[0140] Cell 1 (1110) may transmit an RRC message to the terminal (1130) in step 1140. The RRC message may include information about the scheduling cell and information about the format of the downlink control information to be received. In FIG. 11, the information about the scheduling cell may be information about Cell 1 (1110).

[0141] Cell 1 (1110) can consult with Cell 2 (1120) and the terminal (1130) about the PDSCH to be scheduled in step 1142.

[0142] Meanwhile, the terminal (1130) can, at step 1145, check information about the scheduling cell and the format of the downlink control information to be received through the received RRC message.

[0143] Cell 1 (1110) can transmit downlink control information to the terminal (1130) as a scheduling cell at step 1150.

[0144] The terminal (1130) can receive data from cell 1 (1110) and cell 2 (1120) based on the downlink control information in steps 1155 and 1160.

[0145] FIG. 12 is a flowchart illustrating a cell according to another embodiment of the present disclosure scheduling the PDSCH of a plurality of cells to a terminal. A single base station can operate at least one cell.

[0146] According to one embodiment of the present disclosure, the cell that transmits an RRC message to the terminal and the cell that schedules the PDSCH of a plurality of cells may be different. In FIG. 12, cell 1 (1210) can transmit an RRC message to the terminal (1230), and cell 2 (1220) can schedule the PDSCH of a plurality of cells to the terminal (1230).

[0147] Cell 1 (1210) may transmit an RRC message to the terminal (1230) in step 1240. The RRC message may include information about the scheduling cell and information about the format of the downlink control information to be received. In FIG. 12, the information about the scheduling cell may be information about Cell 2 (1220).

[0148] Cell 2 (1220) can consult with Cell 1 (1210) and the terminal (1230) about the PDSCH to be scheduled in step 1242.

[0149] Meanwhile, the terminal (1230) can, at step 1245, check information about the scheduling cell and the format of the downlink control information to be received through the received RRC message.

[0150] Cell 2 (1220) can transmit downlink control information to the terminal (1230) as a scheduling cell in step 1250.

[0151] The terminal (1230) can receive data from cell 1 (1210) and cell 2 (1220) based on the downlink control information in steps 1255 and 1260.

[0152] FIG. 13 is a drawing illustrating the structure of a base station according to one embodiment of the present disclosure.

[0153] Referring to FIG. 13, the base station may include a transceiver (1310), a control unit (1320), and a storage unit (1330). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0154] The transceiver (1310) can transmit and receive signals with other network entities. The transceiver (1310) can transmit downlink control information to the terminal, for example, through the terminal's scheduling cell. The transceiver (1310) can transmit an RRC message to the terminal. Additionally, the transceiver (1310) can receive data from the terminal and transmit data to the terminal.

[0155] The control unit (1320) can control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the control unit (1320) can control the signal flow between each block to perform operations according to the flowchart described above. For example, the control unit (1320) can transmit data through a plurality of cells based on the downlink control information according to the embodiment of the present invention. The downlink control information may include frequency domain allocation information (FDRA) for the PDSCH of the plurality of cells. The downlink control information may include the index of the plurality of cells and frequency domain resource allocation information for the PDSCH corresponding to the plurality of cells. The downlink control information may include information indicating a combination of the indices of the plurality of cells and frequency domain resource allocation information for the PDSCH corresponding thereto. If a cell that does not schedule a PDSCH is included among the plurality of cells, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH. The control unit (1320) may further transmit an RRC message including information about the scheduling cell and information about the format of the downlink control information to be received by the terminal.

[0156] The storage unit (1330) can store at least one of the information transmitted and received through the transmission and reception unit (1310) and the information generated through the control unit (1320).

[0157] FIG. 14 is a drawing illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0158] Referring to FIG. 14, the terminal may include a transceiver (1410), a control unit (1420), and a storage unit (1430). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0159] The transceiver (1410) can transmit and receive signals with other network entities. The transceiver (1410) can, for example, receive RRC messages from a base station. Additionally, the transceiver (1410) can receive downlink control information from a base station.

[0160] The control unit (1420) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (1420) can control the signal flow between each block to perform operations according to the flowchart described above. For example, the control unit (1420) can check information about the scheduling cell and information about the format of the downlink control information to be received from the RRC message received through the transceiver (1410) according to the embodiment of the present invention, and can receive downlink control information according to the confirmed format from the scheduling cell. The control unit (1420) can receive data through a plurality of cells based on the downlink control information. The downlink control information may include frequency domain resource allocation information for the PDSCH of the plurality of cells. The downlink control information may include the index of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCH. The downlink control information may include information indicating the combination of the plurality of cell indices and frequency domain resource allocation information for the corresponding PDSCH. If a cell that does not schedule a PDSCH is included among the plurality of cells mentioned above, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH. The RRC message may include at least one of the number of cell indices included in the downlink control information, whether the cell indices are combinations, and the number of frequency domain resource allocation information for the PDSCH.

[0161] The storage unit (1430) can store at least one of the information transmitted and received through the transmission and reception unit (1410) and the information generated through the control unit (1420).

[0162] According to various embodiments of the present disclosure, a method of a terminal in a wireless communication system comprises the steps of: receiving a radio resource control (RRC) message; identifying from the received RRC message information regarding a scheduling cell and information regarding a format for downlink control information to be received; receiving downlink control information from the scheduling cell according to the identified format; and receiving data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for a physical downlink shared channel (PDSCH) of the plurality of cells.

[0163] In a method of a terminal according to various embodiments of the present disclosure, the downlink control information may include frequency domain resource allocation information for the index of the plurality of cells and the corresponding PDSCH.

[0164] In a method of a terminal according to various embodiments of the present disclosure, the downlink control information may include information indicating the plurality of cell index combinations and frequency domain resource allocation information for the corresponding PDSCH.

[0165] In a method of a terminal according to various embodiments of the present disclosure, if a cell that does not schedule a PDSCH is included among the plurality of cells, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH.

[0166] In a method of a terminal according to various embodiments of the present disclosure, the RRC message may further include at least one of the number of cell indices included in the downlink control information, whether cell index combination information is included, and the number of frequency domain resource allocation information for the PDSCH.

[0167] Additionally, according to various embodiments of the present disclosure, a method of a base station in a wireless communication system comprises the steps of transmitting downlink control information to a terminal through a scheduling cell of the terminal, and transmitting data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells.

[0168] In a method of a base station according to various embodiments of the present disclosure, the method may further include the step of transmitting a radio resource control (RRC) message comprising information about the scheduling cell and information about the format of the downlink control information to be received by the terminal.

[0169] In a method of a base station according to various embodiments of the present disclosure, the downlink control information may include frequency domain resource allocation information for the index of the plurality of cells and the corresponding PDSCH.

[0170] In a method of a base station according to various embodiments of the present disclosure, the downlink control information may include information indicating a combination of indices of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCH.

[0171] In a method of a base station according to various embodiments of the present disclosure, if a cell that does not schedule a PDSCH is included among the plurality of cells, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH.

[0172] Additionally, according to various embodiments of the present disclosure, a terminal of a wireless communication system comprises a transceiver and a control unit that receives an RRC (radio resource control) message through the transceiver, identifies information regarding a scheduling cell and a format for downlink control information to be received from the received RRC message, receives downlink control information from the scheduling cell according to the identified format, and receives data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells.

[0173] In a terminal according to various embodiments of the present disclosure, the downlink control information may include frequency domain resource allocation information for the index of the plurality of cells and the corresponding PDSCH.

[0174] In a terminal according to various embodiments of the present disclosure, the downlink control information may include information indicating the plurality of cell index combinations and frequency domain resource allocation information for the corresponding PDSCH.

[0175] In a terminal according to various embodiments of the present disclosure, if a cell that does not schedule a PDSCH is included among the plurality of cells, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH.

[0176] In a terminal according to various embodiments of the present disclosure, the RRC message may further include at least one of the number of cell indices included in the downlink control information, whether cell index combination information is included, and the number of frequency domain resource allocation information for the PDSCH.

[0177] Additionally, according to various embodiments of the present disclosure, a base station of a wireless communication system comprises a transceiver and a control unit that transmits downlink control information to a terminal through a scheduling cell using the transceiver and transmits data through a plurality of cells based on the downlink control information, wherein the downlink control information may include frequency domain resource allocation information for the PDSCH (physical downlink shared channel) of the plurality of cells.

[0178] The control unit of the base station according to various embodiments of the present disclosure may further transmit a radio resource control (RRC) message including information about the scheduling cell and information about the format of the downlink control information to be received by the terminal.

[0179] In a base station according to various embodiments of the present disclosure, the downlink control information may include frequency domain resource allocation information for the index of the plurality of cells and the corresponding PDSCH.

[0180] In a base station according to various embodiments of the present disclosure, the downlink control information may include information indicating a combination of indices of the plurality of cells and frequency domain resource allocation information for the corresponding PDSCH.

[0181] In a base station according to various embodiments of the present disclosure, if a cell among the plurality of cells that does not schedule a PDSCH is included, the downlink control information may indicate a value pre-specified in the frequency domain resource allocation information for the PDSCH.

[0182] Although the above description explains PDSCH scheduling of multiple cells as an example, it can also be applied to PUSCH scheduling.

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

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

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

Claims

Claim 1 A method of a terminal in a wireless communication system, comprising: receiving a radio resource control (RRC) message; identifying from the received RRC message information regarding a scheduling cell, information regarding a format for downlink control information to be received, and information regarding the number of cells scheduled through the downlink control information; receiving downlink control information according to the identified format; and receiving a PDSCH from each of the scheduling cells based on frequency domain resource allocations (FDRAs) for each of the PDSCH (physical downlink shared channel) included in the received downlink control information, wherein the received downlink control information includes information indicating a combination of the scheduling cells. Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 A method of a base station in a wireless communication system, comprising: transmitting a radio resource control (RRC) message to a terminal, the message including information indicating a format for downlink control information to be transmitted to a terminal and information related to the number of cells to be scheduled through said downlink control information; transmitting downlink control information according to said format to the terminal; and transmitting data to the terminal based on frequency domain resource allocations (FDRAs) for each of the physical downlink shared channel (PDSCH) of the scheduling cells included in said downlink control information, wherein the downlink control information includes information indicating a combination of said scheduling cells. Claim 7 delete Claim 8 delete Claim 9 delete Claim 10 delete Claim 11 A terminal in a wireless communication system comprises: a transceiver; and at least one processor, wherein the at least one processor receives an RRC (radio resource control) message through the transceiver, identifies from the received RRC message information regarding a scheduling cell, information regarding a format for downlink control information to be received, and information regarding the number of cells scheduled through the downlink control information, receives downlink control information according to the identified format, receives a PDSCH from each of the scheduling cells based on FDRAs (frequency domain resource allocations) for each of the PDSCH (physical downlink shared channel) included in the received downlink control information, and the received downlink control information includes information indicating a combination of the scheduling cells. Claim 12 delete Claim 13 delete Claim 14 delete Claim 15 delete Claim 16 A base station in a wireless communication system comprises: a transceiver; and at least one processor, wherein the at least one processor transmits a radio resource control (RRC) message to the terminal, the RRC message including information indicating a format for downlink control information to be transmitted to the terminal using the transceiver and information related to the number of cells to be scheduled through the downlink control information, transmits downlink control information according to the format to the terminal, transmits data to the terminal based on frequency domain resource allocations (FDRAs) for each of the physical downlink shared channel (PDSCH) of the scheduling cells included in the downlink control information, and the downlink control information includes information indicating a combination of the scheduling cells. Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 In Clause 11, the above FDRAs are terminals located consecutively within the downlink control information. Claim 22 In claim 11, the information indicating the combination of the scheduling cells comprises a terminal including one of the combinations of serving cells. Claim 23 In claim 11, the scheduling cells indicated by information indicating a combination of the scheduling cells include at least one cell included in a cell group, in a terminal. Claim 24 In Clause 11, the FDRAs included in the downlink control information are terminals arranged based on a specified order. Claim 25 In Clause 16, the above FDRAs are base stations located consecutively within the downlink control information. Claim 26 In paragraph 16, the information indicating the combination of the above-mentioned scheduling cells is a base station including one of the combinations of serving cells. Claim 27 In claim 16, the scheduling cells indicated by information indicating a combination of the scheduling cells include at least one cell included in a cell group, and are base stations. Claim 28 In Clause 16, the FDRAs included in the downlink control information are base stations arranged based on a specified order.

Images