Terminal and wireless communication method

The terminal's enhanced UE Capability reporting, based on single downlink control information and subcarrier spacing, addresses the inefficiencies in existing methods, enabling effective scheduling by accurately conveying its capabilities to the network.

WO2024236668A1PCT designated stage expired Publication Date: 2024-11-21NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

The existing UE Capability reporting method for Single DCI Multi-Cell PDSCH/PUSCH scheduling is not ideal, as it may not accurately reflect the capabilities of the terminal, especially when the subcarrier spacing of the scheduling cell and the scheduled cell are different, leading to potential inefficiencies in scheduling.

Method used

A terminal is designed to transmit UE Capability information based on a single downlink control information, including whether the scheduling cell is included in the set of cells and the carrier types used, allowing for efficient reporting of supported cells and carrier types, even when subcarrier spacings differ.

Benefits of technology

This approach enables accurate and efficient UE Capability reporting, allowing the network to perform appropriate scheduling based on the terminal's capabilities, improving the effectiveness of Single DCI Multi-Cell PDSCH/PUSCH scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023018001_21112024_PF_FP_ABST
    Figure JP2023018001_21112024_PF_FP_ABST
Patent Text Reader

Abstract

This terminal transmits terminal capability information related to scheduling for a combination of a plurality of cells based on a single piece of downlink control information. When a subcarrier spacing of a first cell in which the downlink control information is transmitted is the same as a subcarrier spacing of a second cell scheduled simultaneously based on the downlink control information, the terminal transmits terminal capability information including the number of second cells that can be supported, depending on whether the first cell is included in the combination of the plurality of cells.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method that support a mechanism for scheduling data channels transmitted by multiple carriers using single downlink control information transmitted by a specific carrier.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] In 3GPP Release 18, the introduction of a function for scheduling PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by multiple component carriers (CCs) using single downlink control information (DCI) is being considered (see Non-Patent Document 1). Such a function is called single DCI multi-carrier PDSCH / PUSCH scheduling or single DCI multi-cell PDSCH / PUSCH scheduling (hereinafter referred to as single DCI multi-cell PDSCH / PUSCH scheduling).

[0004] Furthermore, in order to support such single DCI multi-cell PDSCH / PUSCH scheduling, a single DCI format (which may be called DCI format 0_3 / 1_3, etc.) capable of scheduling PDSCH / PUSCH for multiple cells has been agreed upon (Non-Patent Document 2).

[0005] Furthermore, a method of reporting the capability of a terminal (User Equipment, UE) regarding Single DCI Multi-Cell PDSCH / PUSCH scheduling to a network has also been studied (Non-Patent Document 3).

[0006] For example, when the subcarrier spacing (SCS) of a cell (scheduling cell) that transmits the DCI is the same as the SCS of a cell (scheduled cell) scheduled by the DCI, it is under consideration to report UE capability according to whether the scheduling cell is included in a combination of multiple cells (set of cells) by the DCI. Also, when the SCS of the scheduling cell and the SCS of the scheduled cell are different, it is under consideration to report UE capability only for cases where the scheduling cell is not included in the set of cells.

[0007] "New WID on Multi-carrier enhancements", RP-213577, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 "RAN1 Chair's Notes", RAN1 Chair's Notes, 3GPP, May 2022 "Initial RAN1 UE features list for Rel-18 NR after RAN1#112bis-e", R1-2304282, 3GPP TSG RAN WG1 #112bis-e, 3GPP, April 2023

[0008] However, the above-described UE capability reporting has the following problem: Specifically, as for the UE capability related to Single DCI Multi-Cell PDSCH / PUSCH scheduling, as described above, it is assumed that there are items that are preferably reported depending on whether the scheduling cell is included in the Set of cells or not, and items that are preferably reported depending on the carrier type used in the scheduling cell or scheduled cell.

[0009] For this reason, even if the above-mentioned considerations are followed, the UE capability report may not necessarily be ideal.

[0010] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal and a radio communication method that can realize efficient UE capability reporting even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced.

[0011] One aspect of the present disclosure is a terminal (UE200) comprising: a transmitter (control signal / reference signal processor 240) that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information; and a controller (controller 270) that, when the subcarrier spacing of a first cell to which the downlink control information is transmitted is the same as the subcarrier spacing of a second cell simultaneously scheduled by the downlink control information, causes the terminal capability information including the number of second cells that can be supported to be transmitted depending on whether the first cell is included in a combination of multiple cells.

[0012] One aspect of the present disclosure is a terminal (UE200) that includes a transmitter (control signal / reference signal processor 240) that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information, and a controller (controller 270) that causes the transmission of the terminal capability information including whether a function or capability related to the scheduling is supported for each carrier type used in a first cell to which the downlink control information is transmitted and a second cell that is simultaneously scheduled by the downlink control information.

[0013] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram showing frequency bands used in the wireless communication system 10. FIG. 3 is a diagram showing an example configuration of radio frames, subframes, and slots used in the wireless communication system 10. FIG. 4 is a functional block diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram showing an example of a scheduling method that can be supported by the wireless communication system 10. FIG. 6 is a diagram showing an example of PDSCH scheduling according to Single DCI Multi-Cell PDSCH / PUSCH scheduling. FIG. 7 is a diagram showing an example of the relationship between a scheduling cell and a scheduled cell. FIG. 8 is a diagram showing an example in which the scheduling cell is not included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same. FIG. 9 is a diagram showing an example in which the scheduling cell is included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same. Fig. 10 is a diagram showing an example in which the scheduling cell is not included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are different. Fig. 11 is a diagram showing an example of the hardware configuration of the gNB 100 and the UE 200. Fig. 12 is a diagram showing an example of the configuration of a vehicle 2001.

[0014] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0015] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0016] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0017] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .

[0018] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0019] The gNB100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO, which generates highly directional beams by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.

[0020] The type of DC may be Multi-RAT Dual Connectivity (MR-DC) that uses multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC) that uses only NR. MR-DC may also be E-UTRA-NR Dual Connectivity (EN-DC) in which the eNB constitutes the master node (MN) and the gNB constitutes the secondary node (SN), or vice versa, NR-E-UTRA Dual Connectivity (NE-DC).

[0021] The wireless communication system 10 may also support multiple frequency ranges (FR).

[0022] FR1: 410 MHz to 7.125 GHz FR2: FR2-1: 24.25 GHz to 52.6 GHz FR2-2: Over 52.6 GHz to 71 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1 and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0023] Furthermore, the wireless communication system 10 may also support frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz up to 114.25 GHz.

[0024] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied, and DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0025] FIG. 3 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10.

[0026] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 (e.g., 28 or 56 symbols). The number of slots per subframe may also vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz, as shown in Figure 3).

[0027] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block (RB), a resource block group (RBG), a subcarrier, a BWP (Bandwidth part), etc.

[0028] As described above, the wireless communication system 10 may have an extended function related to multiple carriers (specifically, CCs). Specifically, the wireless communication system 10 may support a function (single DCI multi-slot PDSCH / PUSCH scheduling) for scheduling PDSCHs (Physical Downlink Shared Channels) / PUSCHs (Physical Uplink Shared Channels) transmitted in multiple slots using single DCI (Downlink Control Information).

[0029] Specifically, the wireless communication system 10 may support a scheduling method (self-carrier scheduling) in which the scheduling DCI and the channel to be scheduled are the same CC, a cross-carrier scheduling method (cross carrier scheduling) in which scheduling of channels spanning multiple CCs is applied, and a single DCI (single DCI), i.e., a scheduling method (multi-carrier scheduling) in which channels are assigned to multiple different CCs by one DCI.

[0030] More specifically, the wireless communication system 10 may support a function of scheduling PDSCH / PUSCHs transmitted by multiple CCs using a single DCI (single DCI multi-carrier PDSCH / PUSCH scheduling or single DCI multi-cell PDSCH / PUSCH scheduling). Hereinafter, this function will be referred to as single DCI multi-cell PDSCH / PUSCH scheduling.

[0031] Only one of single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling can be used, and both do not necessarily have to be used simultaneously, but the wireless communication system 10 may support simultaneous use of both.

[0032] Furthermore, in order to support such Single DCI Multi-Cell PDSCH / PUSCH scheduling, the wireless communication system 10 may use a single DCI format (which may be called DCI format 0_3 / 1_3, etc.) that can schedule the PDSCH / PUSCH of multiple cells. By using DCI conforming to this DCI format, it becomes possible to simultaneously schedule multiple cells included in a set of multiple cells (set of cells).

[0033] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. Fig. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0034] As shown in FIG. 4 , the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0035] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 11.

[0036] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0037] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0038] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0039] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0040] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0041] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0042] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0043] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0044] The channels include a control channel and a data channel. The control channels may include a Physical Downlink Control Channel (PDCCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0045] Furthermore, the data channel includes a PDSCH, a PUSCH, etc. Data may refer to data transmitted via a data channel.

[0046] The control signal and reference signal processor 240 can receive downlink control information (DCI) transmitted from the network. Specifically, the control signal and reference signal processor 240 can receive DCI according to the DCI format defined in 3GPP TS38.212. In particular, in this embodiment, it can receive UL and DL scheduling DCI. More specifically, the control signal and reference signal processor 240 may receive DCI according to DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2.

[0047] Furthermore, in this embodiment, the control signal and reference signal processing unit 240 may receive DCI in accordance with DCI formats 0_3 and 1_3 for Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0048] DCI formats 0_0, 0_1, 0_2, and 0_3 may be interpreted as UL scheduling grants, and DCI formats 1_0, 1_1, 1_2, and 1_3 may be interpreted as DL scheduling assignments.

[0049] Control signal and reference signal processing unit 240 may receive DCI corresponding to single DCI multi-slot PDSCH / PUSCH scheduling and DCI corresponding to single DCI multi-cell PDSCH / PUSCH scheduling.

[0050] Specifically, for single DCI multi-slot PDSCH / PUSCH scheduling, the control signal and reference signal processor 240 can receive a single DCI that schedules channels transmitted by multiple slots. Also, for single DCI multi-cell PDSCH / PUSCH scheduling, the control signal and reference signal processor 240 can receive a single DCI that schedules channels transmitted by multiple carriers.

[0051] Here, the channel may include the above-mentioned control channel and data channel, and may not be particularly limited to the uplink and downlink directions, but may typically mean at least one of PDSCH and PUSCH. The carrier may mean a component carrier (CC), but may also be simply interpreted as a carrier or subcarrier.

[0052] Furthermore, the control signal and reference signal processor 240 may transmit to the network capability information of the UE 200. In particular, in this embodiment, the control signal and reference signal processor 240 can transmit UE capability information (terminal capability information, see FIG. 1 ) related to scheduling to the gNB 100.

[0053] The control signal and reference signal processor 240 may transmit terminal capability information including terminal capability (UE Capability) related to scheduling of the UE 200. In this embodiment, the control signal and reference signal processor 240 may configure a transmitter.

[0054] The control signal and reference signal processing unit 240 can transmit terminal capability information related to scheduling targeting a combination of multiple cells (Set of cells) using DCI (DCI format 0_3 / 1_3) for Single DCI Multi-Cell PDSCH / PUSCH scheduling. Details of the terminal capabilities included in the terminal capability information will be described later, but the information may include terminal capabilities related to the number of scheduling cells (first cells) to which the DCI is transmitted and / or the number of scheduled cells (second cells) to be scheduled by the DCI.

[0055] Furthermore, control signal and reference signal processor 240 may report the terminal capability information each time it is used in a scheduling cell and a scheduled cell.

[0056] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0057] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0058] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0059] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 controls transmission or reception of a channel (for example, PDSCH / PUSCH, the same applies hereinafter) based on DCI for single DCI multi-slot PDSCH / PUSCH scheduling.

[0060] Furthermore, control unit 270 controls transmission or reception of channels based on DCI for Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0061] In this way, control unit 270 may control transmission or reception of channels based on at least one of DCI for single DCI multi-slot PDSCH / PUSCH scheduling and DCI for single DCI multi-cell PDSCH / PUSCH scheduling. Furthermore, single DCI multi-slot PDSCH / PUSCH scheduling and single DCI multi-cell PDSCH / PUSCH scheduling may be used simultaneously, and control unit 270 may perform control based on both scheduling DCIs simultaneously in parallel.

[0062] The control unit 270 may apply different settings to at least one of the cell, slot, or channel scheduled by the DCI for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI for single DCI multi-cell PDSCH / PUSCH scheduling. The cell type (primary cell (PCell), primary / secondary cell (PSCell), and secondary cell (SCell)) may not be particularly limited, and a cell group (master or secondary) may be targeted. The channel type is also not particularly limited, and may be either the uplink or downlink direction, but the PDSCH / PUSCH may be targeted here.

[0063] Note that multiple cells that are simultaneously scheduled by the DCI may be called co-scheduled cells.

[0064] Furthermore, the control unit 270 may control the method of transmitting (reporting) UE Capability Information to the network based on at least one of the subcarrier spacing (SCS) of the scheduling cell and the SCS of the scheduled cell.

[0065] For example, when the SCS of the scheduling cell and the SCS of the scheduled cell (which may include a co-scheduled cell) are the same, the control unit 270 can cause the control signal / reference signal processing unit 240 to transmit UE Capability Information including the number of scheduled cells that can be supported, depending on whether the scheduling cell is included in a combination of multiple cells (Set of cells).

[0066] Here, the number of supportable scheduled cells may be the maximum number of scheduled cells that the UE 200 can support, but is not necessarily limited to the maximum number, and may be the number of scheduled cells that the UE 200 can support.

[0067] The control unit 270 may perform control so as to separately report the maximum number of scheduled cells that can be supported when the scheduling cell is included in the Set of cells and the maximum number of scheduled cells that can be supported when the scheduling cell is not included in the Set of cells. Alternatively, the control unit 270 may perform control so as to report the maximum number of scheduled cells that can be supported only when the scheduling cell is included in the Set of cells or when the scheduling cell is not included in the Set of cells.

[0068] In addition, the control unit 270 can also transmit terminal capability information including whether or not a function or capability related to scheduling is supported for each carrier type used in the scheduling cell and the scheduled cell.

[0069] Specifically, the control unit 270 may cause the terminal capability information to be transmitted for each frequency range (FR1 / FR2 / FR2-1 / FR2-2) of the carrier used in the cell. Furthermore, the control unit 270 may cause the terminal capability information to be transmitted for each duplexing method (time division duplexing (TDD) / frequency division duplexing (FDD)) applied to the carrier used in the cell, or for each band type (licensed band requiring a license / unlicensed band not requiring a license) of the carrier used in the cell. The control unit 270 may target any one of the frequency range, duplexing method, and band type, or may cause the terminal capability information to be transmitted for each of a plurality of combinations.

[0070] When the SCS of the scheduling cell and the SCS of the scheduled cell are different, the control unit 270 may transmit terminal capability information including the supported carrier type according to the supportable SCS of the scheduling cell and the supportable SCS of the scheduled cell. For example, when the SCS of the scheduling cell is low (narrow) and the SCS of the scheduled cell is high (wide), terminal capability information including the supportable frequency range for the combination of the scheduling cell and the scheduled cell may be transmitted. Note that, when the SCS of the scheduling cell is high and the SCS of the scheduled cell is low, terminal capability information including the supportable frequency range may also be transmitted.

[0071] Furthermore, when the SCS of the scheduling cell and the SCS of the scheduled cell are the same, the control unit 270 may transmit terminal capability information including information indicating whether or not the case where different carrier types are supported is supported. A specific example of transmitting (reporting) terminal capability information related to carrier types will be described later.

[0072] Furthermore, the gNB 100 may have a function corresponding to the above-mentioned UE 200. Specifically, the gNB 100 (control signal / reference signal processing unit 240) may be configured with a transmitter that transmits downlink control information instructing scheduling for a combination of multiple cells, and a receiver that receives terminal capability information related to scheduling from the UE 200.

[0073] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to efficient UE capability reporting even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced.

[0074] (3.1) Assumptions and Issues As described above, the wireless communication system 10 may support a function of scheduling PDSCH / PUSCH of multiple CCs using a single (one) DCI (Single DCI Multi-Cell PDSCH / PUSCH scheduling).

[0075] 5 shows an example of a scheduling method that can be supported by the wireless communication system 10. Single DCI Multi-Cell PDSCH / PUSCH scheduling (Single DCI Multi-carrier PDSCH / PUSCH scheduling) has the following features compared to a conventional method in which DCI is prepared for each CC and scheduled one by one.

[0076] ・(Advantages): The load (number of blind decodes (BD)) caused by monitoring DCI (PDCCH) can be reduced. Also, the total PDCCH overhead can be reduced (the smaller the size of the single DCI is compared to the conventional DCI x number of CCs, the more effective it is). ・(Disadvantages): The instructions cannot be changed in detail for each CC (if this were possible, the size of the single DCI would increase, and the PDCCH error rate and overhead would increase). If there is an error in the PDCCH, data reception across multiple CCs will fail.

[0077] 6 shows an example of PDSCH scheduling using single DCI multi-cell PDSCH / PUSCH scheduling. As described above, DCI that schedules PUSCH / PDSCH for multiple cells using a single DCI may be referred to as DCI format 0_3 / 1_3, respectively.

[0078] DCI formats 0_3 / 1_3 can be simultaneously scheduled for a combination of cells included in a set of cells to be scheduled (Set of cells). The following requirements may be applied to the Set of cells.

[0079] - One set of cells consists of a maximum of four cells - Any cell is included in only one set of cells Figure 6 shows an example where Set of cells 1 includes CC#1 / 2 / 3 / 4, and Set of cells 2 includes CC#5 / 6 / 7. The DCI formats of Set of cells 1 and 2 may each be included in a different PDCCH.

[0080] A cell that counts the DCI size / PDCCH candidate (BD) / number of CCEs may be called a reference cell. For each set of cells, one cell may be configured that counts the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH that schedules the cells included in each set of cells. In FIG. 6, for example, the reference cell for set of cells 1 may be CC#1, and the reference cell for set of cells 2 may be CC#5. Here, cell and CC may be interpreted interchangeably.

[0081] In this case, the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH (DCI for set of cells 1) may be counted in CC #1. Also, the DCI size / PDCCH candidate (BD) / number of CCEs of the PDCCH (DCI for set of cells 2) may be counted in CC #5.

[0082] Figure 7 shows an example of the relationship between a scheduling cell and a scheduled cell. The left side of Figure 7 shows an example in which a scheduling cell is included in a scheduled cell (here, a co-scheduled cell that is scheduled at the same time). In Figure 7, PDSCH / PUSCH are collectively referred to as PXSCH (same below). The right side of Figure 7 shows a case in which a scheduling cell is not included in a scheduled cell (co-scheduled cell).

[0083] In addition, Feature Group (FG) 49-1 / 2 (see 3GPP TS38.306) specifies UE capability reporting when the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same, but 3GPP is considering cases where the scheduling cell is included in the set of cells and cases where it is not.

[0084] Figure 8 shows an example in which the scheduling cell is not included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same. Figure 8 shows an example in which the PDCCH is transmitted by CC#0 and the three PXSCHs are transmitted by different CCs (CC#1 to 3). In the example of Figure 8, the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same (X kHz).

[0085] Figure 9 shows an example in which the scheduling cell is included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same. Figure 9 also shows an example in which the PDCCH is transmitted by CC #0 and the three PXSCHs are transmitted by different CCs (CC #1 to 3). In the example of Figure 9, the SCS of the scheduling cell and the SCS of the co-scheduled cell are the same (X kHz).

[0086] Furthermore, FG49-1b / 2b is a UE capability report in the case where the SCS of the scheduling cell and the SCS of the co-scheduled cell are different, and 3GPP is only considering the case where the scheduling cell is not included in the Set of cells.

[0087] Figure 10 shows an example in which the scheduling cell is not included in the Set of cells when the SCS of the scheduling cell and the SCS of the co-scheduled cell are different. Figure 10 shows an example in which the PDCCH is transmitted by CC#0 and the three PXSCHs are transmitted by different CCs (CC#1 to 3). In the example of Figure 10, the SCS of the scheduling cell and the SCS of the co-scheduled cell are different (CC#0 = Y kHz, CC#1 to 3 = X kHz).

[0088] For some UE capabilities related to Single DCI Multi-Cell PDSCH / PUSCH scheduling, it may be preferable to be able to report whether UE 200 supports the capabilities depending on whether the scheduling cell is included in the Set of Cells. Also, for some UE capabilities related to Single DCI Multi-Cell PDSCH / PUSCH scheduling, it may be preferable to be able to report whether UE 200 supports the capabilities depending on the carrier type of the scheduling cell / co-scheduled cell.

[0089] An example of an operation relating to efficient reporting of UE capabilities that takes into account such characteristics of UE capabilities will be described below.

[0090] (3.2) Operation Examples Here, the following two operation examples will be described.

[0091] (Operation example 1): When the SCS is the same for the scheduling cell and the scheduled cell, the maximum number of co-scheduled cells supported by the UE 200 is reported separately depending on whether the scheduling cell is included in the Set of cells.

[0092] (Operation example 2): Whether or not UE 200 supports the functions / capabilities of UE 200 related to Single DCI Multi-Cell PDSCH / PUSCH scheduling is reported for each carrier type of the scheduling cell / co-scheduled cell.

[0093] (3.2.1) Operation Example 1 In this operation example, as described above, when the SCS of a scheduling cell and a scheduled cell are the same, the UE 200 separately reports the maximum number of co-scheduled cells supported by the UE 200 depending on whether the scheduling cell is included in the Set of cells. Specifically, one of the following options may be applied.

[0094] (Opt. 1): UE 200 reports independently whether or not the scheduling cell is included in the Set of cells. The candidate values ​​to be reported may be at least one of 0, 1, 2, 3, and 4. If UE 200 reports 0 or 1, it may be interpreted that the UE does not support Single DCI Multi-Cell PDSCH / PUSCH scheduling in that case.

[0095] (Opt. 2): UE 200 reports a value corresponding to either the case where the scheduling cell is included in the Set of cells or the case where the scheduling cell is not included. Candidates for the value to be reported may be at least one of 0, 1, 2, 3, and 4. For example, it may be interpreted that the number of cells to be reported differs by one cell between the case where the scheduling cell is included in the Set of cells and the case where the scheduling cell is not included (Example 1). Specifically, the maximum number of co-scheduled cells when the scheduling cell is included in the Set of cells may be interpreted as "the maximum number of co-scheduled cells when the scheduling cell is not included in the Set of cells + 1" (Example 1-1). Alternatively, the maximum number of co-scheduled cells when the scheduling cell is not included in the Set of cells may be interpreted as "the maximum number of co-scheduled cells when the scheduling cell is included in the Set of cells - 1" (Example 1-2).

[0096] If UE 200 reports 0 or 1, in this case, it may be interpreted as not supporting Single DCI Multi-Cell PDSCH / PUSCH scheduling (similar to Opt. 1).

[0097] Furthermore, when the SCS is the same for the scheduling cell and the scheduled cell, at least one of the following UE capabilities may be reported separately depending on whether the scheduling cell is included in the Set of cells.

[0098] - Maximum Set of Cells Specifically, the following maximum Set of Cells may be reported:

[0099] - Maximum number of sets of cells per PUCCH group - Maximum total number of sets of cells for multiple PUCCH groups - Maximum number of sets of cells for each primary / secondary PUCCH group - Maximum number of sets of cells scheduled by the same scheduling cell - Method of notifying co-scheduled cells by DCI (FDRA (Frequency Domain Resource Allocation)-based and / or co-scheduled cell indicator-based indication) - Field type (Type-1A and / or Type-2) of configurable fields (Antenna port(s), Precoding information and number of layers, SRS resource indicator field) - Type (Type 1 and / or Type 2) of HARQ (hybrid automatic repeat request) codebook (CB) of PDSCH scheduled by supported DCI format 1_3 Type 1 HARQ-ACK CB is a method in which the CB is determined semi-statically, and Type 2 HARQ-ACK CB may be interpreted as a method in which the CB is determined dynamically.

[0100] Simultaneous monitoring of existing DCI format and DCI format 0_3 / 1_3 Specifically, this may be applied to the following cases:

[0101] - When the reference cell is scheduled by the existing DCI format - When cells other than the reference cell are also scheduled by the existing DCI format - Nominal RBG size configuration 3 for FDRA type 0 - RBG granularity RIV (Resource Indicator Value) for FDRA type 1 - Triggering of type 3 / enhanced type 3 HARQ codebook by DCI format 1_3 For FDRA type 0, Configuration 3 can be set for Single DCI Multi-Cell PDSCH / PUSCH scheduling. Also, for FDRA RA type 1, RIV can be set with the RBG granularity set for DCI format 0_2 / 1_2 for Single DCI Multi-Cell PDSCH / PUSCH scheduling.

[0102] The Type 3 HARQ-ACK CB may include HARQ-ACK bits for all HARQ process numbers in all CCs. The enhanced Type 3 HARQ-ACK CB may include HARQ-ACK bits for any CC or any HARQ process number.

[0103] ・Shared spectrum (unlicensed band) operation and / or ChannelAccess-Cpext-CAPC / ChannelAccess-Cpext signaling using DCI format 0_3 / 1_3 ・Priority signaling (PDSCH or PUSCH) using DCI format 0_3 / 1_3 ・SCell dormancy signaling using DCI format 0_3 / 1_3 ・PDCCH monitoring adaptation signaling using DCI format 0_3 / 1_3 ・Minimum applicable scheduling offset signaling using DCI format 0_3 / 1_3 ・Cross-slot scheduling using DCI format 0_3 / 1_3 ・HARQ retransmission triggering using DCI format 1_3 ・PHY priority handling for one-shot HARQ-ACK using DCI format 1_3 ・Unified TCI (Transmission Configuration Indication) signaling using DCI format 1_3 ・Support for up to 32 HPN (HARQ Process Number)

[0104] (3.2.2) Operation Example 2 In this operation example, as described above, the UE 200 reports whether or not it supports the functions / capabilities of the UE 200 related to Single DCI Multi-Cell PDSCH / PUSCH scheduling for each carrier type of the scheduling cell / co-scheduled cell.

[0105] The carrier type classification may be at least one of FR1 / FR2 / FR2-1 / FR2-2, TDD / FDD, and licensed band / unlicensed band, or a combination of these.

[0106] For example, UE200 may report a combination of carrier types supported for the scheduling cell / co-scheduled cell from among {FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1, FR2-2} (Example 1).

[0107] Furthermore, the UE 200 may report a combination of carrier types supported for the scheduling cell / co-scheduled cell from among {FR1 FDD, FR1 TDD, FR2-1, FR2-2} (Example 2).

[0108] Regarding the relationship between the scheduling cell and the co-scheduled cell, the UE 200 may report the supported types from among {licensed to unlicensed, unlicensed to licensed, unlicensed to unlicensed, licensed to licensed} (Example 3-1). Also, the UE 200 may report the combination of carrier types supported for the scheduling cell / co-scheduled cell from among {licensed, unlicensed} (Example 3-2). Also, the UE 200 may report the combination of Example 2 and Examples 3-1 / 3-2 (Example 4).

[0109] The UE 200 may report whether or not the scheduling cell and the co-scheduled cell support a case where the SCSs are the same but the carrier types are different. Specifically, one of the following options may be applied.

[0110] (Opt.1): UE200 reports whether it supports the case where the carrier type of the scheduling cell and the co-scheduled cell is different by using one bit of information. For example, if it does not support it, it may report "0", and if it supports it, it may report "1" (or vice versa).

[0111] (Opt.2-1): When the SCS between the scheduling cell and the co-scheduled cell is 15 kHz or 30 kHz, report whether or not the carrier type of the FR1 scheduling cell and the co-scheduled cell is different. For example, the carrier type may be any of FR1 licensed FDD, FR1 licensed TDD, and FR1 unlicensed TDD, or report whether only the same carrier type is supported.

[0112] (Opt.2-2): When the SCS between the scheduling cell and the co-scheduled cell is 120 kHz, report whether or not the case where the carrier type is different between the scheduling cell and the co-scheduled cell in FR2 is supported. For example, the carrier type may be either FR2-1 or FR2-2, or it may be reported whether only the case where they are the same is supported.

[0113] (Opt.3-1): When the SCS between the scheduling cell and the co-scheduled cell is 15 kHz or 30 kHz, report which combination of carrier types is supported between the FR1 scheduling cell and the co-scheduled cell. For example, it may report which combination of carrier types the scheduling cell / co-scheduled cell supports: FR1 licensed FDD, FR1 licensed TDD, or FR1 unlicensed TDD.

[0114] (Opt.3-2): When the SCS between the scheduling cell and the co-scheduled cell is 120 kHz, it may be reported which combinations of carrier types are supported between the FR2 scheduling cell and the co-scheduled cell.

[0115] For example, it may be possible to report which combination of FR2-1 and FR2-2 the carrier type of each scheduling cell / co-scheduled cell supports.

[0116] Furthermore, when the SCS of the scheduling cell and the co-scheduled cell are different, the UE 200 may report the supported carrier type according to the relationship between the SCS of the supported scheduling cell and the co-scheduled cell.

[0117] For example, when the supported SCS relationship is low-to-high (scheduling from a scheduling cell with a low SCS to co-scheduled cells with a high SCS), the UE 200 may report the supported types for the combination of {scheduling cell, scheduled cell} from among {FR1, FR1}, {FR1, FR2}, and {FR2, FR2}. Note that FR1 FDD / TDD, FR1 licensed / unlicensed, or FR2-1 / FR2-2 may be distinguished.

[0118] When the supported SCS relationship is high-to-low (scheduling from a scheduling cell with a low SCS to co-scheduled cells with a high SCS), the UE 200 may report the supported types for the combination of {scheduling cell, scheduled cell} from among {FR1, FR1}, {FR2, FR1}, and {FR2, FR2}. Note that, as in the case of low-to-high, FR1 FDD / TDD, FR1 licensed / unlicensed, or FR2-1 / FR2-2 may be distinguished.

[0119] Furthermore, when the supported SCS relationships are both low-to-high and high-to-low, the UE 200 may report the supported types for the combination of {scheduling cell, scheduled cell} from among {FR1, FR1}, {FR1, FR2}, {FR2, FR1}, and {FR2, FR2}. In this case, FR1 FDD / TDD, FR1 licensed / unlicensed, or FR2-1 / FR2-2 may be distinguished.

[0120] In addition, when the carrier type combination of the scheduling cell and the co-scheduled cell supported by the UE 200 is only {FR1, FR2}, the SCS relationship between the supported scheduling cell and the co-scheduled cell may be interpreted as low-to-high.

[0121] Furthermore, when the carrier type combination of the scheduling cell and the co-scheduled cell supported by the UE 200 is only {FR2, FR1}, the SCS relationship between the supported scheduling cell and the co-scheduled cell may be interpreted as high-to-low.

[0122] In addition, when the carrier type combinations of the supported scheduling cell and co-scheduled cell include {FR1, FR1}, {FR2, FR2}, UE200 may report the SCS relationship between the supported scheduling cell and co-scheduled cell from among {low-to-high, high-to-low, both low-to-high and high-to-low}.

[0123] The UE 200 may apply the above-described method to report support for at least one of the following features:

[0124] - Notification method by DCI of co-scheduled cell (FDRA-based and / or co-scheduled cell indicator-based indication) - Field type (Type-1A and / or Type-2) of configurable field (Antenna port(s), Precoding information and number of layers, SRS resource indicator field) - HARQ codebook type (Type 1 and / or Type 2) of PDSCH scheduled by supported DCI format 1_3 - Simultaneous monitoring of existing DCI format and DCI format 0_3 / 1_3 Specifically, it may be applied to the following cases.

[0125] ・When a reference cell is scheduled using an existing DCI format ・When cells other than the reference cell are also scheduled using an existing DCI format ・Nominal RBG size configuration 3 in the case of FDRA type 0 ・RBG granularity RIV in the case of FDRA type 1 ・Triggering type 3 / enhanced type 3 HARQ codebook using DCI format 1_3 ・Shared spectrum (unlicensed band) operation and / or ChannelAccess-Cpext-CAPC / ChannelAccess-Cpext notification using DCI format 0_3 / 1_3 ・Priority notification (PDSCH or PUSCH) using DCI format 0_3 / 1_3 ・SCell dormancy notification using DCI format 0_3 / 1_3 ・PDCCH monitoring adaptation notification using DCI format 0_3 / 1_3 ・Minimum applicable scheduling offset notification using DCI format 0_3 / 1_3 ・Cross-slot scheduling using DCI format 0_3 / 1_3 - Triggering HARQ retransmission using DCI format 1_3 - PHY priority handling of one shot HARQ-ACK using DCI format 1_3 - Unified TCI notification using DCI format 1_3 - Support for HPN up to 32 - Maximum number of co-scheduled cells - Maximum number of set of cells Specifically, the following maximum number of set of cells may be reported:

[0126] - Maximum number of sets of cells per PUCCH group - Maximum total number of sets of cells for multiple PUCCH groups - Maximum number of sets of cells for each primary / secondary PUCCH group - Maximum number of sets of cells scheduled by the same scheduling cell

[0127] (4) Actions and Effects According to the above-described embodiment, the following actions and effects can be obtained. Specifically, according to the above-described operation example, when the SCS of the scheduling cell and the SCS of the scheduled cell are the same, the UE 200 can transmit UE Capability Information including the number of supportable scheduled cells depending on whether the scheduling cell is included in the Set of cells. Therefore, even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced, the functions supported by the UE 200 in Single DCI Multi-Cell PDSCH / PUSCH scheduling and operations related to reporting become clear, and appropriate Single DCI Multi-Cell PDSCH / PUSCH scheduling according to the UE capabilities can be realized. In other words, according to the UE 200, efficient UE capability reporting can be realized even when Single DCI Multi-Cell PDSCH / PUSCH scheduling is introduced.

[0128] In this embodiment, the UE 200 can report the maximum number of scheduled cells that can be supported. Therefore, the network (gNB 100) can realize appropriate scheduling that takes into account the maximum number of scheduled cells of the UE 200.

[0129] In this embodiment, the UE 200 can report whether a function or capability related to scheduling is supported for each carrier type used in the scheduling cell and the scheduled cell. Specifically, when the SCS of the scheduling cell and the SCS of the scheduled cell are different, the UE 200 can report the supported carrier type according to the SCS that the scheduling cell can support and the SCS that the scheduled cell can support. Therefore, the network (gNB 100) can realize appropriate scheduling taking into account the carrier type that the UE 200 can support.

[0130] (5) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0131] For example, in the above-described embodiment, the terms "single DCI multi-slot PDSCH / PUSCH scheduling" and "single DCI multi-cell PDSCH / PUSCH scheduling" are used in the description, but these terms may be called by other names as long as they refer to a function of scheduling PDSCH / PUSCHs of multiple slots using one DCI or a function of scheduling PDSCHs / PUSCHs of multiple CCs using a single (one) DCI. Also, as described above, the channel is not limited to the PDSCH / PUSCH, and may include a control channel and / or other data channels.

[0132] In addition, in the above-described embodiment, UE capability signaling may be per UE, per FR, per TDD / FDD, per band, per BC (Band Combination), per FS (Feature Set), or per FSPC (Feature Set Per CC).

[0133] The UE 200 may report the UE capability to the scheduling CC, or may report the UE capability to the scheduled CC, or may report the UE capability to the CC that transmits the PUCCH.

[0134] In addition, in the above-described embodiments, the terms scheduled cell and co-scheduled cell(s) are used in the description, where a scheduled cell means any one cell and a co-scheduled cell(s) may be interpreted as meaning multiple cells that are scheduled simultaneously, but scheduled cell and co-scheduled cell(s) may be used interchangeably.

[0135] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0136] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0137] The block diagram ( FIG. 4 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0138] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0139] Furthermore, the above-described gNB 100 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 11, the devices may be configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0140] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0141] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0142] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0143] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0144] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0145] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0146] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0147] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0148] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0149] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0150] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0151] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0152] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0153] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0154] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0155] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0156] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0157] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

[0158] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0159] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0160] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0161] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0162] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0163] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0164] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0165] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0166] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0167] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0168] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0169] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0170] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0171] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0172] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0173] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0174] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0175] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0176] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0177] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0178] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.

[0179] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0180] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0181] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0182] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0183] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0184] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0185] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0186] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0187] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0188] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0189] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0190] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0191] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0192] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0193] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0194] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0195] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0196] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0197] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0198] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0199] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0200] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0201] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0202] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0203] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0204] 12 shows an example of the configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0205] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0206] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0207] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0208] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0209] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0210] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0211] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0212] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0213] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0214] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0215] (Additional Note) The above disclosure may be expressed as follows: A first feature is a terminal including: a transmitter that transmits terminal capability information related to scheduling for a combination of multiple cells using single downlink control information; and a controller that, when a subcarrier spacing of a first cell to which the downlink control information is transmitted is identical to a subcarrier spacing of a second cell that is simultaneously scheduled by the downlink control information, causes the terminal capability information to be transmitted including the number of second cells that can be supported, depending on whether the first cell is included in a combination of multiple cells.

[0216] In a second feature based on the first feature, the control unit causes the terminal capability information to be transmitted, the information including a maximum number of the second cells that can be supported.

[0217] A third feature is a terminal including: a transmitter that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information; and a controller that causes the terminal capability information, including whether a function or capability related to the scheduling is supported, to be transmitted for each carrier type used in a first cell to which the downlink control information is transmitted and a second cell that is simultaneously scheduled by the downlink control information.

[0218] A fourth feature is that, in the third feature, when the subcarrier spacing of the first cell and the subcarrier spacing of the second cell are different, the control unit causes the terminal capability information including the supported carrier types to be transmitted in accordance with the supportable subcarrier spacing of the first cell and the supportable subcarrier spacing of the second cell.

[0219] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a transmitter that transmits terminal capability information related to scheduling targeting a combination of multiple cells using single downlink control information; and a control unit that, when the subcarrier spacing of a first cell to which the downlink control information is transmitted is the same as the subcarrier spacing of a second cell that is simultaneously scheduled by the downlink control information, causes the transmission of the terminal capability information including the number of second cells that can be supported depending on whether the first cell is included in the combination of multiple cells.

2. The terminal according to claim 1, wherein the control unit transmits the terminal capability information including a maximum number of the second cells that can be supported.

3. A terminal comprising: a transmitter that transmits terminal capability information related to scheduling targeting a combination of multiple cells using a single downlink control information; and a control unit that causes the transmission of the terminal capability information including whether a function or capability related to the scheduling is supported for each carrier type used in a first cell to which the downlink control information is transmitted and a second cell that is simultaneously scheduled by the downlink control information.

4. The terminal according to claim 3, wherein the control unit transmits the terminal capability information including the supported carrier type in accordance with the supportable subcarrier spacing of the first cell and the supportable subcarrier spacing of the second cell when the subcarrier spacing of the first cell is different from the subcarrier spacing of the second cell.

5. A wireless communication method in a terminal, comprising: a step of transmitting terminal capability information regarding scheduling for a combination of multiple cells using single downlink control information; and a step of transmitting the terminal capability information including the number of supportable second cells depending on whether the first cell is included in the combination of multiple cells, when the subcarrier spacing of a first cell to which the downlink control information is transmitted is the same as the subcarrier spacing of a second cell simultaneously scheduled by the downlink control information.

6. A wireless communication method in a terminal, comprising: a step of transmitting terminal capability information related to scheduling targeting a combination of multiple cells using a single downlink control information; and a step of transmitting the terminal capability information including whether a function or capability related to the scheduling is supported for each carrier type used in a first cell to which the downlink control information is transmitted and a second cell that is simultaneously scheduled by the downlink control information.