Terminal and communication method

Abstract

The present invention comprises: a transmission unit that transmits, to a base station, capability information indicating whether or not to support joint scheduling for a plurality of cells in which a subcarrier spacing and / or a carrier type is different; and a reception unit that receives, from the base station, a single downlink control information (DCI) format. The reception unit receives, from the base station, a physical downlink shared channel (PDSCH) scheduled in the plurality of cells on the basis of the single DCI format.

Description

Terminal and Communication Method

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

[0002] In NR (New Radio), which is a successor system to LTE (Long Term Evolution) (also referred to as "5G"), technologies that satisfy requirements such as a large-capacity system, high data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are being studied (for example, Non-Patent Document 1).

[0003] For example, regarding downlink control information (DCI: Downlink Control Information), in 3GPP (registered trademark) Release 16 / 17, a function of scheduling PD SCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by a plurality of slots with a single DCI, single DCI multi-slot PD SCH / PUSCH scheduling (referred to as single DCI multi-slot PDSCH / PUSCH scheduling) is defined (for example, Non-Patent Document 2).

[0004] Also, in 3GPP Release 18, the introduction of a function of scheduling PD SCH / PUSCH transmitted by a plurality of component carriers (CCs) with a single DCI is being studied (for example, Non-Patent Document 3). Such a function is called single DCI multi-carrier PD SCH / PUSCH scheduling or single DCI multi-cell PD SCH / PUSCH scheduling, etc. (hereinafter, referred to as single DCI multi-carrier PD SCH / PUSCH scheduling). Note that PD SCH / PUSCH may be replaced with PD SCH and / or PUSCH.

[0005] 3GPP TS 38.300 V18.3.0 (2024-09)3GPP TS 38.212 V17.4.0 (2022-12)"New WID on Multi-carrier enhancements", RP-213577, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021"New WID on Multi-carrier enhancements for NR Phase 2", RP-242408, 3GPP TSG RAN Meeting #105, 3GPP, September 20243GPP TS 38.306 V18.3.0 (2024-09)3GPP TS 38.331 V18.3.0 (2024-09)

[0006] Support for co-scheduling to multiple cells with different subcarrier intervals and / or carrier types is being considered (see Non-Patent Document 4). If such co-scheduling is supported, it will be necessary to define UE capability signaling to indicate that such scheduling is supported.

[0007] This invention has been made in view of the above points, and aims to support flexible scheduling to multiple cells in a wireless communication system.

[0008] According to the disclosed technology, a terminal is provided having a transmitting unit that transmits capability information to a base station indicating whether or not it supports joint scheduling to multiple cells with at least one different subcarrier spacing and carrier type, and a receiving unit that receives a single DCI (Downlink Control Information) format from the base station, the receiving unit receiving PDSCH (Physical Downlink Shared Channel) scheduled in the multiple cells based on the single DCI format from the base station.

[0009] According to the disclosed technology, flexible scheduling to multiple cells can be supported in wireless communication systems.

[0010] This figure shows an example of the configuration of a wireless communication system. This figure shows an example of a frequency band according to an embodiment of the present invention. This figure shows an example of a wireless frame according to an embodiment of the present invention. This figure shows an example of scheduling (1) according to an embodiment of the present invention. This figure shows an example of scheduling (2) according to an embodiment of the present invention. This figure shows an example of PDCCH monitoring according to an embodiment of the present invention. This figure shows an example of scheduling (3) according to an embodiment of the present invention. This figure shows an example of scheduling (4) according to an embodiment of the present invention. This is a flowchart for explaining an example of joint scheduling to multiple cells having different SCS and carrier types according to an embodiment of the present invention. This figure shows an example of the functional configuration of a base station 10 according to an embodiment of the present invention. This figure shows an example of the functional configuration of a terminal 20 according to an embodiment of the present invention. This figure shows an example of the hardware configuration of a base station 10 or terminal 20 according to an embodiment of the present invention. This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0012] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

[0014] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).

[0015] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured.

[0016] Figure 1 shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[0017] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, in NR-PBCH and is also called broadcast information. Synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via Carrier Aggregation (CA) through secondary cells (SCell) and primary cells (PCell). Additionally, the terminal 20 may communicate via Dual Connectivity (DC) through the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10.

[0018] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0019] Terminal 20 is capable of performing carrier aggregation, which involves bundling multiple cells (multiple CCs (Component Carriers)) together to communicate with base station 10. Carrier aggregation uses one PCell (Primary cell) and one or more SCells (Secondary cells). A PUCCH-SCell with a PUCCH may also be used.

[0020] Figure 2 shows an example of a frequency band according to an embodiment of the present invention. As shown in Figure 2, the following frequency bands are defined.

[0021] ・FR1: 410 MHz - 7.125 GHz ・FR2: ・FR2-1: 24.25 GHz - 52.6 GHz ・FR2-2: Over 52.6 GHz -71 GHz

[0022] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5–100 MHz may be used. FR2 is a higher frequency than FR1, and an SCS of 60 or 120 kHz (240 kHz may be included) may be used, and a bandwidth (BW) of 50–400 MHz may be used.

[0023] Furthermore, the wireless communication system may also support higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system may support frequency bands exceeding 52.6 GHz and 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 subcarrier spacing may be applied. Furthermore, DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0025] Figure 3 shows an example of a wireless frame according to an embodiment of the present invention. 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 symbols; for example, it may be 28 symbols or 56 symbols. Also, the number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz. For example, as shown in Figure 3, it may be 480 kHz or 960 kHz, or even wider.

[0026] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time, etc. The frequency direction may also be called the frequency domain, resource block, subcarrier, BWP (Bandwidth part), etc.

[0027] The enhancement of PDSCH and / or PUSCH scheduling in multi-carrier environments using a single DCI is being investigated. For example, the maximum number of cells that can be scheduled simultaneously, scheduling in intraband and interband CA, scheduling in FR1 and FR2, and optimization of a single DCI for scheduling three or more multi-cell PDSCH and / or PUSCH are being considered.

[0028] Figure 4 shows an example of scheduling (1) according to an embodiment of the present invention. As shown in Figure 4(A), in conventional self-carrier scheduling, PDCCH and DCI are transmitted for each CC, and PDSCH / PUSCH are scheduled to the CC.

[0029] As shown in Figure 4(B), in conventional cross-carrier scheduling, PDCCH and DCI in other CCs schedule PDSCH / PUSCH to each CC.

[0030] As shown in Figure 4(C), in multi-carrier scheduling, a single DCI schedules PDSCH / PUSCH to each CC.

[0031] When scheduling PDSCH / PUSCH for multiple CCs using a single DCI, compared to preparing a separate DCI for each CC and scheduling each CC individually, the advantage is that the monitoring load (e.g., number of blind decodes) from the DCI (PDCCH) can be reduced. Furthermore, the smaller the size of the single DCI is compared to the size of the conventional DCI multiplied by the number of CCs, the greater the reduction in total PDCCH overhead.

[0032] On the other hand, a drawback is that the instructions cannot be flexibly changed for each CC. If the instructions were to be flexibly changed, the size of the single DCI would increase, leading to a worsening of the PDCCH error rate and an increase in overhead. Also, if the PDCCH is decoded incorrectly, data reception from all multiple CCs will fail.

[0033] Figure 5 shows an example of scheduling (2) according to an embodiment of the present invention. As shown in Figure 5(B), Releases 16 and 17 define a function for scheduling multiple slot PDSCH and / or PUSCH on a single DCI. This function may also be called single DCI multi-slot PDSCH / PUSCH scheduling.

[0034] Comparing the method of arranging DCIs in each slot and scheduling them individually, as shown in Figure 5(A), with single DCI multi-slot PDSCH / PUSCH scheduling, it is possible to reduce the load (e.g., number of blind decodes) due to DCI or PDCCH monitoring. Furthermore, the total PDCCH overhead can be reduced. The effect becomes greater as the size of the single DCI becomes smaller than the conventional DCI × CC number.

[0035] On the other hand, with single DCI multi-slot PDSCH / PUSCH scheduling, it is not possible to change the detailed instructions for each slot. If detailed instruction changes are made possible, the size of the single DCI increases, and the PDCCH error rate and overhead increase. Also, if PDCCH reception fails, data reception for all slots will fail.

[0036] Release 18 Single DCI multi-carrier PDSCH and / or PUCCH scheduling cannot be used in combination with multi-slot PDSCH and / or PUCCH scheduling. Cells included in the same PUCCH cell group cannot be used in combination with multi-carrier PDSCH and / or PUCCH scheduling and multi-slot PDSCH and / or PUCCH scheduling.

[0037] Figure 6 shows an example of PDCCH monitoring according to an embodiment of the present invention. As shown in Figure 6, in FR2, the slot length is shorter compared to FR1, so it is expected that the terminal load and power consumption will increase due to frequent PDCCH monitoring in PDSCH and / or PUSCH scheduling for each slot.

[0038] In order to utilize multi-carrier PDSCH and / or PUSCH scheduling in FR2, it is desirable to be able to combine and utilize multi-slot PDSCH and / or PUSCH scheduling.

[0039] Figure 7 shows an example of scheduling (3) according to an embodiment of the present invention. As shown in Figure 7, scheduling to multiple slots of the same CC and scheduling to multiple CCs of the same slot may be performed in different DCIs.

[0040] Figure 8 shows an example of scheduling (4) according to an embodiment of the present invention. As shown in Figure 8, scheduling to multiple slots of multiple CCs may be performed with a single DCI. Scheduling to multiple CCs may refer to a case where one TB and / or one PDSCH is mapped to multiple CCs, or where HARQ feedback is managed across multiple CCs.

[0041] It is being considered to extend the multi-cell scheduling supported by conventional MCE (Multi-carrier enhancements). For example, multiple cells that could be scheduled with a single DCI (DCI format 0_3 / 1_3) were all limited to the same SCS and carrier type. In the future, this restriction may be removed, allowing co-scheduling of cells with different SCS and carrier types. Also, when scheduling multiple cells with a single DCI (DCI format 0_3 / 1_3), the number of PDSCHs or PUSCHs per cell was limited to one, but it may be possible to schedule multiple PDSCHs or PUSCHs per cell.

[0042] Multi-cell scheduling using a single DCI may be performed as follows (see Non-Patent Document 1).

[0043] - PDSCH, which is scheduled together by PDCCH, uses the same numeric logic. - PUSCH, which is scheduled together by PDCCH, uses the same numeric logic.

[0044] The capabilities related to multi-cell scheduling, multiCell-PDSCH-DCI-1-3-SameSCS-r18, and multiCell-PUSCH-DCI-0-3-SameSCS-r18 are defined as follows (see Non-Patent Document 5).

[0045] - coScheduledCellSCS-r18 included in multiCell-PDSCH-DCI-1-3-SameSCS-r18 or multiCell-PUSCH-DCI-0-3-SameSCS-r18 indicates the same SCS and carrier type of the scheduling cell and the cells scheduled together. - When multiple values are reported for coScheduledCellSCS-r18 included in multiCell-PDSCH-DCI-1-3-SameSCS-r18 or multiCell-PUSCH-DCI-0-3-SameSCS-r18 and the cell to be scheduled is not included in the set of cells to be scheduled, the UE supports multi-cell PDSCH scheduling by DCI format 1_3 from one carrier type notified by coScheduledCellSCS-r18 to another carrier type notified by coScheduledCellSCS-r18, or multi-cell PUSCH scheduling by DCI format 0_3 for the following scheduling cases. For example, scheduling may be performed from an FR1 licensed band TDD to an FR1 unlicensed band TDD. For example, scheduling may be performed from FR2-1 to FR2-2. The UE may further report licensed-fdd-tdd-FR1 indicating support for scheduling from an FR1 licensed band TDD to an FR1 licensed band FDD or from an FR1 licensed band FDD to an FR1 licensed band TDD.

[0046] The capabilities related to multi-cell scheduling, multiCell-PDSCH-DCI-1-3-DiffSCS-r18, and multiCell-PDSCH-DCI-0-3-DiffSCS-r18 are defined as follows (see Non-Patent Document 5). coScheduledCellSCS-r18 included in multiCell-PDSCH-DCI-1-3-DiffSCS-r18 or multiCell-PDSCH-DCI-0-3-DiffSCS-r18 indicates that the cell to be scheduled and the cells to be co-scheduled have different SCSs, and the set of cells to be co-scheduled share the same SCS and carrier type. combinationCarrierType-r18 notifies the combination of the same or different carrier types (FR1 licensed band FDD or FR1 licensed band TDD or FR1 unlicensed band TDD or FR2-1 or FR2-2) of the cell to be scheduled and the cells to be co-scheduled.

[0047] As described above, two capabilities (multiCell-PDSCH-DCI-1-3-SameSCS-r18, multiCell-PDSCH-DCI-1-3-DiffSCS-r18) were defined for multi-cell PDSCH scheduling in DCI format 1_3 (the same applies to 0_3).

[0048] multiCell-PDSCH-DCI-1-3-SameSCS-r18 corresponds to the case where the co-scheduled cells including the cell to be scheduled have the same SCS and carrier type, and the case where the co-scheduled cells do not include the cell to be scheduled and they have the same SCS and a specific combination of carrier types (the same applies to 0_3).

[0049] multiCell-PDSCH-DCI-1-3-DiffSCS-r18 corresponds to the case where the co-scheduled cells do not include the cell to be scheduled and the cell to be scheduled and the co-scheduled cells have different SCSs (the same applies to 0_3).

[0050] The UE capability multiCell-PDSCH-DCI-1-3-SameSCS-r18 (see Non-Patent Document 5) may be defined as follows:

[0051] It supports monitoring DCI format 1_3 for DL ​​scheduling, which has the same SCS between the cell being scheduled by the UE and the cells being scheduled within the set, and indicates whether it supports type 2 for the "antenna port" field.

[0052] For multi-cell PDSCH scheduling using DCI format 1_3, the number of DCI unicast DLs to process per slot of the cells to be scheduled for a set of cells is as follows: one DCI format 1_3 for the set of cells, and one unicast DL for each cell not scheduled by DCI format 1_3, DCI format 1_0 / 1_1 / 1_2 (if supported).

[0053] If the set of cells to be scheduled includes PCell, the scheduling cell is PCell; if the set of cells to be scheduled includes only SCell, the scheduling cell is either PCell or SCell.

[0054] The UE monitors the search space set for DCI format 1_3 for the set of cells scheduled for the following cases:

[0055] - A search space set setting for DCI format 1_3 for a set of cells to be scheduled, provided only on the scheduling cell - or a search space set setting for DCI format 1_3 for a set of cells having the same searchSpaceId, is provided on both the scheduling cell and the serving cell in the set of scheduled cells if the set of cells has scheduling cells that are not in the set of cells.

[0056] - UEs that support multiCell-PDSCH-DCI-1-3-SameSCS-r18 can use supportOfSearchSpace-r18 to report whether they support the case where the scheduling cell is within a set of scheduled cells, and both the scheduling cell and the serving cells within the set of scheduled cells are provided with the same searchSpaceId searchspace set setting.

[0057] The capability signaling includes the following parameters: - coScheduledCellSCS-r18 indicates the same SCS and carrier type possessed by the scheduling cell and the cells it co-scheduled. - maxNumberCoScheduledCell-r18 indicates the maximum number of co-scheduled cells per set of scheduled cells supported by the UE. - maxNumberSetsOfCellAcrossPUCCH-Group-r18 indicates the maximum number of sets of cells supported by the UE across PUCCH groups. - maxNumberSetsOfCellScheduling-r18 indicates the maximum number of sets of cells supported by the UE for the same scheduling cell. - harqFeedbackType-r18 indicates the supported HARQ feedback type. The UE shall report the same value for all BCs (Band Combinations) that support multiCell-PDSCH-DCI-1-3-SameSCS-r18. In other words, the UE shall report the same value for all supported BCs for which multiCell-PDSCH-DCI-1-3-SameSCS-r18 has been reported. - coScheduledCellIndicationScheme-r18 indicates the supported co-scheduled cell notification scheme.

[0058] If multiple values ​​are reported in coScheduledCellSCS-r18 and the cell to be scheduled is not included in the set of cells to be scheduled, the UE supports multi-cell PDSCH scheduling in DCI format 1_3 from one carrier type indicated in coScheduledCellSCS-r18 to another carrier type indicated in coScheduledCellSCS-r18 for the following scheduling cases: - Scheduling from FR1 licensed bandwidth TDD to FR1 unlicensed bandwidth TDD - Scheduling from FR2-1 to FR2-2 - The UE may additionally report licensed-fdd-tdd-FR1 to indicate support for scheduling from FR1 licensed bandwidth TDD to FR1 licensed bandwidth FDD or from FR1 licensed bandwidth FDD to FR1 licensed bandwidth TDD.

[0059] Furthermore, support for CCS (Cross Carrier Scheduling) using DL DCI format 1_1 / 1_2 follows the crossCarrierScheduling-SameSCS standard.

[0060] The UE capability multiCell-PDSCH-DCI-1-3-DiffSCS-r18 (see Non-Patent Document 5) may be defined as follows:

[0061] The UE capability supports monitoring DCI format 1_3 for DL ​​scheduling where the terminal does not include cells to be scheduled in a set of cells within the same PUCCH group, and indicates whether or not it supports type 2 for the "antenna port" field.

[0062] For a set of cells configured for multi-cell PDSCH scheduling using DCI format 1_3, the number of unicast DL DCIs to be processed for each of the N consecutive slots of the cells to be scheduled may be defined as follows:

[0063] - One DCI format 1_3 for a set of cells - One unicast DL DCI format 1_0 / 1_1 / 1_2 (if supported) for each cell not scheduled by DCI 1_3 - For scheduling from low SCS to high SCS, N=1. - For scheduling from high SCS to low SCS, N may be based on pairs of (SCS of the CC scheduling, SCS of the CC being scheduled). For example, N=2 for (30,15), (60,30), (120,60), N=4 for (60,15), (120,30), and N=8 for (120,15).

[0064] The UE monitors the search space set for DCI format 1_3 for a set of cells when a search space set setting for DCI format 1_3 for a set of cells having the same searchSpaceId is provided on both the scheduling cell and the serving cell in the set of cells. The cell to be scheduled is either a PCell or an SCell, and the set of cells to be scheduled contains only SCells.

[0065] Capability signaling includes the following parameters: - coScheduledCellSCS-r18 indicates that the scheduling cell and the co-scheduled cell have different SCSs, and the set of co-scheduled cells share the same SCS and carrier type. - combinationCarrierType-r18 indicates the combination of the same or different carrier types (FR1 licensed bandwidth FDD or FR1 licensed bandwidth TDD or FR1 unlicensed bandwidth TDD or FR2-1 or FR2-2) of the scheduling cell and the co-scheduled cell. - maxNumberCoScheduledCell-r18 indicates the maximum number of co-scheduled cells per set of cells supported by the UE. - maxNumberSetsOfCellAcrossPUCCH-Group-r18 indicates the maximum number of sets of cells supported by the UE across a PUCCH group. - maxNumberSetsOfCellScheduling-r18 indicates the maximum number of sets of cells supported by the UE for the same scheduling cell. -harqFeedbackType-r18 indicates the supported HARQ feedback type. The UE shall report the same value for all BCs that support multiCell-PDSCH-DCI-1-3-DiffSCS-r 18. That is, the UE shall report the same value for all supported BCs that report multiCell-PDSCH-DCI-1-3-DiffSCS-r 18. -coScheduledCellIndicationScheme-r18 indicates the supported co-scheduled cell indication scheme.

[0066] Support for DL ​​CCS using DCI format 1_1 / 1_2 will follow crossCarrierSchedulingDL-DiffSCS-r16.

[0067] Furthermore, the UE capability multiCell-PDSCH-DCI-1-3-DiffSCS-r18 may have the following configuration (see Non-Patent Document 6).

[0068] multiCell-PDSCH-DCI-1-3-SameSCS-r18 SEQUENCE { coScheduledCellSCS-r18 SEQUENCE { nonSharedSpectrum-fdd-fr1 ENUMERATED {supported} OPTIONAL, nonSharedSpectrum-tdd-fr1 ENUMERATED {supported} OPTIONAL, sharedSpectrum-tdd-fr1 ENUMERATED {supported} OPTIONAL, fr2-1 ENUMERATED {supported} OPTIONAL, fr2-2 ENUMERATED {supported} OPTIONAL }, maxNumberCoScheduledCell-r18 INTEGER (2..4), maxNumberSetsOfCellAcrossPUCCH-Group-r18 INTEGER (1..8), maxNumberSetsOfCellScheduling-r18 INTEGER (1..4), harqFeedbackType-r18 ENUMERATED {type1, type2, type1And2}, coScheduledCellIndicationScheme-r18 ENUMERATED {fdra,cellInd, both}, supportOfSearchSpace-r18 ENUMERATED {supported} OPTIONAL, licensed-fdd-tdd-fr1-r18 ENUMERATED {supported} OPTIONAL} OPTIONAL,.

[0069] Furthermore, the UE capability multiCell-PDSCH-DCI-1-3-DiffSCS-r18 may have the following configuration (see Non-Patent Document 6).

[0070] multiCell-PDSCH-DCI-1-3-DiffSCS-r18 SEQUENCE { coScheduledCellSCS-r18 ENUMERATED {lowScheduling-highScheduled, highScheduling-lowScheduled, both}, combinationCarrierType-r18 SEQUENCE (SIZE(1..maxSchedulingBandCombination-r18)) OF CombinationCarrierType-r18, maxNumberCoScheduledCell-r18 INTEGER (2..4), maxNumberSetsOfCellAcrossPUCCH-Group-r18 INTEGER (1..8), maxNumberSetsOfCellScheduling-r18 INTEGER (1..4), harqFeedbackType-r18 ENUMERATED {type1, type2, type1And2}, coScheduledCellIndicationScheme-r18 ENUMERATED {fdra,cellInd, both} } OPTIONAL,

[0071] Figure 9 is a flowchart illustrating an example of co-scheduling to multiple cells having different SCS and carrier types according to an embodiment of the present invention. In step S101, the UE reports its capability to the network, indicating whether or not it supports co-scheduling to multiple cells having different SCS and / or carrier types. The co-scheduling may be performed by a single DCI. In step S102, the UE receives a single DCI that includes co-scheduling to multiple cells having different SCS and / or carrier types. In step S103, based on the DCI, the UE receives a PDSCH or transmits a PUSCH in the multiple cells.

[0072] If co-scheduling to multiple cells with different SCSs and carrier types is supported, then a provision for UE capability signaling is necessary to ensure that terminals properly report this capability to the base station.

[0073] If capabilities are defined in too many small parts, signaling overhead increases, so it is preferable to keep the signaling overhead of capabilities at an appropriate level. On the other hand, if capabilities are grouped together without being divided, the terminal will not be able to report that it possesses a capability unless it supports all the functions included in that grouped capability, making it difficult to use the corresponding functions.

[0074] UE capability signaling may be defined to report support for co-scheduling to multiple cells having different SCS and carrier types. UE capability may also be defined to report support for multi-cell scheduling to co-scheduled cells with different SCS and carrier types in DCI format 0_3 or 1_3.

[0075] Within this UE capability, it may be possible to report which specific SCSs and carrier types are included in the co-scheduled cells that support scheduling to co-scheduled cells, or the network may be interpreted as supporting all possible combinations defined in the specification if it reports supporting this capability without specifying the IE for such specific reporting.

[0076] In either case, whether or not such specific reporting is required, the specifications may limit the possible combinations of SCS and carrier types.

[0077] For example, combinations of three or more (or four or more) different SCS and / or carrier types do not need to be specified.

[0078] For example, specific combinations of SCS and / or carrier types do not need to be specified (e.g., combinations of the FR1 / 2-2 unlicensed band and other bands, or combinations of 15 kHz SCS and SCS of 120 kHz or higher).

[0079] In reporting which specific SCSs and carrier types are supported for scheduling to co-scheduled cells, the report may indicate support for each possible combination pattern, or it may indicate support for each SCS and carrier type, allowing any combination among the SCSs and carrier types that are reported as supported.

[0080] The maximum number of different SCS and / or carrier type combinations that can be supported (the upper limit on the number of combinations between co-scheduled cells scheduled from a single DCI) may be reported within this UE capability, and if the UE capability is reported to be supported without specifying an IE for reporting the number of such combinations, the network may interpret this as supporting up to the maximum number defined in the specification.

[0081] As described above, in reporting which specific SCSs and carrier types are supported for scheduling to jointly scheduled cells, it may be possible to determine the number of combinations by reporting whether each supported combination pattern is supported.

[0082] Support status may be reported separately for SCS and carrier type, or only for carrier type, or for each possible combination of SCS and carrier type (for example, since 15 / 30kHz SCS is not possible with FR2, reporting for combinations including 15 / 30kHz SCS with FR2 is not required).

[0083] It may be a prerequisite to support at least one of the existing UE capabilities related to multi-cell scheduling in DCI format 0_3 or 1_3 (multiCell-PDSCH-DCI-1-3-SameSCS-r18, multiCell-PUSCH-DCI-0-3-SameSCS-r18, multiCell-PDSCH-DCI-1-3-DiffSCS-r18, multiCell-PDSCH-DCI-0-3-DiffSCS-r18), or a UE supporting this feature may also indicate support of xxx, or a UE capability may be defined independently of existing UE capabilities (for example, it may be possible to define a new UE capability that only supports UE capabilities corresponding to the new function).

[0084] Option 1) If existing UE capabilities are assumed, the following actions may be performed. Note that the new UE capability may be a UE capability that reports supporting co-scheduling to multiple cells having different SCS and carrier types.

[0085] Regarding SCS and / or carrier type (combinations) reported under existing UE capabilities, they may be interpreted as being supportable as SCS and / or carrier type combinations between jointly scheduled cells, or they may be reported as being supportable as SCS and / or carrier type combinations between jointly scheduled cells separately under new UE capabilities. If they are reported as being supportable as SCS and / or carrier type combinations between jointly scheduled cells separately under new UE capabilities, it may be required that the SCS and / or carrier type combinations reported as being supportable under new UE capabilities must also be reported as being supportable under existing UE capabilities (for the same BC).

[0086] If we support the existing ability to support cases where the scheduling cell and the scheduled cell have the same SCS (SameSCS (multiCell-PDSCH-DCI-1-3-SameSCS-r18, multiCell-PUSCH-DCI-0-3-SameSCS-r18)) and the new UE ability, we interpret this as supporting cases where the scheduling cell is included in the set of scheduled cells and different SCSs and carrier types are included between the co-scheduled cells. In order to support cases where the scheduling cell is not included in the set of scheduled cells, we will use the existing DiffSCS (multiCell-PDSCH-DCI-1-3-DiffSCS-r18), It may be stated that multiCell-PDSCH-DCI-0-3-DiffSCS-r18 must also be supported, or it may be interpreted that even if the scheduling cell is not included in the set of scheduled cells, if the scheduling cell and the scheduled cells are all the same SCS (co-scheduled cells of different carrier types), then it will be supported by the existing SameSCS (multiCell-PDSCH-DCI-1-3-SameSCS-r18, multiCell-PUSCH-DCI-0-3-SameSCS-r18) and the new UE capabilities.

[0087] Option 2) If existing UE capabilities are not assumed, UE capabilities may be defined separately using DCI format 1_3 / 0_3 and SameSCS / DiffSCS, as in the existing format, or they may be defined without separating SameSCS / DiffSCS, or they may be defined in other ways (for example, whether the scheduling cell is included in the jointly scheduled cell).

[0088] The new UE capability will be able to report the same information as the existing UE capability, but if both the existing and new UE capabilities are supported, the same value may always be reported between them (for the same BC), or different values ​​may be allowed to be reported.

[0089] Joint scheduling to multiple cells with different SCS and / or carrier types in DCI format 0_3 and joint scheduling to multiple cells with different SCS and / or carrier types in DCI format 1_3 may be reported as separate capabilities, or as a combined capability.

[0090] Joint scheduling to multiple cells with the same SCS but different carrier types, joint scheduling to multiple cells with different SCSs and / or carrier types, and joint scheduling to multiple cells with different SCSs but the same carrier type may be reported as separate capabilities, or as a combined capability.

[0091] Co-scheduling to multiple cells with different SCS and / or carrier types when the scheduling cell is included in the co-scheduled cells, and co-scheduling to multiple cells with different SCS and / or carrier types when the scheduling cell is not included in the co-scheduled cells, may be reported as separate capabilities, or as a combined capability.

[0092] Furthermore, the aforementioned new UE capabilities may be defined as capabilities for each band combination.

[0093] In the embodiments of the present invention, time-domain resources may be symbols, slots, subframes, frames, or other units of time as defined in the specification. Also, in the embodiments of the present invention, frequency-domain resources may be bands, CCs, BWPs, RBs, subcarriers, or other units of frequency as defined in the specification.

[0094] In the embodiments of the present invention, the spatial domain resource may be a spatial domain filter, a QCL (Quasi co-location) referring to an RS, a beam, a TCI (Transmission Configuration Indicator) state, a port, a panel, a TRP (Transmission and Reception Point), or a spatial domain resource defined by other terms.

[0095] In the embodiments of the present invention, the code domain resource may be an orthogonal code, OCC (orthogonal cover code), CS (cyclonic shift), quasi-orthogonal code, gold sequence, M sequence, Zadoff-chu sequence, or a code domain resource defined by other terms.

[0096] Embodiments of the present invention may apply only when the corresponding capabilities are supported by a UE, IAB, or ambient IoT device and / or enabled by the corresponding higher-layer parameters.

[0097] In the embodiments described above, the UE can report to the network its capabilities when a single DCI schedules PDSCH or PUSCH to multiple cells having different SCS and / or carrier types.

[0098] In other words, it can support flexible scheduling to multiple cells in a wireless communication system.

[0099] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0100] <Base Station 10> Figure 10 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 10, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 10 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

[0101] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits inter-network node messages to other network nodes. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, higher layer information. The transmitting unit 110 also has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.

[0102] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to multi-carrier scheduling and multi-slot scheduling.

[0103] The control unit 140 performs control to realize the functions described in the embodiment. Furthermore, the control unit 140 performs control related to multi-carrier scheduling and multi-slot scheduling, as described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0104] <Terminal 20> Figure 11 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 11, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 11 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

[0105] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. For example, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to other terminals 20 as D2D communication, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH or PSBCH, etc. from other terminals 20.

[0106] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-configured setting information. The content of the setting information includes, for example, information related to multi-carrier scheduling and multi-slot scheduling.

[0107] The control unit 240 performs control to realize the functions described in the embodiment. Furthermore, the control unit 240 performs control related to multi-carrier scheduling and multi-slot scheduling, as described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0108] (Hardware Configuration) The block diagrams (Figures 10 and 11) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0109] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0110] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 12 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0111] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0112] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0113] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0114] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 10 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 11 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0115] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0116] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0117] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0118] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0120] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0121] Figure 13 shows an example of the configuration of vehicle 2001. As shown in Figure 13, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, 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. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0122] The drive unit 2002 consists 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, which is operated by the user.

[0123] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0124] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0125] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

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

[0127] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0128] 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 external devices. For example, it can send and receive various types of information with external devices 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 or a mobile station.

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

[0130] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers 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 the external device 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, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0131] (Summary of Embodiments) As described above, according to embodiments of the present invention, a terminal is provided which includes a transmitting unit that transmits capability information to a base station indicating whether or not it supports joint scheduling to multiple cells with at least one different subcarrier interval and carrier type, and a receiving unit that receives a single DCI (Downlink Control Information) format from the base station, the receiving unit receiving PDSCH (Physical Downlink Shared Channel) scheduled in the multiple cells from the base station based on the single DCI format.

[0132] With the above configuration, the UE can report to the network its capabilities when a single DCI schedules PDSCH or PUSCH to multiple cells having different SCS and / or carrier types. In other words, it can support flexible scheduling to multiple cells in a wireless communication system.

[0133] The transmitting unit may transmit capability information to the base station indicating whether it supports co-scheduling to the multiple cells, including any subcarrier interval and any carrier type, in a specific DCI format. This configuration allows the UE to report to the network its capability when a PDSCH or PUSCH is scheduled to multiple cells having different SCSs and / or carrier types using a single DCI.

[0134] The transmitting unit may transmit capability information to the base station, including the maximum number of combinations of different subcarrier intervals and carrier types in a single DCI format that supports joint scheduling to the multiple cells. This configuration allows the UE to report to the network its capabilities when a PDSCH or PUSCH is scheduled to multiple cells having different SCSs and / or carrier types using a single DCI.

[0135] The transmitting unit may have the ability to support co-scheduling to multiple cells having the same subcarrier interval and carrier type as a prerequisite for supporting co-scheduling to multiple cells having at least one different subcarrier interval and carrier type. With this configuration, the UE can report to the network its capabilities when a PDSCH or PUSCH is scheduled to multiple cells having different SCSs and / or carrier types by a single DCI.

[0136] The transmitting unit may transmit capability information to the base station indicating whether it supports co-scheduling to multiple cells with different subcarrier intervals and carrier types for each DCI format. This configuration allows the UE to report to the network its capability when a PDSCH or PUSCH is scheduled to multiple cells with different SCSs and / or carrier types using a single DCI.

[0137] Furthermore, according to embodiments of the present invention, a communication method is provided in which a terminal performs the following steps: transmit capability information to a base station indicating whether or not it supports joint scheduling to multiple cells with at least one different subcarrier spacing and carrier type; receive a single DCI (Downlink Control Information) format from the base station; and receive a PDSCH (Physical Downlink Shared Channel) scheduled in the multiple cells from the base station based on the single DCI format.

[0138] With the above configuration, the UE can report to the network its capabilities when a single DCI schedules PDSCH or PUSCH to multiple cells having different SCS and / or carrier types. In other words, it can support flexible scheduling to multiple cells in a wireless communication system.

[0139] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0140] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0141] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0142] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0143] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0144] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0145] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0146] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0147] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0148] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0150] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0151] The terms “system” and “network” as used in this disclosure are interchangeable.

[0152] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0153] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0154] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "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.

[0155] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0156] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0157] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0158] 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 several other appropriate terms.

[0159] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may 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 IoT (Internet of Things) device such as a sensor.

[0160] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0161] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

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

[0163] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0165] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0166] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0168] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0169] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist 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.

[0170] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

[0173] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0174] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), 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.

[0175] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0176] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0177] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0178] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0179] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0181] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0182] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0183] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0184] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0185] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0186] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0187] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0188] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0189] In this 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 "combine" may be interpreted similarly to "different."

[0190] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0191] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0192] This international patent application claims priority based on Japanese Patent Application No. 2024-174656, filed on 3 October 2024, and the entire contents of Japanese Patent Application No. 2024-174656 are incorporated herein by reference.

[0193] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 30 Core network 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

A transmitting unit that transmits capability information to a base station indicating whether or not it supports co-scheduling to multiple cells with at least one different subcarrier spacing and carrier type, It has a receiving unit that receives a single DCI (Downlink Control Information) format from the base station, The receiving unit is a terminal that receives PDSCH (Physical Downlink Shared Channel) scheduled in the multiple cells based on the single DCI format from the base station. 　 The terminal according to claim 1, wherein the transmitting unit transmits capability information to the base station indicating whether or not it supports joint scheduling to the multiple cells, including any subcarrier interval and any carrier type in a specific DCI format. 　 The terminal according to claim 1, wherein the transmitting unit transmits capability information to the base station, including the maximum number of combinations of different subcarrier intervals and carrier types in a single DCI format, which supports joint scheduling to the multiple cells. 　 The terminal according to claim 1, wherein the transmitting unit has the capability to support joint scheduling to multiple cells having the same subcarrier interval and carrier type, which is a prerequisite for supporting joint scheduling to multiple cells having at least one different subcarrier interval and carrier type. 　 The terminal according to claim 1, wherein the transmitting unit transmits capability information to the base station indicating whether or not it supports co-scheduling to multiple cells with at least one different subcarrier interval and carrier type for each DCI format. A procedure for transmitting capability information to a base station indicating whether or not it supports co-scheduling to multiple cells with at least one different subcarrier spacing and carrier type, A procedure for receiving a single DCI (Downlink Control Information) format from the base station, A communication method in which a terminal performs the procedure of receiving a PDSCH (Physical Downlink Shared Channel) scheduled in the multiple cells based on the single DCI format from the base station.

Images